From: David <david@blue-labs.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: USB problem, bug since 2.4.2-ac5
Date: Sun, 04 Mar 2001 18:09:38 -0800 [thread overview]
Message-ID: <3AA2F562.7070705@blue-labs.org> (raw)
In ac5 the USB or related changes broke things for this system I
upgraded, this bug still exists in ac11.
I get the following messages on the order of about 50/second.
usb-uhci.c: interrupt, status 20, frame# 0
usb-uhci.c: interrupt, status 30, frame# 0
They repeat forever evenly, 20-30-20-30..
Alan's announcment for -ac5 has listed in it:
Fix USB thread wakeup scheduling(Arjan van de Ven)
00:04.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32 set
Interrupt: pin D routed to IRQ 9
Region 4: I/O ports at b400 [size=32]
The only USB device I have plugged in atm is:
input0: USB HID v1.00 Mouse [Logitech USB-PS/2 Mouse] on usb1:2.0
/proc/bus/usb has:
# cat devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc=118/900 us (13%), #Int= 1, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=b400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=046d ProdID=c001 Rev= 1.10
S: Manufacturer=Logitech
S: Product=USB-PS/2 Mouse
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 50mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=hid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl= 10ms
# cat drivers
cpia
usbdevfs
hub
hid
48- 63: usbscanner
acm
0- 15: usblp
audio
80- 95: dc2xx
ov511
dsbr100
bluetooth
pegasus
usb-storage
-d
reply other threads:[~2001-03-05 2:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3AA2F562.7070705@blue-labs.org \
--to=david@blue-labs.org \
--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.