On Fri, 19 Jul 2013, Peter Hurley wrote: > > > As far as getting printk output from a custom kernel, I think that may > > > be beyond the reporter's capability. Perhaps one of the Ubuntu devs > > > triaging this bug could provide a test kernel for the OP with those > > > options on. > > > > > > Joseph, would you be willing to do that? > > > > Sure thing. I'll build a kernel and request that the bug reporter > > collect usbmon data. > > Thanks Joseph for building the test kernel and getting it to the reporter! > > Sarah, > > I've attached the dmesg capture supplied by the original reporter on > a 3.10 custom kernel w/ the kbuild options you requested. > > It seems as if your initial suspicion is correct: > > [ 46.785490] xhci_hcd 0000:00:14.0: Endpoint 0x81 not halted, refusing to > reset. > [ 46.785493] xhci_hcd 0000:00:14.0: Endpoint 0x82 not halted, refusing to > reset. > [ 46.785496] xhci_hcd 0000:00:14.0: Endpoint 0x83 not halted, refusing to > reset. > [ 46.785952] xhci_hcd 0000:00:14.0: Waiting for status stage event > > At this point, would you recommend proceeding with the workaround or > waiting for an xHCI bug fix? Thanks for your efforts. Seems like this might be a part of the picture, but not a complete one. Linus claims to have similar problem, but his receiver is not connected through xHCI (I got this as an off-list report, so can't really provide a pointer to ML archives). Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
