[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErSpo6W0zy+HkRWW9bE=Ma--9vwgjrOWin8d5QNvUJWQtwM0w@mail.gmail.com>
Date: Thu, 20 Sep 2012 13:02:15 -0600
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: Thanasis <thanasis@...r.hopto.org>
Cc: LKML <linux-kernel@...r.kernel.org>, nic_swsd@...ltek.com,
Francois Romieu <romieu@...zoreil.com>
Subject: Re: RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
On Thu, Sep 20, 2012 at 12:10 PM, Thanasis <thanasis@...r.hopto.org> wrote:
> on 09/20/2012 08:47 PM Bjorn Helgaas wrote the following:
>> On Thu, Sep 20, 2012 at 11:28 AM, Thanasis <thanasis@...r.hopto.org> wrote:
>>> I have an Acer Aspire One notebook, and it has a NIC as shown below:
>>>
>>> # lspci |grep -i Realtek
>>> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>>> RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
>>>
>>> The driver module that I use is r8169. It works with 2.6 series of
>>> kernels, but it does *not* with the recent 3.x of kernels.
>>> Question: Should I stick with 2.6 kernels, or are there any directions
>>> on how to make the NIC work with recent 3.x kernels?
>>
>> Can you collect the complete dmesg logs from both 2.6.38 and the 3.x
>> kernel? This should just work, so maybe something got broken.
>
> Attached are the dmesg outputs from 2.6.38 and 3.5.4 kernels (file
> dmesg.tar.bz2)
Thanks. I don't see anything wrong from the PCI core point of view.
But searching for "r8169 transmit queue timed out" found lots of
similar reports.
+cc 8169 driver folks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists