Bug 16383 - Regression with e1000e from 2.6.34.1 to 2.6.35-rc5
Summary: Regression with e1000e from 2.6.34.1 to 2.6.35-rc5
Status: CLOSED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: All Linux
: P1 high
Assignee: drivers_network@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks: 16055
  Show dependency tree
 
Reported: 2010-07-14 00:44 UTC by Stefan Behte
Modified: 2010-08-02 21:40 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.35-rc5
Tree: Mainline
Regression: Yes


Attachments
.config (62.70 KB, application/octet-stream)
2010-07-14 00:44 UTC, Stefan Behte
Details
dmidecode output (15.71 KB, application/octet-stream)
2010-07-14 00:45 UTC, Stefan Behte
Details
lspci -vvv output for e1000e (2.98 KB, application/octet-stream)
2010-07-14 00:45 UTC, Stefan Behte
Details
ethtool -e (14.28 KB, application/octet-stream)
2010-07-22 15:40 UTC, Stefan Behte
Details
ethtool -S (1.19 KB, application/octet-stream)
2010-07-22 16:24 UTC, Stefan Behte
Details

Description Stefan Behte 2010-07-14 00:44:48 UTC
Created attachment 27094 [details]
.config

Networking stops working with 2.6.35 (tested rc-3 and rc5).

# egrep "(e1000|eth)" dmesg-2.6.34.1
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
e1000e 0000:00:19.0: setting latency timer to 64
0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 5c:ff:35:02:2d:a9
0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: a002ff-0ff
e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

# egrep "(e1000|eth)" dmesg-2.6.35-rc5
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k4
e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
e1000e 0000:00:19.0: setting latency timer to 64
e1000e 0000:00:19.0: (unregistered net_device): Failed to initialize MSI interrupts.  Falling back to legacy interrupts.
e1000e 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 5c:ff:35:02:2d:a9
e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
e1000e 0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: a002ff-0ff
e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

