[Lenovo ThinkPad X230 Tablet] USB devices in docking station no longer working after resuming from long standby

[Adam Lyall]

When my Lenovo Thinkpad x230t is attached to an Ultrabase Series 3 dock and suspended for many hours, upon resume the USB ports on the dock, but not the laptop, stop working with peripherals (mouse, keyboard, usb drive).

Shorter periods of standby seem unaffected unless the issues has already occurred. E.g. After a fresh boot if I suspend my laptop and resume after less than about 8 hours (I am not at all certain if the period of time is related. Just general observation), everything will continue to work fine. If however the issue has occurred at some point and I have disconnected and reconnected to work around the issue, and then I suspend for a short period of time (20 seconds) and resume, the dock's USB ports will no longer work unless I again disconnect the laptop from the dock and reconnect. So it seems once the issue has happened it will continue to happen until I reboot.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-23-generic 3.16.0-23.31
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: magicmyth 4476 F.... pulseaudio
CurrentDesktop: KDE
Date: Fri Oct 31 12:45:03 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=9204d11f-56e2-4eff-9bae-80cd829eef89
InstallationDate: Installed on 2012-08-15 (807 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: LENOVO 3435CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=8ceeee85-b9c7-41ec-8e1c-24eb1d5e089b ro quiet splash zswap.enabled=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-23-generic N/A
 linux-backports-modules-3.16.0-23-generic N/A
 linux-firmware 1.138
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-10-25 (5 days ago)
dmi.bios.date: 05/28/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET99WW (2.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3435CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn3435CTO:pvrThinkPadX230Tablet:rvnLENOVO:rn3435CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3435CTO
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Adam Lyall, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Adam Lyall (magicmyth)]

Just tried Linux Kernel 3.18.0-031800rc2_3.18.0-031800rc2.201410262035 from the PPA which simply fails to properly boot and falls to a busybox console because for some reason it fails to find the root drive. Considering its an rc2 release it was not unexpected to run into some unrelated issues. FYI the failed boot output was:

Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system waut long enough?)
  - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/MYROOT-DRIVE-UUID does not exist. Dropping to a shell!

BusyBox v1.22.1 (Ubuntu 1:1.22.0-8ubuntu1) built-in shell (ash)

I'm now running 3.17.1-031701_3.17.1-031701.201410150735_all instead. If I don't get the issue I will report back end of next week as it takes a while for it to get triggered.

[Adam Lyall (magicmyth)]

OK so things seems worse on 3.17.1. After resuming my laptop from about 10-11 hours sleep, not only were the inputs connected to the USB docks not working, but after initial display my screen did not seem to be updating (no flashing cursor on log in screen), and the keys and trackpad on the laptop itself did not work. I disconnected the dock and reconnected but still nothing. However, the screen on my external monitor went off as expected but came back after reconnecting. I had thought maybe a hard hang had happened but with the screen coming back that seemed unlikely. I hit CTRL+ALT+F1 to switch to a terminal and nothing happened. I then disconnected again and my laptop screen jumped over to the terminal as if it had registered the CTRL+ALT+F1 previously. Connecting again showed the terminal on my external screen but still the USB keyboard connected to the dock did not work but disconnecting again I found the laptop keys were working. I logged into the terminal and ran dmesg. I then connected to the dock again and my USB keyboard and mouse started working! :-/

After logging back into the desktop I found I had no wifi. I had seen this previously while testing a version of 3.17 in the past. After flicking my wifi hard switch off/on it still did not work and dmesg showed this odd bit (I know this is another issue but adding for prosperity):
 [44576.665593] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio.
[44576.920342] usb 1-1.4: USB disconnect, device number 3
[44584.021782] iwlwifi 0000:03:00.0: RF_KILL bit toggled to enable radio.
[44584.352335] usb 1-1.4: new full-speed USB device number 5 using ehci-pci
[44584.448489] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
[44584.448494] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[44584.448497] usb 1-1.4: Product: BCM20702A0
[44584.448500] usb 1-1.4: Manufacturer: Broadcom Corp
[44584.448502] usb 1-1.4: SerialNumber: E006E6B74E8D
[44584.451317] bluetooth hci0: Direct firmware load for brcm/BCM20702A0-0a5c-21e6.hcd failed with error -2
[44584.451323] bluetooth hci0: Falling back to user helper
[44584.452125] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-21e6.hcd not found

The wifi or ethernet still did not work and ifconfig showed the interfaces were missing so I ran:
$ sudo service networking restart
$ sudo service network-manager restart

and wifi came back alive (along with the bluetooth which I had not actually checked).

