Discussion:
[Bug 276990] [NEW] iwlagn causes kernel panic on 802.11n wifi
(too old to reply)
Launchpad Bug Tracker
2008-10-20 18:21:09 UTC
Permalink
You have been subscribed to a public bug:

I don't know the specific trigger but in my testing with intrepid over
the last few weeks I have found a large amount of kernel panics when
connected to my 802.11n router with an intel 4965 card. This issue does
not at all appear when I use an 802.11b/g network which is what I use
exclusively at my university (student during the day). At one point my
system had 4 kernel panics in 2 hours all while using network intensive
applications (apt, firefox, terminal server client).

I've tried the REISUB magic keys several times but its a completely dead
machine. However, I have found something that works and I think it
should be added to the official repository, the Oct-1-2008 compat-
wireless iwlagn module fixes the kernel panic issue. I've left my
machine on for an extended period of time in the same conditions that
used to kernel panic before and so far all is good. I understand we are
nearing the end of the road and only major showstoppers should be
included for release but I feel this warrants such consideration.

** Affects: ubuntu-release-notes
Importance: Undecided
Status: New

** Affects: linux-meta (Ubuntu)
Importance: High
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Confirmed
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.edge.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel Bugs, which is subscribed to linux-meta in ubuntu.
Leann Ogasawara
2008-10-20 18:21:06 UTC
Permalink
Hi All,

linux-backports-modules most recently pulled in an updated version of
the compat-wireless stack:

https://edge.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.27

linux-backports-modules-2.6.27 (2.6.27-7.3) intrepid; urgency=low

[Tim Gardner]

* Added iwlwifi firmware
* Added the upstream compat-wireless-2.6 tree.
* Updated compat-wireless to wireless-testing tag master-2008-10-14
* Set CONFIG_WIRELESS_OLD_REGULATORY=y by default.

It would be great if everyone here would please install the most recent
linux-backports-modules package and verify if this is still and issue.
Thanks.

** Changed in: linux-meta (Ubuntu)
Sourcepackagename: linux => linux-meta
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
syko21
2008-10-20 20:08:35 UTC
Permalink
Synaptic throws dependency errors when trying to install linux-backports
generic. Screen shot attached.

** Attachment added: "Screenshot-Untitled Window.png"
Loading Image...
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
Derek Kulinski
2008-10-20 20:24:36 UTC
Permalink
worked for me (I used aptitude to install it)
Though the crashes don?t happen as often to me as to other people, so it might take a while to say if it fixed problems or not.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
Derek Kulinski
2008-10-20 20:25:16 UTC
Permalink
Worked for me with aptitude.

BTW: the crashes don hapen as often to me as to others here, so it will
take time for me to say if it helped or not :/
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
Winckler
2008-10-21 02:04:41 UTC
Permalink
Leann Ogasawara,

I did the upgrade and install the backports. It DID NOT solve my
problem. I still have kernel panic when acessing a .11N network.

If you need more tests, let me know.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
syko21
2008-10-21 02:28:15 UTC
Permalink
I attempted other builds after the Oct-1 modules. Some of them had
serious problems, kernel panic with flash, fail to resume from suspend.
Since the Oct-1 modules do not work for everyone I think that either we
use that in backports or enable Winckler's pseudo fix of disabling N


