Kernel-Panic with 3.0.0.12-generic on asus eee pcs and msi wind (both using rt2800 wifi chipset)

[Michael Basse]

The latest Kernel

michael@eeebuntu:/var/log$ uname -a
Linux eeebuntu 3.0.0-12-generic #19-Ubuntu SMP Fri Sep 23 21:18:13 UTC 2011 i686 i686 i386 GNU/Linux

has about 10 Kernelpanics here. All happened on a eeepc 901 from Asus.

Because i have not found anything in /var/log/* i only have a picture from that panic.

Panics are happening with and without power-adapter plugged in

Please let me know if you need more infos

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-generic 3.0.0-12.19
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu2
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michael 1430 F.... pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 44'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,1043831a,00100004'
   Controls : 12
   Simple ctrls : 7
Date: Thu Oct 6 22:45:44 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=3147250b-39a6-47ab-92dd-3ae71a43c9a8
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
MachineType: ASUSTeK Computer INC. 901
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=797c12e0-f5e5-4b81-9464-0d8de0ce0a16 ro acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2011-09-16 (20 days ago)
dmi.bios.date: 06/11/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 901
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/11/2009:svnASUSTeKComputerINC.:pn901:pvrx.x:rvnASUSTeKComputerINC.:rn901:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 901
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Dirk (dirk-redhat-bugs)]

Description of problem:
Kernel 2.6.40.3-0.fc15.x86-64 causes kernel panic and switching back to text mode with system freeze

Version-Release number of selected component (if applicable):
Kernel 2.6.40.3-0.fc15.x86-64

How reproducible:
Updated kernel and used Firefox when crash occurred

Steps to Reproduce:
1.Update Kernel
2.Use Firefox
3.

Actual results:
Kernel panic, switch back to text mode and freeze of system

Expected results:
Normal system performance

Additional info:
Previous kernel version caused kernel panic, too.
Using now kernel 2.6.38.8-35.fc15.x86_64 which is running OK.

[Gareth (gareth-redhat-bugs-1)]

I also see this or similar behaviour with both 2.6.40 kernel updates, but not 2.6.38.

Often the system doesn't drop to text mode, or the screen is scrambled with panic text overlaid. I also get a panic if I login in text-mode, but it usually takes longer.

The most common panic is "BUG: unable to handle kernel NULL pointer dereference", although sometimes it's "Not syncing".

/var/log/messages contains over 300 MiB of such text:
"BUG: scheduling while atomic: swapper"
"bad: scheduling from the idle thread!"

My system: Fedora 15 x86-64, Intel Core i7 940, Asus P6T Deluxe motherboard, NVIDIA 9800 GT graphics with default up-to-date nouveau driver, untainted kernel.

(Screen-shots and log extracts available on request.)

Gareth

[Josip-g (josip-g)]

Probably related to bug 732008 which has a crash screen picture (that bug occurs immediately on boot, within one second)

[Dave (dave-redhat-bugs)]

> (Screen-shots and log extracts available on request.)

We really need only the first one from each session.
A lot of the time an oops or similar warning will occur, and then the kernel state is so messed up that 'follow-up' oopses happen afterwards that aren't really useful.

[Gareth (gareth-redhat-bugs-1)]

Created attachment 519736
Extract from /var/log/messages

Extract from /var/log/messages, starting just before the first kernel oops (as far as I can tell). This and similar errors then repeat for 350 MiB.

[Gareth (gareth-redhat-bugs-1)]

Created attachment 519737
Kernel message as on-screen

This is the sort of thing I see on the screen when the error happens - if I'm lucky enough to see anything on-screen at all: often it just freezes.

[Roland (roland-redhat-bugs)]

Had the same troubles. My temporary solution:
Install "Kernel 2.6.40.3-0.fc15.x86-64.debug" e.g. by using yumextender.
It worked. No idea why though ...

[Dave (dave-redhat-bugs)]

there's a lot going on here, but my gut is telling me this is related to the wireless driver (if only because it's the only prominent thing in the stack traces).

Maybe John has some clues..

Dirk, does this look like the same thing you're seeing ?

[Gareth (gareth-redhat-bugs-1)]

That sounds reasonable. I've noticed a single panic with 2.6.38 which seemed to be rt2500-related.

I'll attach my lspci -vvxxx output in case it helps.

If there's a general feeling that this is related to the rt2500 driver I can ask on the FedoraForums to see if anyone else is having similar problems.

Gareth

[Gareth (gareth-redhat-bugs-1)]

Created attachment 521064
lspci -vvxxx output

The rt2500 hardware is near the end of the file.

[John (john-redhat-bugs)]

Looks like it could relate to power saving mode. You might try this:

   iw dev wlan0 set power_save off

Does that change the issue?

[Gareth (gareth-redhat-bugs-1)]

I added "iw ..." to my /etc/rc.local (I didn't want to bet on having time to type it manually).

So far, so good - 25 mins uptime, which is *considerably* more than I've ever managed with 2.6.40 before.

It's pub time for me now, but I'll report back when I've got some serious usage out of it tomorrow.

Gareth

[Gareth (gareth-redhat-bugs-1)]

Okay, just to confirm, the suggested iw work-around makes 2.6.40 usable for me.

[Dirk (dirk-redhat-bugs)]

(In reply to comment #7)
> there's a lot going on here, but my gut is telling me this is related to the
> wireless driver (if only because it's the only prominent thing in the stack
> traces).
>
> Maybe John has some clues..
>
> Dirk, does this look like the same thing you're seeing ?

I've made some photos of the kernel panic message since the system freezes and doesn't allow for screen shots.

[Dirk (dirk-redhat-bugs)]

Created attachment 521389
Photos of kernel panic message after system freeze

[Gareth (gareth-redhat-bugs-1)]

Dirk and Roland, are you using the rt2500 wireless driver (or similar)? If so, does John's command stop the kernel panics?

Also take a look at your /var/log/messages, as what appears on screen is probably the end result of the problem, not necessarily the start.

That'd be the easiest way to see if you're affected by the same bug as me, whether it's more complicated, or even multiple different bugs.

Gareth

[Dirk (dirk-redhat-bugs)]

(In reply to comment #15)
> Dirk and Roland, are you using the rt2500 wireless driver (or similar)? If so,
> does John's command stop the kernel panics?
>
> Also take a look at your /var/log/messages, as what appears on screen is
> probably the end result of the problem, not necessarily the start.
>
> That'd be the easiest way to see if you're affected by the same bug as me,
> whether it's more complicated, or even multiple different bugs.
>
> Gareth

Using rt2500pci rt2x00lib

John's command seems to stop the kernel panic. System is up one hour now. Without

iw dev wlan0 set power_save off

panic occurred after a couple of minutes.

Regarding /var/log/messages not sure which part might be of any interest now.

[Gareth (gareth-redhat-bugs-1)]

Okay, ditto, I think that's enough to be sure we're seeing the same bug.

[Roland (roland-redhat-bugs)]

(In reply to comment #15)
> Dirk and Roland, are you using the rt2500 wireless driver (or similar)? If so,
> does John's command stop the kernel panics?
>
> Also take a look at your /var/log/messages, as what appears on screen is
> probably the end result of the problem, not necessarily the start.
>
> That'd be the easiest way to see if you're affected by the same bug as me,
> whether it's more complicated, or even multiple different bugs.
>
> Gareth

Gareth,
That PC has no wireless. Therefore, I suppose it has no wireselss drivers installed. Or could it?

Furher, I cannot read the screen so fast. If you need exact info about what happens, please tell me which file to read. And also how to access it, because ... since a while Fedora has changed so that I can no longer operate root in graphical mode. As a dillettant, I find it very difficult to keep this operating system in the air now. Would you have an advice about this?

Roland

[Michael Basse (michael-alpha-unix)]

also the kernel-panic never happened with 3.0.0-11 just with 3.0.0-12

[Ian Corne (icorne)]

This happens to me too on Asus eee 1000H

Never on my desktop/other laptops.

[Michael Basse (michael-alpha-unix)]

Happened again on eeepc 901 with 3.0.0-12-generic.

I was doing nothing for 5-10 Minutes on the netbook, then the panic happened. Maybe some standby-rules triggered it?

Picture of the panic is attached

[Joseph Salisbury (jsalisbury)]

@Michael

Would it be possible for you to roll back to the 3.0.0-11 kernel? That would confirm that there is a possible regression. It will also confirm there are no new hardware issues since upgrading to the new kernel.

[Michael Basse (michael-alpha-unix)]

Hi Joseph,
of course it is possible. I will run this system on 3.0.0-11-generic.

But i think i cant give you a feedback this week because at the weekend this system is not used very often.

[Joseph Salisbury (jsalisbury)]

@Ian

Would it be possible for you to test your system on 3.0.0-11-generic. That would confirm this as a regression.

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[Michael Basse (michael-alpha-unix)]

@Joseph,
i was running 3.0.0-11-generic for 3 days without a kernel-panic. Dont know if that is enough time to say that 3.0.0-11-generic is not affected. However, i am now using 3.0.0.12.20-generic as Brad suggested.

I will put some info here (and change the bug-status) after some days of testing

[Michael Basse (michael-alpha-unix)]

Happening also with 3.0.0.12.20-generic

[Michael Basse (michael-alpha-unix)]

are there any task i can do to give a better report about this issue?

[Joseph Salisbury (jsalisbury)]

@Michael,

Thanks for confirming the issue does not happen with 3.0.0-11-generic. Posting a screen shot of the panic you had while running 3.0.0.12.20-generic would help.

Also, would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

[Ian Corne (icorne)]

I am sorry i'm being so passive in this case, I don't use my eee all that much and as such, won't be much use.

[Michael Basse (michael-alpha-unix)]

Joseph, thank your for the feedback and your time.

First of all there was another kernel-panic on 3.0.0-12.20-generic which i will append here. The last screenshot was also from 3.0.0-12.20-generic

At the moment i am using this kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-rc9-oneiric/

michael@eeebuntu:/var/log# uname -a
Linux eeebuntu 3.1.0-0301rc9-generic #201110050905 SMP Wed Oct 5 11:20:31 UTC 2011 i686 i686 i386 GNU/Linux

I will test this kernel if the panic still comes up.

FYI: at booting i get but that should be a problem for my tests

./boot.log:Cache read/write disabled: /sys/kernel/security/apparmor/features interface file missing. (Kernel needs AppArmor 2.4 compatibility patch.)

[Yann Benigot (yann-benigot)]

Another kernel panic

[Joseph Salisbury (jsalisbury)]

@Michael

Were you able to test the v3.1-rc9-oneiric kernel?

[Yann Benigot (yann-benigot)]

I have tried other kernels and experienced kernel panics with all of them. Tested kernels : 3.0.0-11, 3.0.0-12, 3.0.6-030006, 3.1.0-0301rc9. Perhaps my problem is different since the panic screen differs from the other shown.

[Michael Basse (michael-alpha-unix)]

Joseph, after 3 Days of testing (20 hours uptime each day) there wa no kernel-panic with 3.1.0-0301rc9-generic

Is there something i can help with for the next steps?

[Michael Basse (michael-alpha-unix)]

@Yann
hm strange, with 3.0.0-11 and 3.1.0-0301rc9-generic i dont get kernel-panics on the eeepc 901. All Versions from 3.0.0-12 produced a panic here.

Maybe 3 Days are not enough time for testing here but with the 3.0.0-12 kernels there is more then one panic a day (20hours uptime) and with the other kernels not

[Yann Benigot (yann-benigot)]

I just experienced another panic. The panic message changes each time so it may be the same problem after all. I get about one panic per hour and they seem more frequent when the system is idle : I leave the room for a few minutes and when I come back I see the black screen... I also had kernel panics with arch linux, but only on shutdown. (the last one corrupted the root partition, so I switched back to ubuntu)

[Michael Basse (michael-alpha-unix)]

i also think that my panic happenes more often in idle.

It never happens when playing a video with vlc (and have vlc opened after the endig of the video) but very often in idle mode (terminator opened, libreoffice opened)

i always was connected to a wifi when the panic occures, never happened when not connected with wifi (but wifi enabled) (sometimes i saw the wifi-module in the panic-message (see my pictures))

i never get a panic on shutdown.

I hope this informations are usefull for someone

[Yann Benigot (yann-benigot)]

Happened three times in a row while ssh-ing to another computer. I then started the netbook from the SD Card with a live ubuntu system and no crash in four hours while doing a "while true; do sleep 1 && cat some-random-file; done" through ssh.
Knowing that, we may suppose that the SSD may have something to do with these crashes. I have the 16GB SSD version.
I also ran memtest86 ; it did not find any problem.

[Michael Basse (michael-alpha-unix)]

still no kernel-panic with 3.1rc9

[Joseph Salisbury (jsalisbury)]

@Yann

Would it be possible for you to try teh 3.1rc9 kernel as well?

[Andrea Esuli (andrea-esuli)]

I have found that when I run only on battery I have kernel panics in few minutes (2-10) from start. I have I unplugged the battery and now I run only on the AC adapter, and I haven't got any panic till now (about three hours). @Yann @Michael can you try if this hypothesis is right?

[Michael Basse (michael-alpha-unix)]

Hi Andrea,
i also have kernel-panics when the ac adapter is plugged it. I am not sure but i think i have more panics when using battery only but definitly i also have panics when ac-adapter is plugged in.

btw, still no kernel-panics with 3.1.0-0301rc9-generic. Just with all tested version from 3.0.0-12-x-generic

[Andrea Esuli (andrea-esuli)]

I forgor to mention that I have removed battery while the ac is plugged. Can you check this setup?

[Tomáš (tom-redhat-bugs-1)]

Hello,

I'm seeing the rt2500pci powersave-related panic reproducibly (the kernel panics a few seconds after enabling powersave). I've got a core via kdump on 2.6.40.6 (can provide the whole 2 GiB file if anyone's interested). I'm attaching the panic log, but the most important part is:

[ 853.871216] [<ffffffff810620a6>] msleep+0x1b/0x22
[ 853.871230] [<ffffffffa0314423>] rt2500pci_set_device_state+0x840/0x8a0 [rt2500pci]
[ 853.871241] [<ffffffffa0314ac7>] rt2500pci_config+0x297/0x2bd [rt2500pci]
[ 853.871257] [<ffffffffa02c319e>] rt2x00lib_config+0x144/0x22a [rt2x00lib]
[ 853.871269] [<ffffffffa02c1355>] rt2x00lib_rxdone+0x2a9/0x37b [rt2x00lib]
[ 853.871280] [<ffffffffa02d455e>] rt2x00pci_rxdone+0x76/0x8b [rt2x00pci]
[ 853.871290] [<ffffffffa03144b3>] rt2500pci_rxdone_tasklet+0x14/0x59 [rt2500pci]

Apparently, rt2500pci_set_device_state check whether the requested state change has succeeded in a loop and doesn't care that it could be called from rt2500pci_rxdone_tasklet (after receiving a beacon the tasklet orders to return to powersaving mode if there's no traffic queued):

rt2500pci.c:1212

        /*
         * Device is not guaranteed to be in the requested state yet.
         * We must wait until the register indicates that the
         * device has entered the correct state.
         */
        for (i = 0; i < REGISTER_BUSY_COUNT; i++) {
                rt2x00pci_register_read(rt2x00dev, PWRCSR1, &reg2);
                bbp_state = rt2x00_get_field32(reg2, PWRCSR1_BBP_CURR_STATE);
                rf_state = rt2x00_get_field32(reg2, PWRCSR1_RF_CURR_STATE);
                if (bbp_state == state && rf_state == state)
                        return 0;
                rt2x00pci_register_write(rt2x00dev, PWRCSR1, reg);
                msleep(10);
        }

