From: Justin A <justin@bouncybouncy.net>
To: linux-kernel@vger.kernel.org
Subject: via-rhine timeouts
Date: Tue, 22 Jan 2002 18:42:01 -0500 [thread overview]
Message-ID: <20020122234201.GA835@bouncybouncy.net> (raw)
I've been getting many errors due to timeouts, everything was fine while
I was at home, but here at school it's a major problem:
Jan 22 18:10:00 bouncybouncy kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Jan 22 18:10:00 bouncybouncy kernel: eth0: Transmit timed out, status
0000, PHY
status 782d, resetting...
Jan 22 18:10:10 bouncybouncy kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Jan 22 18:10:10 bouncybouncy kernel: eth0: Transmit timed out, status
0000, PHY
status 782d, resetting...
Jan 22 18:10:18 bouncybouncy kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Jan 22 18:10:18 bouncybouncy kernel: eth0: Transmit timed out, status
0000, PHY
status 782d, resetting...
Jan 22 18:10:26 bouncybouncy kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Jan 22 18:10:26 bouncybouncy kernel: eth0: Transmit timed out, status
0000, PHY
status 782d, resetting...
Jan 22 18:10:34 bouncybouncy kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Jan 22 18:10:34 bouncybouncy kernel: eth0: Transmit timed out, status
0000, PHY
status 782d, resetting...
Jan 22 18:10:34 bouncybouncy kernel: eth0: reset did not complete in 10
ms.
once it complains about that, it stops working until I reboot.
It seems to happen everytime a large transer is done.(apt-get updgrade
-d the last 3 times.)
Is this a problem with me, or are the hubs screwy? The hubs I'm on are
"smart hubs", lets just say they aren't too bright:)
I have a soyo k7vdragon+ using 2.4.17:
eth0: VIA VT6102 Rhine-II at 0xe800, 00:50:2c:01:64:a9, IRQ 11.
eth0: MII PHY found at address 1, status 0x782d advertising 01e1 Link
0021.
CC replies...
-Justin
next reply other threads:[~2002-01-22 23:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 23:42 Justin A [this message]
2002-01-23 0:37 ` Urban Widmark
2002-01-23 1:02 ` Justin A
2002-01-23 9:44 ` Urban Widmark
2002-01-23 10:16 ` Stephan von Krawczynski
2002-01-23 1:07 ` Andy Carlson
2002-01-23 1:58 ` Justin A
2002-01-23 10:36 ` Martin Eriksson
2002-01-23 12:04 ` Urban Widmark
2002-01-23 20:44 ` Andrew Morton
2002-01-23 23:25 ` Stephan von Krawczynski
2002-01-23 23:53 ` Urban Widmark
2002-01-23 23:41 ` Justin A
2002-01-23 23:49 ` Urban Widmark
2002-01-24 8:38 ` Martin Eriksson
2002-01-24 13:01 ` Andy Carlson
2002-01-24 14:42 ` Martin Eriksson
2002-01-24 1:25 ` Andy Carlson
2002-01-23 10:12 ` AW: " Roland Schwarz
[not found] <Pine.LNX.4.33.0201261559580.4687-200000@cola.teststation.com>
2002-01-29 2:13 ` Justin A
2002-01-29 21:06 ` Urban Widmark
2002-01-30 0:15 ` Justin A
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=20020122234201.GA835@bouncybouncy.net \
--to=justin@bouncybouncy.net \
--cc=linux-kernel@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
Powered by JetHome