Re: Kernel v3.0.8 igb driver dies when pulling network cable

[Alexander Duyck]

On 11/22/2011 01:36 AM, Stefan Priebe - Profihost AG wrote:
>> It would be useful if you could try the latest driver from e1000.sf.net
>> just to verify  if this is a bug in the upstream kernel or if it is also
>> present in our e1000.sf.net.driver.  This way we can figure out if this
>> is an issue where a patch wasn't pushed into the stable kernel or if it
>> is an issue that still exists in our latest release.
>>
>> Also could you provide us with the part number you are currently using.
>> If you could provide us with the device ID for the part via lspci we can
>> start narrowing down the root cause for the issue as currently we don't
>> have any information about what hardware you are experiencing this
>> issue on.
>
> Ok another note i missed last time. Ethernet and Server stays fully
> functional - it just prints the message and resets the adapter.
>
> OK let's start with lspci:
> a:00.0 Ethernet controller: Intel Corporation Device 10c9 (rev 01)
>         Subsystem: Super Micro Computer Inc Device 10c9
>         Flags: bus master, fast devsel, latency 0, IRQ 28
>         Memory at fbe60000 (32-bit, non-prefetchable) [size=128K]
>         Memory at fbe40000 (32-bit, non-prefetchable) [size=128K]
>         I/O ports at e880 [size=32]
>         Memory at fbe1c000 (32-bit, non-prefetchable) [size=16K]
>         Expansion ROM at fbe20000 [disabled] [size=128K]
>         Capabilities: [40] Power Management version 3
>         Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+
> Queue=0/0 Enable-
>         Capabilities: [70] MSI-X: Enable+ Mask- TabSize=10
>         Capabilities: [a0] Express Endpoint, MSI 00
>         Capabilities: [100] Advanced Error Reporting <?>
>         Capabilities: [140] Device Serial Number ce-5a-2b-ff-ff-90-25-00
>         Capabilities: [150] #0e
>         Capabilities: [160] #10
>         Kernel driver in use: igb
>
> 0a:00.1 Ethernet controller: Intel Corporation Device 10c9 (rev 01)
>         Subsystem: Super Micro Computer Inc Device 10c9
>         Flags: bus master, fast devsel, latency 0, IRQ 40
>         Memory at fbee0000 (32-bit, non-prefetchable) [size=128K]
>         Memory at fbec0000 (32-bit, non-prefetchable) [size=128K]
>         I/O ports at ec00 [size=32]
>         Memory at fbe9c000 (32-bit, non-prefetchable) [size=16K]
>         Expansion ROM at fbea0000 [disabled] [size=128K]
>         Capabilities: [40] Power Management version 3
>         Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+
> Queue=0/0 Enable-
>         Capabilities: [70] MSI-X: Enable+ Mask- TabSize=10
>         Capabilities: [a0] Express Endpoint, MSI 00
>         Capabilities: [100] Advanced Error Reporting <?>
>         Capabilities: [140] Device Serial Number ce-5a-2b-ff-ff-90-25-00
>         Capabilities: [150] #0e
>         Capabilities: [160] #10
>         Kernel driver in use: igb
>
> Using the latest stable igb driver from e1000.sf.net works fine
> without any message.
>
> Thanks,
>
> Stefan
Hi Stefan,

It seems like there might be an issue with something specific to your
board since I tried reproducing the issue here on an 82576 based adapter
and the stable 3.0.9 kernel I have and I have not had much success.

I'm assuming the device that is failing is eth0.  I was wondering if you
could send me the output of the following three commands so that I can
do some further work to try and isolate the root cause for this issue:
ethtool eth0
ethtool -e eth0
grep eth0 /proc/interrupts

The issue seems to be that your adapter is not detecting that the cable
was unplugged.  This in turn is leaving stale packets on the Tx ring and
is what is resulting in the dev_watchdog message you are seeing. 
Typically this is due to one of two possible causes.  Either the device
is not detecting that the link went down, or the interrupt for the link
down event was never delivered.  Once we can isolate which of these two
events is occurring we will be much closer to having the root cause.

Thanks,

Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/