On Sat, 13 Feb 2010, Anssi Hannula wrote: > On 05.02.2010 23:59, Oliver Neukum wrote: > > Am Freitag, 5. Februar 2010 20:58:17 schrieb Matthew Garrett: > >> drivers/usb/serial/usb-serial.c: usb_serial_port_work - port 0 > >> drivers/usb/serial/usb-serial.c: serial_write - port 0, 2048 byte(s) > >> drivers/usb/serial/generic.c: usb_serial_generic_write - port 0, 2048 bytes > >> drivers/usb/serial/generic.c: usb_serial_generic_write - put 512 bytes into fifo > >> drivers/usb/serial/usb-serial.c: serial_write - port 0, 1536 byte(s) > >> drivers/usb/serial/generic.c: usb_serial_generic_write - port 0, 1536 bytes > >> drivers/usb/serial/generic.c: usb_serial_generic_write - put 0 bytes into fifo > >> drivers/usb/serial/generic.c: usb_serial_generic_write - FIFO is full > > > > OK, could you also get an usbmon trace? This would allow a determination > > whether the submitted URB doesn't finish for some reason, or whether > > no URB is submitted, possibly because a wakeup is missed. > > I'm also affected by this regression. Here's an usbmon trace of > gobi_loader hanging: > http://stuff.onse.fi/gobi2000/gobi-regression.mon.log That's odd. The log shows the final bulk-OUT transfer was cancelled after less than 1 ms. Is there a timeout value somewhere that is too small by a factor of 1000? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
