Bug 100651
| Summary: | Bluetooth broken on MBA 6,2 since Kernel v4.1 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Christoph (kernel) |
| Component: | Bluetooth | Assignee: | linux-bluetooth (linux-bluetooth) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | evangelos, johan.hedberg, kapouer, kernel-bugs, martin.szulecki.kernel.bugzilla, milton.marcinek, net147, v.simankin |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 4.1.0-040100-generic #201506220235 (Ubuntu) | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Kernellog
broken kernel config working kernel config lsusb |
||
Created attachment 181261 [details]
broken kernel config
Created attachment 181271 [details]
working kernel config
Created attachment 181281 [details]
lsusb
Confirming same issue/behavior on MacbookAir5,2 (tested on 4.1.1): Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Looks like all BCM2046B1 devices are affected by the recent config read code changes. same issue starting with 4.1 # dmidecode -t system | grep "Product Name" Product Name: MacBookPro11,3 # lsusb | grep -i 2046B1 Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) # hciconfig hci0 down # hciconfig hci0 up Can't init device hci0: Device or resource busy (16) # dmesg | grep hci0 [ 5.565576] Bluetooth: hci0: BCM: Read verbose config info failed (-16) … [ 1972.306838] Bluetooth: hci0: BCM: Read verbose config info failed (-16) modprobe btbcm ? Oh - what happened is booting linux 4.0.7, then rebooting to 4.1.1 leave it with a properly initialized bluetooth. Possibly fixed by: http://marc.info/?l=linux-bluetooth&m=143690553927903&w=2. (I don't have the hardware to test.) Thank you for pointing me to this patch from Chris Mason. I applied it to kernel v4.1 and the bluetooth device comes up properly. (In reply to Evangelos Foutras from comment #8) > Possibly fixed by: http://marc.info/?l=linux-bluetooth&m=143690553927903&w=2. > > (I don't have the hardware to test.) same problem (on MacBookPro11,3) with patch (and with already patched 4.1.3) dmesg [ 252.023861] usbcore: registered new interface driver btusb [ 252.025037] Bluetooth: hci0: BCM: Read verbose config info failed (-16) [ 252.026044] Bluetooth: hci0: BCM: Read verbose config info failed (-16) # uname -r 4.1.3 (In reply to Victor from comment #10) > same problem (on MacBookPro11,3) with patch (and with already patched 4.1.3) FWIW, 4.1.3 doesn't have the patch. > dmesg > [ 252.023861] usbcore: registered new interface driver btusb > [ 252.025037] Bluetooth: hci0: BCM: Read verbose config info failed (-16) > [ 252.026044] Bluetooth: hci0: BCM: Read verbose config info failed (-16) These messages are still supposed to be there even with the patch, however bringing up the interface should work. (In reply to Johan Hedberg from comment #11) > FWIW, 4.1.3 doesn't have the patch. may be. My gentoo-source - has (i look source btbcm.c just now) > however bringing up the interface should work. Not for me. 4.0.8 work fine (In reply to Johan Hedberg from comment #11) > (In reply to Victor from comment #10) > > same problem (on MacBookPro11,3) with patch (and with already patched > 4.1.3) > > FWIW, 4.1.3 doesn't have the patch. > > > dmesg > > [ 252.023861] usbcore: registered new interface driver btusb > > [ 252.025037] Bluetooth: hci0: BCM: Read verbose config info failed (-16) > > [ 252.026044] Bluetooth: hci0: BCM: Read verbose config info failed (-16) > > These messages are still supposed to be there even with the patch, however > bringing up the interface should work. I fresh installed Arch 4.1.3 on a MacBookPro8,2 and couldn't get it to boot because of this error. Installed abs, compiled the linux-4.1.3-1 package which (now) includes this patch, and I'm still getting the error and the boot hang. Not sure what to do. Note that the patch I linked above will be in 4.1.4; it's currently in the patch queue for 4.1.x. [1] The stock Arch Linux kernel package includes the patch and people have confirmed that Bluetooth works with it. The "Read verbose config info failed" messages still exist but should be harmless. @milton: I don't think your boot failure is related to this issue at all. You could give the linux-lts kernel a try (or an older 4.0.x kernel from [2]). [1] http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git/tree/queue-4.1 [2] http://seblu.net/a/arm/packages/l/linux/ (In reply to Evangelos Foutras from comment #14) > The stock Arch Linux kernel package includes the patch and people have > confirmed that Bluetooth works with it. The "Read verbose config info > failed" messages still exist but should be harmless. also confirm, work in 4.1.4 # uname -r 4.1.4-gentoo Confirming as fixed in Kernel 4.1.4 for MacbookAir5,2. |
Created attachment 181251 [details] Kernellog On Macbook Air 6,2 bluetooth was working till kernel v4.0.3. In version 4.1 bluetooth support is broken: sudo hciconfig hci0 up Can't init device hci0: Device or resource busy (16) dmesg | grep hci0 [ 774.467449] Bluetooth: hci0: BCM: Read verbose config info failed (-16) lsusb | grep -i blue Bus 001 Device 005: ID 05ac:820b Apple, Inc. Bluetooth HID Mouse Bus 001 Device 004: ID 05ac:820a Apple, Inc. Bluetooth HID Keyboard Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) You will find dmesg, Kernel-Configs and lsusb output attached. Christoph