Bug 185591
| Summary: | usb 2-1.5:1.0: rebind failed: -517 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Cristian Aravena Romero (caravena) |
| Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | balbi, szg00000, wendy.wang |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 4.9.0-040900rc2-generic | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
dmesg_4.9.0-040900rc2-generic
lspci -vvnn bdw-mainline-4.9-rc5-dmesg.log broxton-btusb-rebind-fail-dmesg.log |
||
Created attachment 243211 [details]
lspci -vvnn
We also observed this issue on BDW-U (Lenovo L450 platform), checked mainline v4.8 release also has the btusb rebind issue.
[ 56.113746] usb 2-7:1.0: rebind failed: -517
[ 56.114643] usb 2-7:1.1: rebind failed: -517
lsusb -t
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
|__ Port 6: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M
|__ Port 1: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 12M
|__ Port 7: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 7: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 8: Dev 5, If 0, Class=Video, Driver=, 480M
|__ Port 8: Dev 5, If 1, Class=Video, Driver=, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
Till mainline v4.9-rc5, this issue still can be reproduced on BDW-U and Broxton platforms.
Update the reproduce steps: 1. Boot into kernel 2. do s3/s4 and wake up (command : rtcwake -m mem -s 30 or rtcwake -m disk -s 60) 3. After resume from S3/S4, check dmesg will find the btusb rebind fail message. Created attachment 244841 [details]
bdw-mainline-4.9-rc5-dmesg.log
-517 is -EPROBE_DEFER, are you sure the device didn't bind at a later point in time? EPROBE_DEFER is not an indication of failure, it's just the driver saying "I'll try probing later, something I need is still not available". What's bothering me, though, is the fact that you're missing Bluetooth's FW image: [ 3152.616950] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8761 [ 3152.618424] Bluetooth: hci0: rtl: loading rtl_bt/rtl8761a_config.bin [ 3152.620017] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761a_config.bin failed with error -2 [ 3152.621518] bluetooth hci0: Falling back to user helper [ 3152.624931] Bluetooth: hci0: Failed to load rtl_bt/rtl8761a_config.bin [ 3152.626475] Bluetooth: hci0: rtl: loading rtl_bt/rtl8761a_fw.bin [ 3152.628132] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761a_fw.bin failed with error -2 [ 3152.629826] bluetooth hci0: Falling back to user helper [ 3152.632324] Bluetooth: hci0: Failed to load rtl_bt/rtl8761a_fw.bin Can you make sure you *really* have these files? Hello Felipe, FW loading failure should be another problem for card type did not match fw version, but it seems do not related to the rebind message. As I see on another Broxton board with mainline kernel v4.9-rc5 installed, which do not bt fw loading failure message, but also show rebind fail after resume from s4. and no matter how long I wait, dmesg always report the rebind fail info.(attached this machine's dmesg log: broxton-btusb-rebind-fail-dmesg.log) Thanks! Created attachment 244981 [details]
broxton-btusb-rebind-fail-dmesg.log
|
Created attachment 243201 [details] dmesg_4.9.0-040900rc2-generic [ 3777.304454] usb 2-1.5:1.0: rebind failed: -517 [ 3777.304460] usb 2-1.5:1.1: rebind failed: -517