From: drago01 <drago01@gmail.com>
To: "Cahill, Ben M" <ben.m.cahill@intel.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
ipw3945-devel <ipw3945-devel@lists.sourceforge.net>
Subject: Re: [ipw3945-devel] iwl3945 random firmware crashes
Date: Fri, 18 Jul 2008 21:35:52 +0200 [thread overview]
Message-ID: <f6ca9fed0807181235i33125343qab4804b675bafdf9@mail.gmail.com> (raw)
In-Reply-To: <f6ca9fed0807170428i4b386e46sb030316343f4bd4a@mail.gmail.com>
On Thu, Jul 17, 2008 at 1:28 PM, drago01 <drago01@gmail.com> wrote:
> On Thu, Jul 17, 2008 at 1:23 PM, drago01 <drago01@gmail.com> wrote:
>> On Mon, Jul 14, 2008 at 8:05 PM, Cahill, Ben M <ben.m.cahill@intel.com> 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.
next prev parent reply other threads:[~2008-07-18 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 11:37 iwl3945 random firmware crashes drago01
2008-07-14 18:05 ` [ipw3945-devel] " Cahill, Ben M
2008-07-14 18:11 ` Stefanik Gábor
2008-07-14 20:44 ` Cahill, Ben M
2008-07-14 18:18 ` drago01
2008-07-17 11:23 ` drago01
[not found] ` <f6ca9fed0807170428i4b386e46sb030316343f4bd4a@mail.gmail.com>
2008-07-18 19:35 ` drago01 [this message]
2008-07-24 13:17 ` drago01
2008-07-24 13:56 ` Cahill, Ben M
2008-07-24 14:10 ` drago01
2008-08-01 12:38 ` drago01
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f6ca9fed0807181235i33125343qab4804b675bafdf9@mail.gmail.com \
--to=drago01@gmail.com \
--cc=ben.m.cahill@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).