From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org, Wey-Yi W Guy <wey-yi.w.guy@intel.com>
Subject: Re: iwl3945: microcode SW error log decode?
Date: Mon, 14 Mar 2011 14:05:58 +0100 [thread overview]
Message-ID: <1300107958.3802.16.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1300083494.6654.1.camel@dcbw.foobar.com>
On Mon, 2011-03-14 at 01:18 -0500, Dan Williams wrote:
> 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
IIRC, it's quite hard for 3945. But I might be wrong. What's the kernel
version here?
> It appears like the configuration that gets sent to wpa_supplicant is
> TKIP + WPA2 which seems kinda wrong, doesn't WPA2/RSN require CCMP?
That seems fine. WPA2 certification requires the ability to do CCMP I
think, but RSN can also be set up to use TKIP, say if you set up
WPA/WPA2 on the network. WPA is just a pre-RSN (WPA2) method of
advertising pretty much the same thing.
johannes
next prev parent reply other threads:[~2011-03-14 13:06 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 [this message]
2011-03-28 13:01 ` Stanislaw Gruszka
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=1300107958.3802.16.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@intel.com \
/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).