https://bugzilla.novell.com/show_bug.cgi?id=476367 User vok@cvmi.aau.dk added comment https://bugzilla.novell.com/show_bug.cgi?id=476367#c26 Summary: wireless driver iwlagn hangs after waking up from suspend -- only hard shutdown helps Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vok@cvmi.aau.dk QAContact: qa@suse.de Found By: --- Created an attachment (id=273198) --> (https://bugzilla.novell.com/attachment.cgi?id=273198) subset of /var/log/messages User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 I have often a problem with the wireless driver iwlagn after wakeup from standby: When i attempt to connect to a wireless network, it very often results in the machine hanging: I can see that the root process event/1 consumes 100% computation time and keyboard input does not work anymore. All I can do is turn off the machine using the powerbutton. Sometimes, the HW-switch for the wireless manages to shut down the wireless driver, which also stops the event/1 process from using 100% computation time. Then, a rmmod and modprobe of iwlagn _sometimes_ helps. This observation happened on a Thinkpad X200s, opensuse and kernel 2.6.27.7-9 and 2.6.27.17-4, 64bit. This is the same error as in http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1832 And I can confirm comment #26. Reproducible: Always Steps to Reproduce: How to do that: - use wpa connection (not really sure if it would work on nonwpa also, i have wpa everywhere i can) - connect to AP - associate or send some data - turn killswitch on (disable wireless) - turn killswitch off (enable wireless) - close the lid/suspend to ram - restore - try to associate to wpa - you get event/1 cycling, one core is fully loaded, keyboard is blocked in X until i kill signal again. - until i fix it somehow, i cannot connect to wpa station until reboot. Actual Results: Machine hangs, keyboard input does not work anymore under X. Mouse seems to be working, but opening a shell, for example, is _very_ slow Expected Results: There should not have been a lockup of the iwlagn driver after wakeup. I classify it as a "major feature being broken" as it makes the suspend2ram on the laptop useless. i appended an extract from /var/log/messages. It starts with the last line before suspend to ram and ends with the the final hard shutdown after the lock-up. The iwlagn module starts at time 20:12:37 showing a number of microcode errors. -- 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.