On Fri, 26 Feb 2016, Radosław Warowny wrote: > > I agree, but where was a crash? I don't have any context here, was > > there a kernel oops somewhere? I thought the hub just reset itself. I > > have a hub like that here, it resets itself a few times a day, but > > there's no kernel crash because of it. > > Yes, there were kernel oopses, you can find details at syslog output > attached to the bug report: > https://bugzilla.kernel.org/show_bug.cgi?id=112311. I don't cite it > here since it's too large. I provided two versions of logs - with and > without apparmor to exclude it as a cause of problem since there is > some apparmor call at the first call trace. It's worth noting that none of the stack traces in that bug report mentions USB anywhere. In every case the problem occurred during memory allocation for something else. 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