[quote]
I have the same bug here (and didn't test any new drive) but I would like to share a WORKAROUND, while the bug isn't fixed.

If you load the iwlagn with the option 11n_disable, you disable the N
standard, and avoid the kernel panic.

I've add 'options iwlagn 11n_disable=1' to my /etc/modprobe.d/options.
So far, so good.

I want this fixed for the Intrepid release, but if it's not possible, I would consider add this workaround enable by default.
[/quote]
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
UnSandpiper
2008-10-21 11:43:57 UTC
Permalink
Installed the backport this morning (through Synaptic, no problems
there) and I'm working with activated wlan now for 5 hours straight
without freeze.

One thing I noticed is that only now iwconfig shows me "IEEE 802.11abgn" under my WLAN0 interface.
Before the backport it was only "IEEE 802.11abg" although I'm connecting to the same AP.
I guess that's a good thing as well.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
Leann Ogasawara
2008-10-21 15:57:45 UTC
Permalink
Hi syko21,

You probably got that synaptic dependency error because the
mirror/repository you have your /etc/apt/sources.list set up to hadn't
quite sync'd up. I'm assuming if you try again, linux-backports-
modules-2.6.27-7-generic should be there. I'd really appreciate hearing
back from you if linux-backports-modules helps resolve this issue
especially since you are the original bug reporter. Thanks.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
Leann Ogasawara
2008-10-21 16:01:09 UTC
Permalink
@Winckler, I know this sounds a bit silly to be asking but did you
reboot after installing linux-backports-modules? It may be that you
have a slightly different issue and we'll want to have you open a
separate bug report. Thanks.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
syko21
2008-10-21 21:05:23 UTC
Permalink
After installing the backports package my wireless failed completely and
cannot even pick up a single ESSID. I attached the dmesg log of the
relevant portion. A quick purge and reinstall of my self compiled Oct-1
fixed this in a hurry though.

** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/18781753/dmesg.log
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
Ian McKellar
2008-10-21 23:09:48 UTC
Permalink
This crash seems to be occurring for me too with the latest kernel (on
Oct 21st) on my Thinkpad X61 Tablet. I'll try the backports modules
mentioned above.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
Winckler
2008-10-21 23:32:41 UTC
Permalink
@Leann Ogasawara

I did reboot. Without the option "11n_disable", the card worked for
non-N networks (as before). But, as soon as I connected to a N network
and open Vuze (old Azureus), I got a kernel panic.

Now I'm working WITH the backport and the option, and everything is
fine.

I have the feeling that there are two different bugs in this thread too.
The difference, I guess, is the relationship with N networks, or not.

If you would like, I can try to get a picture of my kernel panic. Would
it help?
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
Ian McKellar
2008-10-22 04:00:13 UTC
Permalink
The linux-backports-modules-2.6.27 package seems to have solved my
problem.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
joenix
2008-10-22 07:29:28 UTC
Permalink
The backports module also solved my problem.
Before, transferring large files over the local network would crash my system within seconds. I have now been able to transfer several large files without problems. I still see error messages in dmesg, but they don't seem to cause too much trouble.

For those still experiencing problems, it might be useful to know that you can use this command to check which module is actually being used:
modinfo iwlagn|grep filename

The module in backports is in /lib/modules/2.6.27-7-generic/updates/iwlagn.ko.
If you need to find out what package the file belongs to, you can do for example
dpkg -S /lib/modules/2.6.27-7-generic/updates/iwlagn.ko
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
harking
2008-10-22 07:50:48 UTC
Permalink
The linux backports package also fixed it for me.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
syko21
2008-10-22 11:41:38 UTC
Permalink
I will retry backports since it appears to have fixed it for everyone
else.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
Leann Ogasawara
2008-10-22 21:56:28 UTC
Permalink
@Winckler if you could get a picture of the full panic that would be
great. Especially the beginning of the panic would be most useful. I
suspect as you do we may have 2 bugs here where linux-backports-modules
has resolved the issue for some. It seem that you and syko21 still have
issues specifically connecting to an 802.11n network.

** Changed in: linux-backports-modules-2.6.27 (Ubuntu)
Sourcepackagename: linux-meta => linux-backports-modules-2.6.27
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.
Tom Jaeger
2008-10-30 18:28:24 UTC
Permalink
** Bug watch added: Intel Wireless Linux Bugzilla #1703
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703

** Also affects: linux via
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703
Importance: Unknown
Status: Unknown
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Bug Watch Updater
2008-10-30 18:31:33 UTC
Permalink
** Changed in: linux
Status: Unknown => In Progress
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Tom Jaeger
2008-10-30 19:25:03 UTC
Permalink
It doesn't seem like they have figured out the cause of the bug yet.
This is the patch that turns the kernel panic into a warning. I think
it should be applied to the intrepid kernel.

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=55d6a3cd0cc85ed90c39cf32e16f622bd003117b
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Squaredge
2008-10-30 19:29:42 UTC
Permalink
I'm using linux-backport-modules since yesterday mordning and I've no problem (no freeze in 2 full day).
Without this module, I could freeze every 10-15 min ...
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Tom Jaeger
2008-10-30 21:10:55 UTC
Permalink
Could someone who was experiencing this problem frequently remove the
linux-backports-modules-2.6.27 package and try the attached modules
instead:

tar -xzf bug276990.tar.gz
sudo cp -b bug276990/* /lib/modules/2.6.27-7-generic/kernel/drivers/net/wireless/iwlwifi/

These come from the latest intrepid kernel with the above patch applied
to them.

** Attachment added: "bug276990.tar.gz"
http://launchpadlibrarian.net/19093408/bug276990.tar.gz
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Squaredge
2008-10-30 21:30:19 UTC
Permalink
I just have apply these commands.
I will see tomorrow (at work) if this resolve this wireless bug ...
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Zizzle
2008-10-31 00:43:37 UTC
Permalink
I have tried lbm and the 11n disable to no effect on my X200.

Sometimes the laptop is unusable. Can't event load firefox without the
lockup happening. Other times it will run for hours. Something must be
sending the packet or packet rate of death.

How crappy is this driver?


** Attachment added: "dsc03195.jpg"
Loading Image...
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
David Moreno
2008-10-31 01:02:55 UTC
Permalink
Post by Zizzle
Sometimes the laptop is unusable. Can't event load firefox without the
lockup happening. Other times it will run for hours. Something must be
sending the packet or packet rate of death.
Have you tried sniffing ingoing and outgoing packets? That might lead to
a possible answer.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Derek Kulinski
2008-10-31 03:03:00 UTC
Permalink
I got another crash today, I belive some recent change must broke the
driver.

This is log entry I noticed (instead disabling wireless adapter, I restarted NetworkManager which ended without crash, and brough wifi back):
Oct 30 17:09:52 tkdlap2 NetworkManager: <info> (wlan0): preparing device.
Oct 30 17:09:52 tkdlap2 NetworkManager: <info> (wlan0): deactivating device (reason: 2).
Oct 30 17:09:52 tkdlap2 NetworkManager: <WARN> nm_device_wifi_set_ssid(): error setting SSID to '(null)' for device wlan0: Resource temporarily unavailable
Oct 30 17:09:52 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 17:09:52 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 17:09:52 tkdlap2 kernel: [ 276.892815] ------------[ cut here ]------------
Oct 30 17:09:52 tkdlap2 kernel: [ 276.892833] WARNING: at /build/buildd/linux-backports-modules-2.6.27-2.6.27/debian/build/build-generic/compat-wireless-2.6/net/mac80211/main.c:232 ieee80211_hw_config+0x85/0x90 [lbm_cw_mac80211]()
Oct 30 17:09:52 tkdlap2 kernel: [ 276.892842] Modules linked in: tun ipv6 af_packet i915 drm binfmt_misc rfcomm sco bridge stp bnep l2cap bluetooth ppdev acpi_cpufreq cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_ondemand freq_table wmi container pci_slot sbs sbshc iptable_filter ip_tables x_tables panasonic_acpi parport_pc lp parport loop joydev pcmcia snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm arc4 ecb crypto_blkcipher snd_seq_dummy pcspkr evdev snd_seq_oss snd_seq_midi snd_rawmidi iwlagn video serio_raw snd_seq_midi_event output tpm_infineon tpm tpm_bios iwlcore rfkill psmouse snd_seq led_class snd_timer snd_seq_device lbm_cw_mac80211 snd yenta_socket lbm_cw_cfg80211 rsrc_nonstatic sdhci_pci sdhci pcmcia_core mmc_core ac battery button soundcore iTCO_wdt iTCO_vendor_support snd_page_alloc intel_agp agpgart shpchp pci_hotplug ext3 jbd mbcache sd_mod crc_t10dif sg ata_piix pata_acpi ata_generic ahci libata scsi_mod dock sky2 ehci_hcd uhci_hcd usbcore thermal processor fan
Oct 30 17:09:52 tkdlap2 kernel: bcon tileblit font bitblit softcursor fuse
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893059] Pid: 6069, comm: NetworkManager Tainted: G W 2.6.27-7-generic #1
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893067] [<c037c406>] ? printk+0x1d/0x1f
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893081] [<c0131de9>] warn_on_slowpath+0x59/0x90
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893096] [<c030d400>] ? nlmsg_notify+0x30/0x90
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893108] [<f916335d>] ? inet6_ifinfo_notify+0x7d/0xd0 [ipv6]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893146] [<f91635e8>] ? addrconf_notify+0x238/0x3d0 [ipv6]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893182] [<f8c0acce>] ? iwl_radio_kill_sw_enable_radio+0xe/0x140 [iwlcore]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893206] [<c012a18b>] ? __cond_resched+0x1b/0x40
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893216] [<c037cdf5>] ? _cond_resched+0x35/0x50
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893226] [<c037d3d8>] ? mutex_unlock+0x8/0x20
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893236] [<f8c4ec3d>] ? iwl4965_mac_config+0x4d/0x2c0 [iwlagn]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893255] [<c014c36f>] ? raw_notifier_call_chain+0x1f/0x30
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893267] [<f8bd4875>] ieee80211_hw_config+0x85/0x90 [lbm_cw_mac80211]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893293] [<f8be14f7>] ieee80211_open+0x5e7/0x830 [lbm_cw_mac80211]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893321] [<c02f469a>] dev_open+0xaa/0xe0
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893331] [<c037e866>] ? _spin_unlock_bh+0x16/0x20
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893340] [<c02f3acf>] ? dev_set_rx_mode+0x2f/0x40
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893350] [<c02f3d49>] dev_change_flags+0x139/0x1c0
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893358] [<c02fcded>] do_setlink+0x1cd/0x380
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893368] [<c037e4c8>] ? _read_lock+0x8/0x20
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893377] [<c02fd089>] rtnl_setlink+0xe9/0x120
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893387] [<c0211bb2>] ? cap_netlink_recv+0x12/0x40
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893398] [<c02fcfa0>] ? rtnl_setlink+0x0/0x120
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893408] [<c02fc1f5>] rtnetlink_rcv_msg+0x165/0x200
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893417] [<c01ad388>] ? get_slab+0x8/0x60
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893428] [<c02fc090>] ? rtnetlink_rcv_msg+0x0/0x200
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893438] [<c030dc16>] netlink_rcv_skb+0x76/0xa0
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893447] [<c02fc081>] rtnetlink_rcv+0x21/0x30
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893455] [<c030d3a5>] netlink_unicast+0x265/0x290
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893464] [<c030e423>] netlink_sendmsg+0x1d3/0x2c0
Oct 30 17:09:52 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 17:09:52 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893473] [<c02e65af>] sock_sendmsg+0xef/0x120
Oct 30 17:09:52 tkdlap2 NetworkManager: <info> (wlan0): device state change: 2 -> 3
Oct 30 17:09:52 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893481] [<c0234775>] ? apparmor_socket_recvmsg+0x15/0x20
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893494] [<c01474b0>] ? autoremove_wake_function+0x0/0x50
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893503] [<c01474b0>] ? autoremove_wake_function+0x0/0x50
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893513] [<c02548ca>] ? copy_from_user+0x3a/0x130
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893524] [<c02edc15>] ? verify_iovec+0x35/0xb0
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893534] [<c02e66f1>] sys_sendmsg+0x111/0x230
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893542] [<c01b3578>] ? fput+0x8/0x30
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893551] [<c02e6919>] ? sys_sendto+0xb9/0xd0
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893560] [<c01ba9fa>] ? putname+0x2a/0x40
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893569] [<c01ba9fa>] ? putname+0x2a/0x40
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893577] [<c02549fb>] ? copy_to_user+0x3b/0x130
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893589] [<c02e6edb>] sys_socketcall+0xeb/0x2d0
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893597] [<c0103f7b>] sysenter_do_call+0x12/0x2f
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893606] =======================
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893611] ---[ end trace e7daf9c45af949d8 ]---
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893726] ------------[ cut here ]------------
Oct 30 17:09:52 tkdlap2 NetworkManager: <info> (wlan0): supplicant interface state change: 1 -> 2.
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893733] WARNING: at /build/buildd/linux-backports-modules-2.6.27-2.6.27/debian/build/build-generic/compat-wireless-2.6/net/mac80211/main.c:232 ieee80211_hw_config+0x85/0x90 [lbm_cw_mac80211]()
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893744] Modules linked in: tun ipv6 af_packet i915 drm binfmt_misc rfcomm sco bridge stp bnep l2cap bluetooth ppdev acpi_cpufreq cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_ondemand freq_table wmi container pci_slot sbs sbshc iptable_filter ip_tables x_tables panasonic_acpi parport_pc lp parport loop joydev pcmcia snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm arc4 ecb crypto_blkcipher snd_seq_dummy pcspkr evdev snd_seq_oss snd_seq_midi snd_rawmidi iwlagn video serio_raw snd_seq_midi_event output tpm_infineon tpm tpm_bios iwlcore rfkill psmouse snd_seq led_class snd_timer snd_seq_device lbm_cw_mac80211 snd yenta_socket lbm_cw_cfg80211 rsrc_nonstatic sdhci_pci sdhci pcmcia_core mmc_core ac battery button soundcore iTCO_wdt iTCO_vendor_support snd_page_alloc intel_agp agpgart shpchp pci_hotplug ext3 jbd mbcache sd_mod crc_t10dif sg ata_piix pata_acpi ata_generic ahci libata scsi_mod dock sky2 ehci_hcd uhci_hcd usbcore thermal processor fan
Oct 30 17:09:52 tkdlap2 kernel: bcon tileblit font bitblit softcursor fuse
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893947] Pid: 2778, comm: iwlagn Tainted: G W 2.6.27-7-generic #1
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893954] [<c037c406>] ? printk+0x1d/0x1f
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893964] [<c0131de9>] warn_on_slowpath+0x59/0x90
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893978] [<c025151a>] ? rb_insert_color+0xca/0x100
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893989] [<c025151a>] ? rb_insert_color+0xca/0x100
Oct 30 17:09:52 tkdlap2 kernel: [ 276.893998] [<c014a72d>] ? enqueue_hrtimer+0x7d/0x130
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894009] [<f8c0acce>] ? iwl_radio_kill_sw_enable_radio+0xe/0x140 [iwlcore]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894032] [<c037d3d8>] ? mutex_unlock+0x8/0x20
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894042] [<f8c4ec3d>] ? iwl4965_mac_config+0x4d/0x2c0 [iwlagn]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894061] [<f8acac3e>] ? __lbm_cw_ieee80211_get_channel+0xe/0x80 [lbm_cw_cfg80211]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894079] [<f8bd4875>] ieee80211_hw_config+0x85/0x90 [lbm_cw_mac80211]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894105] [<f8beb17c>] ieee80211_set_freq+0x7c/0x80 [lbm_cw_mac80211]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894136] [<f8bdff0c>] ieee80211_sta_work+0x2fc/0x750 [lbm_cw_mac80211]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894163] [<c0102df6>] ? __switch_to+0xa6/0x160
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894175] [<f8bdfc10>] ? ieee80211_sta_work+0x0/0x750 [lbm_cw_mac80211]
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894204] [<c0143645>] run_workqueue+0x95/0x160
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894214] [<c0147576>] ? finish_wait+0x16/0x70
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894223] [<c01438e8>] worker_thread+0x88/0xf0
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894232] [<c01474b0>] ? autoremove_wake_function+0x0/0x50
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894242] [<c0143860>] ? worker_thread+0x0/0xf0
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894251] [<c0147141>] kthread+0x41/0x80
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894260] [<c0147100>] ? kthread+0x0/0x80
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894270] [<c0105297>] kernel_thread_helper+0x7/0x10
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894279] =======================
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894284] ---[ end trace e7daf9c45af949d8 ]---
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894291] wlan0: Failed to config new BSSID to the low-level driver
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894305] wlan0: direct probe to AP 00:12:7f:07:70:40 try 1
Oct 30 17:09:52 tkdlap2 kernel: [ 276.894724] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 30 17:09:52 tkdlap2 kernel: [ 276.895000] wlan0: Failed to config new SSID to the low-level driver
Oct 30 17:09:52 tkdlap2 kernel: [ 277.092092] wlan0: direct probe to AP 00:12:7f:07:70:40 try 2
Oct 30 17:09:53 tkdlap2 kernel: [ 277.296070] wlan0: direct probe to AP 00:12:7f:07:70:40 try 3
Oct 30 17:09:53 tkdlap2 kernel: [ 277.496051] wlan0: direct probe to AP 00:12:7f:07:70:40 timed out
Oct 30 17:11:13 tkdlap2 NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally.
Oct 30 17:11:13 tkdlap2 NetworkManager: <info> (wlan0): now unmanaged
Oct 30 17:11:13 tkdlap2 NetworkManager: <info> (wlan0): device state change: 3 -> 1
Oct 30 17:11:13 tkdlap2 NetworkManager: <info> (wlan0): cleaning up...
Oct 30 17:11:13 tkdlap2 NetworkManager: <info> (wlan0): taking down device.
Oct 30 17:11:13 tkdlap2 kernel: [ 357.997593] iwlagn 0000:03:00.0: PCI INT A disabled
Oct 30 17:11:13 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 17:11:14 tkdlap2 NetworkManager: <info> starting...
Oct 30 17:11:14 tkdlap2 NetworkManager: <info> eth0: driver is 'sky2'.
Oct 30 17:11:14 tkdlap2 NetworkManager: <info> Found new Ethernet device 'eth0'.

This is what was logged during the crash:
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574078] ata1: EH complete
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574165] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574199] sd 0:0:0:0: [sda] Write Protect is off
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574203] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574261] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574318] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574349] sd 0:0:0:0: [sda] Write Protect is off
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574352] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574410] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.640154] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.640161] pci 0000:00:02.0: setting latency timer to 64
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642076] PM: resume devices took 12.984 seconds
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642084] ------------[ cut here ]------------
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642087] WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642091] Modules linked in: tun ipv6 af_packet i915 drm binfmt_misc rfcomm sco bridge stp bnep l2cap bluetooth ppdev acpi_cpufreq cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_ondemand freq_table wmi container pci_slot sbs sbshc iptable_filter ip_tables x_tables panasonic_acpi parport_pc lp parport loop joydev pcmcia arc4 ecb crypto_blkcipher serio_raw evdev iwlagn pcspkr iwlcore psmouse rfkill led_class lbm_cw_mac80211 iTCO_wdt iTCO_vendor_support sdhci_pci sdhci mmc_core yenta_socket rsrc_nonstatic pcmcia_core tpm_infineon lbm_cw_cfg80211 tpm video snd_hda_intel tpm_bios ac output snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss battery button snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc intel_agp agpgart shpchp pci_hotplug ext3 jbd mbcache sd_mod crc_t10dif sg ata_piix pata_acpi ahci ata_generic libata scsi_mod dock sky2 ehci_hcd uhci_hcd usbcore thermal processor fan
Oct 30 15:21:48 tkdlap2 kernel: bcon tileblit font bitblit softcursor fuse
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642176] Pid: 9635, comm: pm-suspend Tainted: G W 2.6.27-7-generic #1
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642179] [<c037c406>] ? printk+0x1d/0x1f
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642186] [<c0131de9>] warn_on_slowpath+0x59/0x90
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642192] [<c014d255>] ? sched_clock_cpu+0xd5/0x170
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642197] [<c014c0af>] ? down_trylock+0x2f/0x40
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642201] [<c01324c2>] ? try_acquire_console_sem+0x12/0x40
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642207] [<c024e580>] ? kobject_put+0x20/0x50
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642212] [<c015d204>] suspend_test_finish+0x74/0x80
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642217] [<c015d2f6>] suspend_devices_and_enter+0xe6/0x190
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642222] [<c015d571>] enter_state+0xd1/0x100
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642226] [<c015d625>] state_store+0x85/0xd0
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642229] [<c015d5a0>] ? state_store+0x0/0xd0
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642233] [<c024e444>] kobj_attr_store+0x24/0x30
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642237] [<c01ff4c7>] sysfs_write_file+0x97/0x100
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642242] [<c01b24c0>] vfs_write+0xa0/0x110
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642246] [<c01ff430>] ? sysfs_write_file+0x0/0x100
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642250] [<c01b2602>] sys_write+0x42/0x70
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642254] [<c0103f7b>] sysenter_do_call+0x12/0x2f
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642259] [<c0370000>] ? default_device_exit+0x60/0xb0
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642263] =======================
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642266] ---[ end trace bb3e413784405200 ]---
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642489] PM: Finishing wakeup.
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642491] Restarting tasks ... done.
Oct 30 15:21:48 tkdlap2 nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> Waking up...
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> (wlan0): now managed
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> (wlan0): device state change: 1 -> 2
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> (wlan0): bringing up device.
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.087080] iwlagn 0000:03:00.0: enabling device (0000 -> 0002)
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.087132] iwlagn 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.087277] iwlagn 0000:03:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.087416] iwlagn 0000:03:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xfc300004)
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.087459] iwlagn 0000:03:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.087510] iwlagn 0000:03:00.0: restoring config space at offset 0x1 (was 0x100002, writing 0x100006)
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.088071] iwlagn: Radio disabled by HW RF Kill switch
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> (wlan0): preparing device.
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> (wlan0): deactivating device (reason: 2).
Oct 30 15:21:48 tkdlap2 NetworkManager: <WARN> nm_device_wifi_set_ssid(): error setting SSID to '(null)' for device wlan0: Resource temporarily unavailable
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.103728] ------------[ cut here ]------------
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.103747] WARNING: at /build/buildd/linux-backports-modules-2.6.27-2.6.27/debian/build/build-generic/compat-wireless-2.6/net/mac80211/main.c:232 ieee80211_hw_config+0x85/0x90 [lbm_cw_mac80211]()
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.103756] Modules linked in: tun ipv6 af_packet i915 drm binfmt_misc rfcomm sco bridge stp bnep l2cap bluetooth ppdev acpi_cpufreq cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_ondemand freq_table wmi container pci_slot sbs sbshc iptable_filter ip_tables x_tables panasonic_acpi parport_pc lp parport loop joydev pcmcia arc4 ecb crypto_blkcipher serio_raw evdev iwlagn pcspkr iwlcore psmouse rfkill led_class lbm_cw_mac80211 iTCO_wdt iTCO_vendor_support sdhci_pci sdhci mmc_core yenta_socket rsrc_nonstatic pcmcia_core tpm_infineon lbm_cw_cfg80211 tpm video snd_hda_intel tpm_bios ac output snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss battery button snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc intel_agp agpgart shpchp pci_hotplug ext3 jbd mbcache sd_mod crc_t10dif sg ata_piix pata_acpi ahci ata_generic libata scsi_mod dock sky2 ehci_hcd uhci_hcd usbcore thermal processor fan
Oct 30 15:21:48 tkdlap2 kernel: bcon tileblit font bitblit softcursor fuse
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.103994] Pid: 6134, comm: NetworkManager Tainted: G W 2.6.27-7-generic #1
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104004] [<c037c406>] ? printk+0x1d/0x1f
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104019] [<c0131de9>] warn_on_slowpath+0x59/0x90
Oct 30 15:21:48 tkdlap2 acpid: client connected from 5331[0:0]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104034] [<c030d400>] ? nlmsg_notify+0x30/0x90
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104046] [<f916335d>] ? inet6_ifinfo_notify+0x7d/0xd0 [ipv6]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104086] [<f91635e8>] ? addrconf_notify+0x238/0x3d0 [ipv6]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104122] [<f8d1ecce>] ? iwl_radio_kill_sw_enable_radio+0xe/0x140 [iwlcore]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104147] [<c012a18b>] ? __cond_resched+0x1b/0x40
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104158] [<c037cdf5>] ? _cond_resched+0x35/0x50
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104170] [<c037d3d8>] ? mutex_unlock+0x8/0x20
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104180] [<f8c99c3d>] ? iwl4965_mac_config+0x4d/0x2c0 [iwlagn]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104200] [<c014c36f>] ? raw_notifier_call_chain+0x1f/0x30
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104212] [<f8ce8875>] ieee80211_hw_config+0x85/0x90 [lbm_cw_mac80211]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104241] [<f8cf54f7>] ieee80211_open+0x5e7/0x830 [lbm_cw_mac80211]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104271] [<c02f469a>] dev_open+0xaa/0xe0
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104281] [<c037e866>] ? _spin_unlock_bh+0x16/0x20
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104292] [<c02f3acf>] ? dev_set_rx_mode+0x2f/0x40
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104302] [<c02f3d49>] dev_change_flags+0x139/0x1c0
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104313] [<c02fcded>] do_setlink+0x1cd/0x380
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104324] [<c037e4c8>] ? _read_lock+0x8/0x20
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104335] [<c02fd089>] rtnl_setlink+0xe9/0x120
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104346] [<c0211bb2>] ? cap_netlink_recv+0x12/0x40
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104359] [<c02fcfa0>] ? rtnl_setlink+0x0/0x120
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104370] [<c02fc1f5>] rtnetlink_rcv_msg+0x165/0x200
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104381] [<c01ad388>] ? get_slab+0x8/0x60
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104393] [<c02fc090>] ? rtnetlink_rcv_msg+0x0/0x200
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104405] [<c030dc16>] netlink_rcv_skb+0x76/0xa0
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104414] [<c02fc081>] rtnetlink_rcv+0x21/0x30
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104424] [<c030d3a5>] netlink_unicast+0x265/0x290
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104433] [<c030e423>] netlink_sendmsg+0x1d3/0x2c0
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104444] [<c02e65af>] sock_sendmsg+0xef/0x120
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104454] [<c0234775>] ? apparmor_socket_recvmsg+0x15/0x20
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104468] [<c01474b0>] ? autoremove_wake_function+0x0/0x50
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104478] [<c01474b0>] ? autoremove_wake_function+0x0/0x50
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104490] [<c02548ca>] ? copy_from_user+0x3a/0x130
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104503] [<c02edc15>] ? verify_iovec+0x35/0xb0
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104515] [<c02e66f1>] sys_sendmsg+0x111/0x230
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104523] [<c01b3578>] ? fput+0x8/0x30
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104533] [<c02e6919>] ? sys_sendto+0xb9/0xd0
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104544] [<c01ba9fa>] ? putname+0x2a/0x40
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104553] [<c01ba9fa>] ? putname+0x2a/0x40
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104563] [<c02549fb>] ? copy_to_user+0x3b/0x130
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104575] [<c02e6edb>] sys_socketcall+0xeb/0x2d0
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104584] [<c0103f7b>] sysenter_do_call+0x12/0x2f
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104595] =======================
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104602] ---[ end trace bb3e413784405200 ]---
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104718] ------------[ cut here ]------------
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104726] WARNING: at /build/buildd/linux-backports-modules-2.6.27-2.6.27/debian/build/build-generic/compat-wireless-2.6/net/mac80211/main.c:232 ieee80211_hw_config+0x85/0x90 [lbm_cw_mac80211]()
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104744] Modules linked in: tun ipv6 af_packet i915 drm binfmt_misc rfcomm sco bridge stp bnep l2cap bluetooth ppdev acpi_cpufreq cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_ondemand freq_table wmi container pci_slot sbs sbshc iptable_filter ip_tables x_tables panasonic_acpi parport_pc lp parport loop joydev pcmcia arc4 ecb crypto_blkcipher serio_raw evdev iwlagn pcspkr iwlcore psmouse rfkill led_class lbm_cw_mac80211 iTCO_wdt iTCO_vendor_support sdhci_pci sdhci mmc_core yenta_socket rsrc_nonstatic pcmcia_core tpm_infineon lbm_cw_cfg80211 tpm video snd_hda_intel tpm_bios ac output snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss battery button snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc intel_agp agpgart shpchp pci_hotplug ext3 jbd mbcache sd_mod crc_t10dif sg ata_piix pata_acpi ahci ata_generic libata scsi_mod dock sky2 ehci_hcd uhci_hcd usbcore thermal processor fan
Oct 30 15:21:48 tkdlap2 kernel: bcon tileblit font bitblit softcursor fuse
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104970] Pid: 2925, comm: iwlagn Tainted: G W 2.6.27-7-generic #1
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104978] [<c037c406>] ? printk+0x1d/0x1f
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.104990] [<c0131de9>] warn_on_slowpath+0x59/0x90
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105036] [<c025151a>] ? rb_insert_color+0xca/0x100
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105048] [<c014a72d>] ? enqueue_hrtimer+0x7d/0x130
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105060] [<c014a72d>] ? enqueue_hrtimer+0x7d/0x130
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105071] [<c014a72d>] ? enqueue_hrtimer+0x7d/0x130
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105082] [<f8d1ecce>] ? iwl_radio_kill_sw_enable_radio+0xe/0x140 [iwlcore]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105106] [<c037d3d8>] ? mutex_unlock+0x8/0x20
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105117] [<f8c99c3d>] ? iwl4965_mac_config+0x4d/0x2c0 [iwlagn]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105137] [<f8bb3c3e>] ? __lbm_cw_ieee80211_get_channel+0xe/0x80 [lbm_cw_cfg80211]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105157] [<f8ce8875>] ieee80211_hw_config+0x85/0x90 [lbm_cw_mac80211]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105186] [<f8cff17c>] ieee80211_set_freq+0x7c/0x80 [lbm_cw_mac80211]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105219] [<f8cf3f0c>] ieee80211_sta_work+0x2fc/0x750 [lbm_cw_mac80211]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105247] [<c0102df6>] ? __switch_to+0xa6/0x160
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105260] [<f8cf3c10>] ? ieee80211_sta_work+0x0/0x750 [lbm_cw_mac80211]
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105290] [<c0143645>] run_workqueue+0x95/0x160
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105300] [<c0147576>] ? finish_wait+0x16/0x70
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105312] [<c01438e8>] worker_thread+0x88/0xf0
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105322] [<c01474b0>] ? autoremove_wake_function+0x0/0x50
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105333] [<c0143860>] ? worker_thread+0x0/0xf0
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105343] [<c0147141>] kthread+0x41/0x80
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105354] [<c0147100>] ? kthread+0x0/0x80
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105364] [<c0105297>] kernel_thread_helper+0x7/0x10
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105375] =======================
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105381] ---[ end trace bb3e413784405200 ]---
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105391] wlan0: Failed to config new BSSID to the low-level driver
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105407] wlan0: direct probe to AP 00:13:1a:51:cd:f0 try 1
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.105826] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.106093] wlan0: Failed to config new SSID to the low-level driver
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> (wlan0): device state change: 2 -> 3
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Oct 30 15:21:48 tkdlap2 NetworkManager: <info> (wlan0): supplicant interface state change: 1 -> 2.
Oct 30 15:21:48 tkdlap2 kernel: [ 7800.305046] wlan0: direct probe to AP 00:13:1a:51:cd:f0 try 2
Oct 30 15:21:49 tkdlap2 kernel: [ 7800.504115] wlan0: direct probe to AP 00:13:1a:51:cd:f0 try 3
Oct 30 15:21:49 tkdlap2 NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.vpnc' disappeared, cancelling connections
Oct 30 15:21:49 tkdlap2 kernel: [ 7800.705048] wlan0: direct probe to AP 00:13:1a:51:cd:f0 timed out
Oct 30 15:30:41 tkdlap2 syslogd 1.5.0#2ubuntu6: restart.
Oct 30 15:30:42 tkdlap2 kernel: Inspecting /boot/System.map-2.6.27-7-generic
Oct 30 15:30:42 tkdlap2 kernel: Cannot find map file.
Oct 30 15:30:42 tkdlap2 kernel: Loaded 51977 symbols from 97 modules.
Oct 30 15:30:42 tkdlap2 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Oct 30 15:30:42 tkdlap2 kernel: [ 0.000000] Initializing cgroup subsys cpu
Oct 30 15:30:42 tkdlap2 kernel: [ 0.000000] Linux version 2.6.27-7-generic (buildd at palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Oct 30 04:18:38 UTC 2008 (Ubuntu 2.6.27-7.15-generic)
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Tom Jaeger
2008-10-31 21:48:57 UTC
Permalink
Has anyone tested the modules in comment 85? They should fix the issue
in a much less intrusive way than a random compat-wireless snapshot that
constantly spits out all kinds of kernel warnings. The patch is also
100% safe, replacing a kernel panic by a warning so it should be
considered for SRU (and the use of linux-backports-modules should
probably be discouraged).

** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Christophe Dumez
2008-10-31 22:45:32 UTC
Permalink
I have a lot of "wrong command queue 31, command id 0x0" in my logs.
Apparently, this is due to the patch above.


** Attachment added: "kern.log"
http://launchpadlibrarian.net/19150148/kern.log
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Tom Jaeger
2008-10-31 22:57:04 UTC
Permalink
Thanks, these are exactly the cases where the iwlagn module shipped with
the ubuntu kernel would have crashed the kernel.
Post by Christophe Dumez
I have a lot of "wrong command queue 31, command id 0x0" in my logs.
Apparently, this is due to the patch above.
** Attachment added: "kern.log"
http://launchpadlibrarian.net/19150148/kern.log
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Christophe Dumez
2008-10-31 22:54:22 UTC
Permalink
Oh, I just got this (with your patch):
Oct 31 23:48:17 chris-xps kernel: [ 756.402636] WARNING: at
drivers/net/wireless/iwlwifi/iwl-tx.c:1196 iwl_tx_cmd_complete+0x2c9/0x2d0
[iwlcore]()
Oct 31 23:48:17 chris-xps kernel: [ 756.402643] wrong command queue 63,
command id 0x0
Oct 31 23:48:17 chris-xps kernel: [ 756.402648] Modules linked in: iwlagn
iwlcore rfkill led_class mac80211 cfg80211 aes_i586 aes_generic i915 drm
binfmt_misc af_packet rfcomm bridge stp bnep sco l2cap ipv6 ppdev acpi_cpufreq
cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table
cpufreq_conservative sbs sbshc pci_slot container iptable_filter ip_tables
x_tables ext3 jbd mbcache sbp2 parport_pc lp parport joydev snd_hda_intel
snd_pcm_oss snd_mixer_oss arc4 psmouse ecb snd_pcm crypto_blkcipher uvcvideo
iTCO_wdt compat_ioctl32 dcdbas serio_raw videodev pcspkr v4l1_compat
iTCO_vendor_support evdev sdhci_pci sdhci snd_seq_dummy mmc_core snd_seq_oss
btusb snd_seq_midi snd_rawmidi snd_seq_midi_event bluetooth snd_seq snd_timer
video output snd_seq_device snd soundcore intel_agp battery wmi button ac
agpgart shpchp pci_hotplug snd_page_alloc jfs sr_mod cdrom pata_acpi sd_mod
crc_t10dif sg ata_piix usbhid hid ohci1394 ieee1394 ahci ata_generic tg3 libphy
libata scsi_mod dock ehci_hcd uhci_hcd usbco
Oct 31 23:48:17 chris-xps kernel: e thermal processor fan fbcon tileblit font
bitblit softcursor fuse [last unloaded: cfg80211]
Oct 31 23:48:17 chris-xps kernel: [ 756.402886] Pid: 0, comm: swapper Not
tainted 2.6.27-7-generic #1
Oct 31 23:48:17 chris-xps kernel: [ 756.402894] [<c0131d65>]
warn_slowpath+0x65/0x90
Oct 31 23:48:17 chris-xps kernel: [ 756.402912] [<c0136976>] ?
set_normalized_timespec+0x16/0x90
Oct 31 23:48:17 chris-xps kernel: [ 756.402922] [<c037dfae>] ?
account_scheduler_latency+0xe/0x220
Oct 31 23:48:17 chris-xps kernel: [ 756.402934] [<c0118e38>] ?
read_hpet+0x8/0x20
Oct 31 23:48:17 chris-xps kernel: [ 756.402944] [<c014e63b>] ?
getnstimeofday+0x4b/0x100
Oct 31 23:48:17 chris-xps kernel: [ 756.402955] [<c0136976>] ?
set_normalized_timespec+0x16/0x90
Oct 31 23:48:17 chris-xps kernel: [ 756.402965] [<c0151c84>] ?
clockevents_program_event+0x14/0x150
Oct 31 23:48:17 chris-xps kernel: [ 756.402975] [<c014b79e>] ?
ktime_get+0x1e/0x40
Oct 31 23:48:17 chris-xps kernel: [ 756.402985] [<c015310b>] ?
tick_dev_program_event+0x3b/0xc0
Oct 31 23:48:17 chris-xps kernel: [ 756.402995] [<f9243f49>]
iwl_tx_cmd_complete+0x2c9/0x2d0 [iwlcore]
Oct 31 23:48:17 chris-xps kernel: [ 756.403021] [<c014a72d>] ?
enqueue_hrtimer+0x7d/0x130
Oct 31 23:48:17 chris-xps kernel: [ 756.403031] [<f9493a39>]
iwl_rx_handle+0xd9/0x260 [iwlagn]
Oct 31 23:48:17 chris-xps kernel: [ 756.403047] [<f949568d>]
iwl4965_irq_tasklet+0x1ad/0x2f0 [iwlagn]
Oct 31 23:48:17 chris-xps kernel: [ 756.403061] [<c0118e38>] ?
read_hpet+0x8/0x20
Oct 31 23:48:17 chris-xps kernel: [ 756.403071] [<c0137258>]
tasklet_action+0x78/0x100
Oct 31 23:48:17 chris-xps kernel: [ 756.403079] [<c0137682>]
__do_softirq+0x92/0x120
Oct 31 23:48:17 chris-xps kernel: [ 756.403087] [<c013776d>]
do_softirq+0x5d/0x60
Oct 31 23:48:17 chris-xps kernel: [ 756.403095] [<c01378e5>]
irq_exit+0x55/0x90
Oct 31 23:48:17 chris-xps kernel: [ 756.403102] [<c0106c1a>] do_IRQ+0x4a/0x80
Oct 31 23:48:17 chris-xps kernel: [ 756.403111] [<c0105003>]
common_interrupt+0x23/0x30
Oct 31 23:48:17 chris-xps kernel: [ 756.403119] [<c01700d8>] ?
__audit_mq_getsetattr+0x68/0xb0
Oct 31 23:48:17 chris-xps kernel: [ 756.403134] [<f885e800>] ?
acpi_idle_enter_bm+0x268/0x2b7 [processor]
Oct 31 23:48:17 chris-xps kernel: [ 756.403152] [<c02dbf7b>]
cpuidle_idle_call+0x7b/0xd0
Oct 31 23:48:17 chris-xps kernel: [ 756.403161] [<c010288d>]
cpu_idle+0x7d/0x140
Oct 31 23:48:17 chris-xps kernel: [ 756.403169] [<c037a661>]
start_secondary+0x9d/0xcc
Oct 31 23:48:17 chris-xps kernel: [ 756.403179] =======================
Oct 31 23:48:17 chris-xps kernel: [ 756.403184] ---[ end trace
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Earl Malmrose
2008-11-01 06:53:52 UTC
Permalink
So far so good. No crashes with those modules installed. Now all the
panic text quietly goes into the log file rather than killing the system
- which happens on average about once every 10 minutes. I'm always
seeing "wrong command queue 63, command id 0x0".
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Squaredge
2008-11-02 11:04:36 UTC
Permalink
Exactly the same : no crashes with this module but many many many "wrong
command queue 63, command id 0x0" in my log files ! Without this patch I
could reboot every minutes -_-
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
jems
2008-11-02 11:37:17 UTC
Permalink
I confirm things written here. I got a laptop with an intel 4965, and
the latest 8.10 makes it freeze just after a few minutes.

I have tried 3 things from this thread :
- 11n_disable : I couldn't see any wireless networks around me, "no scan results"
- lbm : kept crashing quite the same way
- finally comments 85 : my computer doesn't freeze anymore, but it keeps on writing to kern.log (1G of log/hour) => I attach a part of this file for debugging purpose.

BTW, this problem is not only from the kernel module used, as it has
been reported and I confirm that, that even if you boot with the kernels
that were stable in hardy, it crashes anyway.

Feel free to ask for more information !

** Attachment added: "part_of_kern.log"
http://launchpadlibrarian.net/19226490/part_of_kern.log
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Tom Jaeger
2008-11-02 15:34:28 UTC
Permalink
Post by jems
I confirm things written here. I got a laptop with an intel 4965, and
the latest 8.10 makes it freeze just after a few minutes.
- 11n_disable : I couldn't see any wireless networks around me, "no scan results"
- lbm : kept crashing quite the same way
- finally comments 85 : my computer doesn't freeze anymore, but it keeps on writing to kern.log (1G of log/hour) => I attach a part of this file for debugging purpose.
This looks like bug #286285.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Christophe Dumez
2008-11-02 11:51:30 UTC
Permalink
Yes. I confirm that I did not have any kernel panic on Hardy with hardy
kernel. Then, when I upgraded to Intrepid, I started to experience
kernel panics. Thus, I tried to use Hardy kernel on intrepid but I
experienced kernel panics anyway. This is odd but true.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Ivan Razumov
2008-11-02 12:22:58 UTC
Permalink
I confirm that module from comment 85 works for me.
Post by Christophe Dumez
Yes. I confirm that I did not have any kernel panic on Hardy with hardy
kernel. Then, when I upgraded to Intrepid, I started to experience
kernel panics. Thus, I tried to use Hardy kernel on intrepid but I
experienced kernel panics anyway. This is odd but true.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a direct subscriber
of the bug.
Status in The Linux Kernel: In Progress
Status in Ubuntu Release Notes: Fix Released
Status in "linux" source package in Ubuntu: Confirmed
Status in "linux-backports-modules-2.6.27" source package in Ubuntu: Fix Released
I don't know the specific trigger but in my testing with intrepid over the last few weeks I have found a large amount of kernel panics when connected to my 802.11n router with an intel 4965 card. This issue does not at all appear when I use an 802.11b/g network which is what I use exclusively at my university (student during the day). At one point my system had 4 kernel panics in 2 hours all while using network intensive applications (apt, firefox, terminal server client).
I've tried the REISUB magic keys several times but its a completely dead machine. However, I have found something that works and I think it should be added to the official repository, the Oct-1-2008 compat-wireless iwlagn module fixes the kernel panic issue. I've left my machine on for an extended period of time in the same conditions that used to kernel panic before and so far all is good. I understand we are nearing the end of the road and only major showstoppers should be included for release but I feel this warrants such consideration.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Tom Jaeger
2008-11-02 15:23:29 UTC
Permalink
Post by Christophe Dumez
Yes. I confirm that I did not have any kernel panic on Hardy with hardy
kernel. Then, when I upgraded to Intrepid, I started to experience
kernel panics. Thus, I tried to use Hardy kernel on intrepid but I
experienced kernel panics anyway. This is odd but true.
The reason is that in intrepid, the firmware was moved from the
linux-ubuntu-modules to the linux-firmware package, and even if you boot
the hardy kernel, its iwl4965 module will still use the new firmware.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
jems
2008-11-02 17:26:02 UTC
Permalink
Post by Tom Jaeger
This looks like bug #286285.
I think I got both bugs. Without the patch I got my system frozen, and
couldn't do anything. Now I can see I get also the other problem :-) My
computer is not freezing anymore, but I don't get any wifi anymore,
which I will live with for the time this bug is fixed.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
sorenjensen
2008-11-02 23:05:32 UTC
Permalink
For some of you: The non generic backport didn't work on either of my
computers but the generic did. All though it is really slow to connect
sometimes (1-3 min) and drops out once in a while it is still better
than the total freeze.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Tim Gardner
2008-11-04 01:42:14 UTC
Permalink
SRU Justification

Impact: A mostly benign BUG_ON condition should be WARN_ON, thereby
avoiding kernel oops.

Patch Descripton: Change BUG_ON to WARN

Patch: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
intrepid.git;a=commit;h=f09c6f52dc6b81f02599c8de3ed0ef5c74eadae1


** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu Intrepid)
Status: New => Fix Committed

** Changed in: linux (Ubuntu Intrepid)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
ZeblodS
2008-11-04 19:20:40 UTC
Permalink
I use Intrepid 64 on my Inspiron 1520 notebook, with the linux-
restricted-modules-generic (2.6.27-7.12)

I have compiled the compat-wireless-2008-10-31 by myself as syko21 wrote
on the 2008-10-06, and I have no kernel panic anymore.

But instead, I often lost my connexion and it is very painful because I
use to mount a folder form my server to my notebook with sshfs+autofs
(so using the wifi connection) and watch movies which are in that
folder. So when I lost the connexion, Totem freez, autofs freez and
finally all my computer freez ! I still have to reboot...

In Hardy there where no problem with the wifi, so how can I use the old
driver please ? (because for now it is unusable for me...)

PS : sorry for my poor english
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
syko21
2008-11-04 21:36:13 UTC
Permalink
The old driver from hardy uses a firmware microcode that is incompatible
with kernels after 2.6.24. I tried installing it and it didn't work.
Unless there are specific features you absolutely need from Intrepid you
can continue to use Hardy as it is a LTS release.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Aren Olson
2008-11-04 22:33:33 UTC
Permalink
"""The old driver from hardy uses a firmware microcode that is incompatible with kernels after 2.6.24. I tried installing it and it didn't work. Unless there are specific features you absolutely need from Intrepid you can continue to use Hardy as it is a LTS release."""
Alternatively you can just add the hardy main and restricted repos and install the hardy kernel on intrepid. This is what I did for about a month before there was any workaround for this at all.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Robb Topolski
2008-11-04 23:34:26 UTC
Permalink
Tom (comment 93),

Please see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/63
for some info.

--Robb
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Squaredge
2008-11-05 09:02:54 UTC
Permalink
New kernel panic, today, for me
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Ian Ellis
2008-11-07 00:36:45 UTC
Permalink
I'm having the same problem as ZeblodS after installing the linux-
backports-modules. My laptop will hard-lock and all the kernel log says
is "wlan0: disassociating by local choice (reason=3)".
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
syko21
2008-11-07 16:21:51 UTC
Permalink
The backports technically fixed the issue for me but I found better
stability with my original self-compiled module and I use that now
instead. No issues except suspend is iffy and hibernate does not work at
all, but I can live with that. (Hibernate seems to be linked to my
bluetooth module hci_usb)
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Ian Ellis
2008-11-07 17:42:00 UTC
Permalink
I had a problem where my laptop disconnected from the network and
wouldn't reconnect, but this time the system didn't hard-lock. I've
attached part of the kernel log that looks relevant. The network I use
is an open 802.11g network.

** Attachment added: "kernel log for 802.11g connection trouble"
http://launchpadlibrarian.net/19465178/kern.log
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
M Bageant
2008-11-07 21:10:36 UTC
Permalink
To add another testimony to those compiled here, I've been experiencing
the same problem since I upgraded to Intrepid and the 2.6.27-7 kernel a
few days ago. I have a Dell with an Intel 4965agn, and my school just
installed draft N routers; normally I disable wifi using the hard kill
switch and use a wired connection, which seems to eliminate the problem,
but when I wander around with my laptop and attempt to use the wireless
(usually using the 802.11g network, rather than the n one), I suffer a
kernel panic every 15-20 minutes, always with Firefox open and some
other network activity.

I'll try some of the solutions here and report back on what works or
does not work for me.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Tom Jaeger
2008-11-07 21:35:37 UTC
Permalink
The workaround for this problem has been accepted into intrepid-
proposed. In order to test it, you need make sure that the linux-
backports-modules package is not installed and then install the linux-
image-2.6.27-8-generic package from the intrepid-proposed repository
(see https://wiki.ubuntu.com/Testing/EnableProposed for details on how
to enable -proposed). This will also fix bug #286285.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Alger
2008-11-08 09:09:35 UTC
Permalink
After linux-image-2.6.27-8-generic still
Nov 8 10:06:01 mateusz-laptop kernel: [ 989.345864] iwlagn: Microcode SW error detected. Restarting 0x82000000.
Nov 8 10:06:01 mateusz-laptop kernel: [ 991.538856] iwlagn: Can't stop Rx DMA.
Nov 8 10:06:01 mateusz-laptop kernel: [ 992.765713] Registered led device: iwl-phy0:radio
Nov 8 10:06:01 mateusz-laptop kernel: [ 992.767280] Registered led device: iwl-phy0:assoc
Nov 8 10:06:01 mateusz-laptop kernel: [ 992.769033] Registered led device: iwl-phy0:RX
Nov 8 10:06:01 mateusz-laptop kernel: [ 992.770670] Registered led device: iwl-phy0:TX
Nov 8 10:06:01 mateusz-laptop kernel: [ 992.788123] wlan0: authenticate with AP 00:0e:2e:4b:6c:93
Nov 8 10:06:01 mateusz-laptop kernel: [ 992.849176] wlan0: authenticated
Nov 8 10:06:01 mateusz-laptop kernel: [ 992.849195] wlan0: associate with AP 00:0e:2e:4b:6c:93
Nov 8 10:06:01 mateusz-laptop kernel: [ 992.920318] wlan0: RX ReassocResp from 00:0e:2e:4b:6c:93 (capab=0x411 status=0 aid=1)
Nov 8 10:06:01 mateusz-laptop kernel: [ 992.920330] wlan0: associated
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
sorenjensen
2008-11-08 23:11:24 UTC
Permalink
"you need make sure that the linux-backports-modules package is not
installed and then install the linux-image-2.6.27-8-generic package from
the intrepid-proposed repository"

I tried above on a Sony Vaio VGN-TZ27GN/R and even it did take 5 hours
(Longer than before) to crash, it still died completely exactly as
before.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
John Pye
2008-11-10 13:43:08 UTC
Permalink
Me too! I am seeing this bug on my Dell XPS M1530 machine. I have updated the hwtest results, see here (machine 'roadwork'):
https://launchpad.net/~jdpipe/+hwdb-submissions

I have been getting kernel panics every few minutes, but just now I have
kept a remote SSH window open and seems to have stopped the crash
problem for the moment -- is it possible that stop/start wireless
traffic could be related to the problem?

I am currently downloading the proposed 2.6.27-8 kernel to see if that
fixes the problem.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
M Bageant
2008-11-12 02:52:55 UTC
Permalink
Update:
Adding "options iwlagn 11n_disable=1" to my /etc/modprobe.d/options does not fix the kernel panic. It occurred for me after some 40 minutes. The only thing that prevents it is hard killing the wireless with the keyboard shortcut.

I too will try downloading the proposed 2.6.27-8 kernel and test it.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
mojotoad
2008-11-13 15:15:31 UTC
Permalink
I'm using linux-image-2.6.27-8-generic on a Thinkpad X61s and have
intrepid-proposed enabled. I appear to be experiencing this bug (or
bugs). Sometimes it's fixable by reloading the iwlagn kernel module,
other times a kernel panic is triggered or I get a hard system freeze.

The problems have become fairly chronic, ever hour or so with moderate
network use.

Thanks,
Matt
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
mojotoad
2008-11-14 17:24:45 UTC
Permalink
Some additional observations. I tried linux-backports-modules-intrepid-
generic just to see what would happen and things became even more
unstable. I've attached some messages from kern.log that seem relevant.
I've removed the backports package and am now running just the intrepid-
proposed kernel again.

Thanks,
Matt


** Attachment added: "iwlagn with backport kern.log"
http://launchpadlibrarian.net/19650539/iwlagn.backport.txt
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
mojotoad
2008-11-14 17:29:05 UTC
Permalink
I've also noticed some differences in stability depending on whether or
not I'm using a VPN via the cisco_vpn kernel module. The crashes still
happen regardless of the presence of VPN, but they do seem to occur more
frequently in the presence of the cisco module.

When cisco_vpn is in use, kern.log gets lots of messages of this sort:

iwlagn: Unaligned address = 2e22a82f

Perhaps this can help further narrow down the issue. As for VPN, I
haven't noticed any of the comments above mentioning whether it was in
use or not, so perhaps that's another aspect to keep in mind.

Thanks,
Matt
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
John Pye
2008-11-15 03:52:52 UTC
Permalink
FWIW since I installed the updated 'proposed' kernel, I have not seen
these frequent crashes any more when accessing my 802.11n router.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
sorenjensen
2008-11-15 19:56:26 UTC
Permalink
Is this bug considered solved? If looking on "Bugs in Linux Kernel"
frontpage it seems to be included in "Bugs solved elsewhere (7)"? Please
excuse I am not strong in this bug system, just trying to get my 2
laptops running again, or at least one.

One Dell XPS M1530 and one Sony Vaio VGN-TZ27GN/R, both with intel 4695
card connected to wirelss n router.

Following setups have been tested:
On the M1530:
*Backport package resulted in no connection.
*Backport generic package gives a connection but takes minutes after it states connected before anything bits are allowed through. Disconnects once in while and again minutes to continue work.
*Proposed Kernel (Without backports) still crashes the machine w. wireless on (Works fine without wireless).

On the Vaio:
*Backport package resulted in no connection.
*Backport generic package made it impossible to connect.
*Proposed Kernel (Without backports) still crashes the machine.

If a solution is placed somewhere else I hope someone can help with
directions, thanks in advange.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Peter Schüller
2008-11-17 09:02:47 UTC
Permalink
I had the same problems for some days now.

After seeing this issue I installed the linux-image-2.6.27-8 from
intrepid-proposed and now I also get only warnings in the syslog, no
more hangs.

** Attachment added: "Three warnings in quick succession with 2.6.27-8 proposed kernel."
http://launchpadlibrarian.net/19714455/iwlagncrash.txt
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
John Pye
2008-11-17 12:30:04 UTC
Permalink
More observations from my Dell XPS M1530: since installing the 2.6.27-8
proposed linux-image, my wireless network is correctly running with no
more kernel panics. But I do observe that normally when I turn on my
computer and log in, the connection as it appears in NetworkManager
quite quickly shows two lights (in the task bar) but then fails to
completely connect. It then times out (and a little bubble message says
that connection failed), and then a moment later, it retries, and always
then successfully connects, on its second attempt.

Perhaps this is relevant to your comments, Soren?
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Mozg
2008-11-18 13:25:47 UTC
Permalink
I do experience kernel panic when using 802.11n router. I have tried the
following, but crashes are still there:

1. disabled 802.11n by using options iwlagn 11n_disable=1
2. installed backports (linux-backports-modules-intrepid-generic, linux-backports-modules-intrepid and linux-backports-modules-2.6.27-7-generic)

I did notice that with backports module my connection becomes somewhat
unstable. I would associate and authenticate with the AP, get the IP
address through DHCP, however, I can't ping anything. If i run as root
ping -f -s 65507 <router ip>, after about 10-60 seconds I would get the
connectivity and wireless seems to work until either a kernel panic or a
disconnect.

I have taken a picture with my cam of the console screen with the last
part kernel panic screen, which is attached to this email.

My laptop is Lenovo T61p 6459CTO with Intel 4965 abgn card.

My system is (latest updates):
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.10
Release: 8.10
Codename: intrepid

uname -a
Linux finka 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux

nothing interesting is shown in kern.log at the time of the crash

Hope the information helps to determine the problem

** Attachment added: "Screenshot of kernel panic"
Loading Image...
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
sorenjensen
2008-11-18 21:52:04 UTC
Permalink
To John: On the M1530, which now runs Kernel 2.6.27-7-generic + Backports Generic as it is usable, it connects fine and I don't get any disconnected message, but still a long time before any flow. Honestly I can live with this as its only slightly annoying and a bit worrying with regards to stability. The Vaio is bit more of a problem, but i guess it have to wait until a user friendly upgrade for the likes of me.
Sorry, I am not quite sure how to make a detailed log, which I know i should here.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
jems
2008-11-19 20:57:58 UTC
Permalink
Seems fine to me now, no kernel panics anymore while connecting to a
wifi with WPA encryption.

J?r?my
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
unimatrix
2008-11-22 13:30:10 UTC
Permalink
Just had another kernel panic with backports. Definitely not fixed yet.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Alex Wauck
2008-11-26 22:46:33 UTC
Permalink
I left my machine torrenting a file (Fedora 10, incidentally), and when
I came back, it had panicked. I'm using the latest kernel from
intrepid-backports. I'm now transferring a file with SFTP, so I'll see
what happens. The connection is 802.11g with WPA.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
syko21
2008-11-26 23:12:57 UTC
Permalink
Anyone up for randomly testing compat-wireless daily git archives? Mine
works perfectly from the Oct-1-2008 snapshot. Perhaps other days will
work better for other people. Its been months since I reported the bug
and people are still having problems so this issue seems to be rather
severe. Anyone have any ideas?
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Mozg
2008-11-26 23:27:03 UTC
Permalink
I'll check the latest module and report shortly. This is driving me
insane and I think it is very lame for ubuntu team not to test the
modules before releasing 8.10! It is not like there is only one 802.11n
router on the market and Intel wifi cards are very scarce.

Andrei
------Original Message------
From: syko21
Sender: bounces at canonical.com
To: andrei at arhont.com
ReplyTo: Bug 276990
Subject: [Bug 276990] Re: iwlagn causes kernel panic on 802.11n wifi
Sent: 26 Nov 2008 23:12

Anyone up for randomly testing compat-wireless daily git archives? Mine
works perfectly from the Oct-1-2008 snapshot. Perhaps other days will
work better for other people. Its been months since I reported the bug
and people are still having problems so this issue seems to be rather
severe. Anyone have any ideas?
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a direct subscriber
of the bug.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Mackenzie Morgan
2008-11-27 08:11:51 UTC
Permalink
Post by Mozg
I'll check the latest module and report shortly. This is driving me
insane and I think it is very lame for ubuntu team not to test the
modules before releasing 8.10! It is not like there is only one 802.11n
router on the market and Intel wifi cards are very scarce.
Canonical only has *some* hardware to test. Any other hardware
testing comes from users reporting bugs during unstable. This one was
reported less than a month before release. Unfortunately, most people
don't start testing on actual hardware until around Beta or RC, so we
lose out on a *lot* of time when hardware issues could be fixed. I
intend to install as soon as Jaunty is rebased on 2.6.28.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Alex Wauck
2008-11-27 00:27:19 UTC
Permalink
I was able to transfer the entire file (685MB) via SFTP with no trouble.
I was chatting online for most of the time, so maybe a certain degree of
randomness is involved?
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Bug Watch Updater
2008-11-28 03:13:27 UTC
Permalink
** Changed in: linux
Status: In Progress => Fix Released
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Mozg
2008-11-28 14:46:54 UTC
Permalink
I've noticed the change of status to Fix Released. Could you be more
specific, like how to obtain the fix. Is it in backports? what version
should be installed to fix the problem? Has it been fixed in the latest
2.6.27-9 kernel? Thanks.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
bh1nd3r
2008-11-28 19:08:16 UTC
Permalink
Backports seems to have fixed it for me on kernel 2.6.27-7 I can't say
for sure though, still testing it.. So far so good, my system uptime has
been 11 hours which was never achieved before the fix
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
David Moreno
2008-11-28 20:17:19 UTC
Permalink
People should give it a try with this firmware:
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703#c52
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
syko21
2008-11-28 21:11:43 UTC
Permalink
Please create a new bug report for the new firmware David Moreno posted
above me so that it can be included into Jaunty as soon as possible for
bug fixing if it works.

I'm at work at the moment and don't have access to my linux machine,
I'll try and make a new bug report tonight unless someone else wants to
beat me to it.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
David Moreno
2008-11-29 00:23:28 UTC
Permalink
Just for the record, the updated firmware did fix this issue for me (as
stated on the link to Intel's bugzilla), but I'm using a homebrew
2.6.27.7 kernel on Debian Lenny, not Ubuntu. Apparently, that firmware
will be released "officially" any time now by Intel's people.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
junior
2008-11-29 00:26:09 UTC
Permalink
After the latest update of the kernel I got panics again. But I've got
linux-image-2.6.27-8-generic installed, so is the panic due to something
else??
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Robb Topolski
2008-11-29 06:08:29 UTC
Permalink
They're baaaaaaaaaaaaaaaaaaaaa-ack.

With a patch at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52
and later a 2.6.27-8 kernel update in backports (mentioned later in bug
286285), I was avoiding kernel panics on 802.11n networks. Now with
2.6.27-9, the panics are back. I am able to work around them by turning
off the 802.11n capabilities of my router.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Mozg
2008-11-29 11:41:01 UTC
Permalink
I've tried the latest firmware release from the earlier post and I can confirm that the kernel panic still happens with heavy use of network (torrent at about 600kb of download). I am using the latest amd64 kernel 2.6.27-9.
------Original Message------
From: junior
Sender: bounces at canonical.com
To: andrei at arhont.com
ReplyTo: Bug 276990
Subject: [Bug 276990] Re: iwlagn causes kernel panic on 802.11n wifi
Sent: 29 Nov 2008 00:26

After the latest update of the kernel I got panics again. But I've got
linux-image-2.6.27-8-generic installed, so is the panic due to something
else??
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a direct subscriber
of the bug.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Mozg
2008-11-29 11:45:08 UTC
Permalink
The kernel panic also happen using the latest firmware with 2.6.27-7 on amd64. Will now try 2.6.27-8 from backports.
------Original Message------
From: Robb Topolski
Sender: bounces at canonical.com
To: andrei at arhont.com
ReplyTo: Bug 276990
Subject: [Bug 276990] Re: iwlagn causes kernel panic on 802.11n wifi
Sent: 29 Nov 2008 06:08

They're baaaaaaaaaaaaaaaaaaaaa-ack.

With a patch at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52
and later a 2.6.27-8 kernel update in backports (mentioned later in bug
286285), I was avoiding kernel panics on 802.11n networks. Now with
2.6.27-9, the panics are back. I am able to work around them by turning
off the 802.11n capabilities of my router.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a direct subscriber
of the bug.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Mo
2008-12-01 07:39:23 UTC
Permalink
On Thinkpad T61 I had no problems with the proposed 2.6.27-8 kernel.
With the 2.6.27-9 kernel the kernel panics are back!
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Andy Whitcroft
2008-12-01 08:51:15 UTC
Permalink
Post by Mo
On Thinkpad T61 I had no problems with the proposed 2.6.27-8 kernel.
With the 2.6.27-9 kernel the kernel panics are back!
The 2.6.27-9 kernel was a security update kernel and based on the
officially released version 2.6.27-7 (from the updates pocket), as such
it did not contain everything in the 2.6.27-8 kernel (from the proposed
pocket). There is a new proposed kernel 2.6.27-10 kernel available
now which was based on the 2.6.27-8 kernel plus the security updates
in 2.6.27-9.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
mojotoad
2008-12-01 16:13:01 UTC
Permalink
Okay, for what it's worth:

I've been experimenting with 2.6.28-rc6-wl out of the git repo, on my
X61s thinkpad.

Although I'm not getting as many kernel panics, I still lose
connectivity on a frequent basis, typically preceeded by:

iwlagn: Microcode SW error detected. Restarting 0x82000000.
iwlagn: Can't stop Rx DMA.

Things get horribly more unstable with kernel panics if I attempt a vpn
via the cisco driver. (I realize the cisco vpn module isn't really the
concern here, I'm just noting it for the record).

I'll see what happens with the firmware update.

Matt
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
mojotoad
2008-12-01 17:11:56 UTC
Permalink
So far so good after updating the microcode (comment #136) and
2.6.28-rc6. No network drops, seems stable -- even when running the
cisco vpn.

Matt
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
mojotoad
2008-12-01 23:03:57 UTC
Permalink
I spoke too soon. Things have improved considerably, but I'm still
periodically losing networking albeit less frequently. This is
2.6.28-rc6-wl plus the updated microcode.

kern.log shows the same messages as above.

If I happen to be using cisco vpn, some additional messages sometimes
show up:

kernel: [13311.535973] iwlagn: Microcode SW error detected. Restarting 0x82000000.
kernel: [13313.528088] iwlagn: Can't stop Rx DMA.
kernel: [13314.526425] iwlagn: No space for Tx
kernel: [13314.526435] iwlagn: Error sending REPLY_TX_PWR_TABLE_CMD: enqueue_hcmd failed: -28
kernel: [13314.526446] iwlagn: No space for Tx
kernel: [13314.526451] iwlagn: Error sending SENSITIVITY_CMD: enqueue_hcmd failed: -28
kernel: [13314.526456] iwlagn: SENSITIVITY_CMD failed

Matt
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Austin Lund
2008-12-01 23:30:51 UTC
Permalink
I have been able to recreate this fairly consistently by establishing a
connect with a wireless network (WPA encrypted, dunno if that's
important) then using the NetworkManager Applet to disable wireless.
This is not 100% repeatable, but when I've freshly booted the machine it
seems very repeatable.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
junior
2008-12-02 00:06:01 UTC
Permalink
I installed the interpid-proposed patch and never had kernel panics
after that. BUT after the latest kernel upgrade (the -9 I guess) I've
gotten many of them! I guess it's this bug that suddenly is reoccuring.
Is there any action required after kernel upgrades?
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Andy Whitcroft
2008-12-02 11:25:51 UTC
Permalink
Post by junior
I installed the interpid-proposed patch and never had kernel panics
after that. BUT after the latest kernel upgrade (the -9 I guess) I've
gotten many of them! I guess it's this bug that suddenly is reoccuring.
Is there any action required after kernel upgrades?
If you were running the -8 proposed kernel then upgrading to the -9
security kernel would have lost you some fixes. There is a -10 kernel
in -proposed which should contain the same fixes as -8 plus the security
fixes.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
sorenjensen
2008-12-02 20:57:15 UTC
Permalink
After reading about firmware update (Posted 28/11) I have tried
different setups for some days now:

Out with backports and proposed, upgrade to -9 Kernel (From respectively -7 and -8 proposed) and in with the recommended firmware. The connection stops 1 - 3 minutes each 5 - 15 minutes (It never shows disconnected nor informs about it).
In with the Backports again for Kernel -9 with more or less similar result.
Downgrading the firmware just to test the old one with Kernel -9, still same result.
Upgrading firmware again and in with proposed and backports again upgrading to Kernel -10....same results.

The results are the same on 2 quite different machines (4965 on both). I
run wireless n and WPA/WPA2.

At least the machines stopped crashing completely somewhere along the
way of these 20-30 different setups tried out since the release of 8.10.
At the moment I have lost track in which setup might have a chance of
working.
From testing in another business I get the feeling the patches doesn't
really solve some basic problem and this is why we experience continued
"Arms up - arms down again" - and not really a stable and convincing
result.

If there is something i can test to give more information, please let me
know.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
bh1nd3r
2008-12-06 07:59:36 UTC
Permalink
Kernel -10 seems to have fixed it on my laptop.. no more crashes :)
Post by sorenjensen
After reading about firmware update (Posted 28/11) I have tried
Out with backports and proposed, upgrade to -9 Kernel (From respectively -7
and -8 proposed) and in with the recommended firmware. The connection stops
1 - 3 minutes each 5 - 15 minutes (It never shows disconnected nor informs
about it).
In with the Backports again for Kernel -9 with more or less similar result.
Downgrading the firmware just to test the old one with Kernel -9, still same result.
Upgrading firmware again and in with proposed and backports again upgrading
to Kernel -10....same results.
The results are the same on 2 quite different machines (4965 on both). I
run wireless n and WPA/WPA2.
At least the machines stopped crashing completely somewhere along the
way of these 20-30 different setups tried out since the release of 8.10.
At the moment I have lost track in which setup might have a chance of
working.
From testing in another business I get the feeling the patches doesn't
really solve some basic problem and this is why we experience continued
"Arms up - arms down again" - and not really a stable and convincing
result.
If there is something i can test to give more information, please let me
know.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a direct subscriber
of the bug.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Mozg
2008-12-06 09:40:26 UTC
Permalink
I can confirm that -10 kernel seems to fix the kernel panics. I was able
to work for over 10 hours so far without a single crash. So far so good.

On a side note, did anyone manage to get a good speed out of 802.11n?
The output of iwconfig shows up to 60mbit/s even though I am sitting
next to wifi router. Is it only me?

Andrei
Andrei Mikhailovsky
Director
Arhont Information Security

Web: http://www.arhont.com
http://www.wi-foo.com
Tel: +44 (0)870 4431337
Fax: +44 (0)117 9690141
PGP: Key ID - 0x2B3438DE
PGP: Server - keyserver.pgp.com
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Christophe Dumez
2008-12-06 09:59:13 UTC
Permalink
No, you're not the only one. Apparently, 11n link aggregation does not
work in kernel 2.6.27. Intel said they would try to fix it for kernel
2.6.28.

However, I have tried kernel 2.6.28rc7 yesterday, and this is still not
fixed. I experience 11g speed too.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Martin Pitt
2008-12-06 16:11:08 UTC
Permalink
** Tags added: verification-done
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Daniel Holm
2008-12-19 15:22:01 UTC
Permalink
I also get this "panic". Me and a friend have to laptops of the same
specs and both get these heavy freezes. I got it together with Intrepid
and a D-Link DIR-615 Draft-N router. And as for everyone else, it
happends under intense network traffic, like when I download something
in Deluge, Firefox, treamin movies from my fileserver or editing text
files over SSH on my LAMP server.

Is there a way to fix this (there are to many comments to read here) or
I'm i stuck to Jaunty?
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
kolja_gava
2009-01-06 10:29:44 UTC
Permalink
Hi all,
I got same problem.
i did some test changing setting on my wireless router , and this seams did the trick
especially i set up "Dynamic Ruote" from "RIP2-B" to "RIP2-M".
hope this may help
regards
kolja
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
H0L7 sfpcr
2009-01-14 17:16:07 UTC
Permalink
thank you skyo you are a life saver
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Steve Langasek
2009-01-28 01:21:03 UTC
Permalink
Tim, is this bug fixed in the jaunty kernel? It's been marked 'fix
committed' for over two months now.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Tom Jaeger
2009-01-28 21:55:23 UTC
Permalink
Post by Steve Langasek
Tim, is this bug fixed in the jaunty kernel? It's been marked 'fix
committed' for over two months now.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=55d6a3cd0cc85ed90c39cf32e16f622bd003117b
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Steve Langasek
2009-01-28 23:50:58 UTC
Permalink
Tom,

I'm sorry, does that mean the bug is fixed in jaunty or that it isn't?
I'm not a kernel developer, I don't have a local git checkout of the
linux tree, and I don't see an easy way to go from a commit ID to an
answer "what kernel release is this change included in" without one.
For that matter, the commit you cited talks about downgrading the BUG_ON
to something that can be captured, so it's not clear to me that this
resolves the real issue at all.

So I don't see that this brings me any closer to answering the question
of whether this bug should be marked as fixed in jaunty, or if this
needs to be on the release team's watch list.
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.
Loading...