From: ksardem@linux01.gwdg.de
To: linux-kernel@vger.kernel.org
Cc: manfred@colorfullife.com
Subject: Re: bug in via-rhine network-driver (transmit timed out)
Date: Mon, 9 Dec 2002 17:54:07 +0100 [thread overview]
Message-ID: <1653237694.20021209175407@linux01.gwdg.de> (raw)
Hi,
I successfully got the old transmit-out-error again ;-)
- and this time with "options via-rhine debug=3" in modules.conf.
So here are the debug-messages:
dmesg:
eth0: Shutting down ethercard, status was 081a.
eth0: via_rhine_open() irq 9.
eth0: reset finished after 5 microseconds.
eth0: Done via_rhine_open(), status 081a MII status: 7809.
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Shutting down ethercard, status was 883a.
eth0: via_rhine_open() irq 9.
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Done via_rhine_open(), status 881a MII status: 782d.
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Shutting down ethercard, status was 883a.
eth0: via_rhine_open() irq 9.
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Done via_rhine_open(), status 881a MII status: 7829.
eth0: Shutting down ethercard, status was 883a.
lsmod was:
via-rhine 13612 2
mii 1232 0 [via-rhine]
--
Bye.
Kristof <ksardem@linux01.gwdg.de>
next reply other threads:[~2002-12-09 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 16:54 ksardem [this message]
2002-12-09 16:58 ` bug in via-rhine network-driver (transmit timed out) Jeff Garzik
2002-12-09 21:27 ` Re[2]: " Kristof Sardemann
2002-12-09 21:33 ` Adaptec 2940 not working on 2.5.50 David Lang
-- strict thread matches above, loose matches on Subject: below --
2002-11-17 9:37 bug in via-rhine network-driver (transmit timed out) Manfred Spraul
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=1653237694.20021209175407@linux01.gwdg.de \
--to=ksardem@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.