So lots of fun with 3.17 :(

As for testing 3.18rc1, I am hesitant as I really don't like testing an RC1 release on my production laptop. I might still but I'll likely wait for an RC3 release to try next.

I'm attaching what my dmesg looked like after resume. If you are interested I can attach another which was run after I got the networking working again?

[Adam Lyall (magicmyth)]

I've been running Linux kernel 3.18-rc3 for 6 days and just run into the issue. I think now that the length of time a system has been running without a reboot can cause the issue as I only suspended for an hour and upon resume the usb devices on the dock were no longer working until I un-docked and re-docked. The usual dmesg errors were present:
[265522.355189] usb 1-3.4: USB disconnect, device number 8
[265524.344756] usb 1-3.4: new low-speed USB device number 9 using xhci_hcd
[265524.468746] usb 1-3.4: New USB device found, idVendor=045e, idProduct=00dd
[265524.468752] usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[265524.468755] usb 1-3.4: Product: Comfort Curve Keyboard 2000
[265524.468757] usb 1-3.4: Manufacturer: Microsoft
[265524.468983] usb 1-3.4: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[265524.468989] usb 1-3.4: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
[265524.468999] xhci_hcd 0000:00:14.0: Not enough bandwidth on HS bus for newly activated TT.
[265524.469004] xhci_hcd 0000:00:14.0: Not enough bandwidth
[265524.469011] usb 1-3.4: can't set config #1, error -12
[265539.568853] ACPI: \_SB_.GDCK: undocking
[265539.572735] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
[265539.572742] ata2: irq_stat 0x00400040, connection status changed
[265539.572749] ata2: SError: { PHYRdyChg 10B8B DevExch }
[265539.572758] ata2: hard resetting link
[265540.296949] ata2: SATA link down (SStatus 0 SControl 300)
[265545.298281] ata2: hard resetting link
[265545.618332] ata2: SATA link down (SStatus 0 SControl 300)
[265545.618341] ata2: limiting SATA link speed to 1.5 Gbps
[265546.197581] usb 1-3: USB disconnect, device number 2
[265546.197587] usb 1-3.3: USB disconnect, device number 7
[265546.197906] usb 1-3.4: USB disconnect, device number 9
[265546.823120] thinkpad_acpi: EC reports that Thermal Table has changed
[265546.926796] thinkpad_acpi: undocked from hotplug port replicator
[265546.926878] ACPI: \_SB_.GDCK: undocking

[penalvch (penalvch)]

Adam Lyall, did this problem not occur in a release prior to Utopic?

[Adam Lyall (magicmyth)]

Yes it is present in Ubuntu 14.04. If you see bug #1116525 then it seems this issue was present and affecting other users from at least Ubuntu 12.10.

[penalvch (penalvch)]

Adam Lyall, just to clarify, what is requested is when you tested in personally (not someone else on some other report) was this not reproducible prior to Trusty?

[Adam Lyall (magicmyth)]

I'm afraid I did not have the dock prior to Trusty so I have no experience with any earlier versions of Ubuntu.

[penalvch (penalvch)]

Adam Lyall, for regression testing purposes, could you please test a live environment of 12.04.0 with kernel 3.2.x (not 12.04.5 or some other variant) via http://old-releases.ubuntu.com/releases/12.04.0/ and advise to the results?

[Adam Lyall (magicmyth)]

I don't think that is going to be practical. If I get some spare time I will try a live 12.04 environment but this bug normally takes days to occur and I will just not be able to run the live environment for that long. I may be able to test the kernel from 14.04 if you have suggestions on how to do that or should I just grab the same version from the kernel PPA? However I am concerned with hardware support as I recall Intel Ivybridge based chips not being so great on 12.04. I started using Ubuntu with this laptop from 12.10.

Thanks.

[penalvch (penalvch)]

Adam Lyall, you could install just the kernel from Quantal following https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions .

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Adam Lyall (magicmyth)]

Sorry I've not been able to get back onto this yet. I currently don't have access to the dock but will in a couple of weeks and I'll do some more testing.

[Adam Lyall (magicmyth)]

Finally been able to test Linux 3.5.7 from the kernel ppa () and the same issue was there. I didn't realise there was a new bios out so I'll test that soon and I'll test Linux 3.19.

[Adam Lyall (magicmyth)]

The problem is still present with the latest Lenovo bios (2.60) and Linux 3.19.

[Adam Lyall (magicmyth)]

My dmidecode bio info:
GCETA0WW (2.60 )
09/12/2014

[penalvch (penalvch)]

Adam Lyall, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Adam Lyall (magicmyth)]

Here are the debug bits that guide asks for.

[Adam Lyall (magicmyth)]

This is the dmesg log after resuming from:
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
Note that as the usb peripherals were non-responsive as expected, after resume I had to disconnect from the dock and reconnect the laptop to it.

[penalvch (penalvch)]

Adam Lyall, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (linux-acpi) by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger-lists.html . It can take a day for the new e-mail to show up in the respective archive.

Thank you for your understanding.