Return-path: Received: from nf-out-0910.google.com ([64.233.182.191]:10428 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751087AbYGRTfx (ORCPT ); Fri, 18 Jul 2008 15:35:53 -0400 Received: by nf-out-0910.google.com with SMTP id d3so167547nfc.21 for ; Fri, 18 Jul 2008 12:35:52 -0700 (PDT) Message-ID: (sfid-20080718_213606_468799_996E63C9) Date: Fri, 18 Jul 2008 21:35:52 +0200 From: drago01 To: "Cahill, Ben M" Subject: Re: [ipw3945-devel] iwl3945 random firmware crashes Cc: linux-wireless , ipw3945-devel In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <4220499A1B034C4FA93B547BA01E1FF0017469B4@orsmsx413.amr.corp.intel.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Jul 17, 2008 at 1:28 PM, drago01 wrote: > On Thu, Jul 17, 2008 at 1:23 PM, drago01 wrote: >> On Mon, Jul 14, 2008 at 8:05 PM, Cahill, Ben M 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.