On Mon, 29 May 2006 12:01:02 -0300 "Luiz Fernando N. Capitulino" <[EMAIL PROTECTED]> wrote:
| | Hi Pete, | | On Fri, 26 May 2006 13:34:10 -0700 | Pete Zaitcev <[EMAIL PROTECTED]> wrote: | | | On Fri, 26 May 2006 20:22:17 +0200, Frank Gevaerts <[EMAIL PROTECTED]> wrote: | | | | > usb 1-4.5.7: USB disconnect, address 79 | | > ------------[ cut here ]------------ | | > kernel BUG at kernel/workqueue.c:110! | | | | Please let me know if this helps: | | | | --- linux-2.6.17-rc2/drivers/usb/serial/usb-serial.c 2006-04-23 21:06:18.000000000 -0700 | | +++ linux-2.6.17-rc2-lem/drivers/usb/serial/usb-serial.c 2006-05-22 21:23:29.000000000 -0700 | | @@ -162,6 +162,8 @@ static void destroy_serial(struct kref * | | } | | } | | | | + flush_scheduled_work(); /* port->work */ | | + | | usb_put_dev(serial->dev); | | | | /* free up any memory that we allocated */ | | IIUC, the problem occurred before the call to destroy_serial(), | otherwise it should be in the backtrace. | | It seems that 'port->work' is becoming NULL when the device is | disconnected, but the ipaq_write_bulk_callback() is executing after | that. Err, I meant 'port->work->entry' is empty, of course. -- Luiz Fernando N. Capitulino ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel