From: David Ford <david@linux.com>
To: Manfred <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NETDEV WATCHDOG: eth0: transmit timed out
Date: Thu, 28 Dec 2000 03:36:49 -0800 [thread overview]
Message-ID: <3A4B25D1.127BFDFA@linux.com> (raw)
In-Reply-To: <3A4B234E.7A950A76@colorfullife.com>
[-- Attachment #1: Type: text/plain, Size: 1904 bytes --]
Manfred wrote:
> David wrote:
> >
> > Same old story, bugger still does it. Have to set the link down/up to
> > get it running again.
> >
> > 00:12.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev
> > 20)
> >
>
> I missed your earlier mails, could you resend the details?
> I'm interested in the output from
>
> tulip-diag -m -a -f
>
> before and after a link failure.
>
> I'm aware that the tulip drivers doesn't handle cable disconnects and
> reconnects with MII pnic cards. I have a patch for that problem, but it
> affects _all_ MII tulip cards, and thus it won't be included soon. If
> tulip-diag says "10mbps-serial", then you have run into that bug.
>
> --
> Manfred
Here's the before, when the after happens..
# ./tulip-diag -m -a -f
tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Lite-On 82c168 PNIC adapter at 0xf800.
Lite-On 82c168 PNIC chip registers at 0xf800:
00008000 01ff0000 00450008 0118f000 0118f200 02660010 814c2202 0001ebef
00000000 00000000 0118f2d0 01e3a88c 00000020 00000000 00000000 10000001
00000000 00000000 f0041385 000000bf 609641e1 0118f110 00c99010 0001e978
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Port selection is MII, full-duplex.
Transmit started, Receive started, full-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 72.
MII PHY found at address 1, status 0x782d.
MII PHY #1 transceiver registers:
3000 782d 0040 6212 01e1 41e1 0003 0000
0000 0000 0000 0000 0000 0000 0000 0000
5000 032b 0002 0046 0000 01cd 0100 0000
003f f53e 0f00 ff00 002f 4000 80a0 000b.
This particular one is on a crossover @ 100 FD with a pcmcia tulip
card...which works fine.
The other machine I had reset tonight was on a crossover w/ cisco 3640
iirc.
-d
[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 274 bytes --]
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
url:www.blue-labs.org
adr:;;;;;;
version:2.1
email;internet:david@blue-labs.org
title:Blue Labs Developer
note;quoted-printable:GPG key: http://www.blue-labs.org/david@nifty.key=0D=0A
x-mozilla-cpt:;9952
fn:David Ford
end:vcard
next prev parent reply other threads:[~2000-12-28 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 11:26 NETDEV WATCHDOG: eth0: transmit timed out Manfred
2000-12-28 11:36 ` David Ford [this message]
2000-12-29 0:30 ` idalton
-- strict thread matches above, loose matches on Subject: below --
2001-03-01 16:59 Caleb Epstein
2001-03-01 23:01 ` Andrew Morton
2001-01-13 2:24 Darryl Miles
2000-12-28 10:43 David Ford
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=3A4B25D1.127BFDFA@linux.com \
--to=david@linux.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox