8086:4236 Wifi regression in linux-image-3.2.0-35-generic-pae

[swmike]

Hello.

I have a Thinkpad X200 with Intel 5300 wifi card.

03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
        Subsystem: Intel Corporation Device 1011
        Physical Slot: 1
        Flags: bus master, fast devsel, latency 0, IRQ 48
        Memory at f2a00000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [c8] Power Management version 3
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [e0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 00-21-6a-ff-ff-03-8c-26
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

After upgrading to 3.2.0-35 from 3.2.0-34 I have problems connecting to my D-link DIR-855 on 5GHz. After rebooting the computer, I frequently have to reboot my router in order to connect. Reloading (rmmod/modprobe) iwlwifi doesn't help. I tried several times back and forth between 3.2.0-35 and 3.2.0-34 and with 3.2.0-34 I can always connect without rebooting the router, but with -35 I have yet to be able to connect directly after boot without rebooting the router. I can disconnect the wifi (bring my computer with me in suspended mode, be somewhere else and use it, and then bring it back home) and it can successfully connect. It's just the initial connect after boot that is affected.

When it's trying to connect with -35 I get the following:

Jan 5 06:51:33 swm-laptop kernel: [ 19.458855] cfg80211: Found new beacon on frequency: 5240 MHz (Ch 48) on phy0
Jan 5 06:51:38 swm-laptop kernel: [ 24.955771] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
Jan 5 06:51:38 swm-laptop kernel: [ 25.152031] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
Jan 5 06:51:39 swm-laptop kernel: [ 25.352043] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
Jan 5 06:51:39 swm-laptop kernel: [ 25.552027] wlan0: direct probe to 00:21:91:dc:94:57 timed out
Jan 5 06:51:47 swm-laptop kernel: [ 33.759793] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
Jan 5 06:51:47 swm-laptop kernel: [ 33.956034] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
Jan 5 06:51:47 swm-laptop kernel: [ 34.156044] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
Jan 5 06:51:48 swm-laptop kernel: [ 34.356035] wlan0: direct probe to 00:21:91:dc:94:57 timed out

After rebooting the router and rebooting with -35 again, I get the following:

Jan 5 06:53:48 swm-laptop kernel: [ 19.491134] cfg80211: Found new beacon on frequency: 5200 MHz (Ch 40) on phy0
Jan 5 06:53:54 swm-laptop kernel: [ 25.334809] wlan0: authenticate with 00:21:91:dc:94:57 (try 1)
Jan 5 06:53:54 swm-laptop kernel: [ 25.532032] wlan0: authenticate with 00:21:91:dc:94:57 (try 2)
Jan 5 06:53:54 swm-laptop kernel: [ 25.533294] wlan0: authenticated
Jan 5 06:53:54 swm-laptop kernel: [ 25.539144] wlan0: associate with 00:21:91:dc:94:57 (try 1)
Jan 5 06:53:54 swm-laptop kernel: [ 25.736038] wlan0: associate with 00:21:91:dc:94:57 (try 2)
Jan 5 06:53:54 swm-laptop kernel: [ 25.737848] wlan0: RX AssocResp from 00:21:91:dc:94:57 (capab=0x111 status=0 aid=3)
Jan 5 06:53:54 swm-laptop kernel: [ 25.737851] wlan0: associated
Jan 5 06:53:54 swm-laptop kernel: [ 25.744338] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 5 06:53:54 swm-laptop kernel: [ 25.744413] cfg80211: Calling CRDA for country: GB
Jan 5 06:53:54 swm-laptop kernel: [ 25.750032] cfg80211: Updating information on frequency 2412 MHz for a 20 MHz width chan
nel with regulatory rule:
Jan 5 06:53:54 swm-laptop kernel: [ 25.750036] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)

... snip

Jan 5 06:53:54 swm-laptop kernel: [ 25.750206] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 5 06:53:54 swm-laptop kernel: [ 25.750209] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 5 06:53:54 swm-laptop kernel: [ 25.750211] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 5 06:53:54 swm-laptop kernel: [ 25.750214] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 5 06:53:54 swm-laptop kernel: [ 25.750216] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Jan 5 06:53:54 swm-laptop kernel: [ 25.840049] cfg80211: Found new beacon on frequency: 5200 MHz (Ch 40) on phy0
Jan 5 06:54:03 swm-laptop kernel: [ 34.794517] iwlwifi 0000:03:00.0: Tx aggregation enabled on ra = 00:21:91:dc:94:57 tid = 0
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: swmike 2420 F.... pulseaudio
CRDA:
 country GB:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2b20000 irq 49'
   Mixer name : 'Conexant CX20561 (Hermosa)'
   Components : 'HDA:14f15051,17aa20ff,00100000'
   Controls : 21
   Simple ctrls : 13
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7XHT24WW-1.06'
   Mixer name : 'ThinkPad EC 7XHT24WW-1.06'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DistroRelease: Ubuntu 12.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=/dev/sda6
MachineType: LENOVO 7454CTO
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: root=UUID=2a9a0898-4ec3-4685-a9ac-9afae45ad815 ro quiet splash
ProcVersionSignature: Ubuntu 3.2.0-35.55-generic-pae 3.2.34
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/swmike not ours.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-35-generic-pae N/A
 linux-backports-modules-3.2.0-35-generic-pae N/A
 linux-firmware 1.79.1
StagingDrivers: crystalhd mei
Tags: precise staging
Uname: Linux 3.2.0-35-generic-pae i686
UpgradeStatus: Upgraded to precise on 2012-04-27 (253 days ago)
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 05/16/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET70WW (3.20 )
dmi.board.name: 7454CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET70WW(3.20):bd05/16/2011:svnLENOVO:pn7454CTO:pvrThinkPadX200:rvnLENOVO:rn7454CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7454CTO
dmi.product.version: ThinkPad X200
dmi.sys.vendor: LENOVO

[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 1096294

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.

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

apport information

[swmike (ubuntu-s-plass)]

I just upgraded to the latest version, -36. The problem still occurs, but I would like to quantify my statement.

Sometimes it just works after reboot. The last time I rebooted into -36, it didn't work:

[ 27.331188] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[ 27.528030] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[ 27.728030] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[ 27.928030] wlan0: direct probe to 00:21:91:dc:94:57 timed out
[ 36.032700] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[ 36.232028] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[ 36.432030] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[ 36.632043] wlan0: direct probe to 00:21:91:dc:94:57 timed out
[ 44.940623] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[ 45.140051] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[ 45.340044] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[ 45.540044] wlan0: direct probe to 00:21:91:dc:94:57 timed out
[ 61.945281] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[ 62.144064] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[ 62.344069] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[ 62.544064] wlan0: direct probe to 00:21:91:dc:94:57 timed out
[ 70.851155] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[ 71.048040] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[ 71.248147] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[ 71.448132] wlan0: direct probe to 00:21:91:dc:94:57 timed out

I then rmmod iwlwifi and insmoded it again:

Then after a few retries, it started working:

[ 79.664793] iwlwifi 0000:03:00.0: PCI INT A disabled
[ 84.661642] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[ 84.661645] Copyright(c) 2003-2011 Intel Corporation
[ 84.661694] iwlwifi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 84.661706] iwlwifi 0000:03:00.0: setting latency timer to 64
[ 84.661730] iwlwifi 0000:03:00.0: pci_resource_len = 0x00002000
[ 84.661732] iwlwifi 0000:03:00.0: pci_resource_base = f845c000
[ 84.661734] iwlwifi 0000:03:00.0: HW Revision ID = 0x0
[ 84.661819] iwlwifi 0000:03:00.0: irq 44 for MSI/MSI-X
[ 84.661861] iwlwifi 0000:03:00.0: Detected Intel(R) Ultimate N WiFi Link 5300 AGN, REV=0x24
[ 84.661922] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 84.683775] iwlwifi 0000:03:00.0: device EEPROM VER=0x11f, CALIB=0x4
[ 84.683778] iwlwifi 0000:03:00.0: Device SKU: 0Xf0
[ 84.683802] iwlwifi 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
[ 84.687839] iwlwifi 0000:03:00.0: loaded firmware version 8.83.5.1 build 33692
[ 84.688113] Registered led device: phy1-led
[ 84.688143] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
[ 84.689366] ieee80211 phy1: Selected rate control algorithm 'iwl-agn-rs'
[ 84.701998] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 84.705005] iwlwifi 0000:03:00.0: Radio type=0x0-0x2-0x0
[ 84.857046] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 84.860047] iwlwifi 0000:03:00.0: Radio type=0x0-0x2-0x0
[ 84.909114] ADDRCONF(NETDEV_UP): wlan0: link is not ready...

[penalvch (penalvch)]

swmike, thank you for reporting this and helping make Ubuntu better. As per http://support.lenovo.com/en_US/downloads/default.page? an update is available for your BIOS (3.22). If you update to this, does it change anything?

[swmike (ubuntu-s-plass)]

Hello. Thanks for the interest in my problem.

I updated bios just now:

     *-firmware
          description: BIOS
          vendor: LENOVO
          physical id: 0
          version: 6DET72WW (3.22 )
          date: 10/25/2012
          size: 128KiB
          capacity: 8128KiB

I am now running -26 kernel. First cold boot after BIOS update worked ok (wifi started working after a few direct probe retries), then I rebooted again and got the excessive retries and wifi wouldn't associate. I tried rmmod/modprobe iwlwifi 4 times, still no go, same behaviour. I then rebooted the router and rmmod/insmod again, and then things started working. The behaviour is a bit erratic, but it seems that the problem occurs after 1-2 weeks of uptime for the router. Cold booting the X200 doesn't usually solve the problem either, I tried that with the -35 kernel.

I have had the X200 and the DIR-855 router for 4 years and never seen this behaviour before the 3.2.0-35 kernel.

[swmike (ubuntu-s-plass)]

Hello. Typo above, I meant to say I am running -36 kernel. Sorry.

[penalvch (penalvch)]

swmike, thank you for updating your BIOS. Could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.8-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[swmike (ubuntu-s-plass)]

I downloaded linux-image-3.8.0-030800rc5-generic_3.8.0-030800rc5.201301251535_i386.deb, rebooted, noticed that it didn't have the iwlwifi module, rebooted back into 3.2.0-36, had the wifi problem, rebooted to -34, worked, downloaded the extra package (linux-image-extra-3.8.0-030800rc5-generic_3.8.0-030800rc5.201301251535_i386.deb), rebooted into 3.8.0-rc5, everything worked as it should.

Then I made a mistake and shut the computer down instead of rebooting. Turned it back on and booted into -36 which worked, rebooted again to -36 and still worked. So I think I have to wait 1-2 weeks until I can totally confirm that -36 definitely doesn't work and 3.8.0-rc5 does. I will update this bug report in 1-2 weeks again to confirm.

This is the dmesg output from 3.8.0-rc5:

[ 34.247168] wlan0: authenticate with 00:21:91:dc:94:57
[ 34.251974] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[ 34.342850] init: anacron main process (1450) killed by TERM signal
[ 34.452035] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[ 34.496062] init: plymouth-stop pre-start process (2082) terminated with status 1
[ 34.656029] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[ 34.860022] wlan0: authentication with 00:21:91:dc:94:57 timed out
[ 42.951286] wlan0: authenticate with 00:21:91:dc:94:57
[ 42.956772] wlan0: send auth to 00:21:91:dc:94:57 (try 1/3)
[ 43.160038] wlan0: send auth to 00:21:91:dc:94:57 (try 2/3)
[ 43.364036] wlan0: send auth to 00:21:91:dc:94:57 (try 3/3)
[ 43.473487] wlan0: authenticated
[ 43.476077] wlan0: associate with 00:21:91:dc:94:57 (try 1/3)
[ 43.477066] wlan0: RX AssocResp from 00:21:91:dc:94:57 (capab=0x111 status=0 aid=1)
[ 43.480544] wlan0: associated
[ 43.480610] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 43.480760] cfg80211: Calling CRDA for country: GB
[ 43.492207] cfg80211: Regulatory domain changed to country: GB
[ 43.492217] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 43.492223] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 43.492229] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 43.492234] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
[ 43.492239] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
[ 43.566951] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 00:21:91:dc:94:57
swmike@swm-laptop:~$ uname -a
Linux swm-laptop 3.8.0-030800rc5-generic #201301251535 SMP Fri Jan 25 20:55:12 UTC 2013 i686 i686 i386 GNU/Linux

[swmike (ubuntu-s-plass)]

I rebooted this morning, tried 3.2.0-36, didn't work, rebooted into 3.2.0-36 again, didn't work, rmmod/modprobe iwlwifi, still no go. Rebooted into 3.8-rc5 listed above, wifi immediately started working. Then rebooted into 3.2.0-36 again, which immediately worked.

No cold start above, just reboots.

[swmike (ubuntu-s-plass)]

I rebooted into -39 after it was released. Now my 5Ghz network doesn't seem to want to stay connected at all. I keep getting disconnected:

Mar 21 18:21:11 swm-laptop kernel: [606888.625371] watchdog: only one watchdog can use /dev/watchdog.
Mar 21 18:21:11 swm-laptop kernel: [606888.625377] watchdog: error registering /dev/watchdog (err=-16).
Mar 21 18:21:11 swm-laptop kernel: [606888.625379] mei: unable to register watchdog device.
Mar 21 18:21:14 swm-laptop kernel: [606891.729033] iwlwifi 0000:03:00.0: Tx aggregation enabled on ra = 00:21:91:dc:94:57 ti
d = 0
Mar 21 18:21:16 swm-laptop kernel: [606893.486341] wlan0: deauthenticating from 00:21:91:dc:94:57 by local choice (reason=3)
Mar 21 18:21:16 swm-laptop kernel: [606893.528541] cfg80211: All devices are disconnected, going to restore regulatory settings
Mar 21 18:21:16 swm-laptop kernel: [606893.528548] cfg80211: Restoring regulatory settings

