Hmm, looks like my last two mails didn't get sent to the list. So, with some delay...
> > If you want, you could try an even finer bisection. The commit you > > identified adds a mutex_lock and a mutex_unlock, and it also changes an > > alloc_ordered_workqueue to alloc_workqueue. You could leave the mutex > > stuff out and just include the alloc_workqueue change, or vice versa. I've tried both. The kernel with just the mutex change is good. The one which only changes alloc_ordered_workqueue to alloc_workqueue is bad. Does that mean I'll have to dig into hardware specs next, to see if there's some restriction on the order in which ports must be probed or reset on that specific USB hub? Or maybe I can gather some more debug information about the initialization? As long as I'm the only one bitten by this change, I wouldn't ask to simply revert it. I'm offline for the weekend, but will follow up on suggestions next week. cheers and thanks, Roland -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
