Skip to contentSkip to conversation

2.4.17 usbnet usb.c: USB device not accepting new address

DISCUSSION Pete Zaitcev 3 participants 4 messages Jan 7, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 1 line

kernel: usb.c: USB device not accepting new address=6 (error=-110)

And your /proc/interrupts is ... ?

-- Pete

#3 lore raw
In reply to a message not in the archive
Quoted 9 lines · Johannes Erdfelt
Quoted 3 lines · Pete Zaitcev
Quoted 1 line

kernel: usb.c: USB device not accepting new address=6 (error=-110)

And your /proc/interrupts is ... ?

Almost definately > 0. He was getting hard CRC/Timeout's out of the HC.

JE

before plugging the ipaq in again:

19: 198150 198207 IO-APIC-level aic7xxx, eth0, usb-uhci

NMI:          0          0
LOC:    2554011    2553990
ERR:          0
MIS:          0

after plugging in: (doing cat interrupts continuously)

19: 198178 198233 IO-APIC-level aic7xxx, eth0, usb-uhci

NMI:          0          0
LOC:    2555170    2555148
ERR:          0
MIS:          0

19: 198187 198241 IO-APIC-level aic7xxx, eth0, usb-uhci

NMI:          0          0
LOC:    2555323    2555301
ERR:          0
MIS:          0

19: 198192 198248 IO-APIC-level aic7xxx, eth0, usb-uhci

NMI:          0          0
LOC:    2555437    2555416
ERR:          0
MIS:          0

19: 198194 198250 IO-APIC-level aic7xxx, eth0, usb-uhci

NMI:          0          0
LOC:    2555515    2555494
ERR:          0
MIS:          0

i just realized i might have an issue with shared irqs here. aic7xxx has my system disk, and eth0 is a realtek 8139too.o aic7xxx and usb are on-board, so there's nothing i can do against them sharing an interrupt. i might shuffle my nic around tomorrow, if you guys think that it makes a difference.

Signature · 5 lines
Jörn Nettingsmeier     
home://Kurfürstenstr.49.45138.Essen.Germany      
phone://+49.201.491621
http://spunk.dnsalias.org
http://www.linuxdj.com/audio/lad/
#4 lore raw
In reply to a message not in the archive
Quoted 43 lines · Jörn Nettingsmeier
Quoted 7 lines · Johannes Erdfelt
Quoted 3 lines · Pete Zaitcev
Quoted 1 line

kernel: usb.c: USB device not accepting new address=6 (error=-110)

And your /proc/interrupts is ... ?

Almost definately > 0. He was getting hard CRC/Timeout's out of the HC.

before plugging the ipaq in again:

19: 198150 198207 IO-APIC-level aic7xxx, eth0, usb-uhci

NMI:          0          0
LOC:    2554011    2553990
ERR:          0
MIS:          0

after plugging in: (doing cat interrupts continuously)

19: 198178 198233 IO-APIC-level aic7xxx, eth0, usb-uhci

NMI:          0          0
LOC:    2555170    2555148
ERR:          0
MIS:          0

19: 198187 198241 IO-APIC-level aic7xxx, eth0, usb-uhci

NMI:          0          0
LOC:    2555323    2555301
ERR:          0
MIS:          0

19: 198192 198248 IO-APIC-level aic7xxx, eth0, usb-uhci

NMI:          0          0
LOC:    2555437    2555416
ERR:          0
MIS:          0

19: 198194 198250 IO-APIC-level aic7xxx, eth0, usb-uhci

NMI:          0          0
LOC:    2555515    2555494
ERR:          0
MIS:          0
Quoted 5 lines

i just realized i might have an issue with shared irqs here. aic7xxx has my system disk, and eth0 is a realtek 8139too.o aic7xxx and usb are on-board, so there's nothing i can do against them sharing an interrupt. i might shuffle my nic around tomorrow, if you guys think that it makes a difference.

It shouldn't. It seems to be getting the interrupts correctly since we saw the CRC/Timeo from the HC.

JE