Even booting 3.2.0-34 or 3.8.0 helps, so now I'm restricted to 2.4GHz. I don't know if there was some other change that happened at the same time (network manager) that might be causing this. I tried booting a daily build of raring which had the same behaviour. I'm going to install Windows 7 or windows 8 on a separate harddisk sometime and see if that works ok, to rule out hardware problem.

[swmike (ubuntu-s-plass)]

With 3.2.0-39 and backported 3.6-wireless drivers I now get these:

[302142.996073] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues
[302145.004266] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues
[302147.996316] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues
[302150.996194] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues
[302150.996215] wlan0: deauthenticated from 00:21:91:dc:94:57 (Reason: 6)
[302151.022958] ------------[ cut here ]------------
[302151.022993] WARNING: at /build/buildd/linux-backports-modules-3.2.0-3.2.0/debian/build/build-generic-pae/cw-3.6/drivers/net/wireless/iwlwifi/dvm/tx.c:1187 iwlagn_rx_reply_tx+0x984/0x9b0 [iwldvm]()
[302151.023003] Hardware name: 7454CTO
[302151.023007] Modules linked in: tcp_diag inet_diag iwldvm(O) iwlwifi(O) pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) rfcomm(O) parport_pc bnep(O) ppdev binfmt_misc dm_crypt arc4 mac80211(O) dm_multipath snd_hda_codec_conexant thinkpad_acpi uvcvideo videodev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm btusb(O) bluetooth(O) snd_seq_midi psmouse snd_rawmidi serio_raw crystalhd(C) cfg80211(O) snd_seq_midi_event compat(O) snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc nvram tpm_tis mei(C) mac_hid coretemp lp parport raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear wmi i915 drm_kms_helper drm i2c_algo_bit video [last unloaded: iwlwifi]
[302151.023169] Pid: 0, comm: swapper/0 Tainted: G WC O 3.2.0-39-generic-pae #62-Ubuntu
[302151.023176] Call Trace:
[302151.023191] [<c159294f>] ? printk+0x2d/0x2f
[302151.023204] [<c105a5b2>] warn_slowpath_common+0x72/0xa0
[302151.023224] [<f92a6d44>] ? iwlagn_rx_reply_tx+0x984/0x9b0 [iwldvm]
[302151.023243] [<f92a6d44>] ? iwlagn_rx_reply_tx+0x984/0x9b0 [iwldvm]
[302151.023253] [<c105a602>] warn_slowpath_null+0x22/0x30
[302151.023272] [<f92a6d44>] iwlagn_rx_reply_tx+0x984/0x9b0 [iwldvm]
[302151.023297] [<f92b03ce>] iwl_rx_dispatch+0x6e/0xe0 [iwldvm]
[302151.023308] [<c15a870d>] ? _raw_spin_lock_irqsave+0x2d/0x40
[302151.023331] [<f87c3de1>] iwl_irq_tasklet+0x761/0xe10 [iwlwifi]
[302151.023344] [<c1061270>] ? local_bh_enable_ip+0x90/0x90
[302151.023353] [<c1060d93>] tasklet_action+0x63/0x110
[302151.023362] [<c1061270>] ? local_bh_enable_ip+0x90/0x90
[302151.023370] [<c10612f1>] __do_softirq+0x81/0x1a0
[302151.023379] [<c1061270>] ? local_bh_enable_ip+0x90/0x90
[302151.023385] <IRQ> [<c1061636>] ? irq_exit+0x76/0xa0
[302151.023401] [<c15b00db>] ? do_IRQ+0x4b/0xc0
[302151.023411] [<c1017be8>] ? sched_clock+0x8/0x10
[302151.023422] [<c107ffeb>] ? sched_clock_local+0xcb/0x1c0
[302151.023431] [<c15aff30>] ? common_interrupt+0x30/0x38
[302151.023441] [<c10800d8>] ? sched_clock_local+0x1b8/0x1c0
[302151.023453] [<c132ad49>] ? arch_local_irq_enable+0x7/0xb
[302151.023462] [<c132ba7d>] ? acpi_idle_enter_bm+0x228/0x268
[302151.023474] [<c147e86d>] ? cpuidle_idle_call+0xad/0x250
[302151.023485] [<c101075c>] ? cpu_idle+0x9c/0xe0
[302151.023494] [<c15755a5>] ? rest_init+0x5d/0x68
[302151.023505] [<c1879787>] ? start_kernel+0x352/0x358
[302151.023514] [<c18793c6>] ? pass_bootoption.constprop...

[penalvch (penalvch)]

swmike, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]