On 05.09.2016 19:46, Hasan Mahmood wrote:
System reboots instead of shutting down if xhci is enabled in BIOS and USB hub is connected When I connect the usb hub built into my monitor (http://www.samsung.com/uk/support/model/LS27D85KTSN/XU), the system will reboot instead of shutting down when I do a shut down. If I disable XCHI in the BIOS, the problem does not happen. If I disconnect the hub and enable XHCI, the problem does not occur. Possibly related bugs: https://bugzilla.kernel.org/show_bug.cgi?id=76291 https://bugzilla.kernel.org/show_bug.cgi?id=66171 dmi.bios.date: 06/06/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0358.2016.0606.1423 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-503 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0358.2016.0606.1423:bd06/06/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr: $ cat /proc/version Linux version 4.8.0-040800rc5-lowlatency (kernel@tangerine) (gcc version 6.2.0 20160830 (Ubuntu 6.2.0-2ubuntu11) ) #201609041832 SMP PREEMPT Sun Sep 4 22:38:41 UTC 2016 launchpad bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1606030
Launchpad bug shows you machine has a Wildcat Point-LP USB xHCI Controller [8086:9cb1] Launcpad dmesg log also show xhci loads with quirks 0x00009810 missing XHCI_SPURIOUS_REBOOT and XHCI_SPURIOUS_WAKEUP quirks xHCI on Wildcat point-LP should be quite similar to Lynxpoint-LP xHCI, but driver does not set the quirks as they depend on xHCI Lynxpoint PCI device ID Can you try reloading xhci with those quirks (BIT 13 and BIT 18) In your case the old + new quirks should be 0x0004b810 Something like this should do it: sudo modprobe -r xhci_pci sudo modprobe xhci_hcd quirks=0x0004b810 sudo modprobe xhci_pci (see from dmesg xhci loaded properly and with the new quirks) try to shutdown with hub connected -Mathias -- 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