168c:0036 [Acer Aspire E1-572] ath9k QCA9565/AR9565/QCWB335 Bluetooth works sporadic

[Joshua]

I got myself a brand new Acer Aspire E1-572-54204G50Mnkk, because of the shine new Haswell hardware I choose to install Ubuntu 13.10 Beta 2.

This laptop uses a Atheros AR9565 802.11 b/g/n 1 × 1 WiFi + Bluetooth 4.0 combination adapter, Wireless is working fine. But Bluetooth doesn't, it seems to be successfully detected but I can't see any other Bluetooth devices and they can't see me too:
Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)
 Subsystem: Foxconn International, Inc. Device [105b:e068]

---
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
DistroRelease: Ubuntu 13.10
InstallationDate: Installed on 2013-10-12 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Tags: saucy
Uname: Linux 3.12.0-031200rc4-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: joshua 1348 F.... pulseaudio
 /dev/snd/controlC0: joshua 1348 F.... pulseaudio
DistroRelease: Ubuntu 13.10
InstallationDate: Installed on 2013-10-12 (8 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MachineType: Acer Aspire E1-572
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=287c8de2-616f-42ec-998d-1ac09ffb2d8a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/21/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_HW
dmi.board.vendor: Acer
dmi.board.version: V2.04
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd05/21/2013:svnAcer:pnAspireE1-572:pvrV2.04:rvnAcer:rnEA50_HW:rvrV2.04:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E1-572
dmi.product.version: V2.04
dmi.sys.vendor: Acer

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1237296/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1237296

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joshua (njj)]

I cant run apport-collect because I wiped my drive and installed another system after Ubuntu 13.10 didn't worked.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc4-saucy/

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

The BT device ID was missing in the driver. After recompiling the ath3k and btusb modules with this patch bluetooth works. But I had to modprobe ath3k manually so something is still not working right.

Can this patch be rolled out with the next saucy kernel update or do I have to wait till trusty thar?

[Joseph Salisbury (jsalisbury)]

I don't see that this patch is in the mainline(3.12-rc7) tree as of yet. Do you know the status of it upstream?

[Joshua (njj)]

Not exactly, I got this from the developer through the ath9k-devel mailinglist. He wanted to send it some way upstream yesterday evening.

[Joshua (njj)]

Change the unoffical patch with the link to upstream git at kernel.org

[Joseph Salisbury (jsalisbury)]

I built a Saucy test kernel with the patch mentioned in comment #22. The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1237296/

Can you test this kernel and post back if it resolves this bug?

[Joshua (njj)]

No it doesn't, dmesg shows the following:

[ 7.791682] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096
[ 7.791693] Bluetooth: Loading patch file failed
[ 7.791704] ath3k: probe of 2-5:1.0 failed with error -110
[ 7.791747] usbcore: registered new interface driver ath3k

[Joseph Salisbury (jsalisbury)]

Thanks for testing, Joshua. It sounds like you were able to get the device working, using the patch, per comment #19. Which kernel version did you apply the patch against? Was it the Ubuntu Saucy kernel, or another version?

[Joshua (njj)]

I'm not that experienced in this kind of things. So this is what I did:

apt-get install linux-source
unpack the source to some place and apply the patch
cp .conf and Module.symvers of the current saucy kernel
make prepare
make scripts
make M=drivers/bluetooth
cp the new ath3k.ko and btusb.ko to /lib/modules/3.11.0-12-generic/kernel/drivers/bluetooth/

After a reboot the ath3k modul didn't got loaded, but after issuing "modprobe ath3k" the device worked.

[Joseph Salisbury (jsalisbury)]

Do you still have your test kernel available? If so, can you boot your kernel and run:
dpkg -l | grep linux-firmware

Then also boot my test kernel and run the same command:
dpkg -l | grep linux-firmware

[Joshua (njj)]

Yes and no, as I tried to explain, I didn't compiled a whole test kernel. I only compiled the ath3k and btusb modules and copied them into the directory of the latest default kernel at that time, 3.11.0-12-generic. And linux-firmware package was version 1.116 both times.

Offtopic: I have some other issues, one of them is a shutdown problem. So I'm doing a lot of shutdown and reboot testing atm.
Ontopic: I recently noticed that bluetooth suddenly worked after startup (I'm using your kernel all the time atm). After the next reboot it was broken again. And some reboots later it worked again. But I can't reproduce the reason, no matter how often I try. Some rare times it works and I can't figure out why.

I'm using a SSD and UEFI so startup is very fast, could it be, that there is some problem with the loading order most of the time?

[Joshua (njj)]

If I copy the modules I compiled into the modules dir of your kernel bluetooth works fine. These are the modules I compiled.

[Joshua (njj)]

Forget about my last post, after a reboot bluetooth is broken again. "Loading patch file failed" Seriously wtf!

[Joseph Salisbury (jsalisbury)]

Can you give the latest 3.12 kernel[0] a test?

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/

[Joshua (njj)]

It definitly won't, because the patch arrive upstream just 3 days ago, excatly 2013-11-18 15:46:05.

But I gave 3.12.0-999.201311200458 kernel[0] a try, without success. The bluetooth service doesn't start at all: http://paste.ubuntu.com/6452404/

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-11-20-trusty/

[Joshua (njj)]

Somehow through Google I ended up reading this article [0] and followed the instructions under "Kernel Event Sent to Udev". But no event: "If you do not see an event with these three items, then the kernel request is not being propagated to udev. You should file a bug at this point against the udev package." These are the events [1] which are logged.

However dunno if this helpful in any way or even has todo with the bug at all, just wanted to tell.

[0] https://wiki.ubuntu.com/Kernel/Firmware
[1] http://paste.ubuntu.com/6453360/

[Joseph Salisbury (jsalisbury)]

Yeah, I don't see the patch mentioned in comment #23 in Linus' tree as of yet. It may not land until v3.13-rc1.

[Joshua (njj)]

rc3 and it still hasn't landed, I'm a bit depressed. Could you propably build a rc3 test kernel with patch applied, so I could test if something has changed?

[Joseph Salisbury (jsalisbury)]

You mentioned that you got the patch from the author on the ath9k-devel mailinglist. Can you ping the patch author and see if you submitted the patch upstream or if there is a reason why he did not? Once the patch lands upstream, we can cherry-pick it into the Ubuntu kernel.

[Joshua (njj)]

I successfully flashed the new BIOS version and used the patched kernel from comment #24 but the problem is still the same (Bluetooth: Loading patch file failed).

Full dmesg output: http://paste.ubuntu.com/6681124/
The dmidecode output is as expected:
V2.12
11/04/2013

[Joseph Salisbury (jsalisbury)]

The patch mentioned in comment #23 is queued up for inclusion in 3.14:

https://lkml.org/lkml/2013/12/4/271

However, it sounds like it may not fix this bug per the testing of the kernel in comment #24. I'll see if I can build the linux-next tree to see if it resolves this bug.

[Joshua (njj)]

I got it working with the patch comment #23 at some point, but like 90% of the time it doesn't work. And I can't reproduced why, just some rebooting, using windows, hard power off etc. and 1 of 10 times bluetooth works. A linux-next test kernel would be great.

[penalvch (penalvch)]

Joshua, the patch in #23 is too old and doesn't adhere to standard of the current structure of devices/bluetooth/ath3k.c . But, it looks like the modern version of this patch would be available via:
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=35580d223b6b04d9a570e4fe377c46a102413fe8

[Joshua (njj)]

Stock 3.11.0-14-generic usb-devices: http://paste.ubuntu.com/6681435/
dmesg with WORKAROUND after "modprobe ath3k" (everything from line 1075 is new): http://paste.ubuntu.com/6681473/

However I was NOT able to get bluetooth in a workung state like in #19 again. And I noticed that module btusb isn't loaded, and "modprobe btusb" shows "ERROR: could not insert 'btusb': Invalid argument". This is the output of usb-devices with applied WORKAROUND but broken bluetooth: http://paste.ubuntu.com/6681520/

[Joshua (njj)]

Christopher, is the patch you just mentioned in #44 usable for saucy with kernel 3.11 or should I install trusty and ty to build a 3.12 test kernel?

[penalvch (penalvch)]

Joshua, you are welcome to test the patch out on your default install following https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream .

[Joseph Salisbury (jsalisbury)]

I built a test kernel from the upstream linux-next tree. This kernel includes the latest bluetooth stack, including the patch mentined in comment #44. Can you give this kernel a try to see if it resolves this bug:

http://kernel.ubuntu.com/~jsalisbury/lp1237296/

[Joshua (njj)]

Thanks Joseph, but sadly still "Bluetooth: Loading patch file failed".

dmesg http://paste.ubuntu.com/6685680/

[Joseph Salisbury (jsalisbury)]

This might indicate that the patch mentioned in comment #44 does not fix this bug. We may want to create an upstream bug report, since this bug still affects mainline and linux-next.

[Joseph Salisbury (jsalisbury)]

Do you happen to know if there was a prior kernel version that did not exhibit this bug? It would be good to know if the 3.2 kernel also has the bug:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-precise/

[Joshua (njj)]

No prior kernel works because the device ids are missing.

[Joshua (njj)]

If you had already red my last comment, forget about it. I have hidden it.

I had luck and got bluetooth in a working state for one boot period... Here some logs in a working state, after a reboot it would probably be broken again. And I have to reboot dozen of times to get it working again:

usb-devices http://paste.ubuntu.com/6755892/
dmesg http://paste.ubuntu.com/6755903/
lsmod http://paste.ubuntu.com/6755918/

[Joshua (njj)]

I did a booting marathon now to see how often it works or not. I did 20 boots, working y or n, here is the result:

y y n y n y n n n y n n y n n n n n n y

So it worked 7/20 times, its like playing roulette, completely random. In my understanding it can only be a timing or priority issue at startup.

[Joshua (njj)]

Dear Uubuntu Team,

I found a mailing [0] from AceLan Kao and got in contact with him. The "sporadic working issue" seems to be USB 3.0 xHCI related, I'm trying to evaluate this at the moment. However this has nothing todo with my initial problem where the bluetooth device wasn't recognized at all. So the patch from comment #44 which adds the missing device id is fine and should be implemented into saucy and trust, could you please arrange that?

Thanks in advance
Joshua

[0] http://comments.gmane.org/gmane.linux.bluez.kernel/41109

[penalvch (penalvch)]

Joshua, in order to send this issue upstream, could you please test the latest upstream kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/ and advise to the results?

[Joshua (njj)]

Hello Christopher,

I've already tested the final v3.13 kernel and the "sporadic working issue" does still exists. Same behavior than in the previouse kernel versions. I also created a bug report at the kernel bugzilla some time ago, no reaction until now. [0]

[0] https://bugzilla.kernel.org/show_bug.cgi?id=68731

[penalvch (penalvch)]

Joshua, thank you for testing the latest mainline kernel. The issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel (which would not be bugzilla, and your bugzilla report wouldn't have the information developers would want to see) by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[Joshua (njj)]

Okay, I will report this according to the wiki as soon as I'm able to. What about the patch, will it be implemented into ubuntu kernels?

[Fuujuhi (fuujuhi)]

Hi Joshua, could you have a look at related bug 1260825 (and 1277528), and see if the rfkill block / unblock would work for you?

I experience the same issue as you, and this rfkill trick seems to work 100% of the cases now.

[Joshua (njj)]

Hi Fuujuhi, I've recently build my own kernel which fixes the sporadic working issue for me, maybe you could test it as well.

[Marek ZJ (mzalfres)]

Hi,

I've installed your newly built kernel and my bluetooth device is still not working. I've also rebuilt btusb and ath3k modules with suggested patch for my device identifier (0cf3:311f) which is missing from both drivers, but it still gives me following output in dmesg:

[ 7121.317871] Bluetooth: Can't change to loading configuration err
[ 7121.317901] ath3k: probe of 2-1.4:1.0 failed with error -110
[ 7121.317951] usbcore: registered new interface driver ath3k

My device is reported by lspci as:

02:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)

and by lsusb as:

Bus 002 Device 005: ID 0cf3:311f Atheros Communications, Inc.

I'm currently running only linux (Mint 16) on the machine, but originally it had a pre-installed WIN8.

[Joshua (njj)]

Hi Marek,

my device ids are implemented into upstream since 3.14-rc1, so I don't have to do anything about this anymore. The kernel I've build has a special modification added to the usb driver which prevents all my usb pins to use xHCI (USB 3.0) mode and is only meant for testing. For me it works an fixes the "[ 7.791693] Bluetooth: Loading patch file failed" error, as far as I know your "[ 7121.317871] Bluetooth: Can't change to loading configuration err" message must be a completly different error.

[Marek ZJ (mzalfres)]

Joshua,

I was suggested by your #25, where you displayed your dmesg output - I'm not very experience in kernel debugging (yet), so it looked quite similar for me. Anyway. I have the same device (Atheros AR9565) in my laptop so I'm waiting for solution to finally make it working as BT device and not only WiFi. If I can help somehow with testing, let me know.

[Joshua (njj)]

@everyone, the "Loading patch file failed" error is definitely caused by ath3k incompatibility with USB 3.0. The ath3k driver fails to work approximately 2/3 of the time if btusb is connected to a pin which uses the xhci driver. I compiled a dkms kernel package, with the very extensive help of AceLan Kao, which switches the usb pin of the bt device to ehci. Now ath3k and my bluetooth works like a charm 100% of the time. However this is just a workaround, I will report this issue upstream but it looks like the devs are not really interested in fixing this, because it already got reported before.

@Christopher, could you cherry pick the device id patch for my bluetooth card and backport it to saucy and trust? It is upstream since 3.14-rc1 [0][1] and I don't want to be forced to use the Ubuntu mainline kernel all the time.

[0] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/bluetooth/ath3k.c?id=35580d223b6b04d9a570e4fe377c46a102413fe8
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/bluetooth/btusb.c?id=35580d223b6b04d9a570e4fe377c46a102413fe8

[Russell Faull (rfaull)]

Joshua

Thank you for your efforts and persistence in finding a workaround for this bug. I have recently bought an Acer V5-132 with Atheros AR9565 combined wireless/bluetooth adapter: wifi works, bluetooth fails to detect devices.

I tried your kernel on fresh 64-bit install on a usb stick. Results: mainline kernel fails to detect bluetooth devices, your kernel works beautifully!

Trouble is, my installation on the V5's ssd -- which I have migrated with all my applications and settings from several earlier machines/Ubuntu versions -- is 32-bit.

Have you any suggestions how I could incorporating your dkms kernel package into a 32-bit kernel? Is that possible? Should I bite the bullet and rebuild in 64-bit and use your workaround kernel to enable bluetooth?

Regards
Russell

[Russell Faull (rfaull)]

Further to my post at #69, I installed the 32-bit upstream kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc2-trusty/ and bluetooth works as expected.

[Joshua (njj)]

Russell, what problem/s are you suffering from. Missing device ids, sporadic working because of xHCI, or both? And what exactly do you mean with works as expected? Of course I can share the dkms module source so you can build a package for your 32-bit kernel.

[Joshua (njj)]

This is the dkms kernel module which I use currently use. Please no fame for me, its the work of genius AceLan Kao. I'm just sharing it. If you build and insert this, bluetooth should work fine. (As long as you use a kernel which includes the device ids of your bt card)

If you need further instructions read this:

tar xf xhci-quirk-dkms.tar
sudo apt-get install linux-headers-`uname -r` (only if the headers aren't installed already)
cd xhci-quirk-dkms
make
sudo insmod ./xhci-quirk.ko

Now check bluetooth, if everything works fine you can make it a dkms module:

make clean
cd ..
sudo cp -a xhci-quirk-dkms /usr/src/xhci-quirk-1.0
sudo apt-get install dkms
sudo dkms add -m xhci-quirk -v 1.0
sudo dkms install -m xhci-quirk -v 1.0
dkms status (should show the module as installed)
nano /etc/modules (and add xhci-quirk)

[Russell Faull (rfaull)]

Hi Joshua

Thanks for your response. I have the same adapter and suffering the same problems as you describe in the original bug report, paragraph two: "...But Bluetooth doesn't, it seems to be successfully detected but I can't see any other Bluetooth devices and they can't see me too."

To clarify, I installed the upstream kernel 3.14-rc2-trusty and Bluetooth devices are recognised and connected, my mouse and speakers are working. Booting again into the current Ubuntu kernel 3.11.0-15-generic, they fail to connect, as you describe.

I will try and build and insert the module (attached to #72, thank you) into kernel 3.11.0-15-generic and report back.

[Joshua (njj)]

Hi Russell, if you have exactly the same device (id 0x0489 0xe05f) then be module will not help you get this working with kernel 3.11.0-15-generic. Please read everything from comment #55, the original bug why I opend this report was that my device wasn't recogniced at all. This is fix since 3.14-rc1, but another bug is that even with 3.14 bluetooth only works sporadic. Please reboot several times, if bluetooth only works some times then you are suffering from the same bug as me and the module will help you.

[Russell Faull (rfaull)]

Hi Joshua, thanks. An interim report: 10 reboots with 3.14-rc2, Bluetooth mouse active at login screen each time (no spasmodic effect as you mentioned at #55); USB3 also works; and my device is different to yours

russell@V5-132:~$ lspci -vvnn | grep Atheros
02:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)

I guess this means the module might work with 3.11.0-generic. I'll try it later today (UTC +10 here) and report again.

[penalvch (penalvch)]

Russell Faull, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Joshua (njj)]

Russell, could you please do a "lsusb -t" with any mainline kernel where bluetooth is working fine (not the one I compiled and uploaded), and tell me if btusb uses a xHCI or EHCI port?

[Russell Faull (rfaull)]

Hi Joshua

The results below are for the kernel with Bluetooth working satisfactorily. The computer has two usb ports: one is usb3 and seems to only transfer data at usb2 speeds, ie approximately 30Mb/s.

I have build the module using kernel 3.11.0-15-generic following your instructions at #72 but insmod seems to stall, not returning any results, subsequently sudo modprobe xhci-quirk.ko also fails.

russell@V5-132:~$ uname -a
Linux V5-132 3.14.0-031400rc2-generic #201402092235 SMP Mon Feb 10 03:57:45 UTC 2014 i686 i686 i686 GNU/Linux
russell@V5-132:~$ lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 4: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
        |__ Port 4: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=rts5139, 480M
        |__ Port 4: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
        |__ Port 4: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M

Hi Christopher, thank you. I will file a separate bug report for my hardware later today.

[Joshua (njj)]

Russel, "my" module will not help you get your bt device working under 3.11, it just switches all usb ports from xHCI (USB 3.0) mode to EHCI (USB 2.0) mode, because the ath3k driver is bugy with xHCI. But your "lsusb -t" shows that port 4, which btusb uses, is already in EHCI mode. So you are not suffering from this issue at all.

It is very likely that your device id is just missing in 3.11, could you show me a "lsusb" output without parameter, because the extract you posted in #75 does not show the needed info.

[Russell Faull (rfaull)]

Joshua, thanks, here is the result of lsusb:

russell@V5-132:~$ uname -a
Linux V5-132 3.14.0-031400rc2-generic #201402092235 SMP Mon Feb 10 03:57:45 UTC 2014 i686 i686 i686 GNU/Linux
russell@V5-132:~$ lsusb
Bus 002 Device 003: ID 064e:c400 Suyin Corp.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp.
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Joshua (njj)]

Russel, your bt device is "Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp.". This device id is upstream since 3.14-rc1 just like mine. But you are lucky and your bt card doesn't use a xHCI port, dunno if this is something physical or controlled by your BIOS, so yo definitly don't need "my" module. However you should open your own bug report like Christopher said and ask the ubuntu team to cherry pick the patch for your device id like I did for my device. [0] [1]

[0] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/bluetooth/ath3k.c?id=bd0fca1b2be8c96dfc391a2bc2ee4ce6970ae6af
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/bluetooth/btusb.c?id=bd0fca1b2be8c96dfc391a2bc2ee4ce6970ae6af

[Uldis Kalniņš (ulcha)]

I can confirm same problem and solution - missing device id's and USB3 incompatibility (very sporadic working) for HP ProBook 450 G1.
Kernel id patch and custom compiled kernel with disabled USB3 completely resolves bluetooth problems.

Below - output with default kernel:

uname -a
Linux oskars-HP-ProBook-450-G1 3.11.0-17-generic #31-Ubuntu SMP Mon Feb 3 21:52:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
    |__ Port 7: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 7: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 12: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 12: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M

lsusb
Bus 003 Device 003: ID 0cf3:311f Atheros Communications, Inc.

lspci -vvnn | grep Atheros
03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)

