iwlagn causes kernel panic on 802.11n wifi

[James Ward]

I have a Lenovo W500 Laptop with the latest Jaunty and Intrepid. Both kernel panic within minutes of booting and connecting to a Wifi access point. If I disable the wireless and use a wired connection then I do not get kernel panics. My card's lspci description is:
03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
 Subsystem: Intel Corporation Device 1011
 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Interrupt: pin A routed to IRQ 17
 Region 0: Memory at f4300000 (64-bit, non-prefetchable) [size=8K]
 Capabilities: <access denied>
 Kernel driver in use: iwlagn
 Kernel modules: iwlagn

My AP is G / N mixed mode.

There are other similar bugs but I was asked to file a new report in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.27/+bug/276990

Please fix this bug for the Jaunty release so that I can use Ubuntu again. Thanks!

[James Ward (jamesward)]

Sorry for the big image. Here is a lower resolution one.

[xhu (x-hu1982)]

Hi Guys,

I have the same problem, only that my laptop (Dell XPS M1530 with Intel Next-Gen Wireless-N Mini-PCI Card) doesn't crash so frequently, it happens once per 5 hours or so.

I installed the latest linux-backport-modules 2.6.27.11.14 as suggested in another thread

https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.2/+bug/276990

but it didn't solve the problem. I still get crashes each a few hours.

The thing is, I only experience this problem since I got the new DSL router 2 weeks ago, which is a 802.11n router. Before this router, I had a 802.11g router and I never had any problem.

Does any one know a solution of this problem? Thanks!

[Leann Ogasawara (leannogasawara)]

@James, when running Jaunty, can you comment if you tested with linux-backports-modules-jaunty installed? If not, can you try installing and test. The reason I ask is because it contains an updated compat-wireless stack as of 2009-01-13. Please let us know your results.

@xhu, please attach either dmesg output or a digital photo which captures and confirms you are seeing the same panic that James is. Otherwise you should open a separate report.

[xhu (x-hu1982)]

Hi Leann,

I copied the following entries from my system log file (/var/log/sys/messages, these lines can be also found in kern.log or syslog)... :

