linux-kernel - Re: Intel e1000e: eth0: 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]

Date:	Mon, 5 Jan 2009 16:38:58 -0800
From:	"Jesse Brandeburg" <jesse.brandeburg@...il.com>
To:	"Soeren Sonnenburg" <kernel@....de>
Cc:	"Linux Kernel" <linux-kernel@...r.kernel.org>,
	e1000-devel@...ts.sourceforge.net
Subject: Re: Intel e1000e: eth0: Detected Tx Unit Hang

On Thu, Jan 1, 2009 at 11:56 AM, Soeren Sonnenburg <kernel@....de> wrote:
> Dear list,
>
> I just recently observed a strange problem with an onboard 82567LF-2
> Intel ethernet controller. It completely stopped working and this
> desktop machine required a powerdown to get it to work again. This
> happened with 2.6.27.10. However, the machine was working for weeks
> before using an older kernel version (2.6.27.*, no binary modules, intel
> skyburg mainboard, e8400 c2d cpu).
>
> Relevant details follow, can someone make sense of this?

what does cat /proc/interrupts say?

please also include at least ethtool -e eth0 length 256, do you have
the IOMMU enabled?  your full dmesg would let me know.

also, please double check you're running the latest BIOS for your motherboard.

> 00:19.0 Ethernet controller: Intel Corporation 82567LF-2 Gigabit Network Connection
>
> $ dmesg | grep relevant parts
>
> Intel(R) PRO/1000 Network Driver - version 7.3.20-k3-NAPI
> e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6
> 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
> Intel(R) Gigabit Ethernet Network Driver - version 1.2.45-k2
>
> 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) XX:XX:XX:XX:XX:XX
> 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
> 0000:00:19.0: eth0: MAC: 5, PHY: 8, PBA No: ffffff-0ff
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> 0000:00:19.0: eth0: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> [...]
> [uptime of a couple of days, with lots of network i/o]
> [...]
> saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
> saa7146 (1) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer
> 0000:00:19.0: eth0: Detected Tx Unit Hang:
>  TDH                  <ff>
>  TDT                  <1>
>  next_to_use          <1>
>  next_to_clean        <ff>
> buffer_info[next_to_clean]:
>  time_stamp           <1104ec2c3>
>  next_to_watch        <ff>
>  jiffies              <1104ec8f0>
>  next_to_watch.status <0>

<snip> lots of hangs...

what is the frequency of the hangs?  What kind of traffic are you using?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/