On Monday, May 23, 2011 13:45:06 Paul Bolle wrote: > 0) Since I started running (release candidates of) kernel v2.6.39 errors > like these show up in my log, every now and then: > > iwl4965 0000:03:00.0: Microcode SW error detected. Restarting 0x82000000. > iwl4965 0000:03:00.0: Loaded firmware version: 228.61.2.24 > iwl4965 0000:03:00.0: Start IWL Error Log Dump: > iwl4965 0000:03:00.0: Status: 0x000213E4, count: 5 > iwl4965 0000:03:00.0: Desc Time data1 data2 line > iwl4965 0000:03:00.0: FH_ERROR (0x000C) 1821446380 0x00000008 0x03130000 208 On a unrelated site note, I have a case where I can trigger a FH_ERROR at this line 100% reliably. Not on Linux though.. While being associated to a 5GHz BSS doing a scan chan by chan (instead of all at once) is enough to trigger it. A workaround is too not send probe requests for 2GHz channels at 1Mbps (CCK flag) but at 6Mbps instead. Maybe this bug report [1] is related too? [1] http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1965 -- Bernhard -- 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
