From: Joseph Cheek <joseph@cheek.com>
To: linux-kernel@vger.kernel.org
Subject: test12: eth0 trasmit timed out after one hour uptime
Date: Wed, 13 Dec 2000 15:01:29 -0800 [thread overview]
Message-ID: <3A37FFC9.19F05305@cheek.com> (raw)
hi all,
after about an hour of uptime [and heavy HD usage] my ethernet just
died. couldn't ping a thing. syslog showed:
Dec 13 14:51:46 sanfrancisco kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Dec 13 14:51:46 sanfrancisco kernel: eth0: transmit timed out, tx_status
00 status e680.
Dec 13 14:51:46 sanfrancisco kernel: Flags; bus-master 1, full 1;
dirty 3306(10) current 3322(10).
Dec 13 14:51:46 sanfrancisco kernel: Transmit list 00000000 vs.
c7c732a0.
Dec 13 14:51:46 sanfrancisco kernel: 0: @c7c73200 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 1: @c7c73210 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 2: @c7c73220 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 3: @c7c73230 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 4: @c7c73240 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 5: @c7c73250 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 6: @c7c73260 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 7: @c7c73270 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 8: @c7c73280 length 8000002a
status 8001002a
Dec 13 14:51:46 sanfrancisco kernel: 9: @c7c73290 length 8000002a
status 8001002a
Dec 13 14:51:46 sanfrancisco kernel: 10: @c7c732a0 length 8000004b
status 0001004b
Dec 13 14:51:46 sanfrancisco kernel: 11: @c7c732b0 length 8000004b
status 0001004b
Dec 13 14:51:46 sanfrancisco kernel: 12: @c7c732c0 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 13: @c7c732d0 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 14: @c7c732e0 length 8000002a
status 0001002a
Dec 13 14:51:46 sanfrancisco kernel: 15: @c7c732f0 length 8000002a
status 0001002a
after reboot it works fine again [i'll give it an hour...] test12-pre8
and before worked fine. any ideas?
--
thanks!
joe
--
Joseph Cheek, Sr Linux Consultant, Linuxcare | http://www.linuxcare.com/
Linuxcare. Support for the Revolution. | joseph@linuxcare.com
CTO / Acting PM, Redmond Linux Project | joseph@redmondlinux.org
425 990-1072 vox [1074 fax] 206 679-6838 pcs | joseph@cheek.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-13 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 23:01 Joseph Cheek [this message]
2000-12-13 23:11 ` test12: eth0 trasmit timed out after one hour uptime Mohammad A. Haque
2000-12-13 23:13 ` Joseph Cheek
2000-12-13 23:25 ` Mohammad A. Haque
2000-12-14 2:03 ` James Stevenson
2000-12-14 2:37 ` Michael Peddemors
2000-12-14 1:41 ` Joseph Cheek
2000-12-14 2:34 ` Michael Peddemors
2000-12-15 15:19 ` Ingo Oeser
2000-12-15 14:50 ` Andrew Morton
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=3A37FFC9.19F05305@cheek.com \
--to=joseph@cheek.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.