Re: [BUG] SD card reader disappears after suspend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



As requested by Chen Yu on bugzilla, I added no_console_suspend=1 to
the kernel cmdline and updated to the (roughly) latest kernel,
4.14.14-1-ARCH.

Here's the new log:
https://pastebin.com/buhEMyKk

>From a quick comparison with the old log I don't see any significant
difference, except that these messages

[   32.671107] xhci_hcd 0000:00:14.0: Cannot set link state.
[   32.671112] usb usb2-port4: cannot disable (err = -32)
[   32.671153] xhci_hcd 0000:00:14.0: Cannot set link state.
[   32.671157] usb usb2-port4: cannot disable (err = -32)

don't repeat forever.

2018-01-19 10:52 GMT+01:00 Samuel Sadok <samuel.sadok@xxxxxxxxxx>:
> Hi!
> I just noticed I hit the wrong reply button.
> Here's what I replied to Alexander:
>
> I just tried `echo 0 > /sys/bus/usb/devices/2-4/power/persist`,
> however the card reader is still missing after suspend/resume.
>
> Here's the new kernel log:
> [ 2241.861114] pcieport 0000:00:1c.3: Enabling MPC IRBNCE
> [ 2241.861120] pcieport 0000:00:1c.3: Intel PCH root port ACS workaround enabled
> [ 2241.915528] PM: suspend entry (deep)
> [ 2241.915529] PM: Syncing filesystems ... done.
> [ 2241.925562] Freezing user space processes ... (elapsed 0.001 seconds) done.
> [ 2241.926816] OOM killer disabled.
> [ 2241.926817] Freezing remaining freezable tasks ... (elapsed 0.000
> seconds) done.
> [ 2241.927583] Suspending console(s) (use no_console_suspend to debug)
> [ 2241.927818] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [ 2241.931991] sd 0:0:0:0: [sda] Stopping disk
> [ 2244.178848] thunderbolt 0000:08:00.0: suspending...
> [ 2244.179533] thunderbolt 0000:08:00.0: suspend finished
> [ 2244.179535] thunderbolt 0000:08:00.0: stopping RX ring 0
> [ 2244.179541] thunderbolt 0000:08:00.0: disabling interrupt at
> register 0x38200 bit 12 (0x1001 -> 0x1)
> [ 2244.179547] thunderbolt 0000:08:00.0: stopping TX ring 0
> [ 2244.179552] thunderbolt 0000:08:00.0: disabling interrupt at
> register 0x38200 bit 0 (0x1 -> 0x0)
> [ 2244.179555] thunderbolt 0000:08:00.0: control channel stopped
> [ 2245.127874] ACPI: Preparing to enter system sleep state S3
> [ 2245.147745] ACPI: EC: event blocked
> [ 2245.147746] ACPI: EC: EC stopped
> [ 2245.147746] PM: Saving platform NVS memory
> [ 2245.147751] Disabling non-boot CPUs ...
> [ 2245.176484] smpboot: CPU 1 is now offline
> [ 2245.218761] smpboot: CPU 2 is now offline
> [ 2245.261380] smpboot: CPU 3 is now offline
> [ 2245.289072] smpboot: CPU 4 is now offline
> [ 2245.319017] smpboot: CPU 5 is now offline
> [ 2245.345797] smpboot: CPU 6 is now offline
> [ 2245.362552] smpboot: CPU 7 is now offline
> [ 2245.393870] ACPI: Low-level resume complete
> [ 2245.393931] ACPI: EC: EC started
> [ 2245.393932] PM: Restoring platform NVS memory
> [ 2245.396492] Enabling non-boot CPUs ...
> [ 2245.396546] x86: Booting SMP configuration:
> [ 2245.396547] smpboot: Booting Node 0 Processor 1 APIC 0x2
> [ 2245.476842]  cache: parent cpu1 should not be sleeping
> [ 2245.660075] CPU1 is up
> [ 2245.660120] smpboot: Booting Node 0 Processor 2 APIC 0x4
> [ 2245.733856]  cache: parent cpu2 should not be sleeping
> [ 2245.908088] CPU2 is up
> [ 2245.908132] smpboot: Booting Node 0 Processor 3 APIC 0x6
> [ 2245.977616]  cache: parent cpu3 should not be sleeping
> [ 2246.147615] CPU3 is up
> [ 2246.147661] smpboot: Booting Node 0 Processor 4 APIC 0x1
> [ 2246.154023]  cache: parent cpu4 should not be sleeping
> [ 2246.154213] CPU4 is up
> [ 2246.154236] smpboot: Booting Node 0 Processor 5 APIC 0x3
> [ 2246.218683]  cache: parent cpu5 should not be sleeping
> [ 2246.408703] CPU5 is up
> [ 2246.408730] smpboot: Booting Node 0 Processor 6 APIC 0x5
> [ 2246.474887]  cache: parent cpu6 should not be sleeping
> [ 2246.691669] CPU6 is up
> [ 2246.691698] smpboot: Booting Node 0 Processor 7 APIC 0x7
> [ 2246.762074]  cache: parent cpu7 should not be sleeping
> [ 2247.013633] CPU7 is up
> [ 2247.091979] ACPI: Waking up from system sleep state S3
> [ 2247.152327] pcieport 0000:00:1c.0: Enabling MPC IRBNCE
> [ 2247.152330] pcieport 0000:00:1c.0: Intel PCH root port ACS workaround enabled
> [ 2247.152552] pcieport 0000:07:04.0: quirk: waiting for thunderbolt
> to reestablish PCI tunnels...
> [ 2247.152568] pcieport 0000:07:03.0: quirk: waiting for thunderbolt
> to reestablish PCI tunnels...
> [ 2247.152570] pcieport 0000:07:05.0: quirk: waiting for thunderbolt
> to reestablish PCI tunnels...
> [ 2247.152633] pcieport 0000:07:06.0: quirk: waiting for thunderbolt
> to reestablish PCI tunnels...
> [ 2247.168603] pcieport 0000:00:1c.3: Enabling MPC IRBNCE
> [ 2247.168609] pcieport 0000:00:1c.2: Enabling MPC IRBNCE
> [ 2247.168610] pcieport 0000:00:1c.3: Intel PCH root port ACS workaround enabled
> [ 2247.168616] pcieport 0000:00:1c.2: Intel PCH root port ACS workaround enabled
> [ 2247.168730] thunderbolt 0000:08:00.0: control channel starting...
> [ 2247.168733] thunderbolt 0000:08:00.0: starting TX ring 0
> [ 2247.168748] thunderbolt 0000:08:00.0: enabling interrupt at
> register 0x38200 bit 0 (0x0 -> 0x1)
> [ 2247.168750] thunderbolt 0000:08:00.0: starting RX ring 0
> [ 2247.168766] thunderbolt 0000:08:00.0: enabling interrupt at
> register 0x38200 bit 12 (0x1 -> 0x1001)
> [ 2247.168770] thunderbolt 0000:08:00.0: resuming...
> [ 2247.168771] thunderbolt 0000:08:00.0: resetting switch at 0
> [ 2247.176388] thunderbolt 0000:08:00.0: 0: resuming switch
> [ 2247.176883] thunderbolt 0000:08:00.0: resume finished
> [ 2247.228522] pcieport 0000:00:1c.4: Enabling MPC IRBNCE
> [ 2247.228525] pcieport 0000:00:1c.4: Intel PCH root port ACS workaround enabled
> [ 2247.229197] usb usb1: root hub lost power or was reset
> [ 2247.229200] usb usb2: root hub lost power or was reset
> [ 2247.229265] ACPI: EC: event unblocked
> [ 2247.229322] ACPI: button: The lid device is not compliant to SW_LID.
> [ 2247.239446] sd 0:0:0:0: [sda] Starting disk
> [ 2247.269903] thunderbolt 0000:08:00.0: resetting error on 0:b.
> [ 2247.269909] thunderbolt 0000:08:00.0: 0:b: hotplug: scanning
> [ 2247.269910] thunderbolt 0000:08:00.0: resetting error on 0:c.
> [ 2247.269911] thunderbolt 0000:08:00.0: 0:b: hotplug: no switch found
> [ 2247.269912] thunderbolt 0000:08:00.0: 0:c: hotplug: scanning
> [ 2247.269913] thunderbolt 0000:08:00.0: 0:c: hotplug: no switch found
> [ 2247.335049] pciehp 0000:07:00.0:pcie204: Device 0000:08:00.0
> already exists at 0000:08:00, cannot hot-add
> [ 2247.335050] pciehp 0000:07:00.0:pcie204: Cannot add device at 0000:08:00
> [ 2247.516486] nouveau 0000:01:00.0: devinit: 0x000066e5[0]: script
> needs OR link
> [ 2247.551596] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
> [ 2247.551821] ata1.00: unexpected _GTF length (8)
> [ 2247.552111] ata1.00: unexpected _GTF length (8)
> [ 2247.552184] ata1.00: configured for UDMA/133
> [ 2247.578434] usb 1-12: reset full-speed USB device number 3 using xhci_hcd
> [ 2247.726451] xhci_hcd 0000:00:14.0: dma_pool_free buffer-512,
> ffff8f811c411000/ffc99000 (bad dma)
> [ 2247.841749] usb 1-8: reset full-speed USB device number 2 using xhci_hcd
> [ 2248.268557] usb 1-8.3: reset full-speed USB device number 6 using xhci_hcd
> [ 2250.335295] pciehp 0000:00:1c.0:pcie004: link training error: status 0x1001
> [ 2250.335298] pciehp 0000:00:1c.0:pcie004: Failed to check link status
> [ 2250.335413] usb 1-8.3:1.0: rebind failed: -517
> [ 2250.335472] usb 1-12:1.2: rebind failed: -517
> [ 2250.335729] OOM killer enabled.
> [ 2250.335730] Restarting tasks ...
> [ 2250.341038] input: bcm5974 as
> /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.2/input/input16
> [ 2250.343289] done.
> [ 2250.456189] PM: suspend exit
> [ 2250.456361] Bluetooth: hci0: BCM: chip id 73 build 1068
> [ 2250.457380] Bluetooth: hci0: BCM: product 05ac:8289
> [ 2250.458357] Bluetooth: hci0: BCM: features 0x07
> [ 2250.474387] Bluetooth: hci0: makkintosshu
> [ 2254.375591] usb usb2-port4: Cannot enable. Maybe the USB cable is bad?
> [ 2254.375607] xhci_hcd 0000:00:14.0: Cannot set link state.
> [ 2254.375612] usb usb2-port4: cannot disable (err = -32)
> [ 2254.375616] usb 2-4: USB disconnect, device number 2
> [ 2258.582517] usb usb2-port4: Cannot enable. Maybe the USB cable is bad?
> [ 2258.582535] xhci_hcd 0000:00:14.0: Cannot set link state.
> [ 2258.582542] usb usb2-port4: cannot disable (err = -32)
> [ 2262.622680] usb usb2-port4: Cannot enable. Maybe the USB cable is bad?
> [ 2262.622701] xhci_hcd 0000:00:14.0: Cannot set link state.
> [ 2262.622710] usb usb2-port4: cannot disable (err = -32)
> [ 2266.662754] usb usb2-port4: Cannot enable. Maybe the USB cable is bad?
> [ 2266.662771] xhci_hcd 0000:00:14.0: Cannot set link state.
> [ 2266.662778] usb usb2-port4: cannot disable (err = -32)
> [ 2270.702747] usb usb2-port4: Cannot enable. Maybe the USB cable is bad?
> [ 2270.702757] xhci_hcd 0000:00:14.0: Cannot set link state.
> [ 2270.702760] usb usb2-port4: cannot disable (err = -32)
> [ 2274.742886] usb usb2-port4: Cannot enable. Maybe the USB cable is bad?
> [ 2274.742899] xhci_hcd 0000:00:14.0: Cannot set link state.
> [ 2274.742902] usb usb2-port4: cannot disable (err = -32)
>
> There are some messages missing in this log that were present in the
> original log. In particular:
> [ 38.002847] usb 2-4: Disable of device-initiated U1 failed.
> [ 38.002854] usb 2-4: Disable of device-initiated U2 failed.
> [ 38.002856] usb 2-4: usb_reset_and_verify_device Failed to disable LTM
>
> 2018-01-02 8:55 GMT+01:00 Alexander Kappner <agk@xxxxxxxxxxx>:
>> I've seen similar issues caused by USB persist. Try disabling it (echo 0 > /sys/bus/usb/devices/<your card reader>/power/persist), and then resuming.
>>
>> On 01/01/2018 10:53 PM, Samuel Sadok wrote:
>>> Hello!
>>>
>>> I'm observing a bug where the most prominent symptom is that the
>>> built-in SD card reader disappears after waking up from suspend.
>>>
>>> Laptop: MacBookPro11,3
>>> USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
>>> USB xHCI (rev 05) (prog-if 30 [XHCI])
>>> SD card reader: Apple Card Reader 05ac:8406
>>>
>>> The bug was reported previously on bugzilla but never followed up on:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=111201
>>>
>>>
>>> Steps to reproduce:
>>> $ lsusb
>>> Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 001 Device 006: ID 05ac:8289 Apple, Inc.
>>> Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub
>>> (part of BCM2046 Bluetooth)
>>> Bus 001 Device 003: ID 05ac:0263 Apple, Inc. Apple Internal Keyboard /
>>> Trackpad (MacBook Retina)
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> $ sudo systemctl suspend
>>> [Wait 10s, then wake the system up]
>>> $ lsusb
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 001 Device 006: ID 05ac:8289 Apple, Inc.
>>> Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub
>>> (part of BCM2046 Bluetooth)
>>> Bus 001 Device 003: ID 05ac:0263 Apple, Inc. Apple Internal Keyboard /
>>> Trackpad (MacBook Retina)
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> $ lsusb -vvv
>>>
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> [long hang, on the order of three minutes]
>>> can't get hub descriptor, LIBUSB_ERROR_TIMEOUT (Resource temporarily
>>> unavailable)
>>> [and a couple of more errors]
>>>
>>> Expected result:
>>> The output of both lsusb commands should be equal.
>>>
>>> Actual results:
>>>  - The SD card reader (05ac:8406) is missing from the second lsusb.
>>>  - Running lsusb -vvv hangs for a long time
>>>  - lots of error messages in kernel log
>>>
>>> Logs:
>>> https://gist.github.com/samuelsadok/6d7b3e3015d3370a92ed4702e4d3c4b5
>>>
>>> I'm happy to provide more data, do tests or patch around the kernel if it helps.
>>>
>>> Best,
>>> Samuel
>>> --
>>> 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
>>>
--
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



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux