From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwl3945: microcode SW error log decode?
Date: Mon, 28 Mar 2011 15:01:35 +0200 [thread overview]
Message-ID: <20110328130134.GA4037@redhat.com> (raw)
In-Reply-To: <1300083494.6654.1.camel@dcbw.foobar.com>
On Mon, Mar 14, 2011 at 01:18:13AM -0500, Dan Williams wrote:
> https://bugzilla.gnome.org/show_bug.cgi?id=644551
>
> that has this error log in it. Is that enough to figure out where
> things have gone wrong in the firmware?
>
> [ 1286.750258] iwl3945 0000:03:00.0: Microcode SW error detected. Restarting 0x82000008.
> [ 1286.750268] iwl3945 0000:03:00.0: Loaded firmware version: 15.32.2.9
> [ 1286.750304] iwl3945 0000:03:00.0: Start IWL Error Log Dump:
> [ 1286.750309] iwl3945 0000:03:00.0: Status: 0x0002A2E4, count: 1
> [ 1286.750314] iwl3945 0000:03:00.0: Desc Time asrtPC blink2 ilink1 nmiPC Line
> [ 1286.750543] iwl3945 0000:03:00.0: SYSASSERT (0x5) 0001680217 0x008B6 0x13756 0x00320 0x00000 764
> [ 1286.750547]
> [ 1286.750677] iwl3945 0000:03:00.0: Start IWL Event Log Dump: display last 20 count
> [ 1286.750720] iwl3945 0000:03:00.0: 0001679867 0x00000001 1106
> [ 1286.750746] iwl3945 0000:03:00.0: 0001679867 0x0000000f 1106
> [ 1286.750771] iwl3945 0000:03:00.0: 0001679869 0x00000428 1105
> [ 1286.750796] iwl3945 0000:03:00.0: 0001679873 0x00000483 1115
> [ 1286.750821] iwl3945 0000:03:00.0: 0001679876 0x00000006 0463
> [ 1286.750846] iwl3945 0000:03:00.0: 0001679877 0x00000006 0462
> [ 1286.750871] iwl3945 0000:03:00.0: 0001680003 0x04130097 0401
> [ 1286.750896] iwl3945 0000:03:00.0: 0001680005 0x00000006 0451
> [ 1286.750921] iwl3945 0000:03:00.0: 0001680025 0x00000000 0451
> [ 1286.750947] iwl3945 0000:03:00.0: 0001680157 0x44140080 0401
> [ 1286.750972] iwl3945 0000:03:00.0: 0001680172 0x00000017 0452
> [ 1286.750997] iwl3945 0000:03:00.0: 0001680177 0x00113b6e 0450
> [ 1286.751023] iwl3945 0000:03:00.0: 0001680182 0x00113b6e 0450
> [ 1286.751048] iwl3945 0000:03:00.0: 0001680187 0x00113b6e 0450
> [ 1286.751073] iwl3945 0000:03:00.0: 0001680192 0x00113b6e 0450
> [ 1286.751098] iwl3945 0000:03:00.0: 0001680197 0x00113b6e 0450
> [ 1286.751123] iwl3945 0000:03:00.0: 0001680202 0x00123b6e 0450
> [ 1286.751148] iwl3945 0000:03:00.0: 0001680207 0x00123b6e 0450
> [ 1286.751173] iwl3945 0000:03:00.0: 0001680213 0x00123b6e 0450
> [ 1286.751198] iwl3945 0000:03:00.0: 0001680218 0x00000100 0125
> [ 1286.751212] iwl3945 0000:03:00.0: Error Reply type 0x000002FC cmd REPLY_SCAN_CMD (0x80) seq 0x4414 ser 0x00340000
> [ 1286.755637] iwl3945 0000:03:00.0: Can't stop Rx DMA.
We have information that disable_hw_scan=1 workaround that problem.
That would be second reason to use software scanning by default,
first was very bad performance on some configurations. I'm going
to post a patch, which change that option on iwl3945.
Stanislaw
prev parent reply other threads:[~2011-03-28 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 6:18 iwl3945: microcode SW error log decode? Dan Williams
2011-03-14 13:05 ` Johannes Berg
2011-03-28 13:01 ` Stanislaw Gruszka [this message]
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=20110328130134.GA4037@redhat.com \
--to=sgruszka@redhat.com \
--cc=dcbw@redhat.com \
--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).