linux-kernel - firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 28 Dec 2011 12:20:15 -0430
From:	Andres Cimmarusti <acimmarusti@...il.com>
To:	linux-bluetooth@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, Jonathan Nieder <jrnieder@...il.com>,
	641749@...s.debian.org, info@...uxcertified.com
Subject: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

Dear all,

This is an upstream bug report for known bugs in at least 3 linux distros:

Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641749
Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=702375

***Steps to reproduce***

- Boot current Debian testing / Fedora 16 / Ubuntu 11.10 (using
kernels 3.1.x and 3.0.x)

***Expected behavior***

- Working bluetooth and no problems in rebooting laptop as occurs
using Ubuntu 11.04 / Fedora 15 and/or Debian Squeeze (using kernels
2.6.38 or newer)

- lsusb reveals this:

Bus 001 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth

***Actual Result***

- Boot process stalls and fails to load firmware for this Atheros
AR3011 bluetooth module:

[    9.335184] ath3k_load_firmware: Can't change to loading configuration err
[    9.335413] ath3k: probe of 1-1.3:1.0 failed with error -110
[    9.335459] usbcore: registered new interface driver ath3k

- lsusb of the device shows this:

Bus 001 Device 003: ID 0cf3:3000 Atheros Communications, Inc. AR3011
Bluetooth (no firmware)

- After login bluetooth does not work. Furthermore, choosing to
"Restart" the laptop causes it to hang at first pre-bios post screen.

***Things I've tried***

The weird part about this bug is that using Debian squeeze as a base,
I can run the newest kernels (2.6.39, 3.0.x and 3.1.x) and I have no
problems at all. Also the output of lsusb differs substantially from
the working vs broken system. Ubuntu 11.04 and Fedora 15 also work
fine using kernel 2.6.38.

Here is an example dmesg, using kernel 3.0.8 on Squeeze (no problem):

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=56;filename=dmesg_stable%2B3.0.8.txt;att=2;bug=641749

And here is a similar 3.0.x Debian mainline kernel running on top of
Debian testing (wheezy):

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=56;filename=dmesg_testing%2B3.0.0-2.txt;att=1;bug=641749

If you browse the Debian bug report link listed at the beginning of
this email, you will also be able to get logs for kernel 3.1.x.
Furthermore, I've tested downgrading the version of udev to the one
found in Debian squeeze (version 164) as well as usb-modeswitch (also
tried upgrading to the latest versions in Debian unstable), but this
has yielded no progress and no clues at all...the error messages
remain the same.

Help debugging this issue would be most welcome.

Best Regards

Andres Cimmarusti

PS: For reference this is a Linux Certified laptop model LC2131, also
known as the Zareason Strata Pro 13 or the ASI SpringPeak 13
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/