Is there a line just before the WARNING in dmesg that has "ssb: Backplane Revision" in it? This looks like an unknown revision of the SSB bus...
Hi John, Here are the few lines before "ssb: Backplane Revision": Mar 6 20:13:03 delos NetworkManager[1028]: <info> (wlan0): bringing up device. Mar 6 20:13:03 delos NetworkManager[1028]: NetworkManager[1028]: <info> (wlan0): bringing up device. Mar 6 20:13:03 delos kernel: [518873.488277] ssb: Backplane Revision 0xF0000000 Usually I am able to use wireless on this machine, but not after this error. Hmmm... There is more data in dmesg: [Tue Mar 6 20:11:40 2012] usb 6-2: USB disconnect, device number 4 [Tue Mar 6 20:11:42 2012] tg3 0000:09:00.0: p3p1: Link is down [Tue Mar 6 20:11:45 2012] dell_wmi: Unknown key e044 pressed [Tue Mar 6 20:13:02 2012] ssb: Backplane Revision 0xF0000000 The tg3 link down and usb disconnect are expected as I was disconnecting my laptop so I could use it at a different location - wirelessly. There were also some errors after this trace: [Tue Mar 6 20:13:03 2012] b43-phy0 ERROR: Microcode not responding [Tue Mar 6 20:13:03 2012] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website. [Tue Mar 6 20:13:48 2012] keyboard: can't emulate rawmode for keycode 240 [Tue Mar 6 20:13:48 2012] keyboard: can't emulate rawmode for keycode 240 [Tue Mar 6 20:13:54 2012] keyboard: can't emulate rawmode for keycode 240 [Tue Mar 6 20:13:54 2012] keyboard: can't emulate rawmode for keycode 240
That looks like the hardware is not responding correctly. Are you sure that device is still functional? Could it have not been fully seated in the slot?
After rebooting, my wireless card works just fine. I don't use wireless most days with this machine. I did notice that I had installed a new kernel, but not rebooted before I had the problem.
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.