So powersave works only for people with devices fast enough to switch state instantly (before the CPU gets to the inner if check). Everyone else steps on the msleep and explodes in softirq context.

"Quick fix": Either drop the msleep() and let it spin a bit or check whether in interrupt and completely skip the loop in that case.

Tip: Since rc.local is sooo pre-systemd era (and putting powersave off there is not reliable, too, since the wifi could come up and panic before rc.local is executed), the best is to do add a simple rule to /etc/udev/rules.d to have powersaving off from the very start:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="rt2500pci", KERNEL=="wlan*", RUN="/sbin/iw $name set power_save off"

[Tomáš (tom-redhat-bugs-1)]

Created attachment 528933
Panic log including subsequent fallout

[Michael Basse (michael-alpha-unix)]

the interesting part would be if you have kernel-panics when using ac-adapter and have the battery plugged in. I can not test your suggested setup before the weekend.

[John (john-redhat-bugs)]

Ivo, any thoughts on comment 19?

[James (james-redhat-bugs)]

I think I'm encountering this in F16 on a laptop, running off the Live USB with kernel 3.1.0-0.rc6.git0.3.fc16.i686. Connect to a wireless network, enter the password, and it panics. Disabling power management via iw seems to do the trick... I'll attach the machine's particulars (backtraces look similar) if anyone thinks they'll be of use.

[Michael Basse (michael-alpha-unix)]

Kernelpanic with 3.1.0-0301rc9-generic while watching a video on youtube on eeepc 901.

Picture from the panic is added

[Michael Basse (michael-alpha-unix)]

so i guess its useless to make any further tests if it is happening with 3.0.0-12 and 3.1-rc9. I guess we should discuss about a usefull debugging from the testers here to give usefull input.

I cant find anything in syslog or kern.log

are there some ways to run the kernel in a higher verbose-mode? so that there are maybe some usefull infos in the logs?

[Ian Corne (icorne)]

I've just had it happen on 3.0.0-9 (after finding 3.0.0-12 unusable)

Will upload picture asap

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[Michael Basse (michael-alpha-unix)]

There is no bugzilla.kernel.org anymore. Some kernel-hackers told me to use the "linux kernel mailinglist" so i will go that way. When finished i will post the reference here

[JosephWheatley (skinnyjim)]

Keeps getting me too on my ASUS Eee PC 1000h

Had it three times this morning already - worse than previously.

uname -a

Linux james-1000H 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:50:42 UTC 2011 i686 i686 i386 GNU/Linux

[JosephWheatley (skinnyjim)]

And again while I was trying to upload the previous comment,

This output mentions the kernel and some hardware.

I don't know if this is helpful but am posting it just to show the problem is real.

[Francois Blouin (francois-blouin)]

I don't know if this can help you because i'm on MSI wind and not on eee pc but:

Hi everyone,

I want to let everyone know that i think i found a tricky way to stop the kernel panic on Msi Wind. First, for me 11.10 was the first distro to work correctly on my wireless connection. No disconnection at all. Second the kernel panic only happen when i was on battery. So i add up these facts and i try this and so far (2 days test) no kernel panic at all. What i did: each time i want to pass to AC power to battery, i turn off the wireless connection. When i'm on battery i turn it on, wireless come back and no kernel panics.

Sorry if it's useless to you guys !

[Michael Basse (michael-alpha-unix)]

i looked at the pictures here. most kernelpanics are containing the wifi-modul.

it would be nice if everyone with the kernel-panic would have a look what wifi-chip/module is used

sudo apt-get install hwinfo && sudo hwinfo --netcard

Model: "RaLink RT2860"
  Vendor: pci 0x1814 "RaLink"
  Device: pci 0x0781 "RT2860"
  SubVendor: pci 0x1814 "RaLink"
  SubDevice: pci 0x2790
  Driver: "rt2800pci"
  Driver Modules: "rt2800pci"

in almost every panic i faced, the module "rt2800pci" was named. So maybe this will make the debug easier and we can change the bug-description to that chipset instead of eeepcs

[Andreas Büsching (crunchy)]

I have a eeePC 1001PXD with the following wifi card using the ath9k driver without any problems:

02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
 Subsystem: AzureWave Device 1089
 Flags: bus master, fast devsel, latency 0, IRQ 17
 Memory at fbff0000 (64-bit, non-prefetchable) [size=64K]
 Capabilities: [40] Power Management version 3
 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
 Capabilities: [60] Express Legacy Endpoint, MSI 00
 Capabilities: [100] Advanced Error Reporting
 Capabilities: [140] Virtual Channel
 Capabilities: [160] Device Serial Number 00-15-17-ff-ff-24-14-12
 Capabilities: [170] Power Budgeting <?>
 Kernel driver in use: ath9k
 Kernel modules: ath9k

Linux twoflower 3.0.0-13-generic #21-Ubuntu SMP Mon Oct 17 20:18:09 UTC 2011 i686 i686 i386 GNU/Linux

[Dan Keast (1iz)]

eeepc 1000ha:

  Model: "RaLink WLAN controller"
  Vendor: pci 0x1814 "RaLink"
  Device: pci 0x3090
  SubVendor: pci 0x1a3b
  SubDevice: pci 0x1087
  Driver: "rt2800pci"
  Driver Modules: "rt2800pci"

It's there

[Michael Basse (michael-alpha-unix)]

Another interessing part is

http://us.generation-nt.com/answer/3-0-rt2800usb-kernel-panic-vs-rt2780sta-good-2-6-38-help-204243021.html

they are talking about rt2800usb instead of rt2800pci. I dont know the differences but maybe that is an interesting infos for the kernel-hackers.

i will now write the mail for the lkml

[Michael Basse (michael-alpha-unix)]

also thanks to andreas. He mentioned that there are two types of kernel-panic

one about the rt2800pci, the other about the scsi-system. So maybe were a facing two different problems here.

I would suggest to first handle the rt2800-part

[Ivo (ivo-redhat-bugs)]

(In reply to comment #21)
> Ivo, any thoughts on comment 19?

Sounds like a very valid point, I guess it was introduced when we were moving the interrupts from process to IRQ context back and forth.. :(

[Stanislaw (stanislaw-redhat-bugs)]

Helmut works (or plan to work) on that:
http://marc.info/?l=linux-wireless&m=131702522217100&w=2

[nicolas kleinklaus (nknico)]

Same proble here with a eeepc 901

It's seems the problem occurs too with MSI Wind notebooks :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/873716

[nicolas kleinklaus (nknico)]

It's seems the problem occurs too with eeepc netbooks :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869502

Both systems have in common to use the rt2860 wifi module....

[Toby Anderson (toby-anderson)]

I've tested on three kernels and got panics on all of them:

3.0.0-11-generic
3.0.0-12-generic
3.1.0-030100rc10-generic

I only get panics when When not plugged in to power adapter, and only since upgrading to Ubuntu 11.10

I'm on an Eee PC 1001HA
I know I'm using rt2800pci for the wireless driver because I had to remove that from /etc/modprobe.d/blacklist.conf when I upgraded in order to get wireless working.

Is there a workaround until this gets fixed?

[Leann Ogasawara (leannogasawara)]

Hi Michael,

Would you be able to pinpoint an exact reproducer? That would really help for moving forward and testing possible fixes.

Just to summarize, you've mentioned the following:

3.0.0-11.18 => no panic
3.0.0-12.19 and 3.0.0-12.20 => both panic
upstream v3.1-rc9 => no panic

Could you test two more upstream kernels for me? There is a patch (rt2x00: Serialize TX operations on a queue.) that went into upstream stable v3.0.7 which we also pulled in to the Ubuntu 3.0.0-12.19 kernel. If this patch is the culprit, I'd expect you to experience the panic running v3.0.7 but not v3.0.6. Could you test and confirm if this happens?

v3.0.6 - http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.6-oneiric/

v3.0.7 - http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.7-oneiric/

For anyone else experiencing panics, please hold off on commenting until I hear back from Michael as he is the original bug reporter and I'm not convinced (based on the attached info) the panics anyone else here is seeing are the same as what Michael is seeing (ie it's probably best for you to open a separate bug report, we can always mark it as a duplicate later on if necessary). I want to avoid dog piling this bug with irrelevant information. Thanks.

[Michael Basse (michael-alpha-unix)]

Hi Leaan,
let me summarize my testing. Theese are all kernelpanics i get while using Ubuntu 11.10. Every panic has a picture.

3.0.0-11.18 = no panic after (3-4 days of testing)

3.0.0-12.19 = panic (3-5 days of testing)
https://launchpadlibrarian.net/82161301/IMG_20111006_222737.jpg (no rt2800 in the text)
https://launchpadlibrarian.net/82196440/IMG_20111007_103327.jpg (no rt2800 in the text)

3.0.0-12.20 = panic (10-10 days of testing)
https://launchpadlibrarian.net/82558459/IMG_20111011_211226.jpg (rt2800 in the text)
https://launchpadlibrarian.net/82620705/IMG_20111012_163536.jpg (no rt2800 in the text)

3.1.0-0301rc9-generic = panic (14 days of testing)
https://launchpadlibrarian.net/83329981/IMG_20111020_231054.jpg (no rt2800 in the text)

of course i can test 3.0.6 and 3.0.7

i will report my results on this bug. I would suggest running every version up to a panic or 5 days. If this period is to short or if you need further informations, please let me know.

[Leann Ogasawara (leannogasawara)]

Hi Michael, thanks for the summary. It does indeed look like you're experiencing multiple different panics (some network related, some scsi). I don't suppose you're able to capture the beginning portion of the panics (maybe in you dmesg log or does your system lock up hard after the panics)? The beginning portion has more helpful information.

Also definitely let me know the results of your 3.0.6 and 3.0.7 testing too. Thanks in advance.

[Michael Basse (michael-alpha-unix)]

Hi Leann,
first of all i got two other Kernelpanics on 3.1.0-0301rc9-generic. I will upload the pictures later, because the correct cable is missing at the moment. Both are not showing "rt2800pci". Both happened in a short time after connected the netbook to a monitor.

I dont have a chance to see dmesg or some logs after the panic, because the system is not listening to ctrl +alt +f1 anymoe. Maybe the sys-req-keys are still working, i will try it on the next one. Maybe there is a way to force the kernel trying to write the panic-message to a log? atm its only on tty1 and of course lost after a reboot.

I have now installed 3.0.6 and will test it up to five days (or the first panic). After that i will test 3.0.7

[Jorge Juan (jjchico)]

Hi!

kernel 3.0.8-03008 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.8-oneiric/ also gives a panic after about half an hour.

Currently testing 3.1.0-030100.

With both kernels I get an "Ooops" at boot due to VirtualBox driver. I am testing these disabling the dkms VBox drivers.

[Daniel Arndt (danielarndt)]

Hi all,

Chiming in to say I also get these kernel panics on my LG X120-N (also uses the same network card):

  Model: "RaLink WLAN controller"
  Vendor: pci 0x1814 "RaLink"
  Device: pci 0x3090
  SubVendor: pci 0x1814 "RaLink"
  SubDevice: pci 0x3090
  Driver: "rt2800pci"
  Driver Modules: "rt2800pci"

Don't have a whole lot of time to do any testing right now as I'm super busy, but maybe that information is somewhat useful. I can provide any info that is quick for me to grab, but I'm in the middle of writing a thesis so I don't want to be messing around with my machine too much ;)

[Daniel Arndt (danielarndt)]

Just panic'ed so I thought I'd attach a picture as well incase it is useful.

[Arie Baars (abaars)]

Found some interesting relation between this issue and the upgrade Natty to Oneric. The panic only occurs on my Asus EeePC 1000H when Evolution is running. When a fresh install is used the Evolution product is replaced by Thunderbird, which is not installed / has been removed. No panic on the same system (another partition) with Natty, just Oneric 3.0.0.12-#20 (and previous).
Any points in this ?

[Michael Basse (michael-alpha-unix)]

@Leann
Still no panic on 3.0.6 but please rember, it took 2 weeks to get the first panic on 3.1rc9, so i dont know if the time i already spent with 3.0.6 is enough for a good result

@Arie
michael@eeebuntu:~$ dpkg -l \*evolution\*
un evolution <keine> (keine Beschreibung vorhanden)
un evolution-common <keine> (keine Beschreibung vorhanden)
un evolution-data-server <keine> (keine Beschreibung vorhanden)
un evolution-data-server-co <keine> (keine Beschreibung vorhanden)
un evolution-data-server-db <keine> (keine Beschreibung vorhanden)
un evolution-data-server1.2 <keine> (keine Beschreibung vorhanden)
un evolution-dbg <keine> (keine Beschreibung vorhanden)
un evolution-exchange <keine> (keine Beschreibung vorhanden)
un evolution-exchange-dbg <keine> (keine Beschreibung vorhanden)
un evolution-indicator <keine> (keine Beschreibung vorhanden)
un evolution-plugins <keine> (keine Beschreibung vorhanden)
un evolution-plugins-experi <keine> (keine Beschreibung vorhanden)
un evolution-webcal <keine> (keine Beschreibung vorhanden)
un libevolution <keine> (keine Beschreibung vorhanden)
un libreoffice-evolution <keine> (keine Beschreibung vorhanden)

But getting Panics on most of the kernels.

[Gertjan (gertjan-redhat-bugs)]

Created attachment 531046
Proposed patch

Please check if the attached patch fixes the issue for you.

[Famous Man (duc900ss)]

I'm a non technical Ubuntu user.
 After installing 11.10 I did get get kernel panic on an ASUS EPC900ax .
The RT2800 wireless driver was consistently listed in the panic text.
Panics only occured when running on battery - ok on power.
 I was previously using 11.04 without an issue.

As a workaround I have installed the RT3090 drivers via a deb found at the bottom of this link - www.halibutdepot.org/how_to_build_rt3090_for_ubuntu_lucid/

I did previously try to download and install Rt3090 via the Ralink web site but ran into Error conditions as I've seen other people experience trying the same thing ,and being non technical I thought the deb could work for me.

I dont know if it was required but I also blacklisted rt2800pci, rt2800ucb,rt2x00lib,rt2x00pci,rt2x00usb in /etc/modprobe.d/blaclist.conf as I've seen in other problem reporting

Anyway using the deb and blacklisting rt2800pci etc has worked for me.

Using the workaround a nm-tool displays the wireless driver to be now rt2860i instead of rt2800 as was the case pre deb install

[Arie Baars (abaars)]

@famous man:
when blacklisting the rtl2800* my eeepc doen not have wireless functionality anymore, does not help for me

@others:
found also a relation between when running on battery, no panic occurs when on AC power, only when disconnection from AC power to battery, running Evolution (with 5 min updates) and leaving the system untouched for a while. SImilar panic occur within the hour or so. Hope this helps...

[Dirk (dirk-redhat-bugs)]

(In reply to comment #25)
> Created attachment 531046 [details]
> Proposed patch
>
> Please check if the attached patch fixes the issue for you.

How would I do that?

[Stanislaw (stanislaw-redhat-bugs)]

I'll prepare kernel build with the patch.

[Daniel Arndt (danielarndt)]

I still get the panic on AC power and do not use evolution (though I suppose it is installed by default, and may be running via hooks into gnome such as the calendar). Currently using the most up-to-date versions of everything in the stable repo.

[Stanislaw (stanislaw-redhat-bugs)]

Here is kernel build with patch from comment 25, please test when it finish to compile:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3478051

[Hans-Peter Schadler (hps-abyle)]

I can also confirm this bug. It happens with or without wlan active, on AC and on battery for me. I haven't found out, what triggers this kernel panic. The only thing i noticed, is that it seems to happen, if I do not use the Netbook and it just idles in X, but also not sure with this, it just happens to randomly to say something definite.

[Michael Basse (michael-alpha-unix)]

Just a notice because it seems there are more panics when using the battery of while the system was on idle for some time.

The wifichip from the eeepc 901

Model: "RaLink RT2860"
  Vendor: pci 0x1814 "RaLink"
  Device: pci 0x0781 "RT2860"
  SubVendor: pci 0x1814 "RaLink"
  SubDevice: pci 0x2790
  Driver: "rt2800pci"
  Driver Modules: "rt2800pci"

has some functions to reduce the power of the wifi-card. You can easily reproduce this "feature" when pluging off the ac-adapter. wifi speed is going here from 54mbit/s to a lower value. Directly after pluging in the ac adapter again its 54mbit/s.

This power-saving-feature can be a reason for more panics on battery or idle.

Most of my panics are happening after 5-10minutes when i am not using the netbook and when i am looking the reports from the others, it seems to be the same.

Maybe this make the debugging some kind of easier.

btw, still no panic on 3.0.6

[Famous Man (duc900ss)]

@abaars

Yes I found also that blacklisting rt2800 etc without installing the rt2860 drivers (as I did via the deb in my previous post) leaves you with no wireless function.
In 11.04 my Rt3090 wireless on the asus ePC900ax was using rt2860 driver. This doesn't seem to be available in 11.10 by default.

[Ian (ian-redhat-bugs)]

Thanks for that, ran out of space when trying to do my own kernel build (9GB not enough!)

kernel-2.6.40.6-0.fc15.x86_64
(Current stable I think) has this crash for me when not using set power_save off.

kernel-2.6.40.8-3.bz731672.fc15.x86_64
Hasn't crashed yet at ~ 1/2hour uptime.

[Tomáš (tom-redhat-bugs-1)]

(In reply to comment #25)
> Created attachment 531046 [details]
> Proposed patch
>
> Please check if the attached patch fixes the issue for you.

Indeed it does, thanks.
kernel-2.6.40.8-2.fc15.x86_64 - crashes within a few seconds after enabling powersave

kernel-2.6.40.8-2.rhbz731672.fc15.x86_64 - can't reproduce the crash, power management works as expected now (judging from the "STA will sleep" flag being set in transmitted frames)

[watkin5 (robert-watkin5)]

Me too using an Eee PC 1000.

[Michael Basse (michael-alpha-unix)]

@Leann

Kernelpanic on 3.0.6

Usage: browsing through a NFS-Share on the terminal. Panic happend when pressing "cd TAB TAB".

Exact the same i was doing some weeks ago. While pressing TAB TAB for auto-completion, i got a kernel-panic

[Michael Basse (michael-alpha-unix)]

This is the last output in the dmesg before the panic ( i noticed some warning at boot, that the acpi-daemon cant find a file)

Nov 3 03:30:33 eeebuntu kernel: [ 59.448278] init: Failed to spawn acpid main process: unable to execute: No such file or directory <- this is coming on every boot before switching to lxdm

here is the last dmesg before the panic:

[ 39.317078] init: Failed to spawn acpid main process: unable to execute: No such file or directory
[ 39.596465] init: failsafe main process (991) killed by TERM signal
[ 39.623674] init: lightdm main process (1110) killed by TERM signal
[ 39.781242] init: apport pre-start process (1098) terminated with status 1
[ 39.824337] init: apport post-stop process (1147) terminated with status 1
[ 40.087192] Bluetooth: Core ver 2.16
[ 40.087310] NET: Registered protocol family 31
[ 40.087317] Bluetooth: HCI device and connection manager initialized
[ 40.087326] Bluetooth: HCI socket layer initialized
[ 40.087333] Bluetooth: L2CAP socket layer initialized
[ 40.089063] Bluetooth: SCO socket layer initialized
[ 40.115625] Bluetooth: RFCOMM TTY layer initialized
[ 40.115644] Bluetooth: RFCOMM socket layer initialized
[ 40.115652] Bluetooth: RFCOMM ver 1.11
[ 40.134473] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 40.134483] Bluetooth: BNEP filters: protocol multicast
[ 44.553059] init: Failed to spawn setvtrgb main process: unable to execute: No such file or directory

Last output of syslog (dont know why it is trying to remount my drives)

Nov 3 03:19:54 eeebuntu kernel: [30870.173746] keyboard: can't emulate rawmode for keycode 240
Nov 3 03:19:54 eeebuntu kernel: [30870.173786] keyboard: can't emulate rawmode for keycode 240
Nov 3 03:19:57 eeebuntu kernel: [30873.167050] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro,commit=600
Nov 3 03:19:58 eeebuntu kernel: [30873.369896] keyboard: can't emulate rawmode for keycode 240
Nov 3 03:19:58 eeebuntu kernel: [30873.369949] keyboard: can't emulate rawmode for keycode 240
Nov 3 03:19:58 eeebuntu kernel: [30874.154279] EXT4-fs (sda1): re-mounted. Opts: commit=600
Nov 3 03:19:59 eeebuntu kernel: [30874.499854] EXT4-fs (sdc1): re-mounted. Opts: errors=remount-ro,commit=600
Nov 3 03:20:00 eeebuntu kernel: [30875.565639] keyboard: can't emulate rawmode for keycode 240
Nov 3 03:20:00 eeebuntu kernel: [30875.565701] keyboard: can't emulate rawmode for keycode 240
Nov 3 03:20:00 eeebuntu anacron[4129]: Anacron 2.3 started on 2011-11-03
Nov 3 03:20:00 eeebuntu anacron[4129]: Will run job `cron.daily' in 5 min.
Nov 3 03:20:00 eeebuntu anacron[4129]: Jobs will be executed sequentially
Nov 3 03:20:05 eeebuntu kernel: [30880.830725] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro,commit=0
Nov 3 03:20:06 eeebuntu kernel: [30881.591174] keyboard: can't emulate rawmode for keycode 240
Nov 3 03:20:06 eeebuntu kernel: [30881.591229] keyboard: can't emulate rawmode for keycode 240
Nov 3 03:20:06 eeebuntu kernel: [30882.180564] EXT4-fs (sda1): re-mounted. Opts: commit=0
Nov 3 03:20:06 eeebuntu kernel: [30882.197175] EXT4-fs (sdc1): re-mounted. Opts: errors=remount-ro,commit=0
Nov 3 03:20:07 eeebuntu kernel: [308...

[Yuioup (mghaoui)]

Anybody going to fix this? It seems to be getting worse.

[Don Thompson (vaiodon)]

Just to add my scenario: Asus eee PC 901 (2 of them). panics regularly. Stock 11.10 install up-to-date with System Updates.

Is there any investigation I can perform, logs to capture, etc, that might aid a resolution?

I've also got two Acer Revos with amd64 kernel, 11.10 stock with updates & they're solid, no problems.

[Think-Free (think-free)]

For me it realy seems to come from wifi driver.
I had about 2-3 crash a day and since I've desactivated the driver, no more crash (4 days uptime)

(EEEPC with rt2800)

[Michael Basse (michael-alpha-unix)]

I have opened a bugreport upstream

http://article.gmane.org/gmane.linux.kernel/1211290

[Michael Basse (michael-alpha-unix)]

Until now, no answer from the kernel-hackers. Maybe i just got the wrong persions in CC.

 I will also start a discussion with the rt2800pci-maintainers http://rt2x00.serialmonkey.com/phpBB/ and link to this bug-report and the LKML-Thread

[Colin Watkins (colinwatkins)]

I'm an Ubuntu ignoramus!
However, I've managed to replace the rt2800 driver with an rt2860 version from http://www.ralinktech.com/support.php?s=2.
I haven't had a kernal panic since, after three days of solid use. With the rt2800 driver I was guaranteed to get one within an hour and often it was after 5 / 10 minutes!

[Michael Basse (michael-alpha-unix)]

kernel-hackers on irc mentioned netconsole to provide better debug-informations

http://www.mjmwired.net/kernel/Documentation/networking/netconsole.txt

I will do some research on it and will try to use it.

[Michael Basse (michael-alpha-unix)]

also see https://wiki.ubuntu.com/Kernel/Netconsole

[Michael Basse (michael-alpha-unix)]

another point was to change the fontsize in tty to get more usefull infos. Think that is way more easy then the netconsole-thing

http://linuxconfig.org/change-tty-font-size-with-grub-2-boot-console-resolution

[Michael Basse (michael-alpha-unix)]

after some discussion with some kernel-hackers:

the provided infos /screenshots for the panics are to bad. They dont contain enough informations to do a real debugging. They suggested to use netconsole but for me its not possible to use that kind of setup.

So i will try to provide better screenshots.

The first thing i did was to change the tty-resolution. Maybe someone knows how to to something like "less" for kernel-panics? or to slowdown the output of the panic so i can hit "pause" and provide better screenshots

[Don Thompson (vaiodon)]

Can anyone advise how I determine the firmware version for the RT2860 card (/lib/firmware/rt2860.bin). The file doesn't match md5 chksum to the most recent rev available at ralinktech.com, i.e. v26.

rt2860.bin oneiric md5=75a1da3caa0b1c95e81dfba207f834c6
rt2860.bin ralink-v26=66332d7636ee78db31b056aa0e44b097

[Michael Basse (michael-alpha-unix)]

http://pastie.org/2822013 ( thanks to Maxim Levitsky)

This patch will save dmesg and the panic-infos into ram and at reboot (ram doesnt get cleaned) the messages can be found in

/sys/kernel/debug/printk/crash_dmesg

So it should be possible to get the complete panic as far as i understood the patch

[Michael Basse (michael-alpha-unix)]

@Don

http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2011-April/003556.html

Says that it is Version 34.00

I was doing some searching for the md5sums and there are often bug-reports with that kind of firmware

[Michael Basse (michael-alpha-unix)]

Here is a complete netconsole-output (provided from Hauke Jung)

https://launchpadlibrarian.net/84013101/netconsole.log.out

[Michael Basse (michael-alpha-unix)]

the last panic from #82 happened on a high ram-load. I opened many tabs on Firefox and looking at "top" the system was very near to start swapping. Then the panic was happening.

- System was on ACD-Adapter
- All my drives (sda, sdb and sdc) are SSDs
- The option "spin down the harddisc" in the energy-setting is disabled (dialog from lubuntu-desktop).
- wifi was enabled and

[Ivosh (ivo-anubis)]

still happens with 3.1.0-030100-generic on asus eeepc 1000H

[Ivosh (ivo-anubis)]

It seems that panic occures more often when running on battery then on adapter, but happens when on adapter rarely too. So maybe it has something to do with high ram-load, because usually my ram goes high only when I'm running on battery.

[Michael Basse (michael-alpha-unix)]

as it seems i can repdroduce it now

- using no ac-adapter
- wifi enabled
- connecting to an external monitor
- put the video on eeepc and external monitor
- close the monitor from eeepc (without this its not happening)
- wait 10 minutes without doing anything

happened 5 times today, each time i was doing the same as you see above.

Kernel used 3.1.0-0301rc9-generic

panic is attached as jpg

[Michael Basse (michael-alpha-unix)]

as addition to comment #86. My screensaver/powersaving is set to 10 minutes

[Michael Basse (michael-alpha-unix)]

just as aditinal info (and make it more complex) the eeepcs and ms wind not only using the same wifi-modul (rt2800pci) but also the same vga modul "i915"

[Michael Basse (michael-alpha-unix)]

and of course other things, because they are all based on "intel atom". Like SATA-Controller and so on. But because not all eeepcs are affected maybe it is worth to find out the differences between working and non-working eeepcs?

Feedback would be great

[Troels (tr0e1s)]

Just wanted to report the kernel panic too. My system is Eee Pc 1000HE. Hoping for a fix soon. Will be glad to assist with testing.

[Colin Watkins (colinwatkins)]

I've still not had a single kernal panic since I installed the rt2860 drive as mentioned in #73 above. This after extensive use on a daily basis.
Could someone else try the same to confirm?
Colin

[JosephWheatley (skinnyjim)]

@Colin Watkins

Is this the site to download the rt2860 driver? http://www.ralinktech.com/en/04_support/support.php?sn=501

Did you install it using the methods described here? http://ubuntuforums.org/showpost.php?p=9255730&postcount=1

I'm still having panics on my 1000h. Not changed anything except the Ubuntu updates.

Interestingly Fedora says it is not compatible with rt2860 on 901/1000h Eee PCs giving "non-free drivers or serious hardware support problems" https://fedoraproject.org/wiki/Eee_PC#Hardware_support

[John (john-redhat-bugs)]

So, when will we see this patch upstream? :-)

[Gertjan (gertjan-redhat-bugs)]

As soon as I have returned from my travels I will submit the patch upstream (sorry travels came in between that) ;-)

[Gareth (gareth-redhat-bugs-1)]

I'm currently updating to F16, but I'll give the patch a test when I get a chance (if it isn't already included by then!).

[Michael Basse (michael-alpha-unix)]

i have opened a bug-report for the maintainers of rt2800pci

http://rt2x00.serialmonkey.com/phpBB/viewtopic.php?f=5&t=6192

[Michael Basse (michael-alpha-unix)]

a short summary.

The Bug is only happening on ubuntu-systems when rt2800pci is used. The only difference between ubuntu and other distributions is the version of "rt2860.bin" from the package "linux-firmware".

Also, no panics when using another version (and another firmware-file), so i guess the issues are addressed to that firmware-file ubuntu is using.

So the fix would be put a newer/older firmware-file inside "linux-firmware".

Maybe someone can confirm my guess about it.

[Ian (ian-redhat-bugs)]

I'm not sure this will require a new bug, but while I no longer see this crash I do get disconnected or very slow connection to the AP. NetworkManager keeps asking me for a password, using the iw $name set power_save off seems to prevent it. Could be a separate bug which has been uncovered by fixing the power management?

[Tomáš (tom-redhat-bugs-1)]

(In reply to comment #34)
> I'm not sure this will require a new bug, but while I no longer see this crash
> I do get disconnected or very slow connection to the AP. NetworkManager keeps
> asking me for a password, using the iw $name set power_save off seems to
> prevent it. Could be a separate bug which has been uncovered by fixing the
> power management?

Yes, there probably is some powersave-related bug in there somewhere (I've hit it twice over the last two weeks with PS enabled) - basically the device locks up and requires resetting via modprobe -r rt2500pci; modprobe rt2500pci.

Anyways, that's nowhere near as severe as this panic so I'll recommend opening a separate bug for that (otherwise I'll do that as soon as the patch for this one is applied to Fedora kernel or upstream so that the bug dependencies don't get too confusing).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Brian Ealdwine (eode)]

@Michael Basse
Do you have a d/l link for the (potentially) working version of the firmware so this can be tested?

[Michael Basse (michael-alpha-unix)]

Hi Brian,
the source is http://www.ralinktech.com/en/04_support/license.php?sn=5029#

rt2860.bin - md5 - 75a1da3caa0b1c95e81dfba207f834c6 <- this is the corrupt one from ubuntu

rt2860.bin - md5 - 66332d7636ee78db31b056aa0e44b097 <- this is the one from the website above and seems to be working

if you dont want to register on http://www.ralinktech.com/en/04_support/license.php?sn=5029# you can also find it here

http://alpha-unix.de/~iceroot/rt2860.bin

it has to be placed in /lib/firmware/rt2860.bin

so this command should fix the panics (please test it and give feedback)

sudo mv /lib/firmware/rt2860.bin /lib/firmware/rt2860.bin.orig && sudo wget http://alpha-unix.de/~iceroot/rt2860.bin -O /lib/firmware/rt2860.bin

[Michael Basse (michael-alpha-unix)]

after the command the new firmware has to be used, i dont know how to tell the system to use the new firmware, so i decided to do a reboot

[Ian (ian-redhat-bugs)]

Thanks, just wanted to make sure it wasn't likely to be directly related. https://bugzilla.redhat.com/show_bug.cgi?id=753648

[Brian Ealdwine (eode)]

Changing the firmware didn't fix the issue for me -- using updated firmware with md5 of 66332d7636ee78db31b056aa0e44b097.

[Michael Basse (michael-alpha-unix)]

I am sad to hear that. I was testing the steps from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869502/comments/86 and cant reproduce the panics.

So i guess we have to start again with testing and debugging.

Unfortunately i am out of ideas

[Arie Baars (abaars)]

@Michael Basse; I'm quite optimistic about your (re)solution with the rt2860.bin modifier (#97). Used for about 15 hours now and NO panic whatsoever. Also some strange sideeffects on my LAN are vanished. Will keep testing for now...
(eeepc 1000H with 3.0.0-12-generic #20-Ubuntu SMP i686 i386 GNU/Linux)

[Michael Basse (michael-alpha-unix)]

@Arie
sounds good, I am also not facing panics anymore.

@Brian
do you have some infos about your panic after changing the firmware? maybe its another issue

[Michael Basse (michael-alpha-unix)]

Kernel-Panic after changing the firmware. I am out of this. If someone has another idea please let me know, until then i am out of this and will use 2.6.38

[Hauke Jung (hauke-9)]

I installed the rt2860 driver directly from ralink, as mentioned above.
For several days I didnt had a single kernel panic.
So, at least, this is a workaround.

[Ian Corne (icorne)]

I'm running 12.04 and haven't had a kernel panic.

On Tue, Nov 15, 2011 at 12:47 PM, Hauke Jung <email address hidden> wrote:

> I installed the rt2860 driver directly from ralink, as mentioned above.
> For several days I didnt had a single kernel panic.
> So, at least, this is a workaround.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/869502
>
> Title:
> Kernel-Panic with 3.0.0.12-generic on asus eee pcs and msi wind (both
> using rt2800 wifi chipset)
>
> Status in “linux” package in Ubuntu:
> Confirmed
> Status in “linux-firmware” package in Ubuntu:
> Invalid
>
> Bug description:
> The latest Kernel
>
> michael@eeebuntu:/var/log$ uname -a
> Linux eeebuntu 3.0.0-12-generic #19-Ubuntu SMP Fri Sep 23 21:18:13 UTC
> 2011 i686 i686 i386 GNU/Linux
>
> has about 10 Kernelpanics here. All happened on a eeepc 901 from Asus.
>
> Because i have not found anything in /var/log/* i only have a picture
> from that panic.
>
> Panics are happening with and without power-adapter plugged in
>
> Please let me know if you need more infos
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.10
> Package: linux-image-3.0.0-12-generic 3.0.0-12.19
> ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
> Uname: Linux 3.0.0-12-generic i686
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
> AplayDevices:
> **** List of PLAYBACK Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> ApportVersion: 1.23-0ubuntu2
> Architecture: i386
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: michael 1430 F.... pulseaudio
> CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 44'
> Mixer name : 'Realtek ALC269'
> Components : 'HDA:10ec0269,1043831a,00100004'
> Controls : 12
> Simple ctrls : 7
> Date: Thu Oct 6 22:45:44 2011
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=UUID=3147250b-39a6-47ab-92dd-3ae71a43c9a8
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
> MachineType: ASUSTeK Computer INC. 901
> ProcEnviron:
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic
> root=UUID=797c12e0-f5e5-4b81-9464-0d8de0ce0a16 ro acpi_osi=Linux
> acpi_backlight=vendor quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.0.0-12-generic N/A
> linux-backports-modules-3.0.0-12-generic N/A
> linux-firmware 1.60
> SourcePackage: linux
> UpgradeStatus: Upgraded to oneiric on 2011-09-16 (20 days ago)
> dmi.bios.date: 06/11/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 2103
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: 901
> dmi.board.vendor: ASUSTeK Computer INC.
>...

[Michael Basse (michael-alpha-unix)]

@Hauke
thank you for the reminder. Seems i did not see your comment before. I will test it and give you sme feedback

[Jorge Juan (jjchico)]

Kernel 3.1.0-030100 gave me a panic also. It worked fine several days but I got the panic in the end.

[Michael Basse (michael-alpha-unix)]

http://rt2x00.serialmonkey.com/phpBB/viewtopic.php?f=5&t=6192&p=34806#p34806

http://article.gmane.org/gmane.linux.kernel.wireless.general/80759

here is the patch to fix hopefully fix the issues

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "patch for fixing kernel-panics with rt2800pci" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[Andy Whitcroft (apw)]

The patch both attached and mentioned in comment #108 has not yet shown up in any official tree that I can find:

From: Stanislaw Gruszka <sgruszka@...>
Subject: [PATCH] rt2800pci: handle spurious interrupts
Newsgroups: gmane.linux.kernel.wireless.general
Date: 2011-11-16 10:09:17 GMT (1 day and 15 minutes ago)
Some devices may generate spurious interrupts, we have to handle them
otherwise interrupt line will be disabled with below message and driver
will not work:

[ 2052.114334] irq 17: nobody cared (try booting with the "irqpoll" option)
[ 2052.114339] Pid: 0, comm: swapper Tainted: P 2.6.35.6-48.fc14.x86_64 #1
[ 2052.114341] Call Trace:
[ 2052.114342] <IRQ> [<ffffffff810a6e2b>] __report_bad_irq.clone.1+0x3d/0x8b
[ 2052.114349] [<ffffffff810a6f93>] note_interrupt+0x11a/0x17f
[ 2052.114352] [<ffffffff810a7a73>] handle_fasteoi_irq+0xa8/0xce
[ 2052.114355] [<ffffffff8100c2ea>] handle_irq+0x88/0x90
[ 2052.114357] [<ffffffff8146f034>] do_IRQ+0x5c/0xb4
[ 2052.114360] [<ffffffff81469593>] ret_from_intr+0x0/0x11
[ 2052.114361] <EOI> [<ffffffff8102b7f9>] ? native_safe_halt+0xb/0xd
[ 2052.114366] [<ffffffff81010f03>] ? need_resched+0x23/0x2d
[ 2052.114367] [<ffffffff8101102a>] default_idle+0x34/0x4f
[ 2052.114370] [<ffffffff81008325>] cpu_idle+0xaa/0xcc
[ 2052.114373] [<ffffffff81461f2a>] start_secondary+0x24d/0x28e
[ 2052.114374] handlers:
[ 2052.114375] [<ffffffff81332944>] (usb_hcd_irq+0x0/0x7c)
[ 2052.114378] [<ffffffffa00697da>] (rt2800pci_interrupt+0x0/0x18d [rt2800pci])
[ 2052.114384] Disabling IRQ #17

Resolve:
https://bugzilla.redhat.com/show_bug.cgi?id=658451

Reported-and-tested-by: Amir Hedayaty <hedayaty@...>
Cc: stable@...
Signed-off-by: Stanislaw Gruszka <sgruszka@...>

[JosephWheatley (skinnyjim)]

Has this been solved?

I can't work out if there is a solution or not.

[Michael Basse (michael-alpha-unix)]

Chanelog from linux (3.0.0-13.22) oneiric-proposed; urgency=low

 [ Upstream Kernel Changes ]

  * Revert "rt2x00: Serialize TX operations on a queue."
    - LP: #868628
  * Revert "rt2x00: fix crash in rt2800usb_write_tx_desc"
    - LP: #868628
  * Revert "rt2x00: fix crash in rt2800usb_get_txwi"
    - LP: #868628
  * Revert "rt2x00: Move rt2800_txdone and rt2800_txdone_entry_check to
    rt2800usb."
    - LP: #868628

But because its not rt2800pci i dont think it will fix our issue. Because nothing is happening here, i will build a i386 Kernel from #108 to do some testing. After the build is finished i will provide the kernel and maybe someone else can also do some testing on it

[Kristian Benoit (kristian-benoit)]

Same problem here on a eeepc 1015, the device is RT3090. I downloaded the driver for 3090 from ralink web site and it works fine. I thought I should mention that since everyone seems to have the problem with rt2860.

Output of lspci -k :
Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe
Subsystem: AzureWave Device 1087
Kernel driver in use: rt2860
Kernel modules: rt3090sta, rt2800pci

Output of lsmod | grep ^rt.*
rt3090sta 857317 1

I guess the kernel driver in use is the firmware in use. Under /lib/firmware, there are firmwares for rt2860 and rt3090. Since they have the same md5, I guess it does not mather, but seems weird it's using rt2860.

[Rod Hull (iwantmyjelly)]

@Kristian: How did you get the RT3090 driver to compile correctly in Oneiric (which I assume you are using)? It doesn't build for me unless it's patched with the patches here:
http://www.infty.nl/wordpress/2011/09/patches-for-the-ralink-rt3090-linux-driver/

I am not seeing kernel panics with rt2800pci but am seeing extremely slow speeds instead (my chipset is RT3090).

The "fix" in the rt2x00 forum thread is to do with IRQ handling but was also supposed to fix the "slow speed issue" reported with the rt2800pci driver from a Redhat bugzilla report. It doesn't work for me (when using the latest compat-wireless) on my Lenovo S205 running Oneiric - I still have very slow speeds (but at least no kernel panics).

[Rod Hull (iwantmyjelly)]

By the way, I forgot to say that the RT3090 driver (when patched as I mentioned) does build, installs but will not work correctly to service the WLAN card...any help appreciated!

[Michael Basse (michael-alpha-unix)]

Rod, thank you for the feedback. At the moment i am building a kernel with the patch inside. After that i will provide the debs here for some testing.

But its taking very long to build the kernel on eeepc (8 hours until now) hopefully this is getting finished soon.

[Michael Basse (michael-alpha-unix)]

Because of "the answer to life, the universe and everything" here is

linux (3.0.0-13.42iceroot1) oneiric; urgency=low

  * Hopefully fixing issues with rt2800pci on asus eeepcs (LP: #869502)

 -- Michael Basse <email address hidden> Mon, 21 Nov 2011 22:00:47 +0100

This Kernel is based on the current ubuntu-stable-kernel but with the patch from #108

You can find the i386-build here

http://alpha-unix.de/~iceroot/ubuntu/

at least you need this two debfiles

http://alpha-unix.de/~iceroot/ubuntu/linux-image-3.0.0-13-iceroot_3.0.0-13.42iceroot1_i386.deb
http://alpha-unix.de/~iceroot/ubuntu/linux-headers-3.0.0-13-iceroot_3.0.0-13.42iceroot1_i386.deb

If you downloaded the debs, install them with "sudo dpkg -i linux-image-3.0.0-13-iceroot_3.0.0-13.42iceroot1_i386.deb linux-headers-3.0.0-13-iceroot_3.0.0-13.42iceroot1_i386.deb "

I would be happy about feedback if this new kernel is fixing the issues for you.

Running this setup now for 5 minutes and no kernel-panic :)

[Rod Hull (iwantmyjelly)]

So, I have the x64 arch version of Oneiric, so cannot use this patched kernel as is.

I presume I would get a similar effect by simply installing the latest kernel 3.0.0.13 (that is now in the main Oneiric repo) and using the latest compat-wireless on top (which already has the patched rt2800pci.c) or have I misunderstood what your patched kernel is?

[Michael Basse (michael-alpha-unix)]

Hi Rod,
the latest Kernel-Update from Ubuntu contains

[ Upstream Kernel Changes ]

  * Revert "rt2x00: Serialize TX operations on a queue."
    - LP: #868628
  * Revert "rt2x00: fix crash in rt2800usb_write_tx_desc"
    - LP: #868628
  * Revert "rt2x00: fix crash in rt2800usb_get_txwi"
    - LP: #868628
  * Revert "rt2x00: Move rt2800_txdone and rt2800_txdone_entry_check to
    rt2800usb."
    - LP: #868628

These are other issues (not related to rt2800pci)

The kernel i was building contains the rt2800pci patch (see http://thread.gmane.org/gmane.linux.kernel.wireless.general/80759). Until now that patch is NOT upstream or in any other distro-kernels) so i decied to build a kernel with that patch by using the latest ubuntu-kernel. That patch *should* fix slow connections AND kernel-panics and is also in the newest drivers you mentioned. But because ubuntu is using the kernel-drivers, we are facing that problems until the kernel is patched or you are using the new drivers.

Unfortunately i dont have amd64 hardware here. So i cant built the kernel for amd64, just i386.

If someone has a hint how to build amd64 kernel on an i386-cpu without amd64 instructions, i will build it also and provide it here

[Rod Hull (iwantmyjelly)]

Perfect explanation - many thanks for being so precise!

So, I can update my kernel to the latest stable (which I've just been alerted to by Update Manager along with 50 others!), PLUS install the latest compat-wireless and I should be roughly in the same position as if I were using i386 arch and used your patched kernel/headers?

Thanks for spending the time on helping to get this fixed.

[Michael Basse (michael-alpha-unix)]

Rod, yes that should also fix the kernel-panics

[Rod Hull (iwantmyjelly)]

Not sure if you've seen but the owner of the wireless tree in git has reverted that patch to rt2800pci since he obviously didn't agree with it (he calls it a "misguided attempt to improve performance"!)
http://git.kernel.org/?p=linux/kernel/git/linville/wireless.git;a=commit;h=82e5fc2a34fa9ffea38f00c4066b7e600a0ca5e6

Luckily due to the nature of version control, we can still get the patches should we want to...

To be honest I hadn't got round to trying it with the new kernel yet - the new kernel is certainly not enough to improve the speed. I'm currently trying to improve speeds by testing the latest Ralink firmware (v26) in place of the version shipped in the linux-firmware package which appears to have a different md5sum.

[Rod Hull (iwantmyjelly)]

Well - the firmware makes not a blind bit of difference to speeds (still no kernel panics, however).

I'm now going to test the latest compat-wireless that doesn't have the patch reverted installed alongside the newer kernel (3.0.0.13)

[Michael Basse (michael-alpha-unix)]

Here is a comment from LKML
I will do some testing after work on that and if needed built a new kernel with that patch inside

On Tue, Nov 22, 2011 at 09:33:34PM +0100, Michael Basse wrote:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869502
> http://thread.gmane.org/gmane.linux.kernel/1211290
> http://rt2x00.serialmonkey.com/phpBB/viewtopic.php?f=5&t=6192
>
> I have build the newest ubuntu-kernel with your patch
>
> http://alpha-unix.de/~iceroot/ubuntu/
>
> Hopefully your patch is fixing the issues we are facing.
> Just wanted to say thank you to your work and i will give you feedback
> about your patch.

I do not think my patch fix this problem, but perhaps Gertjan's
patch do this:

http://marc.info/?l=linux-wireless&m=132112188308082&w=2

Note, if you are hitting the same issue, what is fixed by this patch,
it's enough to do "iwconfig wlan0 power off" to workaround the problem.
So you can avoid applying the patch, and just use above command and
check if issue is still reproducible.

Stanislaw

[Michael Basse (michael-alpha-unix)]

so as a workaround this should fix the kernel-panics (thank you to Stanislaw from LKML)

"sudo iwconfig wlan0 power off"

with that you are disabling the powermanagement of wifi-card

After that "iwconfig" should show that the powermanagement is disabled.

michael@eeebuntu:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bgn ESSID:off/any
          Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:on

You can reenable power-management with "sudo iwconfig wlan0 power on"

We dont need to built a new kernel to test that, so everyone should be able to do some testings.

To fix the issue with the power-management a patch already exist and should be built into the (ubuntu)kernel when the workaround (mentioned above) will work

[Kristian Benoit (kristian-benoit)]

@Rod: Here's what I modified to the sources to make RT3090sta build, I moslty looked at what people where doing to build RT2860 :

 diff -uNr 20101216_RT3090_LinuxSTA_V2.4.0.4_WiFiBTCombo_DPO/common/cmm_wpa.c 20101216_RT3090_LinuxSTA_V2.4.0.4_WiFiBTCombo_DPO.mine//common/cmm_wpa.c
--- 20101216_RT3090_LinuxSTA_V2.4.0.4_WiFiBTCombo_DPO/common/cmm_wpa.c 2010-12-15 19:32:06.000000000 -0500
+++ 20101216_RT3090_LinuxSTA_V2.4.0.4_WiFiBTCombo_DPO.mine//common/cmm_wpa.c 2011-11-17 14:17:46.333549539 -0500
@@ -2412,7 +2412,7 @@
  UCHAR PrimaryRsnie;
  BOOLEAN bMixCipher = FALSE; // indicate the pairwise and group cipher are different
  UCHAR p_offset;
- WPA_MIX_PAIR_CIPHER FlexibleCipher = MIX_CIPHER_NOTUSE; // it provide the more flexible cipher combination in WPA-WPA2 and TKIPAES mode
+ WPA_MIX_PAIR_CIPHER FlexibleCipher = WPA_TKIPAES_WPA2_TKIPAES; // it provide the more flexible cipher combination in WPA-WPA2 and TKIPAES mode

  rsnielen_cur_p = NULL;
  rsnielen_ex_cur_p = NULL;
diff -uNr 20101216_RT3090_LinuxSTA_V2.4.0.4_WiFiBTCombo_DPO/os/linux/config.mk 20101216_RT3090_LinuxSTA_V2.4.0.4_WiFiBTCombo_DPO.mine//os/linux/config.mk
--- 20101216_RT3090_LinuxSTA_V2.4.0.4_WiFiBTCombo_DPO/os/linux/config.mk 2010-12-08 21:49:06.000000000 -0500
+++ 20101216_RT3090_LinuxSTA_V2.4.0.4_WiFiBTCombo_DPO.mine//os/linux/config.mk 2011-11-17 14:14:14.468498948 -0500
@@ -108,7 +108,7 @@
 HAS_GREENAP_SUPPORT=n

 #Support MAC80211 LINUX-only function
-HAS_CFG80211_SUPPORT=y
+HAS_CFG80211_SUPPORT=n

 #Support RFKILL hardware block/unblock LINUX-only function
 HAS_RFKILL_HW_SUPPORT=y

[Rod Hull (iwantmyjelly)]

Many thanks Kristian. I'm hoping I now won't need to go down this route, but it's great to know it's possible.

I'm having very good results in Oneiric (finally) by using the stock Ubuntu 3.0.0.13 kernel combined with compat-wireless from 22/11/11 PLUS turning power-saving off on the WLAN interface.

No speed drops anymore, no kernel panics, no problems resuming - basically everything "just working".

[Mr Vahlin (lmvmusik)]

Same issue here on Asus 1001HA, RT3090 kernel 3.0.0.13
Power management was allready turned off on my computer, so that is not the problem.

[Dan Keast (1iz)]

Turning power management off on the wifi seems to have stopped the panics
on this eeepc 1000ha.

On 25 November 2011 17:22, Mr Vahlin <email address hidden> wrote:

> Same issue here on Asus 1001HA, RT3090 kernel 3.0.0.13
> Power management was allready turned off on my computer, so that is not
> the problem.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/869502
>
> Title:
> Kernel-Panic with 3.0.0.12-generic on asus eee pcs and msi wind (both
> using rt2800 wifi chipset)
>
> Status in The Linux Kernel:
> Unknown
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> The latest Kernel
>
> michael@eeebuntu:/var/log$ uname -a
> Linux eeebuntu 3.0.0-12-generic #19-Ubuntu SMP Fri Sep 23 21:18:13 UTC
> 2011 i686 i686 i386 GNU/Linux
>
> has about 10 Kernelpanics here. All happened on a eeepc 901 from Asus.
>
> Because i have not found anything in /var/log/* i only have a picture
> from that panic.
>
> Panics are happening with and without power-adapter plugged in
>
> Please let me know if you need more infos
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.10
> Package: linux-image-3.0.0-12-generic 3.0.0-12.19
> ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
> Uname: Linux 3.0.0-12-generic i686
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
> AplayDevices:
> **** List of PLAYBACK Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> ApportVersion: 1.23-0ubuntu2
> Architecture: i386
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: michael 1430 F.... pulseaudio
> CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 44'
> Mixer name : 'Realtek ALC269'
> Components : 'HDA:10ec0269,1043831a,00100004'
> Controls : 12
> Simple ctrls : 7
> Date: Thu Oct 6 22:45:44 2011
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=UUID=3147250b-39a6-47ab-92dd-3ae71a43c9a8
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
> MachineType: ASUSTeK Computer INC. 901
> ProcEnviron:
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic
> root=UUID=797c12e0-f5e5-4b81-9464-0d8de0ce0a16 ro acpi_osi=Linux
> acpi_backlight=vendor quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.0.0-12-generic N/A
> linux-backports-modules-3.0.0-12-generic N/A
> linux-firmware 1.60
> SourcePackage: linux
> UpgradeStatus: Upgraded to oneiric on 2011-09-16 (20 days ago)
> dmi.bios.date: 06/11/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 2103
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: 901
> dmi.board.vendor: ASUSTeK Computer IN...

[Matti Laakso (matti-laakso)]

I can also confirm that

sudo iwconfig wlan0 power off

stops the panics from occurring. This on a eee 901 (RT2860).

[Mr Vahlin (lmvmusik)]

OK, I got the panic right after login. Then restarted the computer and checked iwconfig; this time power management was on!
I switched it off and keep testing. Don't know how it could be off once and on the other time. Perhaps someone can explain this.
I'll get back with my results after more testing.

[Michael Basse (michael-alpha-unix)]

i can also confirm that disabling the power-feature fixed the kernel-panics.

The patch can be found here

[Michael Basse (michael-alpha-unix)]

http://marc.info/?l=linux-wireless&m=132112188308082&w=2

[Tomáš (tom-redhat-bugs-1)]

Confirming this is fixed on F15 by kernel-2.6.41.4-1.fc15.x86_64 (now in testing).
Fixed upstream by commit ed66ba472a742cd8df37d7072804b2111cdb1014 (starting with 3.1.3).

[bob (bob-redhat-bugs-1)]

*** Bug 728186 has been marked as a duplicate of this bug. ***

[Xan (dxpublica)]

I have this behaviour. But in my case the power adapter in on.

[Knut Wenzig (kwoid)]

No kernel panics if I remember to switch off power management on a Asus 1000H. (driver: rt2800pci)

[Xan (dxpublica)]

I have a kernel panic I attach I suspect it is from this bug.

[Xan (dxpublica)]

I have a kernel panic I attach I suspect it is from this bug.

[Arie Baars (abaars)]

Still the same behaviour with the original 3.0.0.13 #22 Ubuntu kernel. When the powersave is turned OFF no more panics noticed during several days. Sometimes I forget to (manually) disable the powersave and when my pc is left alone, the panic reoccurs. Therefore I made some changes to the sartup file rc.local (as attached), solved for now, awaiting the patch with Ubuntu originals, any progress there / expected version ? Thanks...

<code>
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
#
# Added to bypass RT2800 errors, bug #869502
# Kernel-Panic with 3.0.0.12-generic on asus eee pcs and msi wind (both using rt2800 wifi chipset)
sleep 10
iwconfig wlan0 power off
exit 0
</code>

[jatoo (wainwright-alex)]

Mr Vahlin, I managed to get some help with preventing power management turning on automatically here: http://askubuntu.com/questions/85214/how-can-i-prevent-iwconfig-power-management-from-being-turned-on/85223#85223

[Mr Vahlin (lmvmusik)]

Thanks jatoo, I will give it a try.
Obviously the power management is turned on when battery power is used on my machine.
No panics for several days now when turning it off.

[beni (benicchio)]

Hi there, just to confirm the bug and the workaround. I was also having several kernel panics on my eee 1000h + Ubuntu 11.10 (3.0.0-12 and also 3.0.0-13-generic) with RT2860 and the power management workaround worked for me also. I also report a great improvement on network speed after this workaround.

My first install on this machine was Ubuntu 9.10 and I've been upgrading the system since then.

[bob (bob-redhat-bugs-1)]

Confirming fixed in 2.6.41.4-1.fc15.i686.PAE also for bug 728186 (so it really was a duplicate even though symptoms were somewhat different).

[perezxolote (perezxolote)]

Same problem here. Kubuntu 11.10, Kernel 3.0.0-14. eee-pc 1000h; rt2860 with rt2800 driver.
I have observed, that with this kernel, panic ocurr only in under battery AFTER waking up from suspend-to-ram.

[Gareth (gareth-redhat-bugs-1)]

Confirming that this is fixed in F16 by the equivalent kernel update, but I'm also seeing the disconnecting behaviour described by Ian above.

[michael barany (michael-barany)]

looks like Mr. Basse found a patch in post #134. does someone know where/whether/when/how that makes it through the pipeline into something we can update/install?

[Michael Basse (michael-alpha-unix)]

we have a working patch

http://marc.info/?l=linux-wireless&m=132112188308082&w=2

so i added the kernel-team on cc.

Can you please have a look at it and give as a short info about the next steps?

[dominus_sapiens (dominussapiens)]

I'm also experiencing this problem with 3.0.0-14 on my Asus EEE PC 1001HA.

[Joseph Salisbury (jsalisbury)]

It looks like that patch was accepted in Linus' tree in commit:
ed66ba472a742cd8df37d7072804b2111cdb1014

This fix will eventually make it into Precise(12.04) when we rebase to the upstream kernel. Michael, do you know if this patch will be applied to the upstream stable release kernel?

[Joseph Salisbury (jsalisbury)]

It does appear this patch may be applied to the stable release 3.0 kernel:
https://lkml.org/lkml/2011/11/22/616

[Joseph Salisbury (jsalisbury)]

I am building an Oneiric test kernel with this patch applied. I will post a link to the test kernel shortly.

[Joseph Salisbury (jsalisbury)]

Actually it looks like this patch may have already applied to oneiric per bug 897514

The patch is the following commit in oneiric:
f4a04c4518110f63a402e53988b0143046b66750

So it appears the patch is in 3.0.0-15.24, which is still in oneiric-proposed.

Would it be possible for folks affected by this bug to test oneiric-prooposed?

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Thank you in advance!

[Michael Basse (michael-alpha-unix)]

Ho Joseph,
thank you for the hint about proposed. i will do some testing with that kernel and will give feedback here

@ALL, please remeber to turn the powermanagement on again, if you are testing the porposed kernel

[Michael Basse (michael-alpha-unix)]

Just FYI, i will test the 11.10 kernel on 12.04 because i dont have a 11.10 system here on a eeepc but i think that should not be a problem

[Michael Basse (michael-alpha-unix)]

Joseph, the Kernel is running fine here with enabled power-management.

Do you need a special test-process? should i test other changes to 3.0.0-15-foo is pulling? or does "yes its not producing panics" enough?

It would be no problem for me to do some special testcases (only i386) if needed

[Tristan Schmelcher (tschmelcher)]

My sister has an ASUS EeePC using the rt2800pci driver that experiences a panic regression in Oneiric. I'll install the proposed kernel on her system and test.

[Joseph Salisbury (jsalisbury)]

@Michael,

Thanks for the feedback. That is great news that the panics have stopped. I don't think any special test case is needed, since the panics were a regular issue for you. I would suggest just use your system as you normally would, and report back if any panics do happen.

@Tristan,

Thanks for offering to test. The more folks that report this is resolved in -proposed, the better :)

Thanks again everyone!

[Michał Sawicz (saviq)]

Actually, unless I'm failing something here, the most recent kernel in -proposed is 3.0.0-15-17 - and doesn't help. I'm trying 3.0.0-15-25 from ppa:canonical-kernel-team/ppa now.

[Michał Sawicz (saviq)]

I take that back... Indeed 3.0.0.15.25 is there in -proposed, but the package is named differently so I got lost. I'm not yet sure whether it helped, will report back asap.

[Michał Sawicz (saviq)]

From initial testing it looks like the connection is stable and no kernel panic occurs. I will report back after further testing.

[varangamaiky (eddyborera-c)]

I had the same problem constantly on my hp dm1z (AMD fusion). I have tested the oneiric-proposed, and I haven't had the problem ever since.

[dominus_sapiens (dominussapiens)]

I've been using 3.0.0-15, the version in -proposed, for a few days now in a variety of conditions and I haven't had a panic yet. It seems to be stable, though I'll let you know if anything changes.

[sokai (sokai)]

Thanks a lot! - At my ASUS Eee Pc 1000 I havn't had a kernel panic since I installed kernel 3.0.0-15 from the proposed archive (like mentioned above in comment #150).

[Joseph Salisbury (jsalisbury)]

Thanks for the update sokai. @Michael, can you also confirm the 3.0.0-15 kernel has not had any issues as well?

[Jorge Juan (jjchico)]

3.0.0-15 seems to be working ok here in my MSI Wind U100.

2012/1/18 Joseph Salisbury <email address hidden>:
> Thanks for the update sokai.  @Michael, can you also confirm the
> 3.0.0-15 kernel has not had any issues as well?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (873716).
> https://bugs.launchpad.net/bugs/869502
>
> Title:
>  Kernel-Panic with 3.0.0.12-generic on asus eee pcs and msi wind (both
>  using rt2800 wifi chipset)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/869502/+subscriptions

--
Jorge Juan

[Michael Basse (michael-alpha-unix)]

Joseph, i can confirm that 3.0.0-15 does not have any issues here.

[Michael Basse (michael-alpha-unix)]

Joseph, can you give me and all others here an overview about the status of that patch for 12.04 wih linux3.2.x?

The normal 12.04 Kernel is also producing kernel-panics on rt2800pci-devices

[Joseph Salisbury (jsalisbury)]

Michael,

The fix for this bug is in the 12.04 kernel as the following commit:

ed66ba472a742cd8df37d7072804b2111cdb1014 rt2x00: Fix sleep-while-atomic bug in powersaving code.

Would it be possible for you to test the latest 12.04, which is available at:
https://launchpad.net/ubuntu/+source/linux/3.2.0-10.17

You can download the .deb for your particular arch by selecting one of the links under the "Builds" section.

[Michael Basse (michael-alpha-unix)]

Joseph,
the proposed from 12.04 is working fine. I guess we finally have a working kernel on 11.10 and 12.04 for this ugly bug :)

[Michael Basse (michael-alpha-unix)]

Joseph,
is it correct that the fix is released for 11.10 and 12.04 in the normal repos? So everyone would have the fix and we can close this as "fix released"?

[Michael Basse (michael-alpha-unix)]

I have marked the bug as "fixed released" because the fix is already in all affected stable-releases. So this bug will be closed