Custom kernel is same as original kernel, except disabled USB3 and patched ath3k.ko and btusb.ko, compiled from https://github.com/Satius/mod_0cf3_311f source.

Unfortunately from tomorrow i'll be mostly unable to test any changes, since that computer goes away in production.

[Uldis Kalniņš (ulcha)]

Custom kernel output:

uname -a
Linux oskars-HP-ProBook-450-G1 3.11.10.3 #1 SMP Sun Feb 23 20:43:59 EET 2014 x86_64 x86_64 x86_64 GNU/Linux
oskars@oskars-HP-ProBook-450-G1:~$

lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
        |__ Port 3: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
        |__ Port 3: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
        |__ Port 6: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
        |__ Port 6: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M

lsusb
Bus 001 Device 005: ID 0cf3:311f Atheros Communications, Inc.

lspci -vvnn | grep Atheros
03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)

This laptop don't have any BIOS option to switch USB3 ports in USB2 mode.

[Uldis Kalniņš (ulcha)]

Quick'n dirty fix to get both USB3 and Bluetooth running every time - do automatic xhci_xcd unload / load cycle until no error messages in syslog is detected:

Needs:
1. custom compiled kernel with xhci_xcd as module, not builtin.
2. Upstream kernel with device ids for 168c:0036 or recompiled modules from https://github.com/Satius/mod_0cf3_311f source.

1. Install Logmon from here
http://code.google.com/p/linscripts/wiki/logmon
2. Copy logmon.sh to /usr/sbin
3. Create executable shell script with following contents in /usr/sbin:

sudo touch /usr/sbin/logmon-run.sh
sudo chmod +x /usr/sbin/logmon-run.sh

paste in:
#!/bin/bash
rmmod xhci-hcd
modprobe xhci-hcd

4. modify /etc/rc.local, add before line exit 0

/usr/sbin/logmon-run.sh
/usr/sbin/logmon.sh "/usr/sbin/logmon-run.sh" -m "Error in firmware loading" /var/log/kern.log&

========
Indeed, additional minor bug found for HP ProBook 450 G1, unfortunately no time to go in deeper checks - if USB3 is disabled in kernel, then after suspend / resume all USB ports are dead. Until suspend everything is working perfectly in USB2 mode. So no way to live without USB3.

[joey reichard (smokin420papi)]

ive tried everything in the post and it does not work ive tried xhci and logmon and nothing worked i know nothing about commands it wont load module

[Vasil Yakauleu (vasilbelarus)]

reproducible on LTS 14.04 with latest updates on Packard Bell Z5WT1 laptop

[penalvch (penalvch)]

Vasil Yakauleu, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Antonio J. de Oliveira (ajoliveira)]

Hi. no way, the module is useless bluetooth does not work,never on my hardware. have you checked it? need help in debugging? All the best

[penalvch (penalvch)]

Antonio J. de Oliveira, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Antonio J. de Oliveira (ajoliveira)]

ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ajoliveira 3380 F.... panel-21-mixer
                      ajoliveira 3426 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=a116cc7d-cad3-4aa7-99cf-9e2e5c609029
InstallationDate: Installed on 2014-03-19 (62 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
MachineType: Acer Aspire E1-570G
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=08f4eaf7-f115-466c-b87f-000108c27cab ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-20-generic N/A
 linux-backports-modules-3.13.0-20-generic N/A
 linux-firmware 1.127.2
Tags: trusty
Uname: Linux 3.13.0-20-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-03-29 (52 days ago)
UserGroups: adm audio bumblebee cdrom dip lpadmin plugdev sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 07/30/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.02
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_CX
dmi.board.vendor: Acer
dmi.board.version: V2.02
dmi.chassis.asset.tag: Acer Asset Tag String
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.02
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd07/30/2013:svnAcer:pnAspireE1-570G:pvrV2.02:rvnAcer:rnEA50_CX:rvrV2.02:cvnInsydeCorp.:ct10:cvrV2.02:
dmi.product.name: Aspire E1-570G
dmi.product.version: V2.02
dmi.sys.vendor: Acer

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

Coudn't use ubuntu-bug. Reports kernel is not an official one. So opted for posting here. This bug looks like a duplicate of Bug #1287811 .

[penalvch (penalvch)]

Antonio J. de Oliveira, please do not apport-collect to another persons report. The reason you weren't able to use ubuntu-bug is because you are using an old kernel, which is not officially supported. Please update your kernel, and then file the new report.

[Antonio J. de Oliveira (ajoliveira)]

Ok, sorry for the inconvenience. This bug remains in 3.13.0-24 after I upgraded to it installing the linux-imagepackage and seems to be solved in 3.14.1-031401-generic. A quick fix in trusty seems to be what I did on my 64-bit system:

$ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-headers-3.14.1-031401_3.14.1-031401.201404141220_all.deb

$ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-headers-3.14.1-031401-generic_3.14.1-031401.201404141220_amd64.deb

$ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-image-3.14.1-031401-generic_3.14.1-031401.201404141220_amd64.deb

$ sudo dpkg -i linux-headers-3.14.1-*.deb linux-image-3.14.1-*.deb

Thanks.

[Antonio J. de Oliveira (ajoliveira)]

On 32-bit systems:

$ wget kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-headers-3.14.1-031401_3.14.1-031401.201404141220_all.deb

$ wget kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-headers-3.14.1-031401-generic_3.14.1-031401.201404141220_i386.deb

$ wget kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-image-3.14.1-031401-generic_3.14.1-031401.201404141220_i386.deb

$ sudo dpkg -i linux-headers-3.14.1-*.deb linux-image-3.14.1-*.deb

Don't forget to reboot...

[LE BIDEAU (elbc)]

Any news on this issue ? with kernels older than 3.15 device 0cf3:311f is not recognized and with kernels equal or newer than 3.15 it works sporadic

[penalvch (penalvch)]

LE BIDEAU, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Joseph Salisbury (jsalisbury)]

