> Date: Tue, 5 Oct 2004 11:25:04 +0200 > From: Dominik Karall <[EMAIL PROTECTED]> > To: Andrew Morton <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: 2.6.9-rc3-mm2 > > ... > i get a lot of usb errors on boot. they appear since -rc2-mm1. > below the relevant part of dmesg output.
It's safe to ignore those particular messages. The "string descriptor 0 read error: -113" messages just mean that the device is suspended, so usbcore won't even try to talk to it. The USB "suspend" state means that devices are in a low power mode; it takes at least 30 msec to return them to full power, so that the host can talk to them. That's slightly odd for a root hub, since it actually COULD talk to it (since in this case the host controller is still accessible through PCI MMIO), but not odd enough for me to want to spend time trying to add even more root hub special cases. > i'm not sure if the "Neighbour table > overflow" messages are also relevant? Not to any USB issues. Though you're getting enough of those messages to worry me, that's for sure. > ... > usb usb3: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > ... > usb usb3: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb3: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 > usb usb1: string descriptor 0 read error: -113 I've no idea what was trying so hard to read strings, but maybe those particular messages -- for suspended devices -- should get filtered out. > Neighbour table overflow. > Neighbour table overflow. > Neighbour table overflow. > Neighbour table overflow. > Neighbour table overflow. > Neighbour table overflow. > Neighbour table overflow. > Neighbour table overflow. > Neighbour table overflow. > Neighbour table overflow. > printk: 64315 messages suppressed. > > btw, no usb devices are connected. That wasn't actually what your boot messages said; it said there was a usb-storage device. Maybe that's a built-in card-reader on usb2? You'll notice that only usb1 and usb3 devices reported the "-113" errors. - Dave ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
