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

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

[Jörn Nettingsmeier]

hello * !

when i try to connect my ipaq to the desktop via usbnet, i see the
following:

 kernel: hub.c: port 2, portstatus 103, change 0, 12 Mb/s
 kernel: hub.c: USB new device connect on bus1/2, assigned device
number 6
 kernel: usb.c: USB device not accepting new address=6 (error=-110)

i don't get an usbn network device when i do ifconfig -a.

i'm using 2.4.17 on a dual p3/600, mobo is asus p2b-ds.

the following usb-related modules are present:
usbnet                 10848   0  (unused)
mousedev                3904   0
hid                    12576   0  (unused)
input                   3488   0  [mousedev hid]
usb-uhci               21760   0  (unused)
usbcore                54688   1  [usbnet hid usb-uhci]

i have never been able to use usbnet since i have the ipaq. iirc, 
my first try was with 2.4.10-acsomething.

from a google search i found that some people recommended to boot
with noapic, but i'm not sure whether this is feasible on an smp
system. other than that, the problem seems to be known but yet
unresolved. 

here are some snippets from my .config:

kleineronkel:/usr/src/linux # cat .config|grep APIC
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y

kleineronkel:/usr/src/linux # cat .config|grep USB
CONFIG_USB=m
CONFIG_USB_DEBUG=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_UHCI=m
CONFIG_USB_AUDIO=m
CONFIG_USB_PRINTER=m
CONFIG_USB_HID=m
CONFIG_USB_WACOM=m
CONFIG_USB_DC2XX=m
CONFIG_USB_MDC800=m
CONFIG_USB_SCANNER=m
CONFIG_USB_MICROTEK=m
CONFIG_USB_HPUSBSCSI=m
CONFIG_USB_USBNET=m
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y

thanks in advance for any insights,

regards,

jörn


-- 
Jörn Nettingsmeier     
home://Kurfürstenstr.49.45138.Essen.Germany      
phone://+49.201.491621
http://spunk.dnsalias.org
http://www.linuxdj.com/audio/lad/

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

[Jörn Nettingsmeier]

btw, here's the error message i get from uhci.o
(as opposed to usb-uhci.o, which i had pasted into my earlier post)

Jan  7 22:05:18 kleineronkel kernel: usb.c: kusbd: /sbin/hotplug add
6
Jan  7 22:05:18 kleineronkel kernel: usb.c: kusbd policy returned
0xfffffffe
Jan  7 22:05:18 kleineronkel kernel: hub.c: port 2 connection change
Jan  7 22:05:18 kleineronkel kernel: hub.c: port 2, portstatus 101,
change 1, 12 Mb/s
Jan  7 22:05:18 kleineronkel kernel: hub.c: port 2, portstatus 103,
change 0, 12 Mb/s
Jan  7 22:05:18 kleineronkel kernel: hub.c: USB new device connect
on bus1/2, assigned device number 7
Jan  7 22:05:18 kleineronkel kernel: uhci.c: uhci_result_control()
failed with status 440000
Jan  7 22:05:18 kleineronkel kernel: [d7d000c0] link (17d00062)
element (1193e1e0)
Jan  7 22:05:18 kleineronkel kernel:   0: [d193e1e0] link (1193e210)
e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=0,
PID=2d(SETUP) (buf=1f1fd2a0)
Jan  7 22:05:18 kleineronkel kernel:   1: [d193e210] link (00000001)
e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=0, PID=69(IN)
(buf=00000000)
Jan  7 22:05:18 kleineronkel kernel:
Jan  7 22:05:18 kleineronkel kernel: usb.c: USB device not accepting
new address=7 (error=-110)
Jan  7 22:05:18 kleineronkel kernel: hub.c: port 2, portstatus 103,
change 0, 12 Mb/s
Jan  7 22:05:18 kleineronkel kernel: hub.c: USB new device connect
on bus1/2, assigned device number 8
Jan  7 22:05:18 kleineronkel kernel: uhci.c: uhci_result_control()
failed with status 440000
Jan  7 22:05:18 kleineronkel kernel: [d7d000c0] link (17d00062)
element (1193e1e0)
Jan  7 22:05:18 kleineronkel kernel:   0: [d193e1e0] link (1193e210)
e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=0,
PID=2d(SETUP) (buf=1f1fd2a0)
Jan  7 22:05:18 kleineronkel kernel:   1: [d193e210] link (00000001)
e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=0, PID=69(IN)
(buf=00000000)
Jan  7 22:05:18 kleineronkel kernel:
Jan  7 22:05:18 kleineronkel kernel: usb.c: USB device not accepting
new address=8 (error=-110)

-- 
Jörn Nettingsmeier     
home://Kurfürstenstr.49.45138.Essen.Germany      
phone://+49.201.491621
http://spunk.dnsalias.org
http://www.linuxdj.com/audio/lad/

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

[Johannes Erdfelt]

It's not responding to the SETUP packet. I'd check the cable, or maybe
the connector on the motherboard.

Does it enumerate in Windows?

JE

