From: Manfred Spraul <manfred@colorfullife.com>
To: ksardem@linux01.gwdg.de
Cc: linux-kernel@vger.kernel.org, urban@teststation.com
Subject: Re: bug in via-rhine network-driver (transmit timed out)
Date: Sun, 17 Nov 2002 10:37:53 +0100 [thread overview]
Message-ID: <3DD76371.4060009@colorfullife.com> (raw)
>
>
>When I do a 'dmesg' I get these error-messages:
>
>NETDEV WATCHDOG: eth0: transmit timed out
>eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
>eth0: reset did not complete in 10 ms.
>NETDEV WATCHDOG: eth0: transmit timed out
>
The tx_timeout code performs a full hardware reset to recover from
hangs, but it seems that the nic hangs during the hardware reset :-(
The hang could be caused by incomplete tx underrun handling, the
linuxfet driver resets several registers after a tx underrun.
Could you load the driver with debug=3? For example by adding 'options
via-rhine debug=3' into your /etc/modules.conf?
If it hangs again, then send the dmesg messages to the mailing list -
especially the last few lines before the first transmit timeout will help.
--
Manfred
next reply other threads:[~2002-11-17 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-17 9:37 Manfred Spraul [this message]
2002-11-20 17:13 ` bug in via-rhine network-driver (transmit timed out) Final Test-results Kristof Sardemann
2002-11-21 19:07 ` bug in via-rhine network-driver (transmit timed out) debug-report Kristof Sardemann
-- strict thread matches above, loose matches on Subject: below --
2002-12-09 16:54 bug in via-rhine network-driver (transmit timed out) ksardem
2002-12-09 16:58 ` Jeff Garzik
2002-11-17 8:30 Justin A
2002-11-17 7:59 ksardem
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=3DD76371.4060009@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=ksardem@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=urban@teststation.com \
/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