From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Bernhard Schmidt <bschmidt@freebsd.org>
Cc: Paul Bolle <pebolle@tiscali.nl>, linux-wireless@vger.kernel.org
Subject: Re: [iwl4965] Microcode SW error detected
Date: Tue, 7 Jun 2011 16:54:35 +0200 [thread overview]
Message-ID: <20110607145435.GA5179@redhat.com> (raw)
In-Reply-To: <201106070832.49048.bschmidt@freebsd.org>
On Tue, Jun 07, 2011 at 08:32:48AM +0200, Bernhard Schmidt wrote:
> On Monday, May 23, 2011 13:45:06 Paul Bolle wrote:
> > 0) Since I started running (release candidates of) kernel v2.6.39 errors
> > like these show up in my log, every now and then:
> >
> > iwl4965 0000:03:00.0: Microcode SW error detected. Restarting 0x82000000.
> > iwl4965 0000:03:00.0: Loaded firmware version: 228.61.2.24
> > iwl4965 0000:03:00.0: Start IWL Error Log Dump:
> > iwl4965 0000:03:00.0: Status: 0x000213E4, count: 5
> > iwl4965 0000:03:00.0: Desc Time data1 data2 line
> > iwl4965 0000:03:00.0: FH_ERROR (0x000C) 1821446380 0x00000008 0x03130000 208
>
> On a unrelated site note, I have a case where I can trigger a
> FH_ERROR at this line 100% reliably. Not on Linux though..
> While being associated to a 5GHz BSS doing a scan chan by chan
> (instead of all at once) is enough to trigger it.
That could be useful hint, we do not scan chan by chan, but we
have thing called "plcp check health", which "restart radio"
by requesting one channel scan. So perhaps disabling that could
help.
> A workaround
> is too not send probe requests for 2GHz channels at 1Mbps (CCK
> flag) but at 6Mbps instead.
>
> Maybe this bug report [1] is related too?
>
> [1] http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1965
Hard to tell.
Thanks
Stanislaw
diff --git a/drivers/net/wireless/iwlegacy/iwl-rx.c b/drivers/net/wireless/iwlegacy/iwl-rx.c
index 654cf23..6062da0 100644
--- a/drivers/net/wireless/iwlegacy/iwl-rx.c
+++ b/drivers/net/wireless/iwlegacy/iwl-rx.c
@@ -230,6 +230,8 @@ EXPORT_SYMBOL(iwl_legacy_rx_spectrum_measure_notif);
void iwl_legacy_recover_from_statistics(struct iwl_priv *priv,
struct iwl_rx_packet *pkt)
{
+ return;
+
if (test_bit(STATUS_EXIT_PENDING, &priv->status))
return;
if (iwl_legacy_is_any_associated(priv)) {
next prev parent reply other threads:[~2011-06-07 14:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 11:45 [iwl4965] Microcode SW error detected Paul Bolle
2011-05-24 7:09 ` Stanislaw Gruszka
2011-05-24 15:54 ` Paul Bolle
2011-05-24 16:03 ` Stanislaw Gruszka
2011-05-24 16:50 ` Paul Bolle
2011-05-25 13:11 ` Stanislaw Gruszka
2011-05-25 13:31 ` Paul Bolle
2011-05-31 13:37 ` Stanislaw Gruszka
2011-06-06 8:58 ` Paul Bolle
2011-06-06 11:36 ` Stanislaw Gruszka
2011-06-06 18:29 ` Paul Bolle
2011-05-26 17:26 ` Dan Williams
2011-06-07 6:32 ` Bernhard Schmidt
2011-06-07 14:54 ` Stanislaw Gruszka [this message]
2011-06-07 19:23 ` Paul Bolle
2011-06-08 13:47 ` Stanislaw Gruszka
2011-08-15 10:51 ` Paul Bolle
2011-09-04 8:28 ` Paul Bolle
2011-09-05 9:33 ` Stanislaw Gruszka
2011-09-05 10:32 ` Paul Bolle
2012-09-14 12:17 ` Paul Bolle
2012-10-15 14:51 ` Paul Bolle
2012-10-15 15:17 ` 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=20110607145435.GA5179@redhat.com \
--to=sgruszka@redhat.com \
--cc=bschmidt@freebsd.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.