From: Simon Kirby <sim@netnation.com>
To: Johannes Erdfelt <johannes@erdfelt.com>
Cc: Greg KH <greg@kroah.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.4.11-pre5
Date: Sun, 7 Oct 2001 12:40:38 -0700 [thread overview]
Message-ID: <20011007124038.A22923@netnation.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110071148380.7382-100000@penguin.transmeta.com> <20011007121851.A1137@netnation.com> <20011007153433.G14479@sventech.com>
In-Reply-To: <20011007153433.G14479@sventech.com>; from johannes@erdfelt.com on Sun, Oct 07, 2001 at 03:34:33PM -0400
On Sun, Oct 07, 2001 at 03:34:33PM -0400, Johannes Erdfelt wrote:
> > hub.c: USB new device connect on bus1/2, assigned device number 2
> > usb_control/bulk_msg: timeout
> > usb.c: USB device not accepting new address=2 (error=-110)
>
> Could you give me the output of /proc/interrupts?
CPU0 CPU1
0: 71555 64454 IO-APIC-edge timer
1: 1355 1274 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
5: 0 0 IO-APIC-edge NE2000
14: 4157 5136 IO-APIC-edge ide0
15: 2 19 IO-APIC-edge ide1
16: 2462 2381 IO-APIC-level eth0
17: 0 0 IO-APIC-level Trident 4DWave NX
18: 1 1 IO-APIC-level bttv
19: 2330 2467 IO-APIC-level aic7xxx, usb-uhci
NMI: 0 0
LOC: 135894 135912
ERR: 0
MIS: 0
> Do you see any other messages in dmesg?
Here is an entire "insmod uhci" output:
uhci.c: USB Universal Host Controller Interface driver v1.1
uhci.c: USB UHCI at I/O 0xb400, IRQ 19
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
hub.c: USB new device connect on bus1/2, assigned device number 2
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=2 (error=-110)
hub.c: USB new device connect on bus1/2, assigned device number 3
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=3 (error=-110)
> What UHCI controller is this? (lspci -v)
00:04.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) (prog-if 00 [UHCI])
Flags: bus master, medium devsel, latency 32, IRQ 19
I/O ports at b400 [size=32]
It's on an ASUS P2B-DS (with broken USB resistor shorted).
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
next prev parent reply other threads:[~2001-10-07 19:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-07 18:49 Linux-2.4.11-pre5 Linus Torvalds
2001-10-07 19:18 ` Linux-2.4.11-pre5 Simon Kirby
2001-10-07 19:34 ` Linux-2.4.11-pre5 Johannes Erdfelt
2001-10-07 19:40 ` Simon Kirby [this message]
2001-10-07 20:19 ` Linux-2.4.11-pre5 Johannes Erdfelt
2001-10-07 20:33 ` [patch] uhci.c interrupts Johannes Erdfelt
2001-10-08 19:02 ` Linux-2.4.11-pre5 Simon Kirby
2001-10-08 19:47 ` Linux-2.4.11-pre5 Simon Kirby
2001-10-08 20:21 ` Linux-2.4.11-pre5 Johannes Erdfelt
2001-10-08 20:30 ` Linux-2.4.11-pre5 Simon Kirby
2001-10-07 20:49 ` Linux-2.4.11-pre5 Adrian Bunk
2001-10-07 21:17 ` Linux-2.4.11-pre5 Alessandro Suardi
2001-10-07 23:46 ` Linux-2.4.11-pre5 Linus Torvalds
2001-10-08 16:32 ` [PATCH] Linux-2.4.11-pre5 Robert Schiele
2001-10-07 21:48 ` Linux-2.4.11-pre5 Alan Cox
2001-10-08 1:11 ` Linux-2.4.11-pre5 Keith Owens
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=20011007124038.A22923@netnation.com \
--to=sim@netnation.com \
--cc=greg@kroah.com \
--cc=johannes@erdfelt.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