[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EA929A9653AAE14F841771FB1DE5A1366008789CE3@rrsmsx501.amr.corp.intel.com>
Date: Fri, 10 Sep 2010 11:21:55 -0600
From: "Tantilov, Emil S" <emil.s.tantilov@...el.com>
To: Priit Laes <plaes@...es.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"e1000-devel@...ts.sourceforge.net"
<e1000-devel@...ts.sourceforge.net>
Subject: RE: REGRESSION: e1000e fails to communicate (82566DM)
>-----Original Message-----
>From: Priit Laes [mailto:plaes@...es.org]
>Sent: Friday, September 10, 2010 2:58 AM
>To: Tantilov, Emil S
>Cc: netdev@...r.kernel.org; e1000-devel@...ts.sourceforge.net
>Subject: RE: REGRESSION: e1000e fails to communicate (82566DM)
>
>Ühel kenal päeval, N, 2010-09-09 kell 11:51, kirjutas Tantilov, Emil S:
>> Priit Laes wrote:
>> > Heya!
>> >
>> > After trying out newer 2.6.35-rc3 kernel, the network interface fails
>> > to
>
>Uhoh.. it was a typo ^^, real kernel version is 2.6.36-rc3+ :S
>
>> Is this still an issue in the latest net-next pull?
>Yes, it is still not working (latest net-next pull was on 4th of Aug)
>
>> Also please provide the output of ethtool -e.
>
>Attached output from 2.6.36-rc3
I think this is a known issue for this device - we have a patch currently
in test, and we should have it out soon.
Thanks,
Emil
Powered by blists - more mailing lists