I hadn't set CONFIG_PCI_MSI but enabling it on 2.6.35-rc5 made no difference.
Comment 1 Stefan Behte 2010-07-14 00:45:14 UTC
Created attachment 27095 [details]
dmidecode output
Comment 2 Stefan Behte 2010-07-14 00:45:39 UTC
Created attachment 27096 [details]
lspci -vvv output for e1000e
Comment 3 Stefan Behte 2010-07-14 00:49:14 UTC
Two additonal bits of informatio:
- I can send packets, but never get answers (obviously, as it's unregistered)
- Hardware: Lenovo ThinkPad X201, model 3626W16 (i5)
Comment 4 Andrew Morton 2010-07-21 20:49:23 UTC
(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Wed, 14 Jul 2010 00:44:51 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=16383
> 
>            Summary: Regression with e1000e from 2.6.34.1 to 2.6.35-rc5
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.35
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: Network
>         AssignedTo: drivers_network@kernel-bugs.osdl.org
>         ReportedBy: craig@haquarter.de
>         Regression: Yes
> 
> 
> Created an attachment (id=27094)
>  --> (https://bugzilla.kernel.org/attachment.cgi?id=27094)
> .config
> 
> Networking stops working with 2.6.35 (tested rc-3 and rc5).

This is a post-2.6.34 regression, guys.  There's some more info in bugzilla.

> # egrep "(e1000|eth)" dmesg-2.6.34.1
> e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
> e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
> e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> e1000e 0000:00:19.0: setting latency timer to 64
> 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 5c:ff:35:02:2d:a9
> 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
> 0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: a002ff-0ff
> e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
> 
> # egrep "(e1000|eth)" dmesg-2.6.35-rc5
> e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k4
> e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
> e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> e1000e 0000:00:19.0: setting latency timer to 64
> e1000e 0000:00:19.0: (unregistered net_device): Failed to initialize MSI
> interrupts.  Falling back to legacy interrupts.
> e1000e 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 5c:ff:35:02:2d:a9
> e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
> e1000e 0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: a002ff-0ff
> e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
> 
> I hadn't set CONFIG_PCI_MSI but enabling it on 2.6.35-rc5 made no difference.
>
Comment 5 emil.s.tantilov 2010-07-21 22:58:54 UTC
>-----Original Message-----
>From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org] On
>Behalf Of Andrew Morton
>Sent: Wednesday, July 21, 2010 1:49 PM
>To: Kirsher, Jeffrey T; Brandeburg, Jesse; Allan, Bruce W; Duyck, Alexander
>H; Waskiewicz Jr, Peter P
>Cc: bugzilla-daemon@bugzilla.kernel.org; bugme-daemon@bugzilla.kernel.org;
>netdev@vger.kernel.org; craig@haquarter.de
>Subject: Re: [Bugme-new] [Bug 16383] New: Regression with e1000e from
>2.6.34.1 to 2.6.35-rc5
>
>
>(switched to email.  Please respond via emailed reply-to-all, not via the
>bugzilla web interface).
>
>On Wed, 14 Jul 2010 00:44:51 GMT
>bugzilla-daemon@bugzilla.kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=16383
>>
>>            Summary: Regression with e1000e from 2.6.34.1 to 2.6.35-rc5
>>            Product: Drivers
>>            Version: 2.5
>>     Kernel Version: 2.6.35
>>           Platform: All
>>         OS/Version: Linux
>>               Tree: Mainline
>>             Status: NEW
>>           Severity: high
>>           Priority: P1
>>          Component: Network
>>         AssignedTo: drivers_network@kernel-bugs.osdl.org
>>         ReportedBy: craig@haquarter.de
>>         Regression: Yes
>>
>>
>> Created an attachment (id=27094)
>>  --> (https://bugzilla.kernel.org/attachment.cgi?id=27094)
>> .config
>>
>> Networking stops working with 2.6.35 (tested rc-3 and rc5).
>
>This is a post-2.6.34 regression, guys.  There's some more info in
>bugzilla.
>
>> # egrep "(e1000|eth)" dmesg-2.6.34.1
>> e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
>> e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
>> e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
>> e1000e 0000:00:19.0: setting latency timer to 64
>> 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 5c:ff:35:02:2d:a9
>> 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
>> 0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: a002ff-0ff
>> e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
>>
>> # egrep "(e1000|eth)" dmesg-2.6.35-rc5
>> e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k4
>> e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
>> e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
>> e1000e 0000:00:19.0: setting latency timer to 64
>> e1000e 0000:00:19.0: (unregistered net_device): Failed to initialize MSI
>> interrupts.  Falling back to legacy interrupts.
>> e1000e 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1)
>5c:ff:35:02:2d:a9
>> e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
>> e1000e 0000:00:19.0: eth0: MAC: 9, PHY: 10, PBA No: a002ff-0ff
>> e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
>>
>> I hadn't set CONFIG_PCI_MSI but enabling it on 2.6.35-rc5 made no
>difference.

On what HW is this issue seen? Please provide the output of:
lspci -vvv
ethtool -e 
ethtool -S

kernel config.

Thanks,
Emil
Comment 6 Stefan Behte 2010-07-22 00:52:37 UTC
Hi,

> On what HW is this issue seen? Please provide the output of:
Hardware (it was already on bugzilla as pointed out by Andrew): Lenovo
ThinkPad X201, model 3626W16 (i5)

> lspci -vvv
> ethtool -e 
> ethtool -S
see attached files

> kernel config.
https://bugzilla.kernel.org/attachment.cgi?id=27094

Best regards,

Stefan Behte
Comment 7 Stefan Behte 2010-07-22 15:40:42 UTC
Created attachment 27205 [details]
ethtool -e
Comment 8 Stefan Behte 2010-07-22 16:24:06 UTC
Created attachment 27206 [details]
ethtool -S
Comment 9 Stefan Behte 2010-08-02 21:25:39 UTC
>>> https://bugzilla.kernel.org/show_bug.cgi?id=16383

>>>
>>>            Summary: Regression with e1000e from 2.6.34.1 to 2.6.35-rc5
>>>            Product: Drivers
>>>            Version: 2.5
>>>     Kernel Version: 2.6.35
>>>           Platform: All
>>>         OS/Version: Linux
>>>               Tree: Mainline
>>>             Status: NEW
>>>           Severity: high
>>>           Priority: P1
>>>          Component: Network
>>>         AssignedTo: drivers_network@kernel-bugs.osdl.org
>>>         ReportedBy: craig@haquarter.de
>>>         Regression: Yes
>>>
>>>
>>> Networking stops working with 2.6.35 (tested rc-3 and rc5).
>>
>> This is a post-2.6.34 regression, guys.  There's some more info in
>> bugzilla.

The e1000e works like a charm with 2.6.35, thanks everyone.

Best regards,

Craig

Note You need to log in before you can comment on or make changes to this bug.