From: Larry Finger <Larry.Finger@lwfinger.net>
To: reinette chatre <reinette.chatre@intel.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
"lee_matheson@hotmail.com" <lee_matheson@hotmail.com>
Subject: Re: Problem with IW5300
Date: Tue, 30 Mar 2010 18:09:16 -0500 [thread overview]
Message-ID: <4BB2849C.8060105@lwfinger.net> (raw)
In-Reply-To: <1269986519.2446.3467.camel@rchatre-DESK>
On 03/30/2010 05:01 PM, reinette chatre wrote:
> Hi Larry,
>
> On Tue, 2010-03-30 at 12:56 -0700, Larry Finger wrote:
>> His problem is that the wireless keeps getting a microcode error and is dropping
>> and remaking the connection about every 40 seconds. It logs the following:
>
> How severe is the impact of this restart? Does "remake the connection"
> mean that a reassociation is needed?
>
>> [ 652.749175] iwlagn 0000:04:00.0: Microcode SW error detected. Restarting
>> 0x2000000.
>> [ 652.749201] iwlagn 0000:04:00.0: Start IWL Error Log Dump:
>> [ 652.749207] iwlagn 0000:04:00.0: Status: 0x000212E4, count: 5
>> [ 652.749346] iwlagn 0000:04:00.0: Desc Time
>> data1 data2 line
>> [ 652.749356] iwlagn 0000:04:00.0: NMI_INTERRUPT_WDG (#04)
>> 1197632519 0x00000002 0x07030000 3664
>> [ 652.749361] iwlagn 0000:04:00.0: blink1 blink2 ilink1 ilink2
>> [ 652.749367] iwlagn 0000:04:00.0: 0x005AA 0x006E8 0x008B2 0x0CF76
>
> This is the firmware watchdog timer kicking in because something is
> hanging in firmware or maybe just talking too long. Unfortunately quite
> a few of these have been popping up recently, so far I have recorded six
> bug reports with the same line number you are reporting here.
>
> You could try the patches accompanying
> https://bugzilla.kernel.org/show_bug.cgi?id=15374 ... that will not make
> the firmware error go away, but should help with cleanup when it does
> occur and hopefully enable the connection to recover without user
> noticing ... although I am not sure about that if this error is hit so
> often.
>From what I see in the git log for mainline 2.6.34, these patches are already
there. If that is correct, the OP's problem should go away as I think the next
Milestone release of openSUSE should switch to 2.6.34-rcX.
Thanks for the response.
Larry
prev parent reply other threads:[~2010-03-30 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 19:56 Problem with IW5300 Larry Finger
2010-03-30 22:01 ` reinette chatre
2010-03-30 23:09 ` Larry Finger [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=4BB2849C.8060105@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=lee_matheson@hotmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@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).