ath9k wireless stopped working after kernel upgrade to 3.2.0-12

[Hector Sansores]

It was working fine with the previous kernel version. Computer is an Acer Aspire S3.

It keeps asking for password but never connects.

$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

$ nm-tool

NetworkManager Tool

State: connecting

- Device: wlan0 [INFINITUM5385] -----------------------------------------------
  Type: 802.11 WiFi
  Driver: ath9k
  State: connecting (getting IP configuration)
  Default: no
  HW Address: 74:DE:2B:86:58:0F

  Capabilities:

  Wireless Properties
    WEP Encryption: yes
    WPA Encryption: yes
    WPA2 Encryption: yes

$ sudo lshw -C network
  *-network
       description: Wireless interface
       product: AR9485 Wireless Network Adapter
       vendor: Atheros Communications Inc.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlan0
       version: 01
       version: 01
       serial: 74:de:2b:86:58:0f
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom ethernet physical wireless
       configuration: broadcast=yes driver=ath9k driverversion=3.2.0-12-generic firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11bgn
       resources: irq:17 memory:c0400000-c047ffff memory:afb00000-afb0ffff
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC271X Analog [ALC271X Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: hectorsq 1766 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xc0500000 irq 43'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0269,10250635,00100100 HDA:80862805,80860101,00100000'
   Controls : 18
   Simple ctrls : 8
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=9c4677c1-f16c-4d40-aa23-17b63fabb49f
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
MachineType: Acer Aspire S3
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-12-generic root=UUID=5fedcc21-1960-4555-9b33-9035040f50c3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-12-generic N/A
 linux-backports-modules-3.2.0-12-generic N/A
 linux-firmware 1.68
StagingDrivers: rts5139 mei
Tags: precise running-unity staging
Uname: Linux 3.2.0-12-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-01-27 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 09/28/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire S3
dmi.board.vendor: Acer
dmi.board.version: 1.15
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.15:bd09/28/2011:svnAcer:pnAspireS3:pvr1.15:rvnAcer:rnAspireS3:rvr1.15:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: Aspire S3
dmi.product.version: 1.15
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/923512/+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 923512

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.

[Joseph Salisbury (jsalisbury)]

I'd like to bisect between the two kernels to try to identify the commit that caused this regression. Would you be able to test some test kernels?

[Joseph Salisbury (jsalisbury)]

Also, can you clarify what kernel version you are referring to? Did you upgrade to Precise from a previous release? If you boot back into the 3.2.0-11[1] kernel, does the issue go away?

[1] https://launchpad.net/ubuntu/+source/linux/3.2.0-11.19

[D. Wegener (dpwegener)]

I am experiencing the problem after upgrading from 3.2.0-11 to 3.2.0-12. Booting back into the 3.2.0-11 kernel fixes the problem so it appears to be an issue introduced in 3.2.0-12.

[Hector Sansores (mail-hectorsq)]

Joseph,

The bug appeared after update manager upgraded from 3.2.0-11 to 3.2.0-12.

I can do any tests you need, however, even I am a software developer, I do
not have too much experience with linux, so I would need precise
instructions.

D. Wegener has confirmed that the bug dissapears booting with 3.2.0-11

Regards,
Hector Sansores

On Mon, Jan 30, 2012 at 10:10 AM, Joseph Salisbury <
<email address hidden>> wrote:

> I'd like to bisect between the two kernels to try to identify the commit
> that caused this regression. Would you be able to test some test
> kernels?
>
>

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Hector Sansores (mail-hectorsq)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test two mainline kernels?

The two kernels are:
v3.2.1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.1-precise/

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

I expect the bug to exist in v3.2.2. Testing v3.2.1 will let us know which versions to bisect between.

[Hector Sansores (mail-hectorsq)]

You are right.

v3.2.1 works fine.
v3.2.2 does not work.

[Joseph Salisbury (jsalisbury)]

The first set of bisected kernels are available at:
http://people.canonical.com/~jsalisbury/lp923512/

Can you test that kernel and report back if the bug exists or not. I will then continue to bisect and generate another test kernel based on your results.

[Joseph Salisbury (jsalisbury)]

The test kernel I just posted is built up to commit:
b20b30d4d382e151daaee5466ce2427f653170af

[D. Wegener (dpwegener)]

I tested the kernel you referenced in comment #30. The Wireless card is working with this kernel.

[Hector Sansores (mail-hectorsq)]

I too tested the kernel in comment #30. Wireless is working fine.

[Joseph Salisbury (jsalisbury)]

Further info about this bug upstream:
http://marc.info/?l=linux-wireless&m=132798971403989&w=2

I am building a test kernel with the following commit reverted:
r7a532fe7131216a02c81a6c1b1f8632da1195a58

I'll post a link to the test kernel shortly.

[Joseph Salisbury (jsalisbury)]

There is a test kernel with the previous mentioned commit reverted(r7a532fe7131216a02c81a6c1b1f8632da1195a58). The kernel is available from: http://people.canonical.com/~jsalisbury/lp923512/

Can you test that kernel and report back the results?

[Joseph Salisbury (jsalisbury)]

I actually moved the kernels I build to the following location:
 http://people.canonical.com/~jsalisbury/lp923512/upstream

The kernels I posted are from an upstream build with that commit reverted.

We are building another set of test kernels from the latest Precise tree with the same commit reverted. Those kernels will be posted shortly.

[Leann Ogasawara (leannogasawara)]

I've built a Precise test kernel with the possible offending patch reverted:

http://people.canonical.com/~ogasawara/lp923512/amd64/

If you could please test it would be appreciated. I'd like the feedback from this kernel asap as if this resolves the issue, I'd like to try to get it uploaded before the Alpha-2 milestone. Testing feedback from this kernel instead of the upstream kernel in comment #36 would be more helpful.

[Hector Sansores (mail-hectorsq)]

I have tested the kernel in comment #37

http://people.canonical.com/~ogasawara/lp923512/amd64/

It worked fine!

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 3.2.0-12.21

---------------
linux (3.2.0-12.21) precise; urgency=low

  [ Upstream Kernel Changes ]

  * Revert "ath9k_hw: fix interpretation of the rx KeyMiss flag"
    - LP: #923512
 -- Leann Ogasawara <email address hidden> Mon, 30 Jan 2012 06:46:01 -0800

[Hector Sansores (mail-hectorsq)]

I have tested the kernel in comment #36

http://people.canonical.com/~jsalisbury/lp923512/upstream

It is working fine!

[Leann Ogasawara (leannogasawara)]

Hi Hector et al.

It appears a proper fix has come in via upstream stable. Could you please test the following test kernel I've built and confirm this issue remains fixed. Thanks in advance.

http://people.canonical.com/~ogasawara/lp923512/amd64/