iwlagn causes kernel panic on 802.11n wifi

[syko21]

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.

[Chris Halse Rogers (raof)]

Thank you for reporting this bug, and helping to make Ubuntu better. In order to make it easier for the kernel team to handle this bug, could you please attach at least the "Minimal information" from https://wiki.ubuntu.com/KernelTeamBugPolicies ?

A picture of the panic would also be nice, but if you can't get that then the above information would still be useful.

[Mackenzie Morgan (maco.m)]

Kernel panicking on Intel's newest wireless chip, marking this as High importance.

[Neil Cawse (neilcawse)]

I have a dell XPS M1530 running iwlagn driver and after upgrading from Hardy to Intrepid Beta, i get kernel panics when wifi is busy. It seems to be triggered much more frequently in certain environments with heavy wifi traffic. In this case I always get a kernel panic 20 seconds after boot up but in other busy environments it may take hours.
It may thus depend on whether it is 802.11n or g traffic.
Id be surprised if this isnt a widespread problem.

[syko21 (syko21)]

Try compiling this iwlagn module, http://www.orbit-lab.org/kernel/compat-wireless-2.6/2008/10/compat-wireless-2008-10-01.tar.bz2 .
Extract the archive to your home directory then follow these steps

sudo apt-get install build-essential
cd compat*
make
sudo make install

Then restart your computer. It worked perfectly for me, if it works for more people perhaps the default ubuntu module will be upgraded.

PS> I was not able to test on 802.11g since I only use n and b.

[Michael Rooney (mrooney)]

Confirming based on Neil's input!

[Ivan Razumov (iarspider)]

Still happens with latest kernel.

[Ivan Razumov (iarspider)]

Still happens with latest kernel modules (yet to try the method by syko21)

[Leann Ogasawara (leannogasawara)]

Hi Guys,

Would one of you be able to capture the actual panic you are witnessing and post it to this bug report? Even if you have to take a digital photo of your screen and attach the photo here that would be most helpful. Otherwise it's rather difficult to debug. Can you also make sure you are running the latest 2.6.27-6 kernel. Thanks.

[syko21 (syko21)]

It is awkward to capture since my screen simply freezes on whatever it was doing (running apt, downloading in firefox, using samba shares, etc) so I don't really know how it will help you. If there is a method to retrieve log files or something along those lines then please direct me to those instructions and I will try to get them here ASAP.

[Mackenzie Morgan (maco.m)]

Leann,
What do you suggest syko21 try to capture? Kernel panics don't show up in logs. Kernel panics don't print anything to the screen. They just lock the system up and force you to hold down the power button.

If syko21 somehow has found a computer so ancient it has a serial port yet so very very new it has Intel 4965, and s/he owns a serial console...then, maybe they could catch an error. That hardware combination though? I really doubt it exists. I can't debug my Hardy kernel panics for the same reason.

[Chris Halse Rogers (raof)]

Kernel panics will generally dump _something_ to the (real) terminal.
The way to try and grab this would be to switch to a VT (with ctrl+alt
+F1) and wait for the kernel to die, then take a photo.

I seem to recall something about there being work to enable panics to be
visible while in X, but can't place it.

[Leann Ogasawara (leannogasawara)]

Hi syko21,

As Chris mentioned, the kernel panic will usually be dumped to the terminal window. You may also want to check if it may have been captured at /var/log/kern.log or /var/log/kern.log.0 . However I've also spoken with the Ubuntu kernel team and they are currently doing a backport to pull in an updated wireless stack. So based syko21's comment "the Oct-1-2008 compat-wireless iwlagn module fixes the kernel panic issue" I'm hopeful this backport should resolve this issue. I'll try to update this report when the package is available for testing. Thanks.

[Keithamus (keithamus)]

I don't know if it is helpful now, but I managed to get a capture of the panic (ironically while downloading the module in the comments above)

[Keithamus (keithamus)]

Would just also like to point out that I tried the patch syko21 suggested, and I got kernel panics on every boot. Had to boot into recovery and make uninstall.

Sorry, I wasn't able to catch the panic for that one, as I couldn't get into tty1 before it crapped out.

[syko21 (syko21)]

Sorry about that Keithamus, perhaps a newer version would work better for you. I updated mine to see if it was just a particular build that solved my problem but the one I download on Oct 9th works too. Maybe that one will let you boot normally.

[junior (olav-ekkje)]

I believe it's the same thing happening to me now. I've moved to some friends with a n-network, and suddenly I got alot of cernel panics. I killed gdm and switched to terminal, and got to take this picture of the screen. Hope this helps....

[Keithamus (keithamus)]

Just tried newer versions of the patch and still get panics, perhaps I'm compiling it incorrectly. Tried the 9th and 10th oct versions, as I say, still with panics.

[Jerone Young (jerone)]

