From: David Ford <david@linux.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: NETDEV WATCHDOG: eth0: transmit timed out
Date: Thu, 28 Dec 2000 02:43:14 -0800 [thread overview]
Message-ID: <3A4B1942.D00CF7E4@linux.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
Same old story, bugger still does it. Have to set the link down/up to
get it running again. I had to reset two systems tonight, one up for
~60 days, one up for two days. Both have this card. Unrelated traffic.
This is kernel 2.4.0-test13-pre4
00:12.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev
20)
Subsystem: Unknown device 1385:f004
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64 set
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at f800
Region 1: Memory at fdfffc00 (32-bit, non-prefetchable)
-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 reply other threads:[~2000-12-28 11:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 10:43 David Ford [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-28 11:26 NETDEV WATCHDOG: eth0: transmit timed out Manfred
2000-12-28 11:36 ` David Ford
2000-12-29 0:30 ` idalton
2001-01-13 2:24 Darryl Miles
2001-03-01 16:59 Caleb Epstein
2001-03-01 23:01 ` Andrew Morton
[not found] <3F33470A.6070100@imc-berlin.de>
2003-08-10 20:40 ` Thomas Lange
2006-08-01 9:18 gpio Interrupt handling for omap5912 Arnold
2006-08-01 10:25 ` NETDEV WATCHDOG: eth0: transmit timed out Arnold
2007-12-14 13:48 José Luís
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=3A4B1942.D00CF7E4@linux.com \
--to=david@linux.com \
--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 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.