Vincent Pelletier <plr.vincent@xxxxxxxxx> writes: > Problem is, I could not reproduce the "Command completion event does not > match command" error either (which used to happen even on successful > boots), even without your patch. Checking my syslog, I see it did > happen with my previous kernel (vanilla 4.6.0). > Could something else since 4.6.0 have improved xhci initialisation on > 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e) > From a naive "git log drivers/usb/host/xhci*" read, > commit 3425aa03f484d45dc21e0e791c2f6c74ea656421 > Author: Mathias Nyman <mathias.nyman@xxxxxxxxxxxxxxx> > Date: Wed Jun 1 18:09:08 2016 +0300 > xhci: Fix handling timeouted commands on hosts in weird states. > caught my eye, along with some quirk reworks but I can't tell if they > could be related to the improvement. > FWIW the following log line > did not change since (at least) 4.4.0 on this machine: > xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00009810 > > So I cannot tell for sure whether your patch set improves the situation. > > What I can say though is that after about 5 boots *with* your patch is > that I had no boot failure nor xhci warnings, so at least no obvious > regression either. Thanks for testing. Looks like that root abort cause itself was fixed somewhere. I think that workaround is not needed anymore though, Mathias will decide whether removing or not. Thanks. -- OGAWA Hirofumi <hirofumi@xxxxxxxxxxxxxxxxxx> -- 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
