From: Justin A <justin@bouncybouncy.net>
To: linux-kernel@vger.kernel.org
Cc: Urban Widmark <urban@teststation.com>
Subject: Re: via-rhine timeouts
Date: 28 Jan 2002 21:13:27 -0500 [thread overview]
Message-ID: <1012270407.22269.0.camel@bouncybouncy.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0201261559580.4687-200000@cola.teststation.com>
In-Reply-To: <Pine.LNX.4.33.0201261559580.4687-200000@cola.teststation.com>
I re-addressed the email...the CC's got out of hand...
On Sat, 2002-01-26 at 10:21, Urban Widmark wrote:
>
> Hello, troubled via-rhine users ...
>
> The attached patch vs 2.4.17 is a merge of bits from various sources. It
> contains useful stuff such as turning on bit2 in the cards PCI
> configuration register 0x53 (undocumented).
>
> Please test this and see if the problems go away. Note that this version
> reports a little more information, so send 'dmesg' output even of you
> sent it before.
>
Ok, it was working for a while, even after a reboot...
but now
21:04:33 up 2 days, 20 min, 10 users, load average: 0.12, 0.47, 0.38
Jan 28 01:39:10 bouncybouncy kernel: eth0: Transmitter underflow?,
status 2008.
Jan 28 01:39:20 bouncybouncy kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Jan 28 01:39:20 bouncybouncy kernel: eth0: Transmit timed out, status
0000, PHY status 782d, resetting...
Jan 28 01:39:20 bouncybouncy kernel: eth0: reset finished after 5
microseconds.
Jan 28 02:23:22 bouncybouncy kernel: eth0: Transmitter underflow?,
status 2008.
Jan 28 02:23:26 bouncybouncy kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Jan 28 02:23:26 bouncybouncy kernel: eth0: Transmit timed out, status
0000, PHY status 782d, resetting...
Jan 28 02:23:26 bouncybouncy kernel: eth0: reset finished after 5
microseconds.
This went unnoticed earlier.... until it happened again:
Jan 28 20:26:03 bouncybouncy kernel: eth0: Transmitter underflow?,
status 2008.
Jan 28 20:26:06 bouncybouncy kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Jan 28 20:26:06 bouncybouncy kernel: eth0: Transmit timed out, status
0000, PHY status 782d, resetting...
Jan 28 20:26:06 bouncybouncy kernel: eth0: reset finished after 10005
microseconds.
That repeated over and over again(every 30 seconds or so) until I got
back:
grep "Jan 28.*eth0" /var/log/messages|wc -l
328
After reloading the driver it started working again:
linuxfet.c : v3.23 05/15/2001
The PCI BIOS has not enabled the device at 0/144! Updating PCI
command 0003->0007.
eth0: VIA PCI 10/100Mb Fast Ethernet Adapter
eth0: IO Address = 0xe800, MAC Address = 00:50:2c:01:64:a9, IRQ = 11.
eth0: MII PHY found at address 1, status 0x782d advertising 01e1 Link
0021.
eth0: netdev_open() irq 11.
eth0: Done netdev_open(), status 881a MII status: 782d.
I think that last message might be a clue on why this is happening...
--
-Justin
next parent reply other threads:[~2002-01-29 2:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0201261559580.4687-200000@cola.teststation.com>
2002-01-29 2:13 ` Justin A [this message]
2002-01-29 21:06 ` Urban Widmark
2002-01-30 0:15 ` Justin A
2002-01-22 23:42 Justin A
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
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=1012270407.22269.0.camel@bouncybouncy.net \
--to=justin@bouncybouncy.net \
--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
all inboxes | Powered by JetHome®