On 28.01.2016 17:05, Oliver Neukum wrote:
Hi, with the latest kernels I tested devices connected to XHCI are gone after resume. The ports are not resumed. An error is in dmesg: [ 614.639506] sd 5:0:0:0: [sdc] Starting disk [ 614.672568] xhci_hcd 0000:00:14.0: port 7 resume PLC timeout [ 614.695152] xhci_hcd 0000:00:14.0: port 6 resume PLC timeout [ 614.716345] xhci_hcd 0000:00:14.0: port 4 resume PLC timeout [ 614.906969] iwlwifi 0000:5c:00.0: L1 Enabled - LTR Disabled [ 614.913933] iwlwifi 0000:5c:00.0: L1 Enabled - LTR Disabled [ 614.914034] iwlwifi 0000:5c:00.0: Radio type=0x1-0x2-0x0 [ 614.942266] usb 3-5: reset full-speed USB device number 3 using xhci_hcd [ 614.988670] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 614.988706] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 614.988719] ata4: SATA link down (SStatus 0 SControl 300) [ 614.988749] ata3: SATA link down (SStatus 0 SControl 300) [ 614.990735] ata6.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) [ 614.990830] ata6.00: supports DRM functions and may not be fully accessible [ 614.990920] ata6.00: failed to get NCQ Send/Recv Log Emask 0x1 [ 614.991108] ata6.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) [ 614.991126] ata6.00: supports DRM functions and may not be fully accessible [ 614.991159] ata6.00: failed to get NCQ Send/Recv Log Emask 0x1 [ 614.991188] ata6.00: configured for UDMA/133 [ 615.114778] ata2.00: configured for UDMA/100 [ 615.182266] usb 3-8: reset high-speed USB device number 6 using xhci_hcd [ 615.422230] usb 3-7: reset high-speed USB device number 5 using xhci_hcd [ 616.070075] rtc_cmos 00:04: System wakeup disabled by ACPI Bisecting this failed as I ran into a period the kernel crashes due to S3 git bisect start # bad: [7c553985c6749d9311552d529108104f83b97bc7] Merge branch 'usb-testing' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb into usb-testing git bisect bad 7c553985c6749d9311552d529108104f83b97bc7 # good: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4
So everything was fine with 4.4 still? I just saw that there are changes in PM allowing usb devices to stay suspended if we enter suspend with devices runtime suspended, not sure if that has an impat. Was this limited to USB2 or USB3 devices? -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
