* [REGRESSION] e1000e stopped working
@ 2010-06-27 17:27 Maxim Levitsky
2010-06-27 17:29 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-06-27 17:27 UTC (permalink / raw)
To: netdev@vger.kernel.org
Just that,
It doesn't receive anything from my internet router during DHCP.
00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC Gigabit Network Connection [8086:104b] (rev 02)
Subsystem: Intel Corporation Device [8086:0001]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 47
Region 0: Memory at 50300000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at 50324000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at 30e0 [size=32]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0100c Data: 41c9
Kernel driver in use: e1000e
Kernel modules: e1000e
I use vanilla tree, commit bf2937695fe2330bfd8933a2310e7bdd2581dc2e
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: [REGRESSION] e1000e stopped working
2010-06-27 17:27 [REGRESSION] e1000e stopped working Maxim Levitsky
@ 2010-06-27 17:29 ` Maxim Levitsky
2010-06-27 17:43 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-06-27 17:29 UTC (permalink / raw)
To: netdev@vger.kernel.org
On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
> Just that,
>
> It doesn't receive anything from my internet router during DHCP.
>
>
> 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC Gigabit Network Connection [8086:104b] (rev 02)
> Subsystem: Intel Corporation Device [8086:0001]
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 47
> Region 0: Memory at 50300000 (32-bit, non-prefetchable) [size=128K]
> Region 1: Memory at 50324000 (32-bit, non-prefetchable) [size=4K]
> Region 2: I/O ports at 30e0 [size=32]
> Capabilities: [c8] Power Management version 2
> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
> Status: D0 PME-Enable- DSel=0 DScale=1 PME-
> Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
> Address: 00000000fee0100c Data: 41c9
> Kernel driver in use: e1000e
> Kernel modules: e1000e
>
> I use vanilla tree, commit bf2937695fe2330bfd8933a2310e7bdd2581dc2e
>
>
> Best regards,
> Maxim Levitsky
>
It appears to work now after reboot.
Will keep a look for this.
Disregard for now.
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: [REGRESSION] e1000e stopped working
2010-06-27 17:29 ` Maxim Levitsky
@ 2010-06-27 17:43 ` Maxim Levitsky
2010-06-27 17:47 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-06-27 17:43 UTC (permalink / raw)
To: netdev@vger.kernel.org
On Sun, 2010-06-27 at 20:29 +0300, Maxim Levitsky wrote:
> On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
> > Just that,
> >
> > It doesn't receive anything from my internet router during DHCP.
> >
> >
> > 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC Gigabit Network Connection [8086:104b] (rev 02)
> > Subsystem: Intel Corporation Device [8086:0001]
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
> > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> > Latency: 0
> > Interrupt: pin A routed to IRQ 47
> > Region 0: Memory at 50300000 (32-bit, non-prefetchable) [size=128K]
> > Region 1: Memory at 50324000 (32-bit, non-prefetchable) [size=4K]
> > Region 2: I/O ports at 30e0 [size=32]
> > Capabilities: [c8] Power Management version 2
> > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
> > Status: D0 PME-Enable- DSel=0 DScale=1 PME-
> > Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
> > Address: 00000000fee0100c Data: 41c9
> > Kernel driver in use: e1000e
> > Kernel modules: e1000e
> >
> > I use vanilla tree, commit bf2937695fe2330bfd8933a2310e7bdd2581dc2e
> >
> >
> > Best regards,
> > Maxim Levitsky
> >
>
> It appears to work now after reboot.
> Will keep a look for this.
>
> Disregard for now.
Just s2ram cycle, problem is back.
Did full reboot (power off then on), same thing card doesn't work...
>Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: [REGRESSION] e1000e stopped working
2010-06-27 17:43 ` Maxim Levitsky
@ 2010-06-27 17:47 ` Maxim Levitsky
2010-06-28 17:04 ` Allan, Bruce W
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-06-27 17:47 UTC (permalink / raw)
To: netdev@vger.kernel.org
On Sun, 2010-06-27 at 20:43 +0300, Maxim Levitsky wrote:
> On Sun, 2010-06-27 at 20:29 +0300, Maxim Levitsky wrote:
> > On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
> > > Just that,
> > >
> > > It doesn't receive anything from my internet router during DHCP.
> > >
> > >
> > > 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC Gigabit Network Connection [8086:104b] (rev 02)
> > > Subsystem: Intel Corporation Device [8086:0001]
> > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
> > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> > > Latency: 0
> > > Interrupt: pin A routed to IRQ 47
> > > Region 0: Memory at 50300000 (32-bit, non-prefetchable) [size=128K]
> > > Region 1: Memory at 50324000 (32-bit, non-prefetchable) [size=4K]
> > > Region 2: I/O ports at 30e0 [size=32]
> > > Capabilities: [c8] Power Management version 2
> > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
> > > Status: D0 PME-Enable- DSel=0 DScale=1 PME-
> > > Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
> > > Address: 00000000fee0100c Data: 41c9
> > > Kernel driver in use: e1000e
> > > Kernel modules: e1000e
> > >
> > > I use vanilla tree, commit bf2937695fe2330bfd8933a2310e7bdd2581dc2e
> > >
> > >
> > > Best regards,
> > > Maxim Levitsky
> > >
> >
> > It appears to work now after reboot.
> > Will keep a look for this.
> >
> > Disregard for now.
>
>
> Just s2ram cycle, problem is back.
> Did full reboot (power off then on), same thing card doesn't work...
>
Yep, s2ram sometimes 'fixes', sometimes breaks the card.
Something got broken in device initialization path.
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working
2010-06-27 17:47 ` Maxim Levitsky
@ 2010-06-28 17:04 ` Allan, Bruce W
2010-06-28 17:14 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Allan, Bruce W @ 2010-06-28 17:04 UTC (permalink / raw)
To: Maxim Levitsky, netdev@vger.kernel.org
On Sunday, June 27, 2010 10:47 AM, Maxim Levitsky wrote:
> On Sun, 2010-06-27 at 20:43 +0300, Maxim Levitsky wrote:
>> On Sun, 2010-06-27 at 20:29 +0300, Maxim Levitsky wrote:
>>> On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
>>>> Just that,
>>>>
>>>> It doesn't receive anything from my internet router during DHCP.
>>>>
>>>>
>>>> 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC
>>>> Gigabit Network Connection [8086:104b] (rev 02) Subsystem: Intel
>>>> Corporation Device [8086:0001] Control: I/O+ Mem+ BusMaster+
>>>> SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>>> DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
>>>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0
>>>> Interrupt: pin A routed to IRQ 47 Region 0: Memory at 50300000
>>>> (32-bit, non-prefetchable) [size=128K] Region 1: Memory at
>>>> 50324000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports
>>>> at 30e0 [size=32] Capabilities: [c8] Power Management version 2
>>>> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
>>>> PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0
>>>> DScale=1 PME- Capabilities: [d0] Message Signalled Interrupts:
>>>> Mask- 64bit+ Queue=0/0 Enable+ Address: 00000000fee0100c Data:
>>>> 41c9 Kernel driver in use: e1000e Kernel modules: e1000e
>>>>
>>>> I use vanilla tree, commit bf2937695fe2330bfd8933a2310e7bdd2581dc2e
>>>>
>>>>
>>>> Best regards,
>>>> Maxim Levitsky
>>>>
>>>
>>> It appears to work now after reboot.
>>> Will keep a look for this.
>>>
>>> Disregard for now.
>>
>>
>> Just s2ram cycle, problem is back.
>> Did full reboot (power off then on), same thing card doesn't work...
>>
>
> Yep, s2ram sometimes 'fixes', sometimes breaks the card.
> Something got broken in device initialization path.
>
> Best regards,
> Maxim Levitsky
What distro are you using? If RedHat, since you are using DHCP will you please try putting a "LINKDELAY=10" in the /etc/sysconfig/network-scripts/ifcfg-ethX config file.
Is there anything in the system log that might help narrow down the issue?
Thanks,
Bruce.
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working
2010-06-28 17:04 ` Allan, Bruce W
@ 2010-06-28 17:14 ` Maxim Levitsky
2010-06-29 1:09 ` Allan, Bruce W
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-06-28 17:14 UTC (permalink / raw)
To: Allan, Bruce W; +Cc: netdev@vger.kernel.org
On Mon, 2010-06-28 at 10:04 -0700, Allan, Bruce W wrote:
> On Sunday, June 27, 2010 10:47 AM, Maxim Levitsky wrote:
> > On Sun, 2010-06-27 at 20:43 +0300, Maxim Levitsky wrote:
> >> On Sun, 2010-06-27 at 20:29 +0300, Maxim Levitsky wrote:
> >>> On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
> >>>> Just that,
> >>>>
> >>>> It doesn't receive anything from my internet router during DHCP.
> >>>>
> >>>>
> >>>> 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC
> >>>> Gigabit Network Connection [8086:104b] (rev 02) Subsystem: Intel
> >>>> Corporation Device [8086:0001] Control: I/O+ Mem+ BusMaster+
> >>>> SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> >>>> DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
> >>>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0
> >>>> Interrupt: pin A routed to IRQ 47 Region 0: Memory at 50300000
> >>>> (32-bit, non-prefetchable) [size=128K] Region 1: Memory at
> >>>> 50324000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports
> >>>> at 30e0 [size=32] Capabilities: [c8] Power Management version 2
> >>>> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
> >>>> PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0
> >>>> DScale=1 PME- Capabilities: [d0] Message Signalled Interrupts:
> >>>> Mask- 64bit+ Queue=0/0 Enable+ Address: 00000000fee0100c Data:
> >>>> 41c9 Kernel driver in use: e1000e Kernel modules: e1000e
> >>>>
> >>>> I use vanilla tree, commit bf2937695fe2330bfd8933a2310e7bdd2581dc2e
> >>>>
> >>>>
> >>>> Best regards,
> >>>> Maxim Levitsky
> >>>>
> >>>
> >>> It appears to work now after reboot.
> >>> Will keep a look for this.
> >>>
> >>> Disregard for now.
> >>
> >>
> >> Just s2ram cycle, problem is back.
> >> Did full reboot (power off then on), same thing card doesn't work...
> >>
> >
> > Yep, s2ram sometimes 'fixes', sometimes breaks the card.
> > Something got broken in device initialization path.
> >
> > Best regards,
> > Maxim Levitsky
>
> What distro are you using? If RedHat, since you are using DHCP will you please try putting a "LINKDELAY=10" in the /etc/sysconfig/network-scripts/ifcfg-ethX config file.
>
I use ubuntu 9.10
> Is there anything in the system log that might help narrow down the issue?
Nothing, really nothing.
It seems to detect link, dhcp client sends requests, but doesn't recieve
a thing (even tried promisc mode - doesn't help)
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working
2010-06-28 17:14 ` Maxim Levitsky
@ 2010-06-29 1:09 ` Allan, Bruce W
2010-06-29 10:32 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Allan, Bruce W @ 2010-06-29 1:09 UTC (permalink / raw)
To: Maxim Levitsky; +Cc: netdev@vger.kernel.org
On Monday, June 28, 2010 10:14 AM, Maxim Levitsky wrote:
> On Mon, 2010-06-28 at 10:04 -0700, Allan, Bruce W wrote:
>> On Sunday, June 27, 2010 10:47 AM, Maxim Levitsky wrote:
>>> On Sun, 2010-06-27 at 20:43 +0300, Maxim Levitsky wrote:
>>>> On Sun, 2010-06-27 at 20:29 +0300, Maxim Levitsky wrote:
>>>>> On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
>>>>>> Just that,
>>>>>>
>>>>>> It doesn't receive anything from my internet router during DHCP.
>>>>>>
>>>>>>
>>>>>> 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC
>>>>>> Gigabit Network Connection [8086:104b] (rev 02) Subsystem: Intel
>>>>>> Corporation Device [8086:0001] Control: I/O+ Mem+ BusMaster+
>>>>>> SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>>>>> DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
>>>>>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0
>>>>>> Interrupt: pin A routed to IRQ 47 Region 0: Memory at 50300000
>>>>>> (32-bit, non-prefetchable) [size=128K] Region 1: Memory at
>>>>>> 50324000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O
>>>>>> ports at 30e0 [size=32] Capabilities: [c8] Power Management
>>>>>> version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
>>>>>> PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0
>>>>>> DScale=1 PME- Capabilities: [d0] Message Signalled Interrupts:
>>>>>> Mask- 64bit+ Queue=0/0 Enable+ Address: 00000000fee0100c Data:
>>>>>> 41c9 Kernel driver in use: e1000e Kernel modules: e1000e
>>>>>>
>>>>>> I use vanilla tree, commit
>>>>>> bf2937695fe2330bfd8933a2310e7bdd2581dc2e
>>>>>>
>>>>>>
>>>>>> Best regards,
>>>>>> Maxim Levitsky
>>>>>>
>>>>>
>>>>> It appears to work now after reboot.
>>>>> Will keep a look for this.
>>>>>
>>>>> Disregard for now.
>>>>
>>>>
>>>> Just s2ram cycle, problem is back.
>>>> Did full reboot (power off then on), same thing card doesn't
>>>> work...
>>>>
>>>
>>> Yep, s2ram sometimes 'fixes', sometimes breaks the card.
>>> Something got broken in device initialization path.
>>>
>>> Best regards,
>>> Maxim Levitsky
>>
>> What distro are you using? If RedHat, since you are using DHCP will
>> you please try putting a "LINKDELAY=10" in the
>> /etc/sysconfig/network-scripts/ifcfg-ethX config file.
>>
> I use ubuntu 9.10
>
>> Is there anything in the system log that might help narrow down the
>> issue?
>
> Nothing, really nothing.
> It seems to detect link, dhcp client sends requests, but doesn't
> recieve a thing (even tried promisc mode - doesn't help)
>
>
>
> Best regards,
> Maxim Levitsky
Since you say this is a regression, when did this last work for you without this problem, i.e. which distro, which kernel?
I have been unable to reproduce similar behavior.
Thanks,
Bruce.
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working
2010-06-29 1:09 ` Allan, Bruce W
@ 2010-06-29 10:32 ` Maxim Levitsky
2010-06-29 18:37 ` Tantilov, Emil S
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-06-29 10:32 UTC (permalink / raw)
To: Allan, Bruce W; +Cc: netdev@vger.kernel.org
On Mon, 2010-06-28 at 18:09 -0700, Allan, Bruce W wrote:
> On Monday, June 28, 2010 10:14 AM, Maxim Levitsky wrote:
> > On Mon, 2010-06-28 at 10:04 -0700, Allan, Bruce W wrote:
> >> On Sunday, June 27, 2010 10:47 AM, Maxim Levitsky wrote:
> >>> On Sun, 2010-06-27 at 20:43 +0300, Maxim Levitsky wrote:
> >>>> On Sun, 2010-06-27 at 20:29 +0300, Maxim Levitsky wrote:
> >>>>> On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
> >>>>>> Just that,
> >>>>>>
> >>>>>> It doesn't receive anything from my internet router during DHCP.
> >>>>>>
> >>>>>>
> >>>>>> 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC
> >>>>>> Gigabit Network Connection [8086:104b] (rev 02) Subsystem: Intel
> >>>>>> Corporation Device [8086:0001] Control: I/O+ Mem+ BusMaster+
> >>>>>> SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> >>>>>> DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
> >>>>>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0
> >>>>>> Interrupt: pin A routed to IRQ 47 Region 0: Memory at 50300000
> >>>>>> (32-bit, non-prefetchable) [size=128K] Region 1: Memory at
> >>>>>> 50324000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O
> >>>>>> ports at 30e0 [size=32] Capabilities: [c8] Power Management
> >>>>>> version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
> >>>>>> PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0
> >>>>>> DScale=1 PME- Capabilities: [d0] Message Signalled Interrupts:
> >>>>>> Mask- 64bit+ Queue=0/0 Enable+ Address: 00000000fee0100c Data:
> >>>>>> 41c9 Kernel driver in use: e1000e Kernel modules: e1000e
> >>>>>>
> >>>>>> I use vanilla tree, commit
> >>>>>> bf2937695fe2330bfd8933a2310e7bdd2581dc2e
> >>>>>>
> >>>>>>
> >>>>>> Best regards,
> >>>>>> Maxim Levitsky
> >>>>>>
> >>>>>
> >>>>> It appears to work now after reboot.
> >>>>> Will keep a look for this.
> >>>>>
> >>>>> Disregard for now.
> >>>>
> >>>>
> >>>> Just s2ram cycle, problem is back.
> >>>> Did full reboot (power off then on), same thing card doesn't
> >>>> work...
> >>>>
> >>>
> >>> Yep, s2ram sometimes 'fixes', sometimes breaks the card.
> >>> Something got broken in device initialization path.
> >>>
> >>> Best regards,
> >>> Maxim Levitsky
> >>
> >> What distro are you using? If RedHat, since you are using DHCP will
> >> you please try putting a "LINKDELAY=10" in the
> >> /etc/sysconfig/network-scripts/ifcfg-ethX config file.
> >>
> > I use ubuntu 9.10
> >
> >> Is there anything in the system log that might help narrow down the
> >> issue?
> >
> > Nothing, really nothing.
> > It seems to detect link, dhcp client sends requests, but doesn't
> > recieve a thing (even tried promisc mode - doesn't help)
> >
> >
> >
> > Best regards,
> > Maxim Levitsky
>
> Since you say this is a regression, when did this last work for you without this problem, i.e. which distro, which kernel?
I always compile kernel, and last kernel I compiled here was vanilla
2.6.33-rc4.
It works just fine.
I mostly use my laptop, and therefore didn't update kernel on my desktop
for long time.
If I find some free time I try to bisect the problem.
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working
2010-06-29 10:32 ` Maxim Levitsky
@ 2010-06-29 18:37 ` Tantilov, Emil S
2010-06-30 22:59 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Tantilov, Emil S @ 2010-06-29 18:37 UTC (permalink / raw)
To: Maxim Levitsky; +Cc: netdev@vger.kernel.org, Allan, Bruce W, Pieper, Jeffrey E
Maxim Levitsky wrote:
> On Mon, 2010-06-28 at 18:09 -0700, Allan, Bruce W wrote:
>> On Monday, June 28, 2010 10:14 AM, Maxim Levitsky wrote:
>>> On Mon, 2010-06-28 at 10:04 -0700, Allan, Bruce W wrote:
>>>> On Sunday, June 27, 2010 10:47 AM, Maxim Levitsky wrote:
>>>>> On Sun, 2010-06-27 at 20:43 +0300, Maxim Levitsky wrote:
>>>>>> On Sun, 2010-06-27 at 20:29 +0300, Maxim Levitsky wrote:
>>>>>>> On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
>>>>>>>> Just that,
>>>>>>>>
>>>>>>>> It doesn't receive anything from my internet router during
>>>>>>>> DHCP.
>>>>>>>>
>>>>>>>>
>>>>>>>> 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC
>>>>>>>> Gigabit Network Connection [8086:104b] (rev 02) Subsystem:
>>>>>>>> Intel Corporation Device [8086:0001] Control: I/O+ Mem+
>>>>>>>> BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
>>>>>>>> SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B-
>>>>>>>> ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>>>>>>>> INTx- Latency: 0 Interrupt: pin A routed to IRQ 47 Region 0:
>>>>>>>> Memory at 50300000 (32-bit, non-prefetchable) [size=128K]
>>>>>>>> Region 1: Memory at 50324000 (32-bit, non-prefetchable)
>>>>>>>> [size=4K] Region 2: I/O ports at 30e0 [size=32]
>>>>>>>> Capabilities: [c8] Power Management version 2 Flags: PMEClk-
>>>>>>>> DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
>>>>>>>> Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities:
>>>>>>>> [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
>>>>>>>> Enable+ Address: 00000000fee0100c Data: 41c9 Kernel driver
>>>>>>>> in use: e1000e Kernel modules: e1000e
>>>>>>>>
>>>>>>>> I use vanilla tree, commit
>>>>>>>> bf2937695fe2330bfd8933a2310e7bdd2581dc2e
>>>>>>>>
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> Maxim Levitsky
>>>>>>>>
>>>>>>>
>>>>>>> It appears to work now after reboot.
>>>>>>> Will keep a look for this.
>>>>>>>
>>>>>>> Disregard for now.
>>>>>>
>>>>>>
>>>>>> Just s2ram cycle, problem is back.
>>>>>> Did full reboot (power off then on), same thing card doesn't
>>>>>> work...
>>>>>>
>>>>>
>>>>> Yep, s2ram sometimes 'fixes', sometimes breaks the card.
>>>>> Something got broken in device initialization path.
>>>>>
>>>>> Best regards,
>>>>> Maxim Levitsky
>>>>
>>>> What distro are you using? If RedHat, since you are using DHCP
>>>> will you please try putting a "LINKDELAY=10" in the
>>>> /etc/sysconfig/network-scripts/ifcfg-ethX config file.
>>>>
>>> I use ubuntu 9.10
>>>
>>>> Is there anything in the system log that might help narrow down the
>>>> issue?
>>>
>>> Nothing, really nothing.
>>> It seems to detect link, dhcp client sends requests, but doesn't
>>> recieve a thing (even tried promisc mode - doesn't help)
>>>
>>>
>>>
>>> Best regards,
>>> Maxim Levitsky
>>
>> Since you say this is a regression, when did this last work for you
>> without this problem, i.e. which distro, which kernel?
>
> I always compile kernel, and last kernel I compiled here was vanilla
> 2.6.33-rc4.
> It works just fine.
>
> I mostly use my laptop, and therefore didn't update kernel on my
> desktop for long time.
>
> If I find some free time I try to bisect the problem.
Could you provide some additional info about your setup:
ethtool -e eth0
ethtool -d eth0
kernel config (if possible)
What is the model of your system/MB?
Thanks,
Emil
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working
2010-06-29 18:37 ` Tantilov, Emil S
@ 2010-06-30 22:59 ` Maxim Levitsky
2010-07-04 0:41 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-06-30 22:59 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: netdev@vger.kernel.org, Allan, Bruce W, Pieper, Jeffrey E
[-- Attachment #1: Type: text/plain, Size: 3835 bytes --]
On Tue, 2010-06-29 at 12:37 -0600, Tantilov, Emil S wrote:
> Maxim Levitsky wrote:
> > On Mon, 2010-06-28 at 18:09 -0700, Allan, Bruce W wrote:
> >> On Monday, June 28, 2010 10:14 AM, Maxim Levitsky wrote:
> >>> On Mon, 2010-06-28 at 10:04 -0700, Allan, Bruce W wrote:
> >>>> On Sunday, June 27, 2010 10:47 AM, Maxim Levitsky wrote:
> >>>>> On Sun, 2010-06-27 at 20:43 +0300, Maxim Levitsky wrote:
> >>>>>> On Sun, 2010-06-27 at 20:29 +0300, Maxim Levitsky wrote:
> >>>>>>> On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
> >>>>>>>> Just that,
> >>>>>>>>
> >>>>>>>> It doesn't receive anything from my internet router during
> >>>>>>>> DHCP.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC
> >>>>>>>> Gigabit Network Connection [8086:104b] (rev 02) Subsystem:
> >>>>>>>> Intel Corporation Device [8086:0001] Control: I/O+ Mem+
> >>>>>>>> BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
> >>>>>>>> SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B-
> >>>>>>>> ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> >>>>>>>> INTx- Latency: 0 Interrupt: pin A routed to IRQ 47 Region 0:
> >>>>>>>> Memory at 50300000 (32-bit, non-prefetchable) [size=128K]
> >>>>>>>> Region 1: Memory at 50324000 (32-bit, non-prefetchable)
> >>>>>>>> [size=4K] Region 2: I/O ports at 30e0 [size=32]
> >>>>>>>> Capabilities: [c8] Power Management version 2 Flags: PMEClk-
> >>>>>>>> DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
> >>>>>>>> Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities:
> >>>>>>>> [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
> >>>>>>>> Enable+ Address: 00000000fee0100c Data: 41c9 Kernel driver
> >>>>>>>> in use: e1000e Kernel modules: e1000e
> >>>>>>>>
> >>>>>>>> I use vanilla tree, commit
> >>>>>>>> bf2937695fe2330bfd8933a2310e7bdd2581dc2e
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Best regards,
> >>>>>>>> Maxim Levitsky
> >>>>>>>>
> >>>>>>>
> >>>>>>> It appears to work now after reboot.
> >>>>>>> Will keep a look for this.
> >>>>>>>
> >>>>>>> Disregard for now.
> >>>>>>
> >>>>>>
> >>>>>> Just s2ram cycle, problem is back.
> >>>>>> Did full reboot (power off then on), same thing card doesn't
> >>>>>> work...
> >>>>>>
> >>>>>
> >>>>> Yep, s2ram sometimes 'fixes', sometimes breaks the card.
> >>>>> Something got broken in device initialization path.
> >>>>>
> >>>>> Best regards,
> >>>>> Maxim Levitsky
> >>>>
> >>>> What distro are you using? If RedHat, since you are using DHCP
> >>>> will you please try putting a "LINKDELAY=10" in the
> >>>> /etc/sysconfig/network-scripts/ifcfg-ethX config file.
> >>>>
> >>> I use ubuntu 9.10
> >>>
> >>>> Is there anything in the system log that might help narrow down the
> >>>> issue?
> >>>
> >>> Nothing, really nothing.
> >>> It seems to detect link, dhcp client sends requests, but doesn't
> >>> recieve a thing (even tried promisc mode - doesn't help)
> >>>
> >>>
> >>>
> >>> Best regards,
> >>> Maxim Levitsky
> >>
> >> Since you say this is a regression, when did this last work for you
> >> without this problem, i.e. which distro, which kernel?
> >
> > I always compile kernel, and last kernel I compiled here was vanilla
> > 2.6.33-rc4.
> > It works just fine.
> >
> > I mostly use my laptop, and therefore didn't update kernel on my
> > desktop for long time.
> >
> > If I find some free time I try to bisect the problem.
>
> Could you provide some additional info about your setup:
> ethtool -e eth0
> ethtool -d eth0
> kernel config (if possible)
>
> What is the model of your system/MB?
Sure,
My motherboard on this system is Intel DG965RY
The bug in about 90% reproducible.
Doing several s2ram cycles, its possible to catch a moment when the
device starts working.
Best regards,
Maxim Levitsky
[-- Attachment #2: eeprom --]
[-- Type: text/plain, Size: 14622 bytes --]
Offset Values
------ ------
0x0000 00 19 d1 ed 88 2a 00 08 ff ff 10 10 ff ff ff ff
0x0010 ff ff ff ff c7 10 01 00 86 80 4b 10 86 80 00 00
0x0020 01 0d 00 00 00 00 05 96 20 50 00 33 00 00 07 8d
0x0030 84 06 41 03 00 00 00 00 00 00 00 00 00 00 00 00
0x0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x0060 00 01 00 40 2a 12 07 40 ff ff ff ff ff ff ff ff
0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff 1f ff
0x0080 20 61 1f 00 02 0e 12 00 40 2f 1f 00 18 90 1b 00
0x0090 00 00 12 00 a0 2f 1f 00 24 8b 11 00 f0 f8 12 00
0x00a0 00 20 1f 00 b0 10 10 00 00 00 11 00 c0 20 1f 00
0x00b0 9a 24 1d 00 d3 00 1e 00 a0 28 1f 00 ce 04 14 00
0x00c0 60 2f 1f 00 e4 29 10 00 00 00 1f 00 40 01 00 00
0x00d0 20 1f 1f 00 06 16 10 00 14 b8 11 00 2a 01 15 00
0x00e0 67 00 1e 00 40 1f 1f 00 65 00 14 00 2a 00 15 00
0x00f0 2a 00 16 00 60 1f 1f 00 b0 3f 12 00 ff c0 16 00
0x0100 ec 1d 17 00 ef f9 18 00 10 02 19 00 80 18 1f 00
0x0110 03 00 15 00 80 17 1f 00 08 00 16 00 80 17 1f 00
0x0120 08 d0 18 00 80 18 1f 00 18 d9 18 00 60 18 1f 00
0x0130 00 08 1a 00 00 00 1f 00 01 00 19 00 40 13 00 00
0x0140 51 60 1f 00 01 00 11 00 00 00 1f 00 ff ff ff ff
0x0150 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0160 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0170 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0180 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0190 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x01a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x01b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x01c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x01d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x01e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x01f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0200 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0210 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0220 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0230 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0240 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0250 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0260 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0270 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0280 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0290 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x02a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x02b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x02c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x02d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x02e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x02f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0300 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0310 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0320 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0330 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0340 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0350 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0360 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0370 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0380 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0390 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x03a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x03b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x03c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x03d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x03e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x03f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0400 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0410 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0420 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0430 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0440 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0450 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0460 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0470 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0480 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0490 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x04a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x04b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x04c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x04d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x04e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x04f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0500 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0510 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0520 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0530 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0540 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0550 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0560 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0570 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0580 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0590 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x05a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x05b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x05c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x05d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x05e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x05f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0600 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0610 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0620 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0630 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0640 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0650 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0660 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0670 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0680 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0690 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x06a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x06b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x06c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x06d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x06e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x06f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0700 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0710 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0720 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0730 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0740 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0750 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0760 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0770 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0780 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0790 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x07a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x07b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x07c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x07d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x07e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x07f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0800 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0810 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0820 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0830 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0840 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0850 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0860 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0870 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0880 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0890 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x08a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x08b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x08c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x08d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x08e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x08f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0900 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0910 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0920 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0930 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0940 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0950 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0960 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0970 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0980 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0990 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x09a0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x09b0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x09c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x09d0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x09e0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x09f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0a00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0a10 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0a20 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0a30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0a40 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0a50 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0a60 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0a70 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0a80 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0a90 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0aa0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ab0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ac0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ad0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ae0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0af0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0b00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0b10 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0b20 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0b30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0b40 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0b50 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0b60 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0b70 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0b80 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0b90 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ba0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0bb0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0bc0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0bd0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0be0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0bf0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0c00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0c10 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0c20 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0c30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0c40 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0c50 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0c60 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0c70 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0c80 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0c90 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ca0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0cb0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0cc0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0cd0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ce0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0cf0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0d00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0d10 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0d20 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0d30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0d40 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0d50 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0d60 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0d70 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0d80 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0d90 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0da0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0db0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0dc0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0dd0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0de0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0df0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0e00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0e10 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0e20 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0e30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0e40 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0e50 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0e60 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0e70 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0e80 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0e90 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ea0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0eb0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ec0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ed0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ee0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ef0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0f00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0f10 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0f20 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0f30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0f40 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0f50 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0f60 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0f70 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0f80 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0f90 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0fa0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0fb0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0fc0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0fd0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0fe0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
0x0ff0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[-- Attachment #3: misc --]
[-- Type: text/plain, Size: 1297 bytes --]
maxim@MAIN:~$ sudo ethtool -i eth1
driver: e1000e
version: 1.0.2-k4
firmware-version: 1.1-0
bus-info: 0000:00:19.0
maxim@MAIN:~$ sudo ethtool -g eth1
Ring parameters for eth1:
Pre-set maximums:
RX: 4096
RX Mini: 0
RX Jumbo: 0
TX: 4096
Current hardware settings:
RX: 256
RX Mini: 0
RX Jumbo: 0
TX: 256
maxim@MAIN:~$ ifconfig
eth1 Link encap:Ethernet HWaddr 00:19:d1:ed:88:2a
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3411 (3.4 KB) TX bytes:2736 (2.7 KB)
Interrupt:20 Memory:50300000-50320000
Number of RX packets seems to increase
Wireshark doesn't see them
Example:
maxim@MAIN:~$ sudo dhclient eth1
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth1/00:19:d1:ed:88:2a
Sending on LPF/eth1/00:19:d1:ed:88:2a
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18
[-- Attachment #4: reg_dump --]
[-- Type: audio/x-ape, Size: 2300 bytes --]
[-- Attachment #5: .config.gz --]
[-- Type: application/x-gzip, Size: 16213 bytes --]
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working
2010-06-30 22:59 ` Maxim Levitsky
@ 2010-07-04 0:41 ` Maxim Levitsky
2010-07-04 22:48 ` [REGRESSION] e1000e stopped working [MANUALLY BISECTED] Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-04 0:41 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: netdev@vger.kernel.org, Allan, Bruce W, Pieper, Jeffrey E
On Thu, 2010-07-01 at 01:59 +0300, Maxim Levitsky wrote:
> On Tue, 2010-06-29 at 12:37 -0600, Tantilov, Emil S wrote:
> > Maxim Levitsky wrote:
> > > On Mon, 2010-06-28 at 18:09 -0700, Allan, Bruce W wrote:
> > >> On Monday, June 28, 2010 10:14 AM, Maxim Levitsky wrote:
> > >>> On Mon, 2010-06-28 at 10:04 -0700, Allan, Bruce W wrote:
> > >>>> On Sunday, June 27, 2010 10:47 AM, Maxim Levitsky wrote:
> > >>>>> On Sun, 2010-06-27 at 20:43 +0300, Maxim Levitsky wrote:
> > >>>>>> On Sun, 2010-06-27 at 20:29 +0300, Maxim Levitsky wrote:
> > >>>>>>> On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
> > >>>>>>>> Just that,
> > >>>>>>>>
> > >>>>>>>> It doesn't receive anything from my internet router during
> > >>>>>>>> DHCP.
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC
> > >>>>>>>> Gigabit Network Connection [8086:104b] (rev 02) Subsystem:
> > >>>>>>>> Intel Corporation Device [8086:0001] Control: I/O+ Mem+
> > >>>>>>>> BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
> > >>>>>>>> SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B-
> > >>>>>>>> ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> > >>>>>>>> INTx- Latency: 0 Interrupt: pin A routed to IRQ 47 Region 0:
> > >>>>>>>> Memory at 50300000 (32-bit, non-prefetchable) [size=128K]
> > >>>>>>>> Region 1: Memory at 50324000 (32-bit, non-prefetchable)
> > >>>>>>>> [size=4K] Region 2: I/O ports at 30e0 [size=32]
> > >>>>>>>> Capabilities: [c8] Power Management version 2 Flags: PMEClk-
> > >>>>>>>> DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
> > >>>>>>>> Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities:
> > >>>>>>>> [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
> > >>>>>>>> Enable+ Address: 00000000fee0100c Data: 41c9 Kernel driver
> > >>>>>>>> in use: e1000e Kernel modules: e1000e
> > >>>>>>>>
> > >>>>>>>> I use vanilla tree, commit
> > >>>>>>>> bf2937695fe2330bfd8933a2310e7bdd2581dc2e
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> Best regards,
> > >>>>>>>> Maxim Levitsky
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>> It appears to work now after reboot.
> > >>>>>>> Will keep a look for this.
> > >>>>>>>
> > >>>>>>> Disregard for now.
> > >>>>>>
> > >>>>>>
> > >>>>>> Just s2ram cycle, problem is back.
> > >>>>>> Did full reboot (power off then on), same thing card doesn't
> > >>>>>> work...
> > >>>>>>
> > >>>>>
> > >>>>> Yep, s2ram sometimes 'fixes', sometimes breaks the card.
> > >>>>> Something got broken in device initialization path.
> > >>>>>
> > >>>>> Best regards,
> > >>>>> Maxim Levitsky
> > >>>>
> > >>>> What distro are you using? If RedHat, since you are using DHCP
> > >>>> will you please try putting a "LINKDELAY=10" in the
> > >>>> /etc/sysconfig/network-scripts/ifcfg-ethX config file.
> > >>>>
> > >>> I use ubuntu 9.10
> > >>>
> > >>>> Is there anything in the system log that might help narrow down the
> > >>>> issue?
> > >>>
> > >>> Nothing, really nothing.
> > >>> It seems to detect link, dhcp client sends requests, but doesn't
> > >>> recieve a thing (even tried promisc mode - doesn't help)
> > >>>
> > >>>
> > >>>
> > >>> Best regards,
> > >>> Maxim Levitsky
> > >>
> > >> Since you say this is a regression, when did this last work for you
> > >> without this problem, i.e. which distro, which kernel?
> > >
> > > I always compile kernel, and last kernel I compiled here was vanilla
> > > 2.6.33-rc4.
> > > It works just fine.
> > >
> > > I mostly use my laptop, and therefore didn't update kernel on my
> > > desktop for long time.
> > >
> > > If I find some free time I try to bisect the problem.
> >
> > Could you provide some additional info about your setup:
> > ethtool -e eth0
> > ethtool -d eth0
> > kernel config (if possible)
> >
> > What is the model of your system/MB?
>
>
> Sure,
>
>
> My motherboard on this system is Intel DG965RY
>
> The bug in about 90% reproducible.
> Doing several s2ram cycles, its possible to catch a moment when the
> device starts working.
>
Just tested 2.6.34, and it works, so this is 2.6.35 regression.
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-04 0:41 ` Maxim Levitsky
@ 2010-07-04 22:48 ` Maxim Levitsky
2010-07-05 8:13 ` Jeff Kirsher
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-04 22:48 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: netdev@vger.kernel.org, Allan, Bruce W, Pieper, Jeffrey E
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
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-04 22:48 ` [REGRESSION] e1000e stopped working [MANUALLY BISECTED] Maxim Levitsky
@ 2010-07-05 8:13 ` Jeff Kirsher
2010-07-05 9:58 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Jeff Kirsher @ 2010-07-05 8:13 UTC (permalink / raw)
To: Maxim Levitsky
Cc: Tantilov, Emil S, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
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.
--
Cheers,
Jeff
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-05 8:13 ` Jeff Kirsher
@ 2010-07-05 9:58 ` Maxim Levitsky
2010-07-12 15:56 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-05 9:58 UTC (permalink / raw)
To: Jeff Kirsher
Cc: Tantilov, Emil S, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
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
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-05 9:58 ` Maxim Levitsky
@ 2010-07-12 15:56 ` Maxim Levitsky
2010-07-12 21:23 ` Tantilov, Emil S
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-12 15:56 UTC (permalink / raw)
To: Jeff Kirsher
Cc: Tantilov, Emil S, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
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?
or 2.6.35 will ship with e0000e ? :-)
I really have very little time to help further with that for now.
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-12 15:56 ` Maxim Levitsky
@ 2010-07-12 21:23 ` Tantilov, Emil S
2010-07-13 0:38 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Tantilov, Emil S @ 2010-07-12 21:23 UTC (permalink / raw)
To: Maxim Levitsky, Kirsher, Jeffrey T
Cc: netdev@vger.kernel.org, Allan, Bruce W, Pieper, Jeffrey E
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
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-12 21:23 ` Tantilov, Emil S
@ 2010-07-13 0:38 ` Maxim Levitsky
2010-07-14 22:56 ` Tantilov, Emil S
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-13 0:38 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
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
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-13 0:38 ` Maxim Levitsky
@ 2010-07-14 22:56 ` Tantilov, Emil S
2010-07-14 23:33 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Tantilov, Emil S @ 2010-07-14 22:56 UTC (permalink / raw)
To: Maxim Levitsky
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
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
>>>>> <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.
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)?
Thanks,
Emil
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-14 22:56 ` Tantilov, Emil S
@ 2010-07-14 23:33 ` Maxim Levitsky
2010-07-15 18:57 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-14 23:33 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
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
> >>>>> <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.
>
> 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
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-14 23:33 ` Maxim Levitsky
@ 2010-07-15 18:57 ` Maxim Levitsky
2010-07-15 19:02 ` Tantilov, Emil S
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-15 18:57 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
On Thu, 2010-07-15 at 02:33 +0300, Maxim Levitsky wrote:
> 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
> > >>>>> <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.
> >
> > 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.
Yep, net-next works here.
I have the problem on vanilla kernel.
Last revision of it, I tested is 2.6.35-rc4 exactly
(815c4163b6c8ebf8152f42b0a5fd015cfdcedc78)
Maybe vanilla git master works, I test it too soon.
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-15 18:57 ` Maxim Levitsky
@ 2010-07-15 19:02 ` Tantilov, Emil S
2010-07-15 19:09 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Tantilov, Emil S @ 2010-07-15 19:02 UTC (permalink / raw)
To: Maxim Levitsky
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
Maxim Levitsky wrote:
> On Thu, 2010-07-15 at 02:33 +0300, Maxim Levitsky wrote:
>> 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
>>>>>>>> <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.
>>>
>>> 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.
>
> Yep, net-next works here.
>
>
> I have the problem on vanilla kernel.
> Last revision of it, I tested is 2.6.35-rc4 exactly
> (815c4163b6c8ebf8152f42b0a5fd015cfdcedc78)
>
>
> Maybe vanilla git master works, I test it too soon.
Thanks for the information! Good to know that this issue does not exist in the latest branch.
Have you by any chance tested a stable branch (2.6.34.x)?
>
>
> Best regards,
> Maxim Levitsky
Thanks,
Emil
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-15 19:02 ` Tantilov, Emil S
@ 2010-07-15 19:09 ` Maxim Levitsky
2010-07-16 19:25 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-15 19:09 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
On Thu, 2010-07-15 at 13:02 -0600, Tantilov, Emil S wrote:
> Maxim Levitsky wrote:
> > On Thu, 2010-07-15 at 02:33 +0300, Maxim Levitsky wrote:
> >> 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
> >>>>>>>> <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.
> >>>
> >>> 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.
> >
> > Yep, net-next works here.
> >
> >
> > I have the problem on vanilla kernel.
> > Last revision of it, I tested is 2.6.35-rc4 exactly
> > (815c4163b6c8ebf8152f42b0a5fd015cfdcedc78)
> >
> >
> > Maybe vanilla git master works, I test it too soon.
>
> Thanks for the information! Good to know that this issue does not exist in the latest branch.
>
> Have you by any chance tested a stable branch (2.6.34.x)?
I only did test plain 2.6.34 (v2.6.34)
Also I repeat that revert of e98cac447cc1cc418dff1d610a5c79c4f2bdec7f
(e1000e: Fix/cleanup PHY reset code for ICHx/PCHx) fixes the bug on
vanilla kernel.
Also I just pulled latest vanilla git, and I according to diffstat I see
no changes in e1000e, so its likely that bug remains there.
I will test that soon.
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-15 19:09 ` Maxim Levitsky
@ 2010-07-16 19:25 ` Maxim Levitsky
2010-07-16 23:23 ` Tantilov, Emil S
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-16 19:25 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
On Thu, 2010-07-15 at 22:09 +0300, Maxim Levitsky wrote:
> On Thu, 2010-07-15 at 13:02 -0600, Tantilov, Emil S wrote:
> > Maxim Levitsky wrote:
> > > On Thu, 2010-07-15 at 02:33 +0300, Maxim Levitsky wrote:
> > >> 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
> > >>>>>>>> <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.
> > >>>
> > >>> 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.
> > >
> > > Yep, net-next works here.
> > >
> > >
> > > I have the problem on vanilla kernel.
> > > Last revision of it, I tested is 2.6.35-rc4 exactly
> > > (815c4163b6c8ebf8152f42b0a5fd015cfdcedc78)
> > >
> > >
> > > Maybe vanilla git master works, I test it too soon.
> >
> > Thanks for the information! Good to know that this issue does not exist in the latest branch.
> >
> > Have you by any chance tested a stable branch (2.6.34.x)?
>
> I only did test plain 2.6.34 (v2.6.34)
And forgot to add, that it did work.
>
> Also I repeat that revert of e98cac447cc1cc418dff1d610a5c79c4f2bdec7f
> (e1000e: Fix/cleanup PHY reset code for ICHx/PCHx) fixes the bug on
> vanilla kernel.
>
> Also I just pulled latest vanilla git, and I according to diffstat I see
> no changes in e1000e, so its likely that bug remains there.
> I will test that soon.
Tested, broken as expected.
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-16 19:25 ` Maxim Levitsky
@ 2010-07-16 23:23 ` Tantilov, Emil S
2010-07-17 13:54 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Tantilov, Emil S @ 2010-07-16 23:23 UTC (permalink / raw)
To: Maxim Levitsky
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
Maxim Levitsky wrote:
> On Thu, 2010-07-15 at 22:09 +0300, Maxim Levitsky wrote:
>> On Thu, 2010-07-15 at 13:02 -0600, Tantilov, Emil S wrote:
>>> Maxim Levitsky wrote:
>>>> On Thu, 2010-07-15 at 02:33 +0300, Maxim Levitsky wrote:
>>>>> 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
>>>>>>>>>>> <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.
>>>>>>
>>>>>> 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.
>>>>
>>>> Yep, net-next works here.
>>>>
>>>>
>>>> I have the problem on vanilla kernel.
>>>> Last revision of it, I tested is 2.6.35-rc4 exactly
>>>> (815c4163b6c8ebf8152f42b0a5fd015cfdcedc78)
>>>>
>>>>
>>>> Maybe vanilla git master works, I test it too soon.
>>>
>>> Thanks for the information! Good to know that this issue does not
>>> exist in the latest branch.
>>>
>>> Have you by any chance tested a stable branch (2.6.34.x)?
>>
>> I only did test plain 2.6.34 (v2.6.34)
> And forgot to add, that it did work.
>
>>
>> Also I repeat that revert of e98cac447cc1cc418dff1d610a5c79c4f2bdec7f
>> (e1000e: Fix/cleanup PHY reset code for ICHx/PCHx) fixes the bug on
>> vanilla kernel.
>>
>> Also I just pulled latest vanilla git, and I according to diffstat I
>> see no changes in e1000e, so its likely that bug remains there.
>> I will test that soon.
> Tested, broken as expected.
That makes sense. Unfortunately we are still not able to reproduce even on recent pull from Linus tree.
If you want - you can look at the patches for e1000e in net-next and start applying those to your tree until the issue is resolved.
I will keep trying it here, but none of the systems we have exhibit the issue you described, so the bug could be exposed by something in your system/config.
Thanks,
Emil
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-16 23:23 ` Tantilov, Emil S
@ 2010-07-17 13:54 ` Maxim Levitsky
2010-07-26 0:25 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-17 13:54 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
On Fri, 2010-07-16 at 17:23 -0600, Tantilov, Emil S wrote:
> Maxim Levitsky wrote:
> > On Thu, 2010-07-15 at 22:09 +0300, Maxim Levitsky wrote:
> >> On Thu, 2010-07-15 at 13:02 -0600, Tantilov, Emil S wrote:
> >>> Maxim Levitsky wrote:
> >>>> On Thu, 2010-07-15 at 02:33 +0300, Maxim Levitsky wrote:
> >>>>> 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
> >>>>>>>>>>> <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.
> >>>>>>
> >>>>>> 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.
> >>>>
> >>>> Yep, net-next works here.
> >>>>
> >>>>
> >>>> I have the problem on vanilla kernel.
> >>>> Last revision of it, I tested is 2.6.35-rc4 exactly
> >>>> (815c4163b6c8ebf8152f42b0a5fd015cfdcedc78)
> >>>>
> >>>>
> >>>> Maybe vanilla git master works, I test it too soon.
> >>>
> >>> Thanks for the information! Good to know that this issue does not
> >>> exist in the latest branch.
> >>>
> >>> Have you by any chance tested a stable branch (2.6.34.x)?
> >>
> >> I only did test plain 2.6.34 (v2.6.34)
> > And forgot to add, that it did work.
> >
> >>
> >> Also I repeat that revert of e98cac447cc1cc418dff1d610a5c79c4f2bdec7f
> >> (e1000e: Fix/cleanup PHY reset code for ICHx/PCHx) fixes the bug on
> >> vanilla kernel.
> >>
> >> Also I just pulled latest vanilla git, and I according to diffstat I
> >> see no changes in e1000e, so its likely that bug remains there.
> >> I will test that soon.
> > Tested, broken as expected.
>
> That makes sense. Unfortunately we are still not able to reproduce even on recent pull from Linus tree.
>
> If you want - you can look at the patches for e1000e in net-next and start applying those to your tree until the issue is resolved.
>
That exactly what I will do soon.
Also I can narrow down the problem by reverting the commit partially.
After one week, I will have enough free time to do all the thing like
above. Now I have none.
> I will keep trying it here, but none of the systems we have exhibit the issue you described, so the bug could be exposed by something in your system/config.
I also think so. Otherwise, we would see more bug-reports.
You probably don't need to try anymore and reproduce that issue, because
of that.
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-17 13:54 ` Maxim Levitsky
@ 2010-07-26 0:25 ` Maxim Levitsky
2010-07-28 7:04 ` Maxim Levitsky
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-26 0:25 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
On Sat, 2010-07-17 at 16:54 +0300, Maxim Levitsky wrote:
> On Fri, 2010-07-16 at 17:23 -0600, Tantilov, Emil S wrote:
> > Maxim Levitsky wrote:
> > > On Thu, 2010-07-15 at 22:09 +0300, Maxim Levitsky wrote:
> > >> On Thu, 2010-07-15 at 13:02 -0600, Tantilov, Emil S wrote:
> > >>> Maxim Levitsky wrote:
> > >>>> On Thu, 2010-07-15 at 02:33 +0300, Maxim Levitsky wrote:
> > >>>>> 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
> > >>>>>>>>>>> <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.
> > >>>>>>
> > >>>>>> 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.
> > >>>>
> > >>>> Yep, net-next works here.
> > >>>>
> > >>>>
> > >>>> I have the problem on vanilla kernel.
> > >>>> Last revision of it, I tested is 2.6.35-rc4 exactly
> > >>>> (815c4163b6c8ebf8152f42b0a5fd015cfdcedc78)
> > >>>>
> > >>>>
> > >>>> Maybe vanilla git master works, I test it too soon.
> > >>>
> > >>> Thanks for the information! Good to know that this issue does not
> > >>> exist in the latest branch.
> > >>>
> > >>> Have you by any chance tested a stable branch (2.6.34.x)?
> > >>
> > >> I only did test plain 2.6.34 (v2.6.34)
> > > And forgot to add, that it did work.
> > >
> > >>
> > >> Also I repeat that revert of e98cac447cc1cc418dff1d610a5c79c4f2bdec7f
> > >> (e1000e: Fix/cleanup PHY reset code for ICHx/PCHx) fixes the bug on
> > >> vanilla kernel.
> > >>
> > >> Also I just pulled latest vanilla git, and I according to diffstat I
> > >> see no changes in e1000e, so its likely that bug remains there.
> > >> I will test that soon.
> > > Tested, broken as expected.
> >
> > That makes sense. Unfortunately we are still not able to reproduce even on recent pull from Linus tree.
> >
> > If you want - you can look at the patches for e1000e in net-next and start applying those to your tree until the issue is resolved.
> >
> That exactly what I will do soon.
>
>
> Also I can narrow down the problem by reverting the commit partially.
>
> After one week, I will have enough free time to do all the thing like
> above. Now I have none.
>
>
> > I will keep trying it here, but none of the systems we have exhibit the issue you described, so the bug could be exposed by something in your system/config.
> I also think so. Otherwise, we would see more bug-reports.
>
> You probably don't need to try anymore and reproduce that issue, because
> of that.
>
This commit, present in net-next, solves the problem:
commit 1286950690f0f82ffa504e1e149ee3fdb4c51478
Author: Bruce Allan <bruce.w.allan@intel.com>
Date: Mon Jul 26 03:19:38 2010 +0300
e1000e: cleanup e1000_sw_lcd_config_ich8lan()
Do not acquire and release the PHY unnecessarily for parts that return
from this workaround without actually accessing the PHY registers.
Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Also, the above patch is part of whole series of patches with scary descriptions (that is these fix bugs).
If I were you I would send them to Linus for 2.6.35 inclusion too.
Best regards,
Maxim Levitsky
^ permalink raw reply [flat|nested] 29+ messages in thread
* RE: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-26 0:25 ` Maxim Levitsky
@ 2010-07-28 7:04 ` Maxim Levitsky
2010-07-29 1:10 ` Jeff Kirsher
0 siblings, 1 reply; 29+ messages in thread
From: Maxim Levitsky @ 2010-07-28 7:04 UTC (permalink / raw)
To: Tantilov, Emil S
Cc: Kirsher, Jeffrey T, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
On Mon, 2010-07-26 at 03:25 +0300, Maxim Levitsky wrote:
> On Sat, 2010-07-17 at 16:54 +0300, Maxim Levitsky wrote:
> > On Fri, 2010-07-16 at 17:23 -0600, Tantilov, Emil S wrote:
> > > Maxim Levitsky wrote:
> > > > On Thu, 2010-07-15 at 22:09 +0300, Maxim Levitsky wrote:
> > > >> On Thu, 2010-07-15 at 13:02 -0600, Tantilov, Emil S wrote:
> > > >>> Maxim Levitsky wrote:
> > > >>>> On Thu, 2010-07-15 at 02:33 +0300, Maxim Levitsky wrote:
> > > >>>>> 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
> > > >>>>>>>>>>> <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.
> > > >>>>>>
> > > >>>>>> 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.
> > > >>>>
> > > >>>> Yep, net-next works here.
> > > >>>>
> > > >>>>
> > > >>>> I have the problem on vanilla kernel.
> > > >>>> Last revision of it, I tested is 2.6.35-rc4 exactly
> > > >>>> (815c4163b6c8ebf8152f42b0a5fd015cfdcedc78)
> > > >>>>
> > > >>>>
> > > >>>> Maybe vanilla git master works, I test it too soon.
> > > >>>
> > > >>> Thanks for the information! Good to know that this issue does not
> > > >>> exist in the latest branch.
> > > >>>
> > > >>> Have you by any chance tested a stable branch (2.6.34.x)?
> > > >>
> > > >> I only did test plain 2.6.34 (v2.6.34)
> > > > And forgot to add, that it did work.
> > > >
> > > >>
> > > >> Also I repeat that revert of e98cac447cc1cc418dff1d610a5c79c4f2bdec7f
> > > >> (e1000e: Fix/cleanup PHY reset code for ICHx/PCHx) fixes the bug on
> > > >> vanilla kernel.
> > > >>
> > > >> Also I just pulled latest vanilla git, and I according to diffstat I
> > > >> see no changes in e1000e, so its likely that bug remains there.
> > > >> I will test that soon.
> > > > Tested, broken as expected.
> > >
> > > That makes sense. Unfortunately we are still not able to reproduce even on recent pull from Linus tree.
> > >
> > > If you want - you can look at the patches for e1000e in net-next and start applying those to your tree until the issue is resolved.
> > >
> > That exactly what I will do soon.
> >
> >
> > Also I can narrow down the problem by reverting the commit partially.
> >
> > After one week, I will have enough free time to do all the thing like
> > above. Now I have none.
> >
> >
> > > I will keep trying it here, but none of the systems we have exhibit the issue you described, so the bug could be exposed by something in your system/config.
> > I also think so. Otherwise, we would see more bug-reports.
> >
> > You probably don't need to try anymore and reproduce that issue, because
> > of that.
> >
>
>
> This commit, present in net-next, solves the problem:
>
> commit 1286950690f0f82ffa504e1e149ee3fdb4c51478
> Author: Bruce Allan <bruce.w.allan@intel.com>
> Date: Mon Jul 26 03:19:38 2010 +0300
>
> e1000e: cleanup e1000_sw_lcd_config_ich8lan()
>
> Do not acquire and release the PHY unnecessarily for parts that return
> from this workaround without actually accessing the PHY registers.
>
> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
> Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
>
>
>
> Also, the above patch is part of whole series of patches with scary descriptions (that is these fix bugs).
> If I were you I would send them to Linus for 2.6.35 inclusion too.
>
> Best regards,
> Maxim Levitsky
>
>
>
ping
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-28 7:04 ` Maxim Levitsky
@ 2010-07-29 1:10 ` Jeff Kirsher
2010-08-01 2:08 ` Jeff Kirsher
0 siblings, 1 reply; 29+ messages in thread
From: Jeff Kirsher @ 2010-07-29 1:10 UTC (permalink / raw)
To: Maxim Levitsky
Cc: Tantilov, Emil S, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
On Wed, Jul 28, 2010 at 00:04, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> On Mon, 2010-07-26 at 03:25 +0300, Maxim Levitsky wrote:
>>
>> This commit, present in net-next, solves the problem:
>>
>> commit 1286950690f0f82ffa504e1e149ee3fdb4c51478
>> Author: Bruce Allan <bruce.w.allan@intel.com>
>> Date: Mon Jul 26 03:19:38 2010 +0300
>>
>> e1000e: cleanup e1000_sw_lcd_config_ich8lan()
>>
>> Do not acquire and release the PHY unnecessarily for parts that return
>> from this workaround without actually accessing the PHY registers.
>>
>> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
>> Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>> Signed-off-by: David S. Miller <davem@davemloft.net>
>>
>>
>>
>>
>> Also, the above patch is part of whole series of patches with scary descriptions (that is these fix bugs).
>> If I were you I would send them to Linus for 2.6.35 inclusion too.
>>
>> Best regards,
>> Maxim Levitsky
>>
>>
>>
> ping
>
Sorry for the delayed response. I am working on the issue. Here is
the problem I am having, the patch that fixes the issue you are seeing
is fairly large and is a cleanup to the ich8 function, which as it
stands now, would not be accepted into net-2.6 tree this late into the
-rc cycle. So, what I looking at is, what specifically fixed the
issue you are seeing that resides in that patch, and come up with a
smaller (acceptable) patch that I can submit to net-2.6 now to resolve
your issue.
I have dedicated most of this evening to finding a resolution to your
issue that will be acceptable for the net-2.6 tree. As you noted,
there were several patches before this particular commit that may play
some part in the resolution as well, and that is what I will be
looking into. I greatly appreciate the hard work you have done to
help us resolve this issue, and will make sure you get credit for any
solution I put together to resolve this issue.
--
Cheers,
Jeff
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: [REGRESSION] e1000e stopped working [MANUALLY BISECTED]
2010-07-29 1:10 ` Jeff Kirsher
@ 2010-08-01 2:08 ` Jeff Kirsher
0 siblings, 0 replies; 29+ messages in thread
From: Jeff Kirsher @ 2010-08-01 2:08 UTC (permalink / raw)
To: Maxim Levitsky
Cc: Tantilov, Emil S, netdev@vger.kernel.org, Allan, Bruce W,
Pieper, Jeffrey E
On Wed, Jul 28, 2010 at 18:10, Jeff Kirsher <jeffrey.t.kirsher@intel.com> wrote:
> On Wed, Jul 28, 2010 at 00:04, Maxim Levitsky <maximlevitsky@gmail.com> wrote:
>> On Mon, 2010-07-26 at 03:25 +0300, Maxim Levitsky wrote:
>>>
>>> This commit, present in net-next, solves the problem:
>>>
>>> commit 1286950690f0f82ffa504e1e149ee3fdb4c51478
>>> Author: Bruce Allan <bruce.w.allan@intel.com>
>>> Date: Mon Jul 26 03:19:38 2010 +0300
>>>
>>> e1000e: cleanup e1000_sw_lcd_config_ich8lan()
>>>
>>> Do not acquire and release the PHY unnecessarily for parts that return
>>> from this workaround without actually accessing the PHY registers.
>>>
>>> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
>>> Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
>>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>>> Signed-off-by: David S. Miller <davem@davemloft.net>
>>>
>>>
>>>
>>>
>>> Also, the above patch is part of whole series of patches with scary descriptions (that is these fix bugs).
>>> If I were you I would send them to Linus for 2.6.35 inclusion too.
>>>
>>> Best regards,
>>> Maxim Levitsky
>>>
>>>
>>>
>> ping
>>
>
> Sorry for the delayed response. I am working on the issue. Here is
> the problem I am having, the patch that fixes the issue you are seeing
> is fairly large and is a cleanup to the ich8 function, which as it
> stands now, would not be accepted into net-2.6 tree this late into the
> -rc cycle. So, what I looking at is, what specifically fixed the
> issue you are seeing that resides in that patch, and come up with a
> smaller (acceptable) patch that I can submit to net-2.6 now to resolve
> your issue.
>
> I have dedicated most of this evening to finding a resolution to your
> issue that will be acceptable for the net-2.6 tree. As you noted,
> there were several patches before this particular commit that may play
> some part in the resolution as well, and that is what I will be
> looking into. I greatly appreciate the hard work you have done to
> help us resolve this issue, and will make sure you get credit for any
> solution I put together to resolve this issue.
>
> --
> Cheers,
> Jeff
>
To keep everyone informed...
We have found the root cause for this issue with the help of Maxim,
and will have a patch to fix the issue in the next couple of days.
--
Cheers,
Jeff
^ permalink raw reply [flat|nested] 29+ messages in thread
end of thread, other threads:[~2010-08-01 2:08 UTC | newest]
Thread overview: 29+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-27 17:27 [REGRESSION] e1000e stopped working Maxim Levitsky
2010-06-27 17:29 ` Maxim Levitsky
2010-06-27 17:43 ` Maxim Levitsky
2010-06-27 17:47 ` Maxim Levitsky
2010-06-28 17:04 ` Allan, Bruce W
2010-06-28 17:14 ` Maxim Levitsky
2010-06-29 1:09 ` Allan, Bruce W
2010-06-29 10:32 ` Maxim Levitsky
2010-06-29 18:37 ` Tantilov, Emil S
2010-06-30 22:59 ` Maxim Levitsky
2010-07-04 0:41 ` Maxim Levitsky
2010-07-04 22:48 ` [REGRESSION] e1000e stopped working [MANUALLY BISECTED] Maxim Levitsky
2010-07-05 8:13 ` Jeff Kirsher
2010-07-05 9:58 ` Maxim Levitsky
2010-07-12 15:56 ` Maxim Levitsky
2010-07-12 21:23 ` Tantilov, Emil S
2010-07-13 0:38 ` Maxim Levitsky
2010-07-14 22:56 ` Tantilov, Emil S
2010-07-14 23:33 ` Maxim Levitsky
2010-07-15 18:57 ` Maxim Levitsky
2010-07-15 19:02 ` Tantilov, Emil S
2010-07-15 19:09 ` Maxim Levitsky
2010-07-16 19:25 ` Maxim Levitsky
2010-07-16 23:23 ` Tantilov, Emil S
2010-07-17 13:54 ` Maxim Levitsky
2010-07-26 0:25 ` Maxim Levitsky
2010-07-28 7:04 ` Maxim Levitsky
2010-07-29 1:10 ` Jeff Kirsher
2010-08-01 2:08 ` Jeff Kirsher
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).