From: "Paul Rolland" <rol@as2917.net>
To: <linux-kernel@vger.kernel.org>
Cc: "'Paul Rolland'" <rol@as2917.net>
Subject: eepro100: wait_for_cmd_done timeout
Date: Thu, 27 Feb 2003 17:56:21 +0100 [thread overview]
Message-ID: <01e601c2de81$27527ce0$3f00a8c0@witbe> (raw)
Hello,
We have a server that has gone thru that :
21:30:02.231737 rms-01 network: Result 0 for gateway 192.168.0.254
Feb 26 21:30:29 rms-01 Feb 26 21:30:29:517449 kernel: eepro100:
wait_for_cmd_don
e timeout!
Feb 26 21:30:30 rms-01 Feb 26 21:30:30:514068 kernel: eepro100:
wait_for_cmd_don
e timeout!
Feb 26 21:30:30 rms-01 Feb 26 21:30:30:514094 kernel: eepro100:
wait_for_cmd_don
e timeout!
...
Feb 27 13:48:15 rms-01 Feb 27 13:48:15:940827 kernel: eepro100:
wait_for_cmd_don
e timeout!
Feb 27 13:48:16 rms-01 Feb 27 13:48:16:940946 kernel: eepro100:
wait_for_cmd_don
e timeout!
Feb 27 13:48:20 rms-01 Feb 27 13:48:20:766987 kernel: NETDEV WATCHDOG:
eth0: tra
nsmit timed out
Feb 27 13:48:20 rms-01 Feb 27 13:48:20:767007 kernel: eth0: Transmit
timed out:
status 0090 0c80 at 162209/162269 command 000ca000.
Feb 27 13:48:20 rms-01 Feb 27 13:48:20:842320 kernel: eepro100:
wait_for_cmd_don
e timeout!
Feb 27 13:48:20 rms-01 Feb 27 13:48:20:842333 kernel: eepro100:
wait_for_cmd_don
e timeout!
Feb 27 13:50:01 rms-01 Feb 27 13:50:01:30726 kernel: eepro100:
wait_for_cmd_done
timeout!
The only way to get it out of that is a reboot...
The kernel is a 2.4.19 and dmesg says :
eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://www.scyld.com/network/eepro100.
html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin
<saw@sa
w.sw.com.sg> and others
eth0: OEM i82557/i82558 10/100 Ethernet, 00:06:5B:39:69:2B, IRQ 16.
Board assembly 02d484-000, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
eth1: OEM i82557/i82558 10/100 Ethernet, 00:06:5B:39:69:2C, IRQ 17.
Board assembly 02d484-000, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x04f4518b).
Anyone knows why ?
Regards,
Paul
next reply other threads:[~2003-02-27 16:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 16:56 Paul Rolland [this message]
2003-02-27 20:30 ` eepro100: wait_for_cmd_done timeout Andrey Nekrasov
2003-02-28 6:50 ` Paul Rolland
-- strict thread matches above, loose matches on Subject: below --
2003-03-28 11:42 Chris Bacott
2003-03-28 17:59 ` Jeff Garzik
2001-06-20 23:31 Dionysius Wilson Almeida
2001-06-20 23:51 ` Andrey Savochkin
2001-06-21 0:02 ` Dionysius Wilson Almeida
2001-06-21 13:46 ` Rafael Martinez
2001-06-22 1:36 ` Dionysius Wilson Almeida
2001-06-22 13:31 ` Andrey Savochkin
2001-06-22 20:06 ` Dionysius Wilson Almeida
2001-06-21 14:19 ` Masaru Kawashima
2001-06-21 14:37 ` John Madden
2001-06-22 1:27 ` Masaru Kawashima
2001-06-21 16:28 ` Masaru Kawashima
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='01e601c2de81$27527ce0$3f00a8c0@witbe' \
--to=rol@as2917.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 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.