This bug was nominated against a series that is no longer supported, ie saucy. The bug task representing the saucy nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Mauro (mauromol)]

I have the same wifi card on an HP ProBook 450 G1 laptop. In Linux Mint 17 KDE (based on Ubuntu 14.04) wifi works, Bluetooth doesn't.
Yesterday it couldn't find any Bluetooth devices, nor it was detectable by another Bluetooth device even if visible.
Today the Bluetooth adapter seems to have disappeared completely and I don't understand how it is possible (rfkill list shows only the wifi device, while previously it used to show the non-working Bluetooth device too...).

I read the whole report but I'm a bit lost. Was this bug fixed somewhere? Can we expect to have it working on an upcoming kernel upgrade for Trusty?

[penalvch (penalvch)]

Mauro, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Mauro (mauromol)]

Hi Christopher, in order to track my problem I downloaded the official Ubuntu Desktop Linux 14.04.1 amd64 image with a torrent file from the Ubuntu website, burnt it on a USB stick and booted from it. I reproduced this problem. However, when I type "ubuntu-bug linux" in a terminal, the following error message is shown, after the "collecting data" phase:
Problem in linux-image-3.13.0-32-generic
This is not an official Ubuntu package. Please remove any third-party package and try again.

However, I used the ISO image as-is and didn't install any third-party package!!

