From: Bernd Schubert <bernd-schubert@gmx.de>
To: netdev@vger.kernel.org
Subject: tg3: tg3_stop_block timed out
Date: Tue, 08 Aug 2006 00:43:38 +0200 [thread overview]
Message-ID: <eb8fmt$6lf$1@sea.gmane.org> (raw)
Hi,
I have seen a few reports like this, but now broadcom seems to actively
support tg3, so I decided to send this.
... [many hamilton not responding messages]
4554928.798000] nfs: server hamilton not responding, still trying
[4554935.319000] nfs: server hamilton not responding, still trying
[4555468.940000] NETDEV WATCHDOG: eth1: transmit timed out
[4555468.940000] tg3: eth1: transmit timed out, resetting
[4555469.044000] tg3: tg3_stop_block timed out, ofs=3400 enable_bit=2
[4555469.147000] tg3: tg3_stop_block timed out, ofs=2400 enable_bit=2
[4555469.251000] tg3: tg3_stop_block timed out, ofs=1400 enable_bit=2
[4555469.354000] tg3: tg3_stop_block timed out, ofs=c00 enable_bit=2
[4555469.433000] tg3: eth1: Link is down.
[4555472.593000] tg3: eth1: Link is up at 1000 Mbps, full duplex.
[4555472.594000] tg3: eth1: Flow control is on for TX and on for RX.
[4555498.016000] nfs: server 129.206.21.200 OK
[4555648.015000] nfs: server 129.206.21.200 OK
... [many ok messages]
It seems to be the first time that something like this happend, at least I
don't find anything in the previous logs.
This is with 2.6.16, would it be worth to try a more recent tg3 driver (e.g.
from broadcom (3.58) or backported from 2.6.17 (3.59))?
Thanks,
Bernd
next reply other threads:[~2006-08-07 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 22:43 Bernd Schubert [this message]
2006-08-07 23:07 ` tg3: tg3_stop_block timed out Michael Chan
2006-08-07 23:24 ` Bernd Schubert
2006-08-07 23:46 ` Michael Chan
2006-08-09 14:44 ` Philip Molter
2006-09-03 22:35 ` Philip Molter
2006-09-04 18:25 ` Michael Chan
2006-09-04 21:27 ` Philip Molter
2006-09-12 17:22 ` Philip Molter
2006-08-09 15:20 ` Bernd Schubert
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='eb8fmt$6lf$1@sea.gmane.org' \
--to=bernd-schubert@gmx.de \
--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).