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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <480D0FE7.4010609@intel.com>
Date:	Mon, 21 Apr 2008 15:06:31 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	speedy <speedy@...io.com>
CC:	netdev@...r.kernel.org
Subject: Re: [BUG REPORT, 2.6.22] e1000: detected tx unit hang

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html