From: David Sommerseth <gentoo.list@topphemmelig.net>
To: gentoo-hardened@lists.gentoo.org
Subject: [gentoo-hardened] tg3 driver - transmit timed out, resetting
Date: Fri, 28 Nov 2008 14:28:15 +0100 [thread overview]
Message-ID: <492FF1EF.7020003@topphemmelig.net> (raw)
Hello Folks!
Maybe some of you have seen this before, or know something ... I have a
Broadcom NetXtreme card which have locked up twice within 13 days. I
upgraded to the 2.6.25-hardened-r8 kernel mid-october, and have a feeling
this upgrade introduced this issue. Before that I was
linux-2.6.22-hardened-r8 for over a year without any problems. The log
entries from both episodes are identical.
Any hints? Are there any safe 2.6.26 or 2.6.27 kernels available?
kind regards,
David Sommerseth
----------------------------------------------------------------------------
06:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit
Ethernet PCI Express (rev 21)
Subsystem: IBM eServer xSeries server mainboard
Flags: bus master, fast devsel, latency 0, IRQ 219
Memory at d8200000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data <?>
Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+
Queue=0/3 Enable+
Capabilities: [d0] Express Endpoint, MSI 00
Kernel driver in use: tg3
----------------------------------------------------------------------------
tg3.c:v3.91 (April 18, 2008)
----------------------------------------------------------------------------
Nov 28 12:47:34 linuxbox [51195.788361] NETDEV WATCHDOG: eth0: transmit
timed out
Nov 28 12:47:34 linuxbox [51195.788424] tg3: eth0: transmit timed out,
resetting
Nov 28 12:47:34 linuxbox [51195.788464] tg3: DEBUG: MAC_TX_STATUS[ffffffff]
MAC_RX_STATUS[ffffffff]
Nov 28 12:47:34 linuxbox [51195.788500] tg3: DEBUG: RDMAC_STATUS[ffffffff]
WDMAC_STATUS[ffffffff]
Nov 28 12:47:34 linuxbox [51195.899576] tg3: tg3_stop_block timed out,
ofs=2c00 enable_bit=2
Nov 28 12:47:34 linuxbox [51196.004849] tg3: tg3_stop_block timed out,
ofs=2000 enable_bit=2
Nov 28 12:47:34 linuxbox [51196.110115] tg3: tg3_stop_block timed out,
ofs=2400 enable_bit=2
Nov 28 12:47:34 linuxbox [51196.215378] tg3: tg3_stop_block timed out,
ofs=2800 enable_bit=2
Nov 28 12:47:34 linuxbox [51196.320655] tg3: tg3_stop_block timed out,
ofs=3000 enable_bit=2
Nov 28 12:47:34 linuxbox [51196.425925] tg3: tg3_stop_block timed out,
ofs=1400 enable_bit=2
Nov 28 12:47:34 linuxbox [51196.531191] tg3: tg3_stop_block timed out,
ofs=1800 enable_bit=2
Nov 28 12:47:35 linuxbox [51196.636469] tg3: tg3_stop_block timed out,
ofs=c00 enable_bit=2
Nov 28 12:47:35 linuxbox [51196.741735] tg3: tg3_stop_block timed out,
ofs=4800 enable_bit=2
Nov 28 12:47:35 linuxbox [51196.847001] tg3: tg3_stop_block timed out,
ofs=1000 enable_bit=2
Nov 28 12:47:35 linuxbox [51196.952267] tg3: tg3_stop_block timed out,
ofs=1c00 enable_bit=2
Nov 28 12:47:35 linuxbox [51197.057655] tg3: tg3_abort_hw timed out for
eth0, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff
Nov 28 12:47:35 linuxbox [51197.162912] tg3: tg3_stop_block timed out,
ofs=3c00 enable_bit=2
Nov 28 12:47:35 linuxbox [51197.268179] tg3: tg3_stop_block timed out,
ofs=4c00 enable_bit=2
Nov 28 12:47:38 linuxbox [51199.841388] tg3: eth0: No firmware running.
Nov 28 12:47:39 linuxbox [51201.105071] tg3: tg3_abort_hw timed out for
eth0, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff
Nov 28 12:47:59 linuxbox [51221.133560] tg3: eth0: Link is down.
Nov 28 13:09:03 linuxbox [51330.696020] tg3: tg3_abort_hw timed out for
eth0, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff
------------------------------------------------------------------------
next reply other threads:[~2008-11-28 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 13:28 David Sommerseth [this message]
2008-11-28 14:02 ` [gentoo-hardened] tg3 driver - transmit timed out, resetting atoth
2008-11-28 15:56 ` David Sommerseth
2008-12-12 18:09 ` David Sommerseth
2008-12-12 19:21 ` atoth
2009-02-25 14:02 ` David Sommerseth
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=492FF1EF.7020003@topphemmelig.net \
--to=gentoo.list@topphemmelig.net \
--cc=gentoo-hardened@lists.gentoo.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