From: Andrey Savochkin <saw@saw.sw.com.sg>
To: Dionysius Wilson Almeida <dwilson@technolunatic.com>,
linux-kernel@vger.kernel.org
Subject: Re: eepro100: wait_for_cmd_done timeout
Date: Wed, 20 Jun 2001 19:51:34 -0400 [thread overview]
Message-ID: <20010620195134.A6877@saw.sw.com.sg> (raw)
In-Reply-To: <20010620163134.A22173@technolunatic.com>
In-Reply-To: <20010620163134.A22173@technolunatic.com>; from "Dionysius Wilson Almeida" on Wed, Jun 20, 2001 at 04:31:34PM
What was the first error message from the driver?
NETDEV WATCHDOG report went before wait_for_cmd_done timeout and is more
important. I wonder if you had some other messages before the watchdog one.
Andrey
On Wed, Jun 20, 2001 at 04:31:34PM -0700, Dionysius Wilson Almeida wrote:
> And this is the log when the card hangs :
> =========================================
> Jun 20 16:10:18 debianlap kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Jun 20 16:10:18 debianlap kernel: eth0: Transmit timed out: status 0050 0c80 at 314/342 command 000c0000.
> Jun 20 16:10:18 debianlap kernel: eth0: Tx ring dump, Tx queue 342 / 314:
> Jun 20 16:14:07 debianlap kernel: eepro100: wait_for_cmd_done timeout!
> Jun 20 16:14:38 debianlap last message repeated 5 times
next prev parent reply other threads:[~2001-06-20 23:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 23:31 eepro100: wait_for_cmd_done timeout Dionysius Wilson Almeida
2001-06-20 23:51 ` Andrey Savochkin [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-02-27 16:56 Paul Rolland
2003-02-27 20:30 ` Andrey Nekrasov
2003-02-28 6:50 ` Paul Rolland
2003-03-28 11:42 Chris Bacott
2003-03-28 17:59 ` Jeff Garzik
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=20010620195134.A6877@saw.sw.com.sg \
--to=saw@saw.sw.com.sg \
--cc=dwilson@technolunatic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox