linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Maxime Bizon <mbizon@freebox.fr>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [iwlegacy/4965] Microcode SW error detected on 3.3rc1
Date: Wed, 25 Jan 2012 14:27:56 +0100	[thread overview]
Message-ID: <20120125132755.GA4595@redhat.com> (raw)
In-Reply-To: <1327441910.21837.94.camel@sakura.staff.proxad.net>

[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]

Hello,

On Tue, Jan 24, 2012 at 10:51:50PM +0100, Maxime Bizon wrote:
> I can reliably reproduce this on 3.3rc1 (build from ubuntu ppa), it was
> present on 3.2 too.
What was the latest working kernel you know about?

> [ 1053.054034] iwl4965 0000:03:00.0: Microcode SW error detected.  Restarting 0x2000000.
> [ 1053.054047] iwl4965 0000:03:00.0: Loaded firmware version: 228.61.2.24
> [ 1053.054069] iwl4965 0000:03:00.0: Start IWL Error Log Dump:
> [ 1053.054077] iwl4965 0000:03:00.0: Status: 0x000213E4, count: 5
> [ 1053.054239] iwl4965 0000:03:00.0: Desc                                  Time       data1      data2      line
> [ 1053.054250] iwl4965 0000:03:00.0: NMI_INTERRUPT_WDG            (0x0004) 0643296734 0x00000002 0x07430000 208
> [ 1053.054258] iwl4965 0000:03:00.0: pc      blink1  blink2  ilink1  ilink2  hcmd
> [ 1053.054266] iwl4965 0000:03:00.0: 0x0046C 0x08370 0x004C2 0x006DE 0x018B8 0x7DB001C
[snip]
> Single TCP transfer (AP -> STA) on a 802.11n/HT20 AP 2.4G
> 
> Once rate reaches about 7MB/s, then transfer stalls for 1 second and
> starts again, I get one of this about every minute.
Ehh, looks like scaning problem ..., you can probably workaround it 
by disable_hw_scan=1 module parameter, or setup NetworkManager to
configure constant BSSID (AP MAC address) in your wireless
network parameters in NM, hence stop NM requesting periodic scan.

I'm also attaching patch for test.

> Any log I could enable to help you ?

Yes (if patch does not help) plese configure syslog to log
debug messages into /var/log/kernel (some hint here:
https://fedoraproject.org/wiki/DebugWireless), restart
syslog, then do:

modprobe -r iwl4965
echo > /var/log/kernel
modprobe iwl4965 debug=0x47ffffff
wait minute or two for microcode error.
modprobe -r iwl4965

assure micocode error is in the log, and post me compressed
file. If it will be too big, you can wip out data starting
from microcode error to end of the file.

Thanks
Stanislaw

[-- Attachment #2: iwl4965_th_disabled.patch --]
[-- Type: text/plain, Size: 543 bytes --]

diff --git a/drivers/net/wireless/iwlegacy/4965-mac.c b/drivers/net/wireless/iwlegacy/4965-mac.c
index 1667232..e4ca7b4 100644
--- a/drivers/net/wireless/iwlegacy/4965-mac.c
+++ b/drivers/net/wireless/iwlegacy/4965-mac.c
@@ -962,7 +962,7 @@ il4965_request_scan(struct il_priv *il, struct ieee80211_vif *vif)
 	 * here instead of IL_GOOD_CRC_TH_DISABLED.
 	 */
 	scan->good_CRC_th =
-	    is_active ? IL_GOOD_CRC_TH_DEFAULT : IL_GOOD_CRC_TH_NEVER;
+	    is_active ? IL_GOOD_CRC_TH_DEFAULT : IL_GOOD_CRC_TH_DISABLED;
 
 	band = il->scan_band;
 

      reply	other threads:[~2012-01-25 13:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 21:51 [iwlegacy/4965] Microcode SW error detected on 3.3rc1 Maxime Bizon
2012-01-25 13:27 ` 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=20120125132755.GA4595@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mbizon@freebox.fr \
    /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).