From: khromy@lnuxlab.ath.cx (khromy)
To: linux-kernel@vger.kernel.org
Subject: usb_control/bulk_msg: timeout / NETDEV WATCHDOG: eth0: transmit timed out
Date: Tue, 9 Sep 2003 20:27:20 -0400 [thread overview]
Message-ID: <20030910002720.GA30861@lnuxlab.ath.cx> (raw)
Hi,
Anybody know what's up with this? Running 2.4.23-pre3 I get the following
while booting up:
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=3 (error=-110)
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out, tx_status 00 status e601.
diagnostics: net 0cc0 media 88c0 dma 0000003b.
eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
Flags; bus-master 1, dirty 16(0) current 16(0)
Transmit list 00000000 vs. c15eb200.
0: @c15eb200 length 8000002a status 0000002a
1: @c15eb240 length 8000002a status 0000002a
2: @c15eb280 length 8000002a status 0000002a
3: @c15eb2c0 length 8000002a status 0000002a
4: @c15eb300 length 8000002a status 0000002a
5: @c15eb340 length 8000002a status 0000002a
6: @c15eb380 length 8000002a status 0000002a
7: @c15eb3c0 length 8000002a status 0000002a
8: @c15eb400 length 8000002a status 0000002a
9: @c15eb440 length 8000002a status 0000002a
10: @c15eb480 length 8000002a status 0000002a
11: @c15eb4c0 length 8000002a status 0000002a
12: @c15eb500 length 8000002a status 0000002a
13: @c15eb540 length 8000002a status 0000002a
14: @c15eb580 length 8000002a status 8000002a
15: @c15eb5c0 length 8000002a status 8000002a
eth0: Resetting the Tx ring pointer.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out, tx_status 00 status e601.
diagnostics: net 0cc0 media 88c0 dma 0000003b.
eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
Flags; bus-master 1, dirty 32(0) current 32(0)
Transmit list 00000000 vs. c15eb200.
0: @c15eb200 length 8000002a status 0000002a
1: @c15eb240 length 8000002a status 0000002a
2: @c15eb280 length 8000002a status 0000002a
3: @c15eb2c0 length 80000049 status 00000049
4: @c15eb300 length 80000049 status 00000049
5: @c15eb340 length 80000049 status 00000049
6: @c15eb380 length 80000049 status 00000049
7: @c15eb3c0 length 80000049 status 00000049
8: @c15eb400 length 80000049 status 00000049
9: @c15eb440 length 80000049 status 00000049
10: @c15eb480 length 80000049 status 00000049
11: @c15eb4c0 length 80000049 status 00000049
12: @c15eb500 length 8000004c status 0000004c
13: @c15eb540 length 8000004c status 0000004c
14: @c15eb580 length 8000004c status 8000004c
15: @c15eb5c0 length 8000004c status 8000004c
eth0: Resetting the Tx ring pointer.
..
..
--
L1: khromy ;khromy (at) lnuxlab.ath.cx
next reply other threads:[~2003-09-10 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 0:27 khromy [this message]
2003-09-10 0:35 ` Andrew Morton
2003-09-10 7:50 ` khromy
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=20030910002720.GA30861@lnuxlab.ath.cx \
--to=khromy@lnuxlab.ath.cx \
--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
all inboxes | Powered by JetHome®