[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EA929A9653AAE14F841771FB1DE5A1365FF4A9B949@rrsmsx501.amr.corp.intel.com>
Date: Mon, 12 Jul 2010 15:23:10 -0600
From: "Tantilov, Emil S" <emil.s.tantilov@...el.com>
To: Maxim Levitsky <maximlevitsky@...il.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Allan, Bruce W" <bruce.w.allan@...el.com>,
"Pieper, Jeffrey E" <jeffrey.e.pieper@...el.com>
Subject: RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
Maxim Levitsky wrote:
> On Mon, 2010-07-05 at 12:58 +0300, Maxim Levitsky wrote:
>> On Mon, 2010-07-05 at 01:13 -0700, Jeff Kirsher wrote:
>>> On Sun, Jul 4, 2010 at 15:48, Maxim Levitsky
>>> <maximlevitsky@...il.com> wrote:
>>>> Did few guesses, and now I see that reverting the below commit
>>>> fixes the problem.
>>>>
>>>> "e1000e: Fix/cleanup PHY reset code for ICHx/PCHx"
>>>> e98cac447cc1cc418dff1d610a5c79c4f2bdec7f.
>>>>
>>>>
>>>> Best regards,
>>>> Maxim Levitsky
>>>>
>>>> --
>>>
>>> Can you give us till Tuesday to respond? I know that there are some
>>> additional e1000e patches in my queue, which may resolve the issue,
>>> but this weekend the power is down to do some infrastructure
>>> upgrades
>>> which prevents us from doing any investigation.debugging until
>>> Tuesday.
>>>
>>
>> Sure.
>>
>> Best regards,
>> Maxim Levitsky
>>
>
> Updates?
We are working on reproducing the issue. So far we have not seen the problem when testing with net-next.
I asked in previous email about some additional info from ethtool (-d, -e, -S) and kernel config. That would help us to narrow it down.
Thanks,
Emil
Powered by blists - more mailing lists