speaking of USB...(bug/hub.c)
Here's another one for the books. In the recent test11 series, timing appears to be partially broken for dev addr assignments. If I'm lucky a new usb device will answer back and get all the numbers set up properly. Regularly however a new device gets plugged in and I get several of the below without the success at the end. I usually need to reboot to get my USB stuff alive again. The below is test7.
# dmesg hub.c: USB new device connect on bus1/1, assigned device number 6 usb-uhci.c: interrupt, status 2, frame# 121 usb.c: USB device not accepting new address=6 (error=-110) hub.c: USB new device connect on bus1/1, assigned device number 7
# lspci
00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
(prog-if 00 [UHCI])
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: 64
Interrupt: pin D routed to IRQ 9
Region 4: I/O ports at ef80 [size=32]# cat devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 17/900 us ( 2%), #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=ef80 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=00 Cnt=01 Dev#= 7 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0707 ProdID=0200 Rev= 1.01 S: Manufacturer=SMC, Inc S: Product=EZ USB/Ethernet Converter S: SerialNumber=0001 C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=160mA I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=pegasus E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=128ms
-d
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:[email protected]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard
Quoted 7 lines · David Ford
Here's another one for the books. In the recent test11 series, timing appears to be partially broken for dev addr assignments. If I'm lucky a new usb device will answer back and get all the numbers set up properly. Regularly however a new device gets plugged in and I get several of the below without the success at the end. I usually need to reboot to get my USB stuff alive again. The below is test7.
Quoted 5 lines
# dmesg hub.c: USB new device connect on bus1/1, assigned device number 6 usb-uhci.c: interrupt, status 2, frame# 121 usb.c: USB device not accepting new address=6 (error=-110) hub.c: USB new device connect on bus1/1, assigned device number 7
Status 2 means there was an error with the transfer. This doesn't look like a hub.c bug at all.
What kind of device is this?
Does this problem still happen with the other UHCI driver?
JE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 6 lines · Johannes Erdfelt
Quoted 5 lines
# dmesg hub.c: USB new device connect on bus1/1, assigned device number 6 usb-uhci.c: interrupt, status 2, frame# 121 usb.c: USB device not accepting new address=6 (error=-110) hub.c: USB new device connect on bus1/1, assigned device number 7
Quoted 6 lines
Status 2 means there was an error with the transfer. This doesn't look like a
hub.cbug at all.What kind of device is this?
Does this problem still happen with the other UHCI driver?
This device is any usb device I plug in. Mouse, Kodak camera, Pegasus network module...
I'll try with the JE driver.
-d
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:[email protected]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard