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] [thread-next>] [day] [month] [year] [list]

Message-ID: <480D0ADB.9000308@intel.com>
Date:	Mon, 21 Apr 2008 14:44:59 -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

[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@...kupserver:~# ./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@...kupserver:~#
> 
>         /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

--
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