On Mon, 4 Nov 2013, Luke-Jr wrote: > On Tuesday, October 29, 2013 2:39:14 PM Alan Stern wrote: > > On Mon, 28 Oct 2013, Luke-Jr wrote: > > > https://bugzilla.kernel.org/show_bug.cgi?id=63961 > > > > > > Kernel version 3.10.15 > > > > > > [1774470.503558] hub 2-1.3:1.0: hub_port_status failed (err = -71) > > > [1774475.483021] hub 2-1.4:1.0: config failed, can't get hub status (err > > > -110) [1774475.483042] BUG: unable to handle kernel NULL pointer > > > dereference at (null) > > > [1774475.483075] IP: [<ffffffffa019b30e>] hub_quiesce+0x4e/0xb0 [usbcore] > > > > This bug has been fixed in 3.12-rc1 by commit d0308d4b6b02 (usb: fix > > cleanup after failure in hub_configure()). That commit has not been > > applied to the -stable branches. > > I'm beginning to question if this is a bug at all? That's a strange thing to say. If the kernel always gets an error in the same place and under the same circumstances, doesn't that suggest very strongly there is a bug? How else would you expect a bug to show up? > As of tonight, my kernel is > now panicing this way 100% of the time I turn my new USB3 hub on... :/ Sounds like a bug to me. Have you tried applying the commit mentioned above? If it fixes your problem, you'll know that there really was a bug. 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
