From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Levitsky Subject: RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED] Date: Thu, 15 Jul 2010 02:33:00 +0300 Message-ID: <1279150380.7810.2.camel@localhost.localdomain> References: <1277659633.2989.2.camel@localhost.localdomain> <1277659785.4028.1.camel@localhost.localdomain> <1277660638.3321.1.camel@localhost.localdomain> <1277660831.3321.3.camel@localhost.localdomain> <8DD2590731AB5D4C9DBF71A877482A90015918F40A@orsmsx509.amr.corp.intel.com> <1277745247.12841.1.camel@localhost.localdomain> <8DD2590731AB5D4C9DBF71A877482A90015918FAB6@orsmsx509.amr.corp.intel.com> <1277807529.19417.2.camel@localhost.localdomain> <1277938757.4138.3.camel@localhost.localdomain> <1278204106.21020.0.camel@localhost.localdomain> <1278283714.3444.1.camel@localhost.localdomain> <1278323885.5277.0.camel@localhost.localdomain> <1278950178.17933.2.camel@localhost.localdomain> <1278981483.23017.4.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: "Kirsher, Jeffrey T" , "netdev@vger.kernel.org" , "Allan, Bruce W" , "Pieper, Jeffrey E" To: "Tantilov, Emil S" Return-path: Received: from mail-bw0-f46.google.com ([209.85.214.46]:57172 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757491Ab0GNXdF (ORCPT ); Wed, 14 Jul 2010 19:33:05 -0400 Received: by mail-bw0-f46.google.com with SMTP id 1so261475bwz.19 for ; Wed, 14 Jul 2010 16:33:04 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Wed, 2010-07-14 at 16:56 -0600, Tantilov, Emil S wrote: > Maxim Levitsky wrote: > > On Mon, 2010-07-12 at 15:23 -0600, Tantilov, Emil S wrote: > >> 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 > >>>>> 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 > > I did send -e and -d output. > > Sorry, looks like I lost the email with the attachements. > > Could you provide the output of dmesg after the failure occurs? > > > Since you probably want -S output during failure, I need to recompile > > kernel for that. I will do that soon. > > > > > > One question, in two weeks I hope 2.6.35 won't be released? > > If so, I will have enough free time then to narrow down this issue. > > > > Other solution, is to revert this commit. > > (I have never seen this problem with it reverted). > > We have been running reboot tests on 2 separate systems with recent net-next kernels > using your config and so far no luck in reproducing this issue. > > What is the make model of your system (or MB)? the motherboard is Intel DG965RY. However, I am using vanilla kernel. net-next might contain further fixes. I see if net-next works here. Best regards, Maxim Levitsky