Created attachment 339096 [details] /var/log/messages from the crashed session Description of problem: My laptop wireless (iwl3945) failed -- the connection dropped and would not reconnect. In previous Linux distributions (Fedora included) I was able to work around this bug/problem by removing and reloading the iwl3945 kernel module. Under F11/rawhide, attempting to do so locks up my system. Version-Release number of selected component (if applicable): kernel-2.6.29.1-54.fc11.x86_64 kernel-firmware-2.6.29.1-54.fc11.noarch How reproducible: Every time the wireless quits like this, though it does not happen more than once every day or few days. Steps to Reproduce: 1. Wait for wireless to fail 2. modprobe -r iwl3945 3. X goes away and is replaced by the blue Fedora boot screen (Fedora logo with white bar across the bottom). Keys and mouse do not respond, except Numlock which can be toggled on and off. I have not tested this to see if the hang will occur without the other wireless problems showing up first. Actual results: System hangs Expected results: Clean module unload, or (better), no need to unload the module in the first place Additional info: I have attached the contents of /var/log/messages from this particular boot -> lockup. The potentially interesting looking stuff is toward the end of the log.
I just tested using modprobe -r iwl3945 on a "clean" boot without any other errors with a similar result as above. X goes away and is replaced by the plymouth screen. The difference is that this time the system seemed to have locked up slightly differently as it left the Caps Lock key blinking (kernel panic?).
Can you boot to runlevel 3 (add the number 3 to the boot options), remove the driver, and see if you can capture the oops messages?
I started normally then switched to runlevel 3 with "init 3" from a VT. I hope this is sufficient. Unfortunately most of the text scrolled by before I could read it. I took pictures with my digital camera of what is left on the screen when it is done. They are here: http://www.atmos.umd.edu/~hcarty/iwl3945_oops/ I wasn't sure if I should attach ~5 megabytes of images to this bug just to catch a bit of text. Please let me know if I can provide anything further.
*** This bug has been marked as a duplicate of bug 495003 ***