RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]

[Maxim Levitsky <maximlevitsky@gmail.com>]

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
> >>> <maximlevitsky@gmail.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
I did send -e and -d output.

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).


Best regards,
	Maxim Levitsky