USB 3 hangup during file transfer

[klerai]

During file transfer (rsync) over a powered USB 3 hub from sda to sdb, the kernel disconnects the USB channel after a few minutes. The board needs be rebooted.

The failure occurs with the first message in the kernel log (more details further down):
Feb 26 14:26:30 r64omv kernel: core: dev_pm_opp_get_voltage: Invalid parameters

• messages displayed on the terminal during rsync session:

  Message from syslogd@r64omv at Feb 26 14:27:37 ...
  kernel:[ 1440.377657] Kernel panic - not syncing: hung_task: blocked tasks

  Message from syslogd@r64omv at Feb 26 14:27:38 ...
  kernel:[ 1440.849084] Kernel Offset: disabled

  Message from syslogd@r64omv at Feb 26 14:27:38 ...
  kernel:[ 1440.851529] Memory Limit: none

• journalctl -k
  Feb 26 14:21:13 r64omv kernel: sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
  Feb 26 14:21:13 r64omv kernel: sdb: sdb1
  Feb 26 14:21:13 r64omv kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk
  Feb 26 14:21:13 r64omv kernel: BTRFS: device label DATA devid 1 transid 23 /dev/sdb1
  Feb 26 14:21:13 r64omv kernel: BTRFS info (device sdb1): disk space caching is enabled
  Feb 26 14:21:13 r64omv kernel: BTRFS: has skinny extents
  Feb 26 14:26:30 r64omv kernel: core: dev_pm_opp_get_voltage: Invalid parameters
  Feb 26 14:26:30 r64omv kernel: mali-utgard ff300000.gpu: Failed to get voltage for frequency 163840000: -34
  Feb 26 14:26:30 r64omv kernel: devfreq ff300000.gpu: Couldn't update frequency transition information.
  Feb 26 14:28:05 r64omv kernel: xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.
  Feb 26 14:28:05 r64omv kernel: xhci-hcd xhci-hcd.8.auto: Assuming host is dying, halting host.
  Feb 26 14:28:05 r64omv kernel: xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.
  Feb 26 14:28:05 r64omv kernel: xhci-hcd xhci-hcd.8.auto: Assuming host is dying, halting host.
  Feb 26 14:28:05 r64omv kernel: xhci-hcd xhci-hcd.8.auto: Host not halted after 16000 microseconds.
  Feb 26 14:28:05 r64omv kernel: hub 5-1.1:1.0: hub_port_status failed (err = -22)
  Feb 26 14:28:05 r64omv kernel: xhci-hcd xhci-hcd.8.auto: HC died; cleaning up
  Feb 26 14:28:05 r64omv kernel: usb 5-1.1-port1: cannot reset (err = -22)
  Feb 26 14:28:05 r64omv kernel: usb 5-1.1-port1: cannot reset (err = -22)
  Feb 26 14:28:05 r64omv kernel: usb 5-1.1-port1: cannot reset (err = -22)
  Feb 26 14:28:05 r64omv kernel: usb 5-1.1-port1: cannot reset (err = -22)
  Feb 26 14:28:05 r64omv kernel: usb 5-1.1-port1: cannot reset (err = -22)
  Feb 26 14:28:05 r64omv kernel: usb 5-1.1-port1: Cannot enable. Maybe the USB cable is bad?

[Linux-cpp-lisp]

Can reproduce, having the same problem. Seems to only happen during periods of heavy writing; when I only run my read-heavy task things seem to be fine. I have two USB 3.0 hard drives on an unpowered hub attached to the USB 3.0 port on the Rock64. These errors make both of them malfunction, even though I'm only writing to one.

I've attached a more complete log, but I'm seeing many of the same error messages as @klerai above:

core: dev_pm_opp_get_voltage: Invalid parameters
[106534.429998] mali-utgard ff300000.gpu: Failed to get voltage for frequency 163840000: -34

Followed by some:

[107314.389632] usb 5-1-port1: cannot reset (err = -108)
[107314.389634] usb 5-1-port1: Cannot enable. Maybe the USB cable is bad?