I am also seeing this issue on my Thinkpad T61 with Intel Wireless WiFi Link 4965AGN REV=0x4 when I connect to my WRT600N with 802.11n on 5ghz band. Will get a term hooked up and try to get a dump. The screen shots posted are not showing the entire dump, and it is not making it to logs. Complete hard lockup after a little time connected to 802.11n 5gz.

Though it does not do this when connected to the 2.4ghz band connected via 802.11b or 802.11g.

[Jerone Young (jerone)]

linux-backports-modules 2.6.27-6.1 appears to fix this issue. I've run some large file transfer tests that easily caused the iwlagn module that comes with the kernel now to crash. But now running those tests with linux-backports-modules installed I no longer see the issue, and it doesn't crash at all.

I think most would prefer a non crashing module be apart of the regular kernel and not backports though. Hopefully later this week I'll have time to get a serial cable and see the crash

I was unable to get the kernel dump from the iwlagn driver as I really need a thinkpad docking station and getting kernel output out of USB serial ports seems like an impossible task.

[Neil Cawse (neilcawse)]

Thanks syko21, installing a recent iwlagn module does fix it for me.
Each time Ubuntu updates the kernel, I have to make / make install or the random crashes return.
Crashing on the latest update 2.6.27-7 without the update.
My kernel dumps looks same as others but Ive attached anyway.

[junior (olav-ekkje)]

How do I install the backported modules? I have added the backport repo, but what's the package I need? I'm eager to get the wifi working

[Mackenzie Morgan (maco.m)]

On Mon, 2008-10-13 at 15:45 +0000, junior wrote:
> How do I install the backported modules? I have added the backport repo,
> but what's the package I need? I'm eager to get the wifi working

I don't think you need the backports repo to get linux-backports-modules
That should be in Main.

[Tv (tv42)]

Running linux-backports-modules-2.6.27-6-generic 2.6.27-6.1 and linux-image-2.6.27-7-generic 2.6.27-7.10, still getting crashes.

[syko21 (syko21)]

Tv, try compiling the Oct-1 module manually using my instructions from the above post.

[junior (olav-ekkje)]

It's not any danger compiling this yourself with regards to the e1000e problems?

[syko21 (syko21)]

junior, the e1000e problem was due to the module writing to part of the EEPROM that it should not have been touching. The iwlagn module is fully open sourced and has been for a few kernel versions now allowing for a lot of eyes to look for any bugs. I hesitate to say there is 0 risk with bleeding edge software, but as it stands right now the only problem you may have is software based system instability at the very worst, and that can be corrected by uninstalling the module.

[junior (olav-ekkje)]

Well, I tried the module, and it won't connect to my wireless network.. To bad!

[junior (olav-ekkje)]

And how do I remove this module? I tried sudo make unistall, didn't work. Where are the modules located?

[Tv (tv42)]

I can confirm that the drivers at http://www.orbit-lab.org/kernel/compat-wireless-2.6/2008/10/compat-wireless-2008-10-01.tar.bz2 make all my crashes go away, on my Thinkpad T61. Haven't tested with 802.11n yet, but I had frequent crashes with just 802.11g (there was a 802.11n AP close by, but I wasn't using it), and now I haven't had a crash in 1 hour of active file transfer.

For just iwlagn, you may want to edit the Makefile in the above tarball, you don't need to stuff in /usr/lib. Littering is a bad habbit.

[Winckler (winckler)]

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.

[junior (olav-ekkje)]

Sorry, a typo, sudo make uninstall works fine. But the problem is to unload mac80211 and cfg80211, it says the modules are in use. But anyways, I'll try the disable option you mentioned Winckler!

[UnSandpiper (aybora)]

Winckler, I've tried your suggestion, but I got a kernel panic within few minutes.

Also, like Tv, I'm not even connecting to a 802.11n AP.
iwconfig tells me: wlan0 IEEE 802.11abg ESSID:"xxxxx"

[junior (olav-ekkje)]

Winckler, it works for me!! :)

[junior (olav-ekkje)]

No, it worked BETTER, but it didn't fix it. After starting Vuze and downloaded some torrents, it paniced again! Would be greatfull if someone could explain how to unload the mac80211 and cfg802 modules and use the compiled ones?

[syko21 (syko21)]

junior, if you unload iwlagn then cfg80211 then mac80211 it will work. Its a dependency issue with the modules. However the modules get rewritten right after you use the sudo make install command. The only reason you don't see the effect immediately is because the old modules were read in during the boot up sequence and are stored safely in the RAM. If you restarted then it won't make a difference if you reload those modules.

I will test my machine with a lot of torrents at once later today to see if I can reproduce the issue though.

[junior (olav-ekkje)]

It was Wincklers fix that didn't work with alot of network traffic. Now I've installed the 10.10 modules, but something in yesterdays update broke my wireless completely somehow, so I don't know the result yet

[junior (olav-ekkje)]

After installing the new module, no wireless networks shows up, so I cannot confirm if this works or not

[takeda64 (takeda64)]

Same here... after installing the modules, wifi card cannot connect anywhere. When I look Aat the logs is shows timeouts etc.

[Leann Ogasawara (leannogasawara)]

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.

[syko21 (syko21)]

Synaptic throws dependency errors when trying to install linux-backports generic. Screen shot attached.

[takeda64 (takeda64)]

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.

[takeda64 (takeda64)]

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 :/

[Winckler (winckler)]

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.

[syko21 (syko21)]

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]

[UnSandpiper (aybora)]

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.

[Leann Ogasawara (leannogasawara)]

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.

[Leann Ogasawara (leannogasawara)]

@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.

[syko21 (syko21)]

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.

[Ian McKellar (ianloic)]

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.

[Winckler (winckler)]

@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?

[Ian McKellar (ianloic)]

The linux-backports-modules-2.6.27 package seems to have solved my problem.

[joenix (woutersj)]

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

[Montana Harkin (montanaharkin)]

The linux backports package also fixed it for me.

[syko21 (syko21)]

I will retry backports since it appears to have fixed it for everyone else.

[Leann Ogasawara (leannogasawara)]

@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.

[Winckler (winckler)]

I have a good news. The kernel 2.6.27-7 with the backports is stable (so far).

Honestly, I don't know if my grub didn't upgrade automatically or had a kernel upgrade in the last 24 hours (I lost the track). The important is that all my reports were for the 2.6.27-5.

So far (3 hours of intense use), no error occur.

If anything change, I will post here.

[Steve Langasek (vorlon)]

Thanks for the confirmation, Winckler. Based on the more or less unanimous reports that lbm-2.6.27-7 fixes this problem, I'm closing the lbm-2.6.27 bug task.

Users who are running a 2.6.27-7 kernel and have linux-backports-modules 2.6.27-7.3 or later installed, and are still seeing problems, should file a separate bug report.

This still needs to be documented in the release notes, since users will only receive this fix by installing lbm explicitly.

[Steve Langasek (vorlon)]

Documented now at <https://wiki.ubuntu.com/IntrepidReleaseNotes#System%20lock-ups%20with%20Intel%204965%20wireless>.

[Tom Jaeger (thjaeger)]

So the plan is to ship intrepid with a version of the iwlagn driver that is known to cause kernel panics that are impossible for the average user to trace back to that driver? Not everybody reads release notes, so many people will end up with a system that is unstable for no apparent reason. If it's really not possible to backport the newer version of the driver, wouldn't it be a better idea to disable the broken driver altogether? That way people would be forced to look for a solution and then hopefully figure out that they need to install linux-backports-modules.

[Steve Langasek (vorlon)]

On Fri, Oct 24, 2008 at 09:43:44PM -0000, Tom Jaeger wrote:
> If it's really not possible to backport the newer version of the driver,
> wouldn't it be a better idea to disable the broken driver altogether?

No, that wouldn't be better; for some users this may make it impossible (or
nearly so) to download the updates needed to make it work.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[takeda64 (takeda64)]

Since I upgraded the driver, I haven't yet had any crash yet. So either I was just extremely lucky, or it also fixed problem for me.

It took me quite a while to link the crashes to the vireless driver (I initially thought it was problem with compiz).

I really think that if you can't provide the backports, then at least there should be some kind of notification for the first run, something like: "you seem to be running an Intel 4965 wireless card. There's a known bug that will make your system unstable. If you are experiencing this problems go to: https://wiki.ubuntu.com/IntrepidReleaseNotes#System%20lock-ups%20with%20Intel%204965%20wireless"

[syko21 (syko21)]

There is an inherent problem in putting the driver in backports. To get backports the person must use their wireless card to download the package, if the problem crops up during download it will not resume on the next reboot. Theoretically it would keep kernel panicking until they hooked up ethernet and then downloaded the package. This, to me, seems absolutely unacceptable when ubuntu is touting the new network-manager and improved wireless functionality.

PS> Backports worked for me too, my custom compiled driver got in the way when I installed it the last time.

[Michael Rooney (mrooney)]

On Sat, Oct 25, 2008 at 11:37 PM, syko21 <email address hidden> wrote:
> To get backports the person must use their wireless card to download the package

You definitely have a point but it is not necessarily a MUST, as wired
ethernet can download it, or the package can be put on removable
media. I agree that it is problematic but not guaranteed to be so.

[syko21 (syko21)]

That is true, at the very least it should be included on the iso, its only 2-3 MB at the very most. I think space can be found on the discs for them.

[Tom Jaeger (thjaeger)]

Could the bug please also be assigned to the linux kernel package (and its status be set to Confirmed). iwl4965 hardware is pretty common, people are going to start looking for this bug, we should at least make sure they have a fighting chance of finding the bug report.

The RC release notes are still understating the problem: It in fact also occurs when connected to an 802.11g access point (though it might well be that it only occurs when other 802.11n capable clients are within range), so the release notes might give people a false sense of security if they're only using 802.11b/g networks.

Finally, since this is a serious issue that has the potential to drive users (who'll just experience random freezes with no clue what hit them) away from Ubuntu, could the decision to not make the fix available by default please be reconsidered? How about splitting the ubuntu-backports-modules package into intel and non-intel drivers and have the regular kernel (modules) package depend on the intel (or just iwlagn) part?

[Mackenzie Morgan (maco.m)]

I updated the release notes to state that the kernel panics happen on 802.11g and 802.11n but that installing l-b-m will only fix the 802.11g issue about an hour ago.

[Steve Langasek (vorlon)]

Based on previous comments in this bug, that's inaccurate. A number of users have reported that lbm does fix the problem with 802.11n for them.

If the problem does affect 802.11g also then we certainly should mention that in the release notes, but by all evidence it's incorrect to say that only 802.11g is fixed.

[Mackenzie Morgan (maco.m)]

After Leann said to use l-b-m on 20 Oct:

These users say it works, but they don't say if they use g or n:
- Derek
- Ian
- harking

These users say it doesn't work for 802.11n:
- syko21
- Winckler

This user says it works, but they weren't using 802.11n to begin with:
- UnSandpiper

[Christophe Dumez (hydr0g3n)]

Well, I'm using 802.11n AP and intel 4965agn card and backport modules did fix my kernel panics.

BTW, I'm coming from duplicate bug 283212.

[Ivan Razumov (iarspider)]

As for me:
Before installing l-b-m: crashing on 802.11n (Cisco Aironet 1250), not crashing on 802.11g (don't know the exact model, but Cisco also)
After installing l-b-m: no crashed with 802.11n, and no crashes with 802.11g.

[Winckler (winckler)]

@Mackenzie Morgan

For me (Winckler, see comment on 2008-10-22), the l-b-m FIX the bug in .11N network. (I NEVER had troubles with .11b/g)

Also for syko21 (at 2008-10-26), he says that works for him too.

I guess works for everyone.

[syko21 (syko21)]

This makes it unanimous for all those that responded and tried the fix. If that doesn't warrant careful consideration for default inclusion I really don't know what will.

@Mike Rooney
What is your reasoning for saying it should not be included by default?

PS> I use 802.11N

[takeda64 (takeda64)]

@Mackenzie:
Right, I'm still not sure if the network that was crashing my laptop was n, but I'm pretty sure it wasn't (still I don't know how to verify it, since I'm not the owner of it)

BTW: at least half of my crashes happened during association to the network.

[Mackenzie Morgan (maco.m)]

OK, sorry. I didn't read all the way up to yesterday's "nevermind"s from syko21 and Winckler. I just saw where they said it didn't work before. I'm still a bit confused by UnSandpiper's though, since s/he wasn't using a n network.

[takeda64 (takeda64)]

Ehhh... sorry guys, but either the bug that I reported isn't duplicate of my bug, or the driver still didn't fix the issue.

After installing those drivers, and the intensity of crashes decreased, but my linux just crashed (first time since installing it).

I'm pretty certain that this was fault of the wireless driver, those are steps I did, before it happen.

My computer was in suspend to RAM state.
- made computer come back from suspend to RAM state
- since wireless card wasn't connecting to anything, I called sudo iwlist scan in terminal (it would be great to have that option in network manager)
- it showed wlan0: No scan results (didn't even take time to scan); while annoying this is normal and happens randomly.
- when this happens, I generally either restart NetworkManager, or untick & tick back "Enable Wireless" in Network Manager.
- there's 2 seconds freeze when I do, but this time it ended with caps lock & scroll lock blinking, and the mouse pointer pointing at "Enable Wireless" checkbox, with the checkbox still being ticked.

I'm sorry I'm unable to provide more detail. Does ubuntu have option to make kernel dump core when it crashes?
It seems to be much easier to debug things on FreeBSD (it can be configured so when it crashes it dumps memory to swap, and uppon next reboot it moves it from swap to a file in /var/crash.

[syko21 (syko21)]

This seems to be another issue not associated with this bug. I think you should file a separate bug report. This used to happen when I tested the daily builds of the iwl4965, I would load the driver and some sort of issue with mac80211 or cfg80211 would make my machine kernel panic. Try unloading all the modules

sudo modprobe -r iwlagn
sudo modprobe -r cfg80211
sudo modprobe -r mac80211

then uninstall backports (use completely remove in synaptic or aptitude purge from the command line) and restart.
Then reinstall backports and immediately restart after it is finished installing.

It worked for me when backports failed the first time.

[takeda64 (takeda64)]

The thing is, that the backports installed correctly. I rebooted the system several times, so there's no way old module is running. I noticed very drastic decrease frequency of the crashes. This is the first crash since then.
But I'lll do your recommendation just in case.

I think that my bug #284733 perhaps wasn't duplicate of this one. Few of the crashes earlier I experienced while trying to associate/deassociate to/from an AP. I think it might be another bug which existed in previous version.
(this crash happened at home and I'm not using 802.11n here) actually I doubt that the card had enough time to do any communication at that time, since it happened when I wasn't connected to any AP, and I was turning the wireless in network manager.

[Christophe Dumez (hydr0g3n)]

Very bad news. I have just experienced another kernel panic although I'm using linux-backport-modules.

I confirm that kernel panics happen a lot less often but they are still happening.

For me, the kernel panic happened although I was not using my laptop. The laptop was simply connected to the wifi and internet (no particular activity).

[Tom Jaeger (thjaeger)]

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

[Squaredge (squaredge62)]

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 ...

[Tom Jaeger (thjaeger)]

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.

[Squaredge (squaredge62)]

I just have apply these commands.
I will see tomorrow (at work) if this resolve this wireless bug ...

[Zizzle (mattpratt)]

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?

[David Moreno (damog)]

On Fri, 2008-10-31 at 00:43 +0000, Zizzle wrote:
> 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.

[takeda64 (takeda64)]

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 1...

[Tom Jaeger (thjaeger)]

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).

[Christophe Dumez (hydr0g3n)]

I have a lot of "wrong command queue 31, command id 0x0" in my logs. Apparently, this is due to the patch above.

[Christophe Dumez (hydr0g3n)]

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...

[Tom Jaeger (thjaeger)]

Thanks, these are exactly the cases where the iwlagn module shipped with
the ubuntu kernel would have crashed the kernel.

Christophe Dumez wrote:
> 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
>

[Earl Malmrose (earl)]

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".

[Squaredge (squaredge62)]

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 -_-

[jems (jmonnet)]

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 !

[Christophe Dumez (hydr0g3n)]

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.

[Ivan Razumov (iarspider)]

I confirm that module from comment 85 works for me.

2008/11/2 Christophe Dumez <email address hidden>:
> 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
>
> Bug description:
> 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.
>

[Tom Jaeger (thjaeger)]

Christophe Dumez wrote:
> 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.

[Tom Jaeger (thjaeger)]

jems wrote:
> 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.
This looks like bug #286285.

[jems (jmonnet)]

 Tom Jaeger wrote:
> 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.

[sorenjensen (soren-sbj)]

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.

[Tim Gardner (timg-tpi)]

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

[ZeblodS (forum-zeblods)]

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

[syko21 (syko21)]

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.

[reacocard (reacocard)]

"""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.

[Robb Topolski (funchords)]

Tom (comment 93),

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

--Robb

[Squaredge (squaredge62)]

New kernel panic, today, for me

[Ian Ellis (ianmailstuff)]

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)".

[syko21 (syko21)]

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)

[Ian Ellis (ianmailstuff)]

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.

[M Bageant (maiarb)]

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.

[Tom Jaeger (thjaeger)]

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.

[Alger (mateusz555)]

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

[sorenjensen (soren-sbj)]

"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.

[John Pye (jdpipe)]

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.

[M Bageant (maiarb)]

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.

[mojotoad (sisk)]

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

[mojotoad (sisk)]

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

[mojotoad (sisk)]

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

[John Pye (jdpipe)]

FWIW since I installed the updated 'proposed' kernel, I have not seen these frequent crashes any more when accessing my 802.11n router.

[sorenjensen (soren-sbj)]

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.

[Peter Schüller (schueller-p)]

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.

[John Pye (jdpipe)]

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?

[Mozg (andrei-arhont)]

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

[sorenjensen (soren-sbj)]

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.

[jems (jmonnet)]

Seems fine to me now, no kernel panics anymore while connecting to a wifi with WPA encryption.

Jérémy

[Dan Quade (danquade)]

Just had another kernel panic with backports. Definitely not fixed yet.

[Alex Wauck (awauck)]

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.

[syko21 (syko21)]

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?

[Mozg (andrei-arhont)]

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: <email address hidden>
To: <email address hidden>
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.

[Alex Wauck (awauck)]

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?

[Mackenzie Morgan (maco.m)]

On Wed, Nov 26, 2008 at 6:27 PM, Mozg <email address hidden> wrote:
> 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.

[Mozg (andrei-arhont)]

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.

[bh1nd3r (preet-bhinder)]

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

[David Moreno (damog)]

People should give it a try with this firmware:
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703#c52

[syko21 (syko21)]

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.

[David Moreno (damog)]

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.

[junior (olav-ekkje)]

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??

[Robb Topolski (funchords)]

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.

[Mozg (andrei-arhont)]

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: <email address hidden>
To: <email address hidden>
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.

[Mozg (andrei-arhont)]

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: <email address hidden>
To: <email address hidden>
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.

[Mo (audimax)]

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!

[Andy Whitcroft (apw)]

On Mon, Dec 01, 2008 at 07:39:23AM -0000, Mo wrote:
> 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.

[mojotoad (sisk)]

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

[mojotoad (sisk)]

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

[mojotoad (sisk)]

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

[Austin Lund (austin-lund)]

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.

[junior (olav-ekkje)]

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?

[Andy Whitcroft (apw)]

On Tue, Dec 02, 2008 at 12:06:01AM -0000, junior wrote:
> 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.

[sorenjensen (soren-sbj)]

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.

[bh1nd3r (preet-bhinder)]

Kernel -10 seems to have fixed it on my laptop.. no more crashes :)

On Tue, Dec 2, 2008 at 3:57 PM, sorenjensen <email address hidden> wrote:

> 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 direct subscriber
> of the bug.
>

[Mozg (andrei-arhont)]

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: [phone]
Fax: [phone]
PGP: Key ID - 0x2B3438DE
PGP: Server - keyserver.pgp.com

[Christophe Dumez (hydr0g3n)]

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.

[Daniel Holm (danielholm)]

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?

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[kolja_gava (kolja-bgblog)]

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

[H0L7 sfpcr (h0l7-edge)]

thank you skyo you are a life saver

[Steve Langasek (vorlon)]

Tim, is this bug fixed in the jaunty kernel? It's been marked 'fix committed' for over two months now.

[Tom Jaeger (thjaeger)]

Steve Langasek wrote:
> 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

[Steve Langasek (vorlon)]

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.

[Tom Jaeger (thjaeger)]

Steve Langasek wrote:
> 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.

Yes, it is part of the 2.6.28 release, having been committed to Linus'
tree in Sep 08. It's also in 2.6.27.x, by the way.

> 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.

From a user's perspective it doesn't make a difference if the patch
fixes the underlying issue or if it's "just" a workaround. What does
matter is that the fix has gotten a good amount of testing and is
confirmed to work.

This turned out to be a bug in the 4965's firmware, so the "proper" fix
is in jaunty since linux-firmware 1.3.

> 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.

Well, it certainly should be (along with bug #286285) on the list for
intrepid.

[James Ward (jamesward)]

I have linux-firmware 1.5 on Jaunty and I am still getting frequent kernel panics related to iwlagn. They usually happen within minutes of booting and only happen when the kill switch is off.

[Steve Langasek (vorlon)]

Ok, marking fixed for jaunty. Thanks for the explanation!

[Steve Langasek (vorlon)]

James,

Do the kernel panics crash the machine, or are you able to capture one and post it here to the bug?

If this is ultimately a firmware bug, we should probably also open a task on linux-firmware -- though I would hope the kernel driver could be made more resilient against firmware bugs, too.

[James Ward (jamesward)]

@Steve

Doesn't "fixed" usually mean the kernel panics have stopped? :)

[syko21 (syko21)]

@James Ward

THIS bug is fixed. The issue you are talking about is a completely different bug altogether. I reported this bug several months ago because I found stability issues AFTER connecting to wireless networks, not while the hardware was powered off or the power switch was set to off. I recommend you try finding out as much information as possible about your situation and post a separate bug report.

[Steve Langasek (vorlon)]

On Thu, Jan 29, 2009 at 01:10:14AM -0000, James Ward wrote:
> Doesn't "fixed" usually mean the kernel panics have stopped? :)

Yes, but it's not altogether clear that your panics are the same as the ones
in this bug. You mention booting with the killswitch off, whereas this bug
is about a panic when associating - if the antenna is off, you certainly
wouldn't be associating, so yours is probably a different bug.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[James Ward (jamesward)]

Hi Steve,

Yes. My machine (Jaunty updated 30 minutes ago) locks up a few minutes after booting if the kill switch is not on. If I instantly rmmod iwlagn then I can use it for days without lockup. So this is certainly a iwlagn kernel panic.

I have no idea how to get any details as to what is causing the kernel panic. Any pointers would be appreciated.

The bug description "iwlagn causes kernel panic on 802.11n wifi" fits my problem. So unless linux-firmware 1.3 fixed other people's kernel panics then it doesn't seem this bug is really fixed.

[Mackenzie Morgan (maco.m)]

James:
The kernel panics that happen when the killswitch is disabled (so
networking is enabled) and 802.11n is in use have stopped. Your kernel
panics, which you say occur when networking is disabled in hardware are
something new.

[Mackenzie Morgan (maco.m)]

Are you or are you not associated to an 802.11n network? Your
description sounds like you are *not* online, so while the same module
may be to blame, it would be a different bug than one that occurs only
when using 802.11n to get online.

[James Ward (jamesward)]

Sorry to not be clear. My kernel panics happen when my iwlagn is on and connected to an AP.

So how do I get more information about what is causing my kernel panic?

[Steve Langasek (vorlon)]

If the system is hard locking, your best option is to switch to the console with Ctrl+Alt+F1 immediately after boot, wait for the panic, and then take a photograph of the resulting kernel panic.

[Mackenzie Morgan (maco.m)]

Is your AP using 802.11n or 802.11g or mixed mode or....you get the
picture?

[Michael Rooney (mrooney)]

On Wed, Jan 28, 2009 at 5:41 PM, James Ward wrote:

> Sorry to not be clear. My kernel panics happen when my iwlagn is on and
> connected to an AP.
>

I think your language "killswitch is off" was confusing some people :) I
assume by that you meant the killswitch was not enabled, ie the wireless was
not disabled, ie it was on.

[James Ward (jamesward)]

Ok. Got the picture, but I couldn't get the whole message. I'll try again with a different vga boot parameter. But I've attached what I have so far.

My AP is mixed mode G and N.

[Steve Langasek (vorlon)]

James,

Your backtrace corresponds to that seen by Zizzle (in
<https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.27/+bug/276990/comments/87>) modulo kernel version differences, but not with any of the other kernel panics shown in this bug report or the ones I can find being discussed upstream. I would suggest filing a new bug report and attaching your screenshot, so that this crash can be traced separately - it does appear that the problem has been addressed for most users.

[James Ward (jamesward)]

I've created a new big with the whole kernel panic message:
https://bugs.launchpad.net/ubuntu/+bug/323622

[oc (oc-rynning)]

Even though I no longer get kernel panics from iwlagn, the bug is still not completely fixed. Once in a while I get these traces in my messages. Wireless is disabled, and modprobe -r && modprobe, nor rmmod or insmod will reload the iwlagn (nor cfg80211, iwlcore, mac80211, ...) module. A reboot is required to get wireless up and working again.

Hardware: HP Compaq 8710W, Core 2 Duo T7700 @ 2.40, 2gb ram, Mobile PM965/GM965/GL960 chipset, 82801H (ICH8) USB, Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) wireless...

Kernel: Linux oc-laptop 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009 x86_64 GNU/Linux
OS: Ubuntu Jaunty

Call trace:

Feb 14 19:20:51 oc-laptop kernel: [16006.397148] iwlagn/0: page allocation failure. order:4, mode:0x40d0
Feb 14 19:20:51 oc-laptop kernel: [16006.397150] Pid: 2266, comm: iwlagn/0 Tainted: P 2.6.28-7-generic #20-Ubuntu
Feb 14 19:20:51 oc-laptop kernel: [16006.397152] Call Trace:
Feb 14 19:20:51 oc-laptop kernel: [16006.397159] [<ffffffff802b38fe>] __alloc_pages_internal+0x3ee/0x500
Feb 14 19:20:51 oc-laptop kernel: [16006.397176] [<ffffffffa0971537>] ? iwl_tx_queue_init+0x57/0x180 [iwlcore]
Feb 14 19:20:51 oc-laptop kernel: [16006.397179] [<ffffffff802b3a8e>] __get_free_pages+0x1e/0x60
Feb 14 19:20:51 oc-laptop kernel: [16006.397185] [<ffffffffa096f8e9>] iwl_tx_queue_alloc+0x39/0x1a0 [iwlcore]
Feb 14 19:20:51 oc-laptop kernel: [16006.397191] [<ffffffffa09715a8>] iwl_tx_queue_init+0xc8/0x180 [iwlcore]
Feb 14 19:20:51 oc-laptop kernel: [16006.397198] [<ffffffffa09719ac>] iwl_txq_ctx_reset+0x18c/0x1e0 [iwlcore]
Feb 14 19:20:51 oc-laptop kernel: [16006.397204] [<ffffffffa096af8b>] iwl_hw_nic_init+0xfb/0x160 [iwlcore]
Feb 14 19:20:51 oc-laptop kernel: [16006.397212] [<ffffffffa098c10b>] __iwl4965_up+0xbb/0x2f0 [iwlagn]
Feb 14 19:20:51 oc-laptop kernel: [16006.397225] [<ffffffffa098c340>] ? iwl4965_bg_up+0x0/0x60 [iwlagn]
Feb 14 19:20:51 oc-laptop kernel: [16006.397230] [<ffffffffa098c379>] iwl4965_bg_up+0x39/0x60 [iwlagn]
Feb 14 19:20:51 oc-laptop kernel: [16006.397233] [<ffffffff8026127a>] run_workqueue+0xba/0x190
Feb 14 19:20:51 oc-laptop kernel: [16006.397235] [<ffffffff80261557>] worker_thread+0xa7/0x120
Feb 14 19:20:51 oc-laptop kernel: [16006.397238] [<ffffffff802658d0>] ? autoremove_wake_function+0x0/0x40
Feb 14 19:20:51 oc-laptop kernel: [16006.397240] [<ffffffff802614b0>] ? worker_thread+0x0/0x120
Feb 14 19:20:51 oc-laptop kernel: [16006.397242] [<ffffffff80265469>] kthread+0x49/0x90
Feb 14 19:20:51 oc-laptop kernel: [16006.397245] [<ffffffff80213979>] child_rip+0xa/0x11
Feb 14 19:20:51 oc-laptop kernel: [16006.397247] [<ffffffff80265420>] ? kthread+0x0/0x90
Feb 14 19:20:51 oc-laptop kernel: [16006.397249] [<ffffffff8021396f>] ? child_rip+0x0/0x11
Feb 14 19:20:51 oc-laptop kernel: [16006.397251] Mem-Info:
Feb 14 19:20:51 oc-laptop kernel: [16006.397252] DMA per-cpu:
Feb 14 19:20:51 oc-laptop kernel: [16006.397253] CPU 0: hi: 0, btch: 1 usd: 0
Feb 14 19:20:51 oc-laptop kernel: [16006.397254] CPU 1: hi: 0, btch: 1 usd: 0
Feb 14 19:20:51 oc-laptop kernel: [16006.397256] DMA32 per-cpu:
Feb 14 19:20:51 oc-laptop kernel...

[syko21 (syko21)]

@oc
Since you no longer get kernel panics as a result of the iwlagn module I recommend submitting your findings as a separate bug report so it can be fixed instead of buried in a bug report that has already been marked fixed.

Please any admins/mods around can you please close this bug report. The fix has been released and the issue is documented in the release notes for Intrepid so people who do not know can still find the solution.

[Tom Jaeger (thjaeger)]

syko21 wrote:
> @oc
> Since you no longer get kernel panics as a result of the iwlagn module I recommend submitting your findings as a separate bug report so it can be fixed instead of buried in a bug report that has already been marked fixed.
>
> Please any admins/mods around can you please close this bug report. The
> fix has been released and the issue is documented in the release notes
> for Intrepid so people who do not know can still find the solution.
>

I've never been happy with that release notes (individual changes can
always be cherry-picked), but now that the fix is in the -updates
kernel, the release notes are plain incorrect.

[Steve Langasek (vorlon)]

This issue was documented in the 8.10 release notes; closing this task.

[Joachim Dahl (jdahl)]

Do you mean that it is fixed in the updates for Ubuntu 8.10? I still
experience frequent crashes
after installing all the proposed kernel updates for 8.10.

Steve Langasek skrev:
> This issue was documented in the 8.10 release notes; closing this task.
>
> ** Changed in: ubuntu-release-notes
> Status: New => Fix Released
>
>

[Mackenzie Morgan (maco.m)]

He only closed the release notes task.

[Michael Rooney (mrooney)]

On Thu, Mar 26, 2009 at 12:10 AM, JDahl wrote:

> Do you mean that it is fixed in the updates for Ubuntu 8.10?

No, Steve just means that it was addressed in the release notes so that
specific task for the release notes is done.

[Rocko (rockorequin)]

Is it possible that this is back in the Jaunty beta? Since I installed the 2.6.28-11#37 kernel (ie that ships with the beta) on the 25th March, I've had five kernel panics. Jaunty was rock solid for me with 2.6.28-11#36 and earlier.

I can't be sure what is causing the panics though because X is running, so everything freezes, the indicator lights (wlan, bluetooth etc) blink, and the keyboard no longer works. Since I'm in X, I can't see any console output.

[syko21 (syko21)]

I've been running a clean jaunty install since alpha 3, I can't confirm that this particular bug is back. What are you doing when the kernel panic presents?

[Rocko (rockorequin)]

In each of the kernel panics, I've been doing something different - it's not readily reproducible. The most surprising one happened sometime very early in the morning when the computer should have been idling, although it's possible it had decided to do an auto apt-get update or was updating the locate database. There's absolutely no information in the logs.

[Geir Ove Myhr (gomyhr)]

I don't think this particular bug is back. I had this problem with early intrepid, but I've been running updated Jaunty since February and have not had a crash yet.

Rocko, maybe you can switch to console (Ctrl+Alt+F1) whenever you leave the computer, so that if it panics during that time it will show the console output.

[Winckler (winckler)]

In the same way that Rocko reported, my kernel panics are back, since the beta release.

I'm using Jaunty since before alpha, and everything was ok. But now, I have a average of 2 kernel panics per day, all in different scenarios, but always with the wireless working. If I'm not using the wireless connection, it seems to not happen.

An other difference is that it happens in non-N networks. (I only had the initial bug in N networks.)

Also, I notice that many shutdowns gives me a kernel fault in the iwlang module. I will try to get a picture.

If anyone have any suggestions, please, let me know.

[Rocko (rockorequin)]

@Winckler: I've had some kernel panics while connected to a non-11n network as well. So I assume it's nothing to do with this 11n bug and I've opened a new bug for the panics, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/348731, so perhaps you could add something about your system config there. There are also some suggestions on how to capture kernel output about the panic (not that easy since the whole system locks up).

[Tim Gardner (timg-tpi)]

2.6.27-8.17

  * iwlagn: downgrade BUG_ON in interrupt

[Steve Langasek (vorlon)]

Please do not reopen bugs without explanation.

[James Ward (jamesward)]

I'm not seeing this bug anymore on karmic.

[Alex Valavanis (valavanisalex)]

Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the
report. The bug has been fixed in newer releases of Ubuntu.