Hmm...I don't know why, but I don't get those error messages again. But I didn't changed anything on my system, like disconnecting any usb device, etc. Here is the output of the usb debug messages:
"dmesg | grep usb": usb_get_descriptor:type=1, index=0, i=0, result=18 usb_get_descriptor:type=2, index=0, i=0, result=9 usb_get_descriptor:type=2, index=0, i=0, result=25 usb_get_descriptor:type=1, index=0, i=0, result=18 usb_get_descriptor:type=2, index=0, i=0, result=9 usb_get_descriptor:type=2, index=0, i=0, result=25 usb_get_descriptor:type=1, index=0, i=0, result=18 usb_get_descriptor:type=2, index=0, i=0, result=9 usb_get_descriptor:type=2, index=0, i=0, result=25 usb_get_descriptor:type=1, index=0, i=0, result=18 usb_get_descriptor:type=2, index=0, i=0, result=9 usb_get_descriptor:type=2, index=0, i=0, result=25 usbcore: registered new driver cdc_acm drivers/usb/class/cdc-acm.c: v0.23:USB Abstract Control Model driver for USB modems and ISDN adapters usbcore: registered new driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver usbcore: registered new driver usb-storage usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver usb 3-1: new full speed USB device using address 2 usb_get_descriptor:type=1, index=0, i=0, result=8 usb_get_descriptor:type=1, index=0, i=0, result=18 usb_get_descriptor:type=2, index=0, i=0, result=9 usb_get_descriptor:type=2, index=0, i=0, result=39 usb_get_descriptor:type=3, index=0, i=0, result=4 usb 4-1: new full speed USB device using address 2 usb_get_descriptor:type=1, index=0, i=0, result=8 usb_get_descriptor:type=1, index=0, i=0, result=18 usb_get_descriptor:type=6, index=0, i=0, result=-32 usb_get_descriptor:type=6, index=0, i=1, result=-32 usb_get_descriptor:type=6, index=0, i=2, result=-32 usb_get_descriptor:type=2, index=0, i=0, result=9 usb_get_descriptor:type=2, index=0, i=0, result=32 drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x03F0 pid 0x7004 usb_get_descriptor:type=3, index=0, i=0, result=4 usb_get_descriptor:type=3, index=0, i=0, result=4 usb_get_descriptor:type=3, index=0, i=0, result=4 usb_get_descriptor:type=3, index=0, i=0, result=4 usb_get_descriptor:type=3, index=0, i=0, result=4 Maybe you can find anything useful, if I can reproduce the error again, I will post it on the list! greets dominik On Monday 14 June 2004 20:21, Alan Stern wrote: > On Mon, 14 Jun 2004, Dominik Karall wrote: > > OK, I greped through the usb sources and searched for the message string, > > so I get a match in drivers/usb/core/message.c. > > I removed the message.c patch from -mm2 patch and it works now without > > those error messages. > > > > @William > > thx for your explanation! :) > > That's something I wrote. It's hard to see how it could cause problems, > but... > > Try applying this test patch to the -mm2 kernel. The output should let us > know what's really going on. > > Alan Stern > > > ===== drivers/usb/core/message.c 1.92 vs edited ===== > --- 1.92/drivers/usb/core/message.c Fri Jun 11 07:49:33 2004 > +++ edited/drivers/usb/core/message.c Mon Jun 14 14:17:18 2004 > @@ -577,6 +577,8 @@ > USB_REQ_GET_DESCRIPTOR, USB_DIR_IN, > (type << 8) + index, 0, buf, size, > HZ * USB_CTRL_GET_TIMEOUT); > + printk(KERN_INFO "%s: type=%d, index=%d, i=%d, result=%d\n", > + __FUNCTION__, type, index, i, result); > if (!(result == 0 || result == -EPIPE)) > break; > } ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
