Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#35013 - [linux] 3.8.x - 3.11.x Atheros Bluetooth fails on Sony Vaio VPCF22:

Attached to Project: Arch Linux
Opened by Thorsten Reinbold (Thorsten Reinbold) - Sunday, 28 April 2013, 12:54 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 10 October 2013, 10:15 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The Bluetooth-Device on my Sony Vaio VPCF22 is not usable at all. It seems like the firmware is not loaded correctly.


Output from journalctl:

kernel: Bluetooth: Can't change to loading configuration err
kernel: ath3k: probe of 2-1.5:1.0 failed with error -110


Output from dmseg:

dmesg | grep ath3
[ 5.097666] usbcore: registered new interface driver ath3k
[ 11.459461] ath3k: probe of 2-1.5:1.0 failed with error -110

lsusb:

Bus 002 Device 006: ID 0489:e027 Foxconn / Hon Hai


It seems as if this launchpad-bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/898826) points to a similar error. I wanted to test if I could apply the patch there to the Arch-kernel, so I downloaded the sources with abs. But the Patch from launchpad is already applied.

Additional info:
* Kernel: 3.8.8-2-ARCH
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 10 October 2013, 10:15 GMT
Reason for closing:  Upstream
Comment by Thorsten Reinbold (Thorsten Reinbold) - Sunday, 28 April 2013, 19:09 GMT
Info: I'm not really experienced in Bugreporting, but I would really like to solve this. If any other Infos are needed, please let me know. I will give them as fast as I can.
Comment by Tobias Powalowski (tpowa) - Monday, 29 April 2013, 06:30 GMT
This patch is already in kernel since december.
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=acd9454433e28c1a365d8b069813c35c1c3a8ac3
Comment by Thorsten Reinbold (Thorsten Reinbold) - Tuesday, 30 April 2013, 02:19 GMT
Yes, I know that it is applied. I've seen this in the source. But apart from this, Bluetooth is not working and the symptomps are the same as before the patch. The device is recognized wrong and not working at all. So, what can I do?
Comment by Tobias Powalowski (tpowa) - Tuesday, 30 April 2013, 06:37 GMT
Get in touch with module developers and or those who checked in the last patch.
Comment by Tobias Powalowski (tpowa) - Thursday, 23 May 2013, 20:05 GMT
Status on 3.9?
Comment by Thorsten Reinbold (Thorsten Reinbold) - Thursday, 23 May 2013, 20:19 GMT
Sadly, still the same.

uname -r
3.9.3-1-ARCH

journalctl -b
kernel: Bluetooth: Can't change to loading configuration err
kernel: ath3k: probe of 1-1.5:1.0 failed with error -110
Comment by Thorsten Reinbold (Thorsten Reinbold) - Friday, 07 June 2013, 09:43 GMT
Interesting: I noticed that BT now wasn't working under Windows 7 (fresh install) and Ubuntu as well. Then, after booting the latest PartedMagic-LiveCD, it was working again under this Systems. Could it be that Windows leaves some devices in a state that makes it impossible to use them correctly? Sadly, Arch does not benefit here. Same state as before.
Comment by Tobias Powalowski (tpowa) - Tuesday, 30 July 2013, 10:34 GMT
Status on 3.10.x?
Comment by Thorsten Reinbold (Thorsten Reinbold) - Tuesday, 30 July 2013, 10:40 GMT
Still exactly the same.
Comment by Tobias Powalowski (tpowa) - Tuesday, 30 July 2013, 10:51 GMT
Please take this upstream, we cannot solve this.
Comment by Tobias Powalowski (tpowa) - Tuesday, 17 September 2013, 09:57 GMT
Status on 3.11.1?
Comment by Thorsten Reinbold (Thorsten Reinbold) - Tuesday, 17 September 2013, 15:39 GMT
Still exactly the same error message. Is there a good manual somewhere about sending bugs upstream? I'm really not experienced with this, but I guess it is necessary to bring this to attention.
Comment by Tobias Powalowski (tpowa) - Thursday, 19 September 2013, 06:51 GMT
Gustavo Padovan <gustavo.padovan@collabora.co.uk> try to get in contact with him, he commits to ath3k code.

Loading...