Feb 5 22:29:56 baumhaus kernel: [14880.526755] Pid: 0, comm: swapper Tainted: P (2.6.27-7-generic #1)
Feb 5 22:29:56 baumhaus kernel: [14880.526763] EIP: 0060:[<f885a800>] EFLAGS: 00000246 CPU: 0
Feb 5 22:29:56 baumhaus kernel: [14880.526781] EIP is at acpi_idle_enter_bm+0x268/0x2b7 [processor]
Feb 5 22:29:56 baumhaus kernel: [14880.526788] EAX: c0510760 EBX: 00004272 ECX: 00000000 EDX: 02a84000
Feb 5 22:29:56 baumhaus kernel: [14880.526796] ESI: 00000000 EDI: 00d5755d EBP: c04a7f90 ESP: c04a7f74
Feb 5 22:29:56 baumhaus kernel: [14880.526803] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Feb 5 22:29:56 baumhaus kernel: [14880.526810] CR0: 8005003b CR2: b7ffe000 CR3: 355dd000 CR4: 00000690
Feb 5 22:29:56 baumhaus kernel: [14880.526817] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
Feb 5 22:29:56 baumhaus kernel: [14880.526824] DR6: ffff0ff0 DR7: 00000400
Feb 5 22:29:56 baumhaus kernel: [14880.526831] [<c02dbf7b>] cpuidle_idle_call+0x7b/0xd0
Feb 5 22:29:56 baumhaus kernel: [14880.526842] [<c010288d>] cpu_idle+0x7d/0x140
Feb 5 22:29:56 baumhaus kernel: [14880.526850] [<c036edd3>] rest_init+0x53/0x60
Feb 5 22:29:56 baumhaus kernel: [14880.526860] =======================
Feb 5 22:29:56 baumhaus kernel: [14880.526874] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Feb 5 22:29:56 baumhaus kernel: [14880.526881] [<c037c406>] ? printk+0x1d/0x1f
Feb 5 22:29:56 baumhaus kernel: [14880.526892] [<c0122b8a>] dequeue_task_idle+0x2a/0x40
Feb 5 22:29:56 baumhaus kernel: [14880.526900] [<c012107f>] dequeue_task+0xcf/0x130
Feb 5 22:29:56 baumhaus kernel: [14880.526910] [<c012112a>] deactivate_task+0x1a/0x30
Feb 5 22:29:56 baumhaus kernel: [14880.526919] [<c037ca23>] schedule+0x4b3/0x790
Feb 5 22:29:56 baumhaus kernel: [14880.526930] [<c012b6ab>] ? default_wake_function+0xb/0x10
Feb 5 22:29:56 baumhaus kernel: [14880.526941] [<c037e511>] ? _spin_lock_irqsave+0x31/0x40
Feb 5 22:29:56 baumhaus kernel: [14880.526951] [<c013c91c>] ? __mod_timer+0xac/0xf0
Feb 5 22:29:56 baumhaus kernel: [14880.526962] [<c037d0a4>] schedule_timeout+0x84/0xf0
Feb 5 22:29:56 baumhaus kernel: [14880.526970] [<c013c260>] ? process_timeout+0x0/0x10
Feb 5 22:29:56 baumhaus kernel: [14880.526980] [<c037d09f>] ? schedule_timeout+0x7f/0xf0
Feb 5 22:29:56 baumhaus kernel: [14880.526991] [<c037d12a>] schedule_timeout_uninterruptible+0x1a/0x20
Feb 5 22:29:56 baumhaus kernel: [14880.527001] [<c013c97d>] msleep+0x1d/0x30
Feb 5 22:29:56 baumhaus kernel: [14880.527013] [<f8bf9ceb>] iwl_scan_cancel_timeout+0x4b/0x80 [iwlcore]
Feb 5 22:29:56 baumhaus kernel: [14880.527071] [<f8bd3eb2>] iwl4965_mac_update_tkip_key+0x32/0xe0 [iwlagn]
Feb 5 22:29:56 baumhaus kernel: [14880.527090] [<f8b7510e>] ? tkip_mixing_phase1+0xe/0x140 [mac80211]
Feb 5 22:29:56 baumhaus kernel: [14880.527127] [<f8b7559c>] ieee80211_tkip_decrypt_data+0x16c/0x210 [mac80211]
Feb 5 22:29:56 baumhaus kernel: [14880.527160] [<c0123454>] ? __enqueue_entity+0xd4/0x100
Feb 5 22:29:56 baumhaus kernel: [14880.5...

[xhu (x-hu1982)]

Here is another kernel log entry, looks pretty the same as james' problem, hope this helps:

Feb 5 22:29:56 baumhaus kernel: [14880.525109] BUG: scheduling while atomic: swapper/0/0x00000100
Feb 5 22:29:56 baumhaus kernel: [14880.525124] Modules linked in: xt_limit xt_tcpudp ipt_LOG ipt_MASQUERADE xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp xt_state af_packet binfmt_mi
sc bridge stp bnep rfcomm sco l2cap bluetooth ppdev ipv6 acpi_cpufreq cpufreq_stats cpufreq_conservative cpufreq_userspace cpufreq_powersave cpufreq_ondemand freq_table pci_slot container sb
s sbshc sbp2 parport_pc lp parport snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm arc4 snd_seq_dummy ecb snd_seq_oss crypto_blkcipher snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd
_timer iwlagn iwlcore uvcvideo snd_seq_device joydev compat_ioctl32 rfkill snd soundcore led_class videodev psmouse mac80211 snd_page_alloc v4l1_compat iTCO_wdt sdhci_pci sdhci iTCO_vendor_s
upport cfg80211 dcdbas evdev mmc_core pcspkr ricoh_mmc serio_raw nvidia(P) i2c_core video output wmi intel_agp button battery shpchp pci_hotplug agpgart ac iptable_nat nf_nat nf_conntrack_ip
v4 nf_conntrack iptable_mangle iptable_filter ip_tables x_tables usbhid hid ex
Feb 5 22:29:56 baumhaus kernel: 3 jbd mbcache sr_mod cdrom sd_mod crc_t10dif sg ata_piix pata_acpi ahci ohci1394 ata_generic ieee1394 libata scsi_mod dock sky2 ehci_hcd uhci_hcd usbcore the
rmal processor fan fbcon tileblit font bitblit softcursor fuse
Feb 5 22:29:56 baumhaus kernel: [14880.525388]
Feb 5 22:29:56 baumhaus kernel: [14880.525396] Pid: 0, comm: swapper Tainted: P (2.6.27-7-generic #1)
Feb 5 22:29:56 baumhaus kernel: [14880.525404] EIP: 0060:[<f885a800>] EFLAGS: 00000246 CPU: 0
Feb 5 22:29:56 baumhaus kernel: [14880.525425] EIP is at acpi_idle_enter_bm+0x268/0x2b7 [processor]
Feb 5 22:29:56 baumhaus kernel: [14880.525433] EAX: c0510760 EBX: 00004272 ECX: 00000000 EDX: 02a84000
Feb 5 22:29:56 baumhaus kernel: [14880.525440] ESI: 00000000 EDI: 00d5755d EBP: c04a7f90 ESP: c04a7f74
Feb 5 22:29:56 baumhaus kernel: [14880.525447] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
Feb 5 22:29:56 baumhaus kernel: [14880.525454] CR0: 8005003b CR2: b7ffe000 CR3: 00515000 CR4: 00000690
Feb 5 22:29:56 baumhaus kernel: [14880.525461] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
Feb 5 22:29:56 baumhaus kernel: [14880.525468] DR6: ffff0ff0 DR7: 00000400
Feb 5 22:29:56 baumhaus kernel: [14880.525476] [<c02dbf7b>] cpuidle_idle_call+0x7b/0xd0
Feb 5 22:29:56 baumhaus kernel: [14880.525490] [<c010288d>] cpu_idle+0x7d/0x140
Feb 5 22:29:56 baumhaus kernel: [14880.525500] [<c036edd3>] rest_init+0x53/0x60
Feb 5 22:29:56 baumhaus kernel: [14880.525511] =======================
Feb 5 22:29:56 baumhaus kernel: [14880.525520] bad: scheduling from the idle thread!
Feb 5 22:29:56 baumhaus kernel: [14880.525529] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
Feb 5 22:29:56 baumhaus kernel: [14880.525536] [<c037c406>] ? printk+0x1d/0x1f
Feb 5 22:29:56 baumhaus kernel: [14880.525547] [<c0122b8a>] dequeue_task_idle+0x2a/0x40
Feb 5 22:29:56 baumhaus kernel: [14880.525555] [<c012107f>] dequeue_task+0xcf/0x1...

[James Ward (jamesward)]

I just tried the latest linux-backports-modules-jaunty and it's still giving me a kernel panic almost immediately after I being using my wireless.

[Leann Ogasawara (leannogasawara)]

Hi James,

Could you do one more round of testing. Could you test the latest compat-wireless stack available from upstream? This may very well be an issue we should escalate to the upstream developers as well but we need confirmation first. It should be a fairly simple process to install and test, see Step 4 of https://wiki.ubuntu.com/KernelTeam/LinuxWireless . Thanks.

[Josh Hill (ingenium)]

I'm also having this issue. New laptop, and it seems to happen specifically when I resume from suspend, and it auto connects to an N network at school. It only happens after resuming, and not every time. It happens almost as soon as it establishes a connection to the network. I have linux-backports-modules-jaunty installed.

I'm not sure if this is related or not, but I also get this message every few minutes, which started appearing after I installed the backports:
wlan0: beacon loss from AP ffff8801384c7ac0 - sending probe request

[SaintDanBert (saint-grillongroup)]

I have this same problem. Wired ethernet works fine under linux.
Wireless worked fine with a type-G network.
Type-N works for a short time and the the system stalls with a blinking caps LED.

I can dual-boot to Windows(tm) XP/Pro Tablet PC edition and both wired
and wireless type-N work just fine so I doubt that this is a hardware problem.

Added a new type-N access point at home as a present to me and this trouble
raised its head. The box is a D-Link DIR-655. Previous box was Linksys WRT54GS.
A search of the net turns up loads of "bugs" and other complaints with these same
symptoms for all sorts of distros and kernels and mostly intel drivers.

I have no idea how to get any details about what is happening. I'm told that the
blinking LED means "kernel panic" but I don't find any sort of record in /var/logs
of a crash or dump or log entries.

My Platform:
** EmperorLinux Raven Tablet (Lenovo Thinkpad X61 Tablet)
** Intel 4965 A/G/N wireless
** Intel 965 graphics
** 3 GiB RAM, 500 GiB disk
** Ubuntu Hardy (v8.04.3 LTS) with all relevant updates to the LTS

Desparate,
~~~ 0;-Dan

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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