On Mon, Jan 07, 2002, Jörn Nettingsmeier <nettings@folkwang-hochschule.de> wrote:
> btw, here's the error message i get from uhci.o
> (as opposed to usb-uhci.o, which i had pasted into my earlier post)
> 
> Jan  7 22:05:18 kleineronkel kernel: usb.c: kusbd: /sbin/hotplug add
> 6
> Jan  7 22:05:18 kleineronkel kernel: usb.c: kusbd policy returned
> 0xfffffffe
> Jan  7 22:05:18 kleineronkel kernel: hub.c: port 2 connection change
> Jan  7 22:05:18 kleineronkel kernel: hub.c: port 2, portstatus 101,
> change 1, 12 Mb/s
> Jan  7 22:05:18 kleineronkel kernel: hub.c: port 2, portstatus 103,
> change 0, 12 Mb/s
> Jan  7 22:05:18 kleineronkel kernel: hub.c: USB new device connect
> on bus1/2, assigned device number 7
> Jan  7 22:05:18 kleineronkel kernel: uhci.c: uhci_result_control()
> failed with status 440000
> Jan  7 22:05:18 kleineronkel kernel: [d7d000c0] link (17d00062)
> element (1193e1e0)
> Jan  7 22:05:18 kleineronkel kernel:   0: [d193e1e0] link (1193e210)
> e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=0,
> PID=2d(SETUP) (buf=1f1fd2a0)
> Jan  7 22:05:18 kleineronkel kernel:   1: [d193e210] link (00000001)
> e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=0, PID=69(IN)
> (buf=00000000)
> Jan  7 22:05:18 kleineronkel kernel:
> Jan  7 22:05:18 kleineronkel kernel: usb.c: USB device not accepting
> new address=7 (error=-110)
> Jan  7 22:05:18 kleineronkel kernel: hub.c: port 2, portstatus 103,
> change 0, 12 Mb/s
> Jan  7 22:05:18 kleineronkel kernel: hub.c: USB new device connect
> on bus1/2, assigned device number 8
> Jan  7 22:05:18 kleineronkel kernel: uhci.c: uhci_result_control()
> failed with status 440000
> Jan  7 22:05:18 kleineronkel kernel: [d7d000c0] link (17d00062)
> element (1193e1e0)
> Jan  7 22:05:18 kleineronkel kernel:   0: [d193e1e0] link (1193e210)
> e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=0,
> PID=2d(SETUP) (buf=1f1fd2a0)
> Jan  7 22:05:18 kleineronkel kernel:   1: [d193e210] link (00000001)
> e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=0, PID=69(IN)
> (buf=00000000)
> Jan  7 22:05:18 kleineronkel kernel:
> Jan  7 22:05:18 kleineronkel kernel: usb.c: USB device not accepting
> new address=8 (error=-110)
> 
> -- 
> Jörn Nettingsmeier     
> home://Kurfürstenstr.49.45138.Essen.Germany      
> phone://+49.201.491621
> http://spunk.dnsalias.org
> http://www.linuxdj.com/audio/lad/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

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

[Pete Zaitcev]

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

And your /proc/interrupts is ... ?

-- Pete

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

[Johannes Erdfelt]

On Mon, Jan 07, 2002, Pete Zaitcev <zaitcev@redhat.com> wrote:
> >  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

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

[Jörn Nettingsmeier]

Johannes Erdfelt wrote:
> 
> It's not responding to the SETUP packet. I'd check the cable, or maybe
> the connector on the motherboard.
> 
> Does it enumerate in Windows?

i don't have windows available for testing.

i just checked on a powerbook g3 using the ohci driver, and i get
the same errors as with uhci.o on my intel.
which rules out the mobo connector.

the cable is a slightly wobbly cradle, but this model works fine for
others.
no matter how i press or tilt the ipaq, the error is the same (i.e.
no intermittent contacts obviously). 

could it possibly be anything else ?

are there any measurements i can do on the cable ?
i would expect to have two +/- voltage supplies and two data wires.





-- 
Jörn Nettingsmeier     
home://Kurfürstenstr.49.45138.Essen.Germany      
phone://+49.201.491621
http://spunk.dnsalias.org
http://www.linuxdj.com/audio/lad/

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

[Jörn Nettingsmeier]

Johannes Erdfelt wrote:
> 
> On Mon, Jan 07, 2002, Pete Zaitcev <zaitcev@redhat.com> wrote:
> > >  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.



-- 
Jörn Nettingsmeier     
home://Kurfürstenstr.49.45138.Essen.Germany      
phone://+49.201.491621
http://spunk.dnsalias.org
http://www.linuxdj.com/audio/lad/

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

[Johannes Erdfelt]

On Mon, Jan 07, 2002, Jörn Nettingsmeier <nettings@folkwang-hochschule.de> wrote:
> Johannes Erdfelt wrote:
> > 
> > On Mon, Jan 07, 2002, Pete Zaitcev <zaitcev@redhat.com> wrote:
> > > >  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
> 
> 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

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

[Sebastian Heidl]

On Mon, Jan 07, 2002 at 09:54:50PM +0100, Jörn Nettingsmeier wrote:
> when i try to connect my ipaq to the desktop via usbnet, i see the
> following:
> 
>  kernel: hub.c: port 2, portstatus 103, change 0, 12 Mb/s
>  kernel: hub.c: USB new device connect on bus1/2, assigned device
> number 6
>  kernel: usb.c: USB device not accepting new address=6 (error=-110)
a guy over here had the same problem when using a quite long USB extension
cable for a USB-camera. whithout the extension it worked fine.

try another cable if you can.

regards,
_sh_