In this way, I can't proceed with the bug reporting. What's wrong?

[penalvch (penalvch)]

Mauro, please try http://cdimage.ubuntu.com/daily-live/current/ . If it still doesn't work, please contact me directly so as to not impede this report with non-relevant information.

[Mauro (mauromol)]

Hi Christopher,
I'm still writing here because I think this is useful to know for other people with this problem (affecting ath9k).
with http://cdimage.ubuntu.com/daily-live/current/vivid-desktop-amd64.iso Bluetooth works! However, is it useful to track it anyway for a possible backporting to Trusty? If so, which image should I use, since the 14.04.1 image is giving me the mentioned error with ubuntu-bug command?

Also please note that with Vivid there's a regression with the wireless button switch, I'm going to add a note to bug #1313196.

[Mauro (mauromol)]

oh well, it seems like with Trusty and kernel version 3.13.0-39-generic I just installed, Bluetooth is working correctly! So, I think this can be considered fixed, at least on my hardware.

[António J. de Oliveira (barcarossa-g)]

With Trusty 3.16.2-031602-generic #201409052035 SMP Sat Sep 6 00:36:44 UTC 2014 x86_64 x86_64 x86_64 bluetooth works as expected.

[Daniel van Vugt (vanvugt)]

This bug is 8 years old so we should defer to more current bugs like bug 1925318 and bug 1940759