Linux wireless drivers development
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Jan Schneider <jan@horde.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: Microcode SW error detected.
Date: Fri, 06 Feb 2009 14:45:18 -0800	[thread overview]
Message-ID: <1233960318.11530.114.camel@rc-desk> (raw)
In-Reply-To: <20090206233134.11116cap9kcroxgc@neo.wg.de>

On Fri, 2009-02-06 at 14:31 -0800, Jan Schneider wrote:
> I've seen in a post from January that someone already had this problem  
> but couldn't reproduce it.
> I can't reliably reproduce, but I see this more often than I like.  
> When this happens, it usually doesn't help to reload the kernel  
> module. Sometimes it helps to use the rfkill switch though.
> 
> Here's a log with debug=0x43fff:

It does not seem as though your driver is compiled with debug support.
You can confirm that by looking at the version number of the driver
printed when it loads ... it should have a "d" in it like "1.2.26kds".
Could you please recompile the driver with debug support (IWLWIFI_DEBUG)
and rerun your test?  This will provide us with a complete event log of
the uCode error.

Thank you

Reinette



  reply	other threads:[~2009-02-06 22:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 22:31 iwlagn: Microcode SW error detected Jan Schneider
2009-02-06 22:45 ` reinette chatre [this message]
2009-02-08 18:23   ` Jan Schneider
2009-02-08 19:59     ` Gábor Stefanik
2009-02-08 22:51       ` Jan Schneider
2009-02-08 23:45         ` Jan Schneider
2009-02-10 11:19           ` Jan Schneider
2009-02-10 18:07             ` reinette chatre
2009-02-10 23:45               ` Jan Schneider
2009-02-11 23:09                 ` Jan Schneider
2009-02-12  2:22                   ` reinette chatre
2009-02-12  6:58                     ` reinette chatre
2009-02-12 16:15                       ` Jan Schneider

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=1233960318.11530.114.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=jan@horde.org \
    --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