Linux wireless drivers development
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Jan Schneider <jan@horde.org>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: Microcode SW error detected.
Date: Tue, 10 Feb 2009 10:07:27 -0800	[thread overview]
Message-ID: <1234289247.11530.178.camel@rc-desk> (raw)
In-Reply-To: <20090210121904.94213ubhpr3wui04@neo.wg.de>

On Tue, 2009-02-10 at 03:19 -0800, Jan Schneider wrote:
> Zitat von Jan Schneider <jan@horde.org>:
>=20
> > Zitat von Jan Schneider <jan@horde.org>:
> >
> >> Zitat von G=C3=A1bor Stefanik <netrolller.3d@gmail.com>:
> >>
> >>> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <jan@horde.org> wro=
te:
> >>>> Zitat von reinette chatre <reinette.chatre@intel.com>:
> >>>>
> >>>>> 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 l=
ike.
> >>>>>> When this happens, it usually doesn't help to reload the kerne=
l
> >>>>>> module. Sometimes it helps to use the rfkill switch though.
> >>>>>>
> >>>>>> Here's a log with debug=3D0x43fff:
> >>>>>
> >>>>> It does not seem as though your driver is compiled with debug s=
upport.
> >>>>> You can confirm that by looking at the version number of the dr=
iver
> >>>>> printed when it loads ... it should have a "d" in it like "1.2.=
26kds".
> >>>>> Could you please recompile the driver with debug support (IWLWI=
=46I_DEBUG)
> >>>>> and rerun your test?  This will provide us with a complete even=
t log of
> >>>>> the uCode error.
> >>>>
> >>>> Enabling debug didn't help:
> >>>>
> >>>> Feb  7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(R) Wir=
eless WiFi
> >>>> Link
> >>>> AGN driver for Linux, 1.3.27kds
> >>>>
> >>>>
> >>>> /etc/modprobe.d/iwlagn:
> >>>>
> >>>> options iwlagn debug=3D0x43fff
> >>>>
> >>>>
> >>>> I still get:
> >>>>
> >>>> Feb  8 18:40:53 tank kernel: [77584.979829] iwlagn 0000:0c:00.0:=
 Microcode
> >>>> SW er
> >>>> ror detected.  Restarting 0x2000000.
> >>>> Feb  8 18:40:53 tank kernel: [77585.029747] Registered led devic=
e:
> >>>> iwl-phy0::rad
> >>>> io
> >>>> Feb  8 18:40:53 tank kernel: [77585.030765] Registered led devic=
e:
> >>>> iwl-phy0::ass
> >>>> oc
> >>>> Feb  8 18:40:53 tank kernel: [77585.031602] Registered led devic=
e:
> >>>> iwl-phy0::RX
> >>>> Feb  8 18:40:53 tank kernel: [77585.032467] Registered led devic=
e:
> >>>> iwl-phy0::TX
> >>>
> >>> No - enable IWLWIFI_DEBUG in your kernel config, then rebuild the
> >>> kernel (or at least the iwlwifi modules).
> >>
> >> That's what I did, see the "d" in "1.2.26kds" above.
> >
> > Eh, that was the wrong citation of course. But it's still a "d" in =
=20
> > "1.3.27kds".
>=20
> Anything else I can try to provide more information?

Which hardware are you running? If it is a member of the 5k series then
you need to use the debug50 parameter.

Reinette

--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-02-10 18:03 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
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 [this message]
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=1234289247.11530.178.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=jan@horde.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.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