Re: USB device not accepting new address...

From: Stephen L Johnson <sjohnson.a.t.monsters.org>
Date: Tue Jul 17 2001 - 12:04:57 EDT

> I get this in my RedHat /var/log/messages from time to time:
>
> Jul 17 16:03:45 beastie kernel: hub.c: USB new device connect on bus2/1,
> assigned device number 7
> Jul 17 16:03:45 beastie kernel: usb-uhci.c: interrupt, status 2, frame# 836
> Jul 17 16:03:45 beastie kernel: usb.c: USB device not accepting new
> address=7 (error=-110)
>
> It is usually when I restart networking on my RedHat box, not sure if it
> happens when I unplug the iPAQ from the USB cradle first though.
>
> If I reboot my iPAQ and configure everything from scratch it is ok - but I
> figure there must be a more elegant method. I noticed that I couldn't rmmod
> the the usb modules on the iPAQ under this condition - the modules are
> reported as busy.
>
> Any clues?
>
> Paul

I get these errors also. I've tracked is down to suspending pending my iPAQ. After a wake I get these errors.

I take own the usbf interface, unload the usb-eth module, load the usb-eth module and configure the usbf interface to clear the problem. I've got a small script in a menu entry to do automate it.

Stephen L Johnson <sjohnson@monsters.org>
Received on Tue Jul 17 08:58:38 2001

This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:38:27 EDT