求助：android休眠唤醒后不能识别U盘了，怎么回事？

ximuyi

机器挂着U盘，测试android的休眠唤醒功能，唤醒后有时候无法识别U盘，这个时候，即使重新插拨U盘也没用，必须要重启机器才能识别。
唤醒后的LOG如下：
[  313.540302] <<-GTP-INFO->> System resume.
[  313.564334] <<-GTP-INFO->> Guitar reset
[  313.564334]
[  313.740584] <<-GTP-INFO->> GTP wakeup sleep.
[  313.824634] intel_otg_mode_write,req_mode=2

[  314.130264] intel-usb2phy e4800000.phy: OTG runtime resume
[  314.131545] intel-usb2phy e4800000.phy: got usb reset in 0 us
[  314.131580] intel-usb2phy e4800000.phy: USB exited from low power mode
[  314.131633] intel-usb2phy e4800000.phy: b_idle work
[  314.131656] intel-usb2phy e4800000.phy: !id
[  314.131678] intel-usb2phy e4800000.phy: a_idle work
[  314.131696] intel-usb2phy e4800000.phy: !a_bus_drop && (a_srp_det || a_bus_req)
[  314.190290] intel-usb2phy e4800000.phy: starting a_wait_vrise timer
[  314.290446] intel-usb2phy e4800000.phy: expired a_wait_vrise timer
[  314.296800] intel-usb2phy e4800000.phy: a_wait_vrise work
[  314.296850] intel-usb2phy e4800000.phy: a_vbus_vld
[  314.296873] intel-usb2phy e4800000.phy: host on
[  314.500471] dwc2 e2100000.usb: _dwc2_hcd_resume()
[  314.787066] intel_otg_mode_write,req_mode=2

[  314.787560] ttyBT btif-0: Revision Id: 0x2, Module Id: 0x52, TopSpin Rev: 0x307
[  314.800351] usb 1-1: new high-speed USB device number 10 using dwc2
[  319.990459] hsotg->flags.b.port_connect_status

[  319.990750] dwc2 e2100000.usb: dwc2_hc_halt: HCCHAR 0x00000000, ep_type 0
[  325.200706] hsotg->flags.b.port_connect_status

[  325.200847] dwc2 e2100000.usb: dwc2_hc_halt: HCCHAR 0x00000000, ep_type 0
[  325.410460] usb 1-1: device not accepting address 10, error -110
[  325.600641] usb 1-1: new high-speed USB device number 11 using dwc2
[  330.600632] hsotg->flags.b.port_connect_status

[  330.600813] dwc2 e2100000.usb: dwc2_hc_halt: HCCHAR 0x00000000, ep_type 0

与正常能识别的LOG对比，发现这么一句：usb 1-1: device not accepting address 10, error -110

不知道有没有人碰到过这样的问题，是怎么解决的？

ximuyi

没人帮看吗，真找不到原因了

隐婚出轨渣男

ximuyi 发表于 2016-12-19 08:56
没人帮看吗，真找不到原因了

找到原因了，可以私聊啊。我告诉你原因

lininglive

If Linux suddenly happen to fail to recognize a USB drive, check dmesg for errors. Once you see a bunch of errors like

usb 1-5: device descriptor read/64, error -32  
usb 1-5: new high speed USB device using ehci_hcd and address 21  
usb 1-5: device not accepting address 21, error -32
most probably it’s a result of hardware failure rather than a driver or kernel bug. USB has an over-current protection, which gets triggered when power consumption from the port is too high.

Unplug all USB devices from PC, turn power off, and wait a minute or two. Plug everything back and boot into Linux.

I spent the whole morning, until found out why. I hope that this message will save someone a few hours, and nerves.

PS: Actual errors may vary. You may see different port and/or error code. Ex.:

usb 3-1: device descriptor read/64, error -62
or

usb 4-2: device descriptor read/64, error -71
or

usb 2-3: device descriptor read/64, error -101

貌似电流过大，硬件进入保护状态