And finally a large pile of Ext4 errors.

[xalius]

Have you eliminated power supply problems (also on the hub), the USB3 spec only allows up to 900mA per port...

[Linux-cpp-lisp]

I'm running three wall powered (have their own individual power supply) desktop hard drives off of an unpowered hub. I was under the impression that there wouldn't be any power draw (except for maybe the hub's status light), and that power wouldn't be the issue, but I'm no electrical engineer, so that may not be true.

It may also be relevant that, upon rebooting, one or two of the drives will often not be recognized as connected (i.e. don't show up in the output of sudo blkid), and have to be physically reattached to be recognized by the system.

[klerai]

The USB 3.0 power specs were taken in consideration. Beside the Rock board with its standard power adapter, my USB in use is powered by its own 4 A power supply.

All tests runs were duplicated on a Gigabyte BRX i5 desktop machine (flawlessly).

The following tests were executed

• with a pair of 2.5" 4TB external Seagate disks (data volume around 1.6 TB).
• one 2.5" 4TB external Seagate disk and 1 64GB USB flash drive
• two 64 GB USB flash drive
  using rsync -av /srv/dev1/* /srv/dev2/

My initial work was done on the Rock64 with release 0.5.14: jenkins-linux-build-rock-64-133. - It ended with the errors reported in my first message.
After I recognizing that a newer version 0.5.15: jenkins-linux-build-rock-64-136, which initially seemed to have solved the USB dropouts. I was able to run an initial backup from the first to the second Seagate disk. But sub sequential runs on modified content failed.

My experiences with other systems showed that USB dropouts of external disks are usually handled by the kernel as soon the sub-system becomes back online, while the hub stays online. But with the Rock64, the whole USB channel disappears no unplug or re-plugin helps. The board has to go through a complete reboot.

Below are my relevant kernel messages.

====
-- from boot-up...
Apr 07 21:14:05 r64omv kernel: Linux version 4.4.77-rockchip-ayufan-136 (root@713b8312374e)
..
Apr 07 21:14:05 r64omv kernel: Kernel command line: earlycon=uart8250,mmio32,0xff130000 rw root=LABEL=linux-root rootwait rootfstype=ext4
..
Apr 07 21:14:05 r64omv kernel: sched-energy: CPU device node has no sched-energy-costs
Apr 07 21:14:05 r64omv kernel: Invalid sched_group_energy for CPU0
...
Apr 07 21:14:05 r64omv kernel: genirq: Setting trigger mode 8 for irq 176 failed (gic_set_type+0x0/0x68)
..
Apr 07 21:14:05 r64omv kernel: rockchip-thermal ff250000.tsadc: Missing tshut mode property, using default (cru)
Apr 07 21:14:05 r64omv kernel: rockchip-thermal ff250000.tsadc: Missing tshut-polarity property, using default (low)
..
Apr 07 21:14:05 r64omv systemd[1]: Failed to insert module 'autofs4'
..
Apr 07 21:14:15 r64omv kernel: usb 5-1.1.1: New USB device found, idVendor=0bc2, idProduct=61b7
Apr 07 21:14:15 r64omv kernel: usb 5-1.1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
..
Apr 07 21:14:15 r64omv kernel: usb 5-1.1.1: UAS is blacklisted for this device, using usb-storage instead
..
Apr 07 21:14:05 r64omv kernel: rockchip-thermal ff250000.tsadc: Missing tshut mode property, using default (cru)
Apr 07 21:14:05 r64omv kernel: rockchip-thermal ff250000.tsadc: Missing tshut-polarity property, using default (low)
..
Apr 07 21:14:05 r64omv systemd[1]: Failed to insert module 'autofs4'

==================================================
===> and this is the kernel log after the USB channel drops out
Apr 7 15:10:46 r64omv kernel: [ 31.872062] rk_gmac-dwmac ff540000.eth eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Apr 7 16:28:08 r64omv kernel: [ 4655.943883] xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.
Apr 7 16:28:08 r64omv kernel: [ 4655.944763] xhci-hcd xhci-hcd.8.auto: Assuming host is dying, halting host.
Apr 7 16:28:08 r64omv kernel: [ 4655.945499] xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.
Apr 7 16:28:08 r64omv kernel: [ 4655.946354] xhci-hcd xhci-hcd.8.auto: Assuming host is dying, halting host.
Apr 7 16:28:08 r64omv kernel: [ 4655.968853] xhci-hcd xhci-hcd.8.auto: Host not halted after 16000 microseconds.
Apr 7 16:28:08 r64omv kernel: [ 4655.969628] xhci-hcd xhci-hcd.8.auto: Non-responsive xHCI host is not halting.
Apr 7 16:28:08 r64omv kernel: [ 4655.970388] xhci-hcd xhci-hcd.8.auto: Completing active URBs anyway.
Apr 7 16:28:08 r64omv kernel: [ 4655.970436] xhci-hcd xhci-hcd.8.auto: Host not halted after 16000 microseconds.
Apr 7 16:28:08 r64omv kernel: [ 4655.971836] xhci-hcd xhci-hcd.8.auto: Non-responsive xHCI host is not halting.
Apr 7 16:28:08 r64omv kernel: [ 4655.972597] xhci-hcd xhci-hcd.8.auto: Completing active URBs anyway.
Apr 7 16:28:08 r64omv kernel: [ 4655.973306] xhci-hcd xhci-hcd.8.auto: HC died; cleaning up
Apr 7 16:28:08 r64omv kernel: [ 4655.973311] xhci-hcd xhci-hcd.8.auto: HC died; cleaning up
Apr 7 16:28:08 r64omv kernel: [ 4655.973346] hub 5-1.1:1.0: hub_port_status failed (err = -108)
Apr 7 16:28:08 r64omv kernel: [ 4655.973401] usb 5-1.1.1: USB disconnect, device number 4
Apr 7 16:28:08 r64omv kernel: [ 4655.978022] usb 4-1: USB disconnect, device number 6
Apr 7 16:28:08 r64omv kernel: [ 4655.978579] usb 4-1.1: USB disconnect, device number 7
Apr 7 16:28:08 r64omv kernel: [ 4655.980772] usb 5-1: USB disconnect, device number 2
Apr 7 16:28:08 r64omv kernel: [ 4655.981408] usb 5-1.1: USB disconnect, device number 3
Apr 7 16:28:08 r64omv kernel: [ 4655.981929] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
Apr 7 16:28:08 r64omv kernel: [ 4655.981937] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 6e 7c 26 00 00 00 00 f0 00 00

[Linux-cpp-lisp]

It's also quite clear that this issue is specifically ties to disk writes: I mounted the same disks as read-only and have been running a read-intensive workload for at least a week now without issue. When I run the same read-intensive workload but mount the disks RW, the issue occurs after a few days, I'm assuming as a result of the constant updating of atimes.

If I run a write-intensive load on the same disks, I get this issue within hours if not minutes.

[PeterPlatt]

Same problem here. I'm trying to switch to the USB 2.0 port to see if it helps. System hangs when there are heavy writes to the external drive.

[marcosscriven]

Just came to report the same issue - this time by hitting two USB3 ethernet adapters at the same time (with connection bonding software).
I'll try another hub, but there's too many reports both on this issue, and this forum post https://forum.pine64.org/showthread.php?tid=5557 to suggest it's anything other than the Rock64 at fault here.

[Linux-cpp-lisp]

Can confirm (again) that this has happened many more times with moderately heavy USB 3.0 I/O -- I was actually forced to stop using the Rock64 since it couldn't run my workload without failing.

…

On Sat, Jun 16, 2018, 4:56 PM Marcos Scriven ***@***.***> wrote: Just came to report the same issue - this time by hitting two USB3 ethernet adapters at the same time (with connection bonding software). I'll try another hub, but there's too many reports both on this issue, and this forum post https://forum.pine64.org/showthread.php?tid=5557 to suggest it's anything other than the Rock64 at fault here. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#112 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABZ8bF-UuXEdcAFCTLOOt5PRqcusW1K5ks5t9Ry0gaJpZM4STaMx> .

[stevefan1999-personal]

Can confirm. Just yesterday my Rock64 halted but I have no logs available because my system was booted from an external USB3 HDD, so presumably, USB3 is the problem of my random freezes. I used to reproduce this behavior by setting my APM and AAM to the best performant option possible (and hence power-hungry), maybe I triggered the polyfuse or some other protection mechanism that I'm unaware of? Or is it the temp sensor detected an anomaly so it just went off without leaving any logs for me...

Thankfully there are no bad blocks. The system has ran without trouble for a week before. If this keeps going on how am I going to keep this R64 for my NAS solution?

EDIT: It happened again 30 minutes ago. I was under both frequent reads and writes that I have BitTorrent and Plex running alongside each other. Too bad I hadn't got a spare and long enough USB cable to see what happened. That's why you shouldn't put a headless server around your router only.

EDIT 2: Just realized the absense of logs are pretty reasonable to be caused by folder2ram, so the logs are discarded in memory when I forcefully reboots. Gotta see something interesting in the dmesg after removing folder2ram if the USB hell ever happened again.

EDIT 3: Nope, nothing special beside the spamming of this line during the USB hang up:

Jul 15 14:46:07 nas kernel: [59526.130023] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
Jul 15 14:46:07 nas kernel: [59526.131809] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
Jul 15 14:46:07 nas kernel: [59526.152878] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
Jul 15 14:46:07 nas kernel: [59526.154704] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
Jul 15 14:46:07 nas kernel: [59526.215919] rockchip-sip: function[82000008]: args:[2,0,2] => res:[0,2ed96880,0,0]
...

So yeah I think I tripped the USB3 chipset, it has some flaws in it.

[Redwid]

The same for me.
Two 2.5" disks connected to usb 3.0 powered hub. On rsync data from one to another - disks disconnects. No way to return them back, only reboot helps.
I'm on 4.4.126-rockchip-ayufan-239.

[ayufan]

Can you check if the same happens on 0.5.15? Kamil

…

On Mon, Jul 16, 2018 at 11:33 AM, Redwid ***@***.***> wrote: The same for me. Two 2.5" disks connected to usb 3.0 powered hub. On rsync data from one to another - disks disconnects. No way to return them back, only reboot helps. I'm on 4.4.126-rockchip-ayufan-239. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#112 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACTpQZSNzeh-NwRxUB_ec6dWqG_NjwBrks5uHF32gaJpZM4STaMx> .

[Redwid]

Thanks ayufan, I'll try in the evening.
Is that 0.5.15, right?
https://github.com/ayufan-rock64/linux-build/releases/tag/0.5.15

[ayufan]

Yes

…

On Mon, Jul 16, 2018 at 11:49 AM, Redwid ***@***.***> wrote: Thanks ayufan, I'll try in the evening. Is that 0.5..15, right? https://github.com/ayufan-rock64/linux-build/releases/tag/0.5.15 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#112 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACTpQTpAvjpv9AvZQVHqMvfmPQdJ5aE_ks5uHGGxgaJpZM4STaMx> .

[Redwid]

The same result for jessie-openmediavault-rock64-0.5.15-136-armhf.img.xz
All usb disk are gone after copying about 7Gb of files.

[    1.962239] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller
[    1.970443] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 4
[    1.978738] xhci-hcd xhci-hcd.8.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x00210010
[    1.987008] xhci-hcd xhci-hcd.8.auto: irq 180, io mem 0xff600000
[    2.019606] usb usb4: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 xhci-hcd
[    2.027901] usb usb4: SerialNumber: xhci-hcd.8.auto
[    2.053603] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller
[    2.062301] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 5
[    2.105026] usb usb5: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 xhci-hcd
[    2.113525] usb usb5: SerialNumber: xhci-hcd.8.auto
[    2.367992] usb 4-1: new high-speed USB device number 2 using xhci-hcd
[    2.650176] usb 5-1: new SuperSpeed USB device number 2 using xhci-hcd
[    3.107050] usb 5-1.2: new SuperSpeed USB device number 3 using xhci-hcd
[    3.215063] usb 5-1.3: new SuperSpeed USB device number 4 using xhci-hcd
[  538.069919] usb 5-1.3: new SuperSpeed USB device number 5 using xhci-hcd
[  538.333933] usb 5-1.1: new SuperSpeed USB device number 6 using xhci-hcd
[  915.868847] xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.
[  915.873804] xhci-hcd xhci-hcd.8.auto: Assuming host is dying, halting host.
[  915.878549] xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.
[  915.883450] xhci-hcd xhci-hcd.8.auto: Assuming host is dying, halting host.
[  915.901904] xhci-hcd xhci-hcd.8.auto: Host not halted after 16000 microseconds.
[  915.905494] xhci-hcd xhci-hcd.8.auto: HC died; cleaning up
[  916.342611] xhci-hcd xhci-hcd.8.auto: Non-responsive xHCI host is not halting.
[  916.348589] xhci-hcd xhci-hcd.8.auto: Completing active URBs anyway.
[  916.354428] xhci-hcd xhci-hcd.8.auto: HC died; cleaning up```


```root@rock64:~# dmesg | grep "usb"
[    0.587825] usbcore: registered new interface driver usbfs
[    0.588430] usbcore: registered new interface driver hub
[    0.589038] usbcore: registered new device driver usb
[    1.106062] phy phy-ff450000.syscon:usb2-phy@100.0: Looking up phy-supply from device tree
[    1.106083] phy phy-ff450000.syscon:usb2-phy@100.0: Looking up phy-supply property in node /syscon@ff450000/usb2-phy@100/host-port failed
[    1.106614] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up phy-supply from device tree
[    1.106634] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up phy-supply property in node /syscon@ff450000/usb2-phy@100/otg-port failed
[    1.107150] rockchip-usb2phy ff450000.syscon:usb2-phy@100: GPIO lookup for consumer otg-vbus
[    1.107166] rockchip-usb2phy ff450000.syscon:usb2-phy@100: using device tree for GPIO lookup
[    1.107209] of_get_named_gpiod_flags: parsed 'otg-vbus-gpios' property of node '/syscon@ff450000/usb2-phy@100[0]' - status (0)
[    1.107958] rockchip-u3phy ff470000.usb3-phy: GPIO lookup for consumer vbus-drv
[    1.107975] rockchip-u3phy ff470000.usb3-phy: using device tree for GPIO lookup
[    1.108007] of_get_named_gpiod_flags: parsed 'vbus-drv-gpios' property of node '/usb3-phy@ff470000[0]' - status (0)
[    1.108402] phy phy-ff470000.usb3-phy.2: Looking up phy-supply from device tree
[    1.108421] phy phy-ff470000.usb3-phy.2: Looking up phy-supply property in node /usb3-phy@ff470000/utmi@ff470000 failed
[    1.108918] phy phy-ff470000.usb3-phy.3: Looking up phy-supply from device tree
[    1.108937] phy phy-ff470000.usb3-phy.3: Looking up phy-supply property in node /usb3-phy@ff470000/pipe@ff478000 failed
[    1.110685] rockchip-u3phy ff470000.usb3-phy: Rockchip u3phy initialized successfully
[    1.426222] usbcore: registered new interface driver cdc_ether
[    1.434287] usbcore: registered new interface driver rndis_host
[    1.443898] phy phy-ff470000.usb3-phy.2: u3phy u2 power on
[    1.451610] phy phy-ff470000.usb3-phy.3: u3phy u3 power on
[    1.460065] dwc2 ff580000.usb: Looking up vusb_d-supply from device tree
[    1.460086] dwc2 ff580000.usb: Looking up vusb_d-supply property in node /usb@ff580000 failed
[    1.460103] ff580000.usb supply vusb_d not found, using dummy regulator
[    1.467685] dwc2 ff580000.usb: Looking up vusb_a-supply from device tree
[    1.467704] dwc2 ff580000.usb: Looking up vusb_a-supply property in node /usb@ff580000 failed
[    1.467718] ff580000.usb supply vusb_a not found, using dummy regulator
[    1.631113] dwc2 ff580000.usb: DWC OTG Controller
[    1.638195] dwc2 ff580000.usb: new USB bus registered, assigned bus number 1
[    1.645471] dwc2 ff580000.usb: irq 40, io mem 0x00000000
[    1.652794] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.659977] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.667109] usb usb1: Product: DWC OTG Controller
[    1.673885] usb usb1: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 dwc2_hsotg
[    1.680967] usb usb1: SerialNumber: ff580000.usb
[    1.726426] ehci-platform ff5c0000.usb: EHCI Host Controller
[    1.733479] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 2
[    1.740833] ehci-platform ff5c0000.usb: irq 41, io mem 0xff5c0000
[    1.752897] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00
[    1.760152] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    1.767153] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.774178] usb usb2: Product: EHCI Host Controller
[    1.781056] usb usb2: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 ehci_hcd
[    1.788330] usb usb2: SerialNumber: ff5c0000.usb
[    1.826658] ohci-platform ff5d0000.usb: Generic Platform OHCI controller
[    1.834615] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3
[    1.842595] ohci-platform ff5d0000.usb: irq 42, io mem 0xff5d0000
[    1.905175] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    1.913039] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.920937] usb usb3: Product: Generic Platform OHCI controller
[    1.928730] usb usb3: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 ohci_hcd
[    1.936725] usb usb3: SerialNumber: ff5d0000.usb
[    1.995280] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[    2.003420] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.011587] usb usb4: Product: xHCI Host Controller
[    2.019606] usb usb4: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 xhci-hcd
[    2.027901] usb usb4: SerialNumber: xhci-hcd.8.auto
[    2.070960] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.079784] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
[    2.088269] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.096794] usb usb5: Product: xHCI Host Controller
[    2.105026] usb usb5: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 xhci-hcd
[    2.113525] usb usb5: SerialNumber: xhci-hcd.8.auto
[    2.141273] usbcore: registered new interface driver usbtouchscreen
[    2.321148] usbcore: registered new interface driver uvcvideo
[    2.367992] usb 4-1: new high-speed USB device number 2 using xhci-hcd
[    2.416998] usbcore: registered new interface driver bfusb
[    2.424928] usbcore: registered new interface driver btusb
[    2.552225] usb 4-1: New USB device found, idVendor=05e3, idProduct=0610
[    2.552230] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.552233] usb 4-1: Product: USB2.0 Hub
[    2.552237] usb 4-1: Manufacturer: GenesysLogic
[    2.613522] of_get_named_gpiod_flags: parsed 'gpios' property of node '/switches/usb-switch[0]' - status (0)
[    2.625722] usbcore: registered new interface driver usbhid
[    2.631459] usbhid: USB HID core driver
[    2.637485] usbcore: registered new interface driver snd-usb-audio
[    2.650176] usb 5-1: new SuperSpeed USB device number 2 using xhci-hcd
[    2.813900] usb 5-1: New USB device found, idVendor=05e3, idProduct=0616
[    2.813905] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.813909] usb 5-1: Product: USB3.0 Hub
[    2.813913] usb 5-1: Manufacturer: GenesysLogic
[    3.107050] usb 5-1.2: new SuperSpeed USB device number 3 using xhci-hcd
[    3.123152] usb 5-1.2: New USB device found, idVendor=0bc2, idProduct=ab26
[    3.128511] usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.133802] usb 5-1.2: Product: BUP Slim BK
[    3.138675] usb 5-1.2: Manufacturer: Seagate
[    3.143560] usb 5-1.2: SerialNumber: NA97MBXT
[    3.215063] usb 5-1.3: new SuperSpeed USB device number 4 using xhci-hcd
[    3.230707] usb 5-1.3: New USB device found, idVendor=2537, idProduct=1068
[    3.234948] usb 5-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.239215] usb 5-1.3: Product: NS1068
[    3.243131] usb 5-1.3: Manufacturer: Norelsys
[    3.247138] usb 5-1.3: SerialNumber: 0123456789ABCDE
[    3.256436] usb 5-1.2: UAS is blacklisted for this device, using usb-storage instead
[    3.260745] usb-storage 5-1.2:1.0: USB Mass Storage device detected
[    3.265693] usb-storage 5-1.2:1.0: Quirks match for vid 0bc2 pid ab26: 800000
[    3.270094] scsi host0: usb-storage 5-1.2:1.0
[    3.274550] usb 5-1.3: UAS is blacklisted for this device, using usb-storage instead
[    3.279016] usb-storage 5-1.3:1.0: USB Mass Storage device detected
[    3.283643] usb-storage 5-1.3:1.0: Quirks match for vid 2537 pid 1068: 800000
[    3.288222] scsi host1: usb-storage 5-1.3:1.0
[    3.292872] usbcore: registered new interface driver usb-storage
[    3.298157] usbcore: registered new interface driver uas
[    3.871933] usb 1-1: new high-speed USB device number 2 using dwc2
[    4.338793] usb 1-1: New USB device found, idVendor=0bc2, idProduct=ab26
[    4.338800] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.338805] usb 1-1: Product: BUP Slim RD
[    4.338810] usb 1-1: Manufacturer: Seagate
[    4.338814] usb 1-1: SerialNumber: NA9JK89E
[    4.339752] usb 1-1: UAS is blacklisted for this device, using usb-storage instead
[    4.339760] usb-storage 1-1:1.0: USB Mass Storage device detected
[    4.375079] usb-storage 1-1:1.0: Quirks match for vid 0bc2 pid ab26: 800000
[    4.380152] scsi host2: usb-storage 1-1:1.0
[  533.797163] usb 1-1: USB disconnect, device number 2
[  537.799553] usb 5-1.3: USB disconnect, device number 4
[  538.069919] usb 5-1.3: new SuperSpeed USB device number 5 using xhci-hcd
[  538.081470] usb 5-1.3: New USB device found, idVendor=2537, idProduct=1068
[  538.082230] usb 5-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  538.083040] usb 5-1.3: Product: NS1068
[  538.083451] usb 5-1.3: Manufacturer: Norelsys
[  538.083942] usb 5-1.3: SerialNumber: 0123456789ABCDE
[  538.085325] usb 5-1.3: UAS is blacklisted for this device, using usb-storage instead
[  538.086179] usb-storage 5-1.3:1.0: USB Mass Storage device detected
[  538.087626] usb-storage 5-1.3:1.0: Quirks match for vid 2537 pid 1068: 800000
[  538.089073] scsi host3: usb-storage 5-1.3:1.0
[  538.333933] usb 5-1.1: new SuperSpeed USB device number 6 using xhci-hcd
[  538.346007] usb 5-1.1: New USB device found, idVendor=0bc2, idProduct=ab26
[  538.346752] usb 5-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  538.347553] usb 5-1.1: Product: BUP Slim RD
[  538.348032] usb 5-1.1: Manufacturer: Seagate
[  538.348490] usb 5-1.1: SerialNumber: NA9JK89E
[  538.349801] usb 5-1.1: UAS is blacklisted for this device, using usb-storage instead
[  538.350682] usb-storage 5-1.1:1.0: USB Mass Storage device detected
[  538.351975] usb-storage 5-1.1:1.0: Quirks match for vid 0bc2 pid ab26: 800000
[  538.352791] scsi host4: usb-storage 5-1.1:1.0
[  915.905561] usb 5-1.1: USB disconnect, device number 6
[  915.905600] usb 4-1: USB disconnect, device number 2
[  915.906698] usb 5-1: USB disconnect, device number 2
[  918.129776] usb 5-1.2: USB disconnect, device number 3
[  919.322503] usb 5-1.3: USB disconnect, device number 5