[Bug 694725] New: OS freeze after using the WIFI kill switch; can't reenable WIFI after reboot following the freeze
https://bugzilla.novell.com/show_bug.cgi?id=694725 https://bugzilla.novell.com/show_bug.cgi?id=694725#c0 Summary: OS freeze after using the WIFI kill switch; can't reenable WIFI after reboot following the freeze Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mike@mk.tc QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_7; en-us) AppleWebKit/533.21.1 (KHTML, like Gecko) Version/5.0.5 Safari/533.21.1 Hardware details: Lenovo S10-3 OS version: openSUSE 11.4 x86_64, kernel: 2.6.37.6-0.5-desktop #1 SMP PREEMPT 2011-04-25 21:48:33 +0200 x86_64 x86_64 GNU/Linux Graphical environment: GNOME3 Not sure if the GUI has anything to do with issues I've experienced, but I thought I'd list it anyway. When I use the kill switch for Bluetooth and WIFI, the system freezes completely. I'm not able to even move the mouse pointer on the screen. Nothing gets logged in the system logs. Following that, I have to cold-restart the system (press and hold the power button until the system turns off, press the power button again to power it back on). When the system comes back up, if I slide the kill switch back to enable position, the bluetooth becomes available again, however the WIFI module is still disabled. At this stage another reboot makes the WIFI module available again. I've traced it to ideapad_laptop kernel module blocking the reenabling of the WIFI module - if I do "sudo rmmod ideapad_laptop" then the WIFI module becomes available immediately without the need for the second reboot above. I can then do "sudo modprobe ideapad_laptop" again and all works fine. In that session (that is - until the next time the computer is shutdown or rebooted), the kill switch works as expected and I'm able to disable and reenable both bluetooth and wifi repeatedly with no issues. Following another reboot, the freeze after WIFI kill switch use occurs again. Reproducible: Always Steps to Reproduce: 1. Boot up the OS with the WIFI kill switch in ON position, log in 2. Use WIFI kill switch (move it to OFF position) - system freezes completely 3. press and hold power button to switch machine off 4. press power to start the machine again, boot it up, log in 5. switch the WIFI kill switch to ON - bluetooth becomes available, WIFI module not available --- two scenarios to fix the issue possible from this step --- scenario 1: 6a. reboot the computer again (use shutdown, or 'sudo reboot' or any other graceful restart method) 7a. wait for the OS to come back up, log in 8a. move the WIFI slider in the GUI to ON if in OFF position (use the software function and NOT the WIFI switch - it should have been left in ON position since the last time it was enabled) 9a. WIFI is now available scenario 2: 6b. issue "sudo rmmod ideapad_laptop" 7b. the WIFI module becomes available automatically, of if not - move the WIFI slider in the GUI to ON position (again - use the software function) 8b. issue "sudo modprobe ideapad_laptop" Actual Results: 1. after step 2 above the computer freezes 2. after step 5 above the bluetooth module becomes available as expected, however the WIFI module is still not available 3. either scenario 1 (steps 6a-9a) or scenario 2 (steps 6b-8b) bring the WIFI module back to life Expected Results: move WIFI kill switch to OFF position disables both bluetooth and WIFI move WIFI kill switch back to ON position enables both bluetooth and WIFI I use GNOME3 graphical environment (I installed the standard openSUSE 11.4 OS and then added GNOME3 as per http://en.opensuse.org/openSUSE:GNOME_3.0 (I used the one click install of x86 86 openSUSE 11.4) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=694725
https://bugzilla.novell.com/show_bug.cgi?id=694725#c1
Gary Ching-Pang Lin
https://bugzilla.novell.com/show_bug.cgi?id=694725
https://bugzilla.novell.com/show_bug.cgi?id=694725#c3
Vladimir Botka
Graphical environment: GNOME3 I've traced it to ideapad_laptop kernel module blocking the reenabling of the WIFI module
I guess there is a conflict among the ideapad_laptop modul and bios in dealing with the rfkill. To isolate the problem, would it be possible to perform few experiments in runlevel 3 ? Install the rfkill utility (#zypper in rfkill) and take a look at the output of "rkill list all". Switch to runlevel 3 "init 3" to sort out the desktop interference, login as root and proceed from the command line. Slide the rfkill switch, check the wlan/bt functionality and post the output of "rfkill list all". To check wlan just bring the wlan interface up "ifconfig wlan0 up" and try to scan the APs "iwlist scan". To check bt just take a look on the adapter "hciconfig -a" and scan the bt devices "hcitool scan". If there are still problems in runlevel 3, unload the ideapad_laptop and repeat the test. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=694725
https://bugzilla.novell.com/show_bug.cgi?id=694725#c4
--- Comment #4 from Michal Krzysztofowicz
https://bugzilla.novell.com/show_bug.cgi?id=694725
https://bugzilla.novell.com/show_bug.cgi?id=694725#c5
Vladimir Botka
Some more details. When I remove the acpi_osi="Linux" from the boot args list, everything works as expected Do you still want me to add the "acpi_osi" parameter back in and run the tests?
Thank you. No, it's not necessary. I'll close as invalid then. If you observe any problems reopen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com