I get the following log each time I disconnect a hub (had to type it from the display, so its not complete). I do not have the problem with 2.5.64.
I see something like this also when unloading a host controller driver.
I had one of those, then it went away when I removed that check of yours that prevents disconnect() callbacks from cleaning up using usb_unlink_urb() calls! That is, a 6b6b6b6b kind of oops like you described below -- odd.
However, there's another one I'm seeing too. It seems to happen when usb-storage hits some kind of trouble, and a couple times I've seen usb_reset_device() calls on the stack. That one could be partly because of some other patches though.
- Dave
Do you have CONFIG_DEBUG_SLAB and CONFIG_KALLSYMS enabled? To me it looks like we are submitting a urb that has already been freed, and we oops in usb_submit_urb() as we are passed a pointer of 6b6b6b6b.
-------------------------------------------------------
This SF.net email is sponsored by: Tablet PC. Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
