kernel crashes when toggling off wlan on Eee PC 701SD

Bug #522119 reported by MrAuer
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This bug affects at least Jaunty, Karmic and Lucid Lynx alpha 2 - I tested the behaviour on each with the latest kernels for the releases. I also tested its behaviour with EB4 that is based on Debian unstable, that kernel crashes as well. I suspect that Hardy is affected as well, because the owner of the laptop reported it hanging at times - Im supposing it happened after toggling the wlan off but am unable to confirm that.

Hardware affected is an Eee PC 701SD, with Realtek RTL8187SE chipset. The wlan itself works, and I am able to turn the card on using the Fn-F2 hotkeys, but when turning wlan off it causes a kernel panic and hard locks the machine necessitating poweroff via holding the power key for 5 seconds. This happens both when Im connected to a wireless network as well as when I am not, and it happens every time wlan is toggled off.

This machine is not my own and I need to send it back to the person I was upgrading it for, so I dont know how much additional information I can give later - I have the laptop for a couple more days tops. I think I will have to inform the owner about the problem and ask her not to use the wlan toggle key. My own Eee pcs, the regular 701 4GB model and 901 20GB model are not affected by this as they have a different wlan chipset, and after https://bugs.launchpad.net/ubuntu/+source/linux/+bug/404626 was fixed, they now work perfectly. From browsing forums I found out that other owners of this specific 701SD model also report that toggling wlan off causes a kernel crash every time, for example here: http://ubuntuforums.org/showthread.php?p=8819267#post8819267 others also tell of problems connecting to a WEP network - I have only used in WPA2 networks and there it worked, even though it sometimes drops the connection even when the laptop is right next to the router.

I installed kernel-crashdump and caused the panic, I will attach the Apport-generated crashdump. I tried to do that via Apports automatic bug reporting as well, but Apport itself reported an error connecting to the bug server and crashed when it had sent about 98% of the kernel crashdump, so Im not going to try that again as it took about an hour for the slow lappie to process that in any case.

The exact time of the crash was 21.00.54 on 14th of February. If you need additional information, please request it as soon as possible as I cannot keep the machine for much longer.

Revision history for this message
MrAuer (mr-auer) wrote :
Revision history for this message
MrAuer (mr-auer) wrote :
Revision history for this message
MrAuer (mr-auer) wrote :
Revision history for this message
MrAuer (mr-auer) wrote :
Revision history for this message
MrAuer (mr-auer) wrote :

Bah, Launchpad had an error after my browser sent the 120 mb crash report and failed to upload it. I will see if I can upload it somewhere else and will post a link here ASAP.

Revision history for this message
MrAuer (mr-auer) wrote :

I uploaded the Apport - generated kernel crash report here:
http://koti.welho.com/mauserman/linux/linux-image-2.6.31-19-generic.0.crash

(If someone else is able to attach the file directly to this report, please do so - for some reason uploading it via Apport or Launchpad fails for me, I will leave the file at the link for some time in any case)

Revision history for this message
MrAuer (mr-auer) wrote :

How would I go about to disable the Fn-F2 keycombo completely, so it would not be pressed accidentally? It is fine if it could only be toggled via BIOS - better than to have the machine hang if accidentally pressed.

Revision history for this message
MrAuer (mr-auer) wrote :

Oops, lspci -vnvn omitted the Wlan card as it was turned off after causing the panic. Attached lspci with it here.

tags: added: kernel-series-unknown
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi MrAuer,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 522119

Also, if you could test the latest upstream kernel available that would be great. 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.

Thanks in advance.

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

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
MrAuer (mr-auer) wrote :

Im sorry, but I cannot test it anymore. I dont have the machine, I mailed it to the person I installed it for shortly after reporting the bug. If it comes back to me for updating at some point I can try Lucid Lynx on it from a USB stick and see if that fixes it. As it is the machine is on the other side of the country ;)

Thank you.

Revision history for this message
James Womack (james-c-womack) wrote :

I can confirm that the bug also occurs for me. Toggling off the wireless using Fn+F2 on my eeePC 701SD causes Ubuntu Lucid (standard desktop edition) to hang and I need to hard reset the machine to use it again. Toggling on the wireless is not a problem as far as I can tell.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

James,
   please file a new bug for your issue so that we can work it based on it's merit. you can do this by running 'ubuntu-bug linux' from the command line in a terminal window.

MrAuer,
   I'm going to close this bug as Invalid. You can reopen it once you get the chance to test further.

Thanks!

~JFo

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
James Womack (james-c-womack) wrote :

I have reported the bug and selected this report as describing the bug I am trying to report, specifically the WLAN Fn+F2 toggle off causing the kernel to crash. I am open to further testing of the issue.

Revision history for this message
Robie Basak (racb) wrote :

I have reported bug 674285 which I believe is the same issue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.