"USB: use kfifo to buffer usb-generic serial writes" causes gobi_loader to hang
in [Kernel]
|
Prev: "USB: use kfifo to buffer usb-generic serial writes" causes gobi_loader to hang
Next: crypto: make Open Firmware device id constant
From: Anssi Hannula on 20 Feb 2010 11:10 On maanantai 15 helmikuu 2010 15:08:27 Oliver Neukum wrote: > Am Samstag, 13. Februar 2010 20:01:54 schrieb Anssi Hannula: > > > I'll get back to this later today, including testing with mdelay in > > > port_release with the extra sleep calls in gobi_loader. > > > > port_release is only called when the serial device is removed, so this > > has no effect here. > > But something must kill your last URB. > You are not using autosuspend are you? Don't know, usbcore has autosuspend=2 and the gobi device has autosuspend=2 and supports_autosuspend=1. > Can load usbserial with "debug=1"? Here's the end of dmesg when running with that option: http://stuff.onse.fi/gobi2000/gobi-regression.dmesg.log This is again with the gobi_loader with extra sleep added in the beginning. Otherwise it hangs (which is the actual original problem). -- Anssi Hannula -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Oliver Neukum on 20 Feb 2010 13:20 Am Samstag, 20. Februar 2010 17:03:41 schrieb Anssi Hannula: > > But something must kill your last URB. > > You are not using autosuspend are you? > > Don't know, usbcore has autosuspend=2 and the gobi device has autosuspend=2 > and supports_autosuspend=1. What is the content of "level"? > > Can load usbserial with "debug=1"? > > Here's the end of dmesg when running with that option: > http://stuff.onse.fi/gobi2000/gobi-regression.dmesg.log > > This is again with the gobi_loader with extra sleep added in the beginning. > Otherwise it hangs (which is the actual original problem). That log makes sure that the final cancellation comes from closing the file. Is that a log of a working run? Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Anssi Hannula on 21 Feb 2010 16:40 On lauantai 20 helmikuu 2010 20:19:10 Oliver Neukum wrote: > Am Samstag, 20. Februar 2010 17:03:41 schrieb Anssi Hannula: > > > But something must kill your last URB. > > > You are not using autosuspend are you? > > > > Don't know, usbcore has autosuspend=2 and the gobi device has > > autosuspend=2 and supports_autosuspend=1. > > What is the content of "level"? "on" > > > Can load usbserial with "debug=1"? > > > > Here's the end of dmesg when running with that option: > > http://stuff.onse.fi/gobi2000/gobi-regression.dmesg.log > > > > This is again with the gobi_loader with extra sleep added in the > > beginning. Otherwise it hangs (which is the actual original problem). > > That log makes sure that the final cancellation comes from closing > the file. Is that a log of a working run? No. -- Anssi Hannula -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Anssi Hannula on 21 Feb 2010 16:50 On sunnuntai 21 helmikuu 2010 23:28:54 Alan Stern wrote: > On Sat, 20 Feb 2010, Oliver Neukum wrote: > > Am Samstag, 20. Februar 2010 17:03:41 schrieb Anssi Hannula: > > > > Can load usbserial with "debug=1"? > > > > > > Here's the end of dmesg when running with that option: > > > http://stuff.onse.fi/gobi2000/gobi-regression.dmesg.log > > > > > > This is again with the gobi_loader with extra sleep added in the > > > beginning. Otherwise it hangs (which is the actual original problem). > > > > That log makes sure that the final cancellation comes from closing > > the file. Is that a log of a working run? > > Could this simply be one of those cases where the device file is closed > just after the final write URB is submitted but before it can complete, > so the URB gets cancelled and the data isn't transferred? Seems so. I don't think that is the expected behaviour though (and of course it used to work). And of course this doesn't explain why it hangs (and the WARNING) if I remove the sleep calls I added in gobi_loader. -- Anssi Hannula -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Oliver Neukum on 21 Feb 2010 17:20
Am Sonntag, 21. Februar 2010 22:42:12 schrieb Anssi Hannula: > And of course this doesn't explain why it hangs (and the WARNING) if I remove > the sleep calls I added in gobi_loader. Please tell us where you put a delay. Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |