[BUG REPORT, 2.6.22] e1000: detected tx unit hang

[BUG REPORT, 2.6.22] e1000: detected tx unit hang

[speedy]

Hello Linux crew,

        I've just switched the

        Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet Controller (rev 01)

        netword card to an NForce 2 based motherboard and after a day
        of work it got stuck with "detected tx unit hang" messages
        showing in the console.

        The card worked flawlessly under load in a different computer
        for two years now, under the same/similar Ubuntu operating system.

        Unfortunaltly, the EEPROM fix from

        http://e1000.sourceforge.net/doku.php?id=known_issues&DokuWiki=9502f399bc8cae1528c5e85d2bc423f6

        from is not working/applicable:

        root@backupserver:~# ./fixeep-82573-dspd.sh eth1
        No appropriate hardware found for this fixup
        root@backupserver:~#

        /var/log/messages:  http://87.230.23.147/messages.txt
        /proc/interrupts: http://87.230.23.147/proc_interrupts.txt
        lspci -vv: http://87.230.23.147/lspcivv.txt


        If more info is needed, let me know.

        Thanks!

        ps. I don't follow the lists so please keep me in CC:

-- 
Best regards,
 speedy                          mailto:speedy@3d-io.com

Re: [BUG REPORT, 2.6.22] e1000: detected tx unit hang

[Kok, Auke]

[dropped lkml from the Cc]

speedy wrote:
> Hello Linux crew,
> 
>         I've just switched the
> 
>         Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet Controller (rev 01)
> 
>         netword card to an NForce 2 based motherboard and after a day
>         of work it got stuck with "detected tx unit hang" messages
>         showing in the console.
> 
>         The card worked flawlessly under load in a different computer
>         for two years now, under the same/similar Ubuntu operating system.
> 
>         Unfortunaltly, the EEPROM fix from
> 
>         http://e1000.sourceforge.net/doku.php?id=known_issues&DokuWiki=9502f399bc8cae1528c5e85d2bc423f6
> 
>         from is not working/applicable:
> 
>         root@backupserver:~# ./fixeep-82573-dspd.sh eth1
>         No appropriate hardware found for this fixup

correct, that fix is only for very specific adapters which are based on a totally
different chipset than the one you have.

>         root@backupserver:~#
> 
>         /var/log/messages:  http://87.230.23.147/messages.txt
>         /proc/interrupts: http://87.230.23.147/proc_interrupts.txt
>         lspci -vv: http://87.230.23.147/lspcivv.txt
> 
> 
>         If more info is needed, let me know.


basically it's inserted into a new motherboard?

what was the old motherboard?

can you check the BIOS and disable things like "PCI Write combining" or
"Writeback" or any option looking similar to that?

It appears you hit an issue that is exposed by these adapters on some AMD/NVIDIA
chipset-based motherboards. This issue is known and we are investigating this and
have been for a long time. The root cause is still yet unknown however.

For some people disabling TSO helps to relieve the situation. You could give that
a try.

Cheers,

Auke

Re[2]: [BUG REPORT, 2.6.22] e1000: detected tx unit hang

[speedy]

Hello Auke,

Monday, April 21, 2008, 11:44:59 PM, you wrote:

KA> [dropped lkml from the Cc]

KA> speedy wrote:
>> Hello Linux crew,
>> 
>>         I've just switched the
>> 
>>         Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet Controller (rev 01)
>> 
>>         netword card to an NForce 2 based motherboard and after a day
>>         of work it got stuck with "detected tx unit hang" messages
>>         showing in the console.
>> 
>>         The card worked flawlessly under load in a different computer
>>         for two years now, under the same/similar Ubuntu operating system.
>> 
>>         /var/log/messages:  http://87.230.23.147/messages.txt
>>         /proc/interrupts: http://87.230.23.147/proc_interrupts.txt
>>         lspci -vv: http://87.230.23.147/lspcivv.txt
>> 
>> 
>>         If more info is needed, let me know.


KA> basically it's inserted into a new motherboard?

Yup.

I've changed the PCI slot in which the card is inserted (just out of
hunch) and rebooted the server. I'll let you know if the problem
happens again.

KA> what was the old motherboard?

QDI Legend KinetiZ 7B

http://www.qdigrp.com/qdisite/eng/products/K7B.htm

(had uptimes of 200+ days :)

KA> can you check the BIOS and disable things like "PCI Write combining" or
KA> "Writeback" or any option looking similar to that?

I'm curious to see how often does the problem happen. I'll try such
measures if it reproduces itself.

KA> It appears you hit an issue that is exposed by these adapters on some AMD/NVIDIA
KA> chipset-based motherboards. This issue is known and we are investigating this and
KA> have been for a long time. The root cause is still yet unknown however.

Does it also happen with newer AMD/NVIDIA motherboards? :(

KA> For some people disabling TSO helps to relieve the situation. You could give that
KA> a try.

TSO? What is that and how to disable it? :)

KA> Cheers,

KA> Auke

Thanks!


-- 
Best regards,
 speedy                            mailto:speedy@3d-io.com

Re: [BUG REPORT, 2.6.22] e1000: detected tx unit hang

[Kok, Auke]

speedy wrote:
> Hello Auke,
> 
> Monday, April 21, 2008, 11:44:59 PM, you wrote:
> 
> KA> [dropped lkml from the Cc]
> 
> KA> speedy wrote:
>>> Hello Linux crew,
>>>
>>>         I've just switched the
>>>
>>>         Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet Controller (rev 01)
>>>
>>>         netword card to an NForce 2 based motherboard and after a day
>>>         of work it got stuck with "detected tx unit hang" messages
>>>         showing in the console.
>>>
>>>         The card worked flawlessly under load in a different computer
>>>         for two years now, under the same/similar Ubuntu operating system.
>>>
>>>         /var/log/messages:  http://87.230.23.147/messages.txt
>>>         /proc/interrupts: http://87.230.23.147/proc_interrupts.txt
>>>         lspci -vv: http://87.230.23.147/lspcivv.txt
>>>
>>>
>>>         If more info is needed, let me know.
> 
> 
> KA> basically it's inserted into a new motherboard?
> 
> Yup.
> 
> I've changed the PCI slot in which the card is inserted (just out of
> hunch) and rebooted the server. I'll let you know if the problem
> happens again.
> 
> KA> what was the old motherboard?
> 
> QDI Legend KinetiZ 7B
> 
> http://www.qdigrp.com/qdisite/eng/products/K7B.htm
> 
> (had uptimes of 200+ days :)
> 
> KA> can you check the BIOS and disable things like "PCI Write combining" or
> KA> "Writeback" or any option looking similar to that?
> 
> I'm curious to see how often does the problem happen. I'll try such
> measures if it reproduces itself.
> 
> KA> It appears you hit an issue that is exposed by these adapters on some AMD/NVIDIA
> KA> chipset-based motherboards. This issue is known and we are investigating this and
> KA> have been for a long time. The root cause is still yet unknown however.
> 
> Does it also happen with newer AMD/NVIDIA motherboards? :(

yes, that's what the reports are.

it appears to be related to a bridge chip which is common on both older and newer
motherboards.

> KA> For some people disabling TSO helps to relieve the situation. You could give that
> KA> a try.
> 
> TSO? What is that and how to disable it? :)

TCP Segmentation offload - the hardware will split up the payload into MTU-size
fragments itself instead of doing it in the kernel.

ethtool -K ethX tso off


Auke