On Wednesday 16 April 2008 19:28 in <D936D925018D154694D8A362EEB08920043535A1@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Chatre, Reinette wrote: > On , Marcus Furlong wrote: > >> Hi, >> >> Have had a look through bugzilla and not sure if any of the >> existing bugs >> are exactly the same as mine, so thought I'd post here first >> to make sure >> I'm not missing anything obvious. >> >> Kernel 2.6.25-rc9 (although the same thing seems to happen on 2.6.24 >> kernels, so I stuck with the ipw driver and 2.6.23 til now) >> Using iwl3945 firmware 2.14.1.5 >> >> Machine doesn't associate with any AP (although it does seem to see >> the closer ones) and I get lots of the following errors: >> >> iwl3945: Microcode SW error detected. Restarting 0x82000008. >> >> Also, and unsure if this is related or not, the mouse and >> keyboard behave >> erratically when the iwl3945 module is loaded. Both keyboard >> and mouse lock >> up, but store all input in a buffer and spurt it out after a >> few seconds. >> After between 1-10 minutes the machine hangs and the Caps Lock >> and Scroll >> Lock lights flash on and off (not the Num Lock one though). >> >> Dmesg log is available here using netconsole on a wired >> connection, up to >> the point where it crashes: >> >> https://www.cs.tcd.ie/~furlongm/iwlwifi/iwlwifi-output.bz2 >> >> I also reloaded the module with debug=0x43ffb after booting, >> so the output >> becomes more verbose at that stage. > > Looks like the device is being brought up and down a lot ... are you > perhaps running wpa_supplicant or some other user application that is > doing this? Could you please give more information about what you were > doing when these errors started to appear? Yes, wpa_supplicant is running as part of the boot process. Should I use some other application? (Do wireless-tools support WPA?) Or should I just load the module on it's own and give the dmesg output from that? Marcus. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
