On Thu, Jul 17, 2008 at 1:28 PM, drago01 <drago01@xxxxxxxxx> wrote: > On Thu, Jul 17, 2008 at 1:23 PM, drago01 <drago01@xxxxxxxxx> wrote: >> On Mon, Jul 14, 2008 at 8:05 PM, Cahill, Ben M <ben.m.cahill@xxxxxxxxx> wrote: >>> Try loading driver using module param: >>> >>> debug=0x43fff >>> >>> This will provide more information in the log, including an event log >>> (where you see "Microcode SW Error detected" in your log, you would have >>> captured Event Log if you had the debug=0x43fff setting). >> >> It happend again and this time I captured the log. >> Debug output including event log is attached. >> > > Resend with compressed attachment. > Happend again ... is there a tool that "decrypts" the event log to be readable? The whole thing does not make any sense to me and the log does not tell me what is really happening to debug it. -- 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
