From: Frans Pop <elendil@planet.nl>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [REGRESSION] 2.6.24-rc7: e1000: Detected Tx Unit Hang
Date: Tue, 15 Jan 2008 06:25:10 +0100 [thread overview]
Message-ID: <200801150625.10823.elendil@planet.nl> (raw)
After compiling v2.6.24-rc7-163-g1a1b285 (x86_64) yesterday I suddenly see this error
repeatedly:
kernel: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
kernel: Tx Queue <0>
kernel: TDH <a>
kernel: TDT <a>
kernel: next_to_use <a>
kernel: next_to_clean <ff>
kernel: buffer_info[next_to_clean]
kernel: time_stamp <10002738a>
kernel: next_to_watch <ff>
kernel: jiffies <1000275b4>
kernel: next_to_watch.status <1>
My previous kernel was v2.6.24-rc7 and with that this error did not occur. I
have also never seen it with earlier kernels.
The values for "TX Queue" and "next_to_watch.status" are constant, the
others vary.
My NIC is:
01:00.0 Ethernet controller [0200]: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03)
01:00.0 0200: 8086:108c (rev 03)
Subsystem: 8086:3096
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 1273
Region 0: Memory at 90200000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at 90100000 (32-bit, non-prefetchable) [size=1M]
Region 2: I/O ports at 1000 [size=32]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0300c Data: 41a9
Capabilities: [e0] Express Endpoint IRQ 0
Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <512ns, L1 <64us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM unknown, Port 0
Link: Latency L0s <128ns, L1 <64us
Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
The system is an Intel D945GCZ main board with
Intel(R) Pentium(R) D CPU 3.20GHz (dual core) processor.
Cheers,
FJP
next reply other threads:[~2008-01-15 5:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 5:25 Frans Pop [this message]
2008-01-15 5:53 ` [REGRESSION] 2.6.24-rc7: e1000: Detected Tx Unit Hang David Miller
2008-01-15 6:17 ` Frans Pop
2008-01-15 14:04 ` Frans Pop
2008-01-15 16:04 ` slavon
2008-01-15 21:53 ` Brandeburg, Jesse
2008-01-16 5:02 ` David Miller
2008-01-16 8:56 ` Frans Pop
2008-01-16 10:29 ` David Miller
2008-01-16 17:07 ` Robert Olsson
2008-01-18 12:11 ` David Miller
2008-01-18 13:00 ` Robert Olsson
2008-01-18 13:37 ` David Miller
2008-01-20 9:20 ` Brandeburg, Jesse
2008-01-20 9:28 ` Andrey Rahmatullin
2008-01-21 13:27 ` Robert Olsson
2008-01-21 13:29 ` David Miller
2008-01-17 7:09 ` Brandeburg, Jesse
2008-01-17 7:20 ` David Miller
2008-01-17 7:51 ` Frans Pop
2008-01-17 8:00 ` David Miller
2008-01-17 9:40 ` Arnaldo Carvalho de Melo
2008-01-17 9:45 ` David Miller
2008-01-16 9:02 ` Badalian Vyacheslav
2008-01-16 12:25 ` David Miller
2008-01-16 12:28 ` David Miller
2008-01-21 6:54 ` Badalian Vyacheslav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801150625.10823.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).