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:
Feb 6 21:32:20 tank kernel: [11142.667719] iwlagn 0000:0c:00.0:
Microcode SW error detected. Restarting 0x2000000.
Feb 6 21:32:20 tank kernel: [11142.725640] Registered led device:
iwl-phy0::radio
Feb 6 21:32:20 tank kernel: [11142.725789] Registered led device:
iwl-phy0::assoc
Feb 6 21:32:20 tank kernel: [11142.725840] Registered led device:
iwl-phy0::RX
Feb 6 21:32:20 tank kernel: [11142.725876] Registered led device:
iwl-phy0::TX
That's unfortunately not more than without debug.
Here are follow-up retries from the module to restart itself:
Feb 6 21:38:31 tank kernel: [11514.361232] wlan0: deauthenticated (Reason: 2)
Feb 6 21:38:31 tank kernel: [11514.361257] HW problem - can not stop
rx aggregation for tid 0
Feb 6 21:38:31 tank kernel: [11514.372228] mac80211-phy0: failed to
remove key(0, ffff8800d9100b40) from hardware (-22)
Feb 6 21:38:32 tank kernel: [11515.360263] wlan0: direct probe to AP
ffff880119882a20 try 1
Feb 6 21:38:32 tank kernel: [11515.362305] wlan0 direct probe responded
Feb 6 21:38:32 tank kernel: [11515.362315] wlan0: authenticate with
AP ffff880119882a20
Feb 6 21:38:32 tank kernel: [11515.364878] wlan0: authenticated
Feb 6 21:38:32 tank kernel: [11515.364885] wlan0: associate with AP
ffff880119882a20
Feb 6 21:38:32 tank kernel: [11515.368128] wlan0: RX ReassocResp from
ffff8800cac28016 (capab=0x431 status=0 aid=1)
Feb 6 21:38:32 tank kernel: [11515.368137] wlan0: associated
Feb 6 21:38:34 tank kernel: [11517.377006] iwlagn 0000:0c:00.0:
Microcode SW error detected. Restarting 0x2000000.
Feb 6 21:38:34 tank kernel: [11517.421241] Registered led device:
iwl-phy0::radio
Feb 6 21:38:34 tank kernel: [11517.421711] Registered led device:
iwl-phy0::assoc
Feb 6 21:38:34 tank kernel: [11517.422034] Registered led device:
iwl-phy0::RX
Feb 6 21:38:34 tank kernel: [11517.422336] Registered led device:
iwl-phy0::TX
Feb 6 21:48:31 tank kernel: [12114.362612] wlan0: deauthenticated (Reason: 2)
Feb 6 21:48:31 tank kernel: [12114.362636] HW problem - can not stop
rx aggregation for tid 0
Feb 6 21:48:31 tank kernel: [12114.381137] mac80211-phy0: failed to
remove key(0, ffff88002e06a740) from hardware (-22)
Feb 6 21:48:32 tank kernel: [12115.360108] wlan0: direct probe to AP
ffff880119882a20 try 1
Feb 6 21:48:32 tank kernel: [12115.361948] wlan0 direct probe responded
Feb 6 21:48:32 tank kernel: [12115.361957] wlan0: authenticate with
AP ffff880119882a20
Feb 6 21:48:32 tank kernel: [12115.372072] wlan0: authenticated
Feb 6 21:48:32 tank kernel: [12115.372082] wlan0: associate with AP
ffff880119882a20
Feb 6 21:48:32 tank kernel: [12115.375111] wlan0: RX ReassocResp from
ffff8800bfb0c016 (capab=0x431 status=0 aid=1)
Feb 6 21:48:32 tank kernel: [12115.375123] wlan0: associated
Feb 6 21:48:34 tank kernel: [12116.976224] iwlagn 0000:0c:00.0:
Microcode SW error detected. Restarting 0x2000000.
Feb 6 21:48:34 tank kernel: [12117.025630] Registered led device:
iwl-phy0::radio
Feb 6 21:48:34 tank kernel: [12117.027965] Registered led device:
iwl-phy0::assoc
Feb 6 21:48:34 tank kernel: [12117.030202] Registered led device:
iwl-phy0::RX
Feb 6 21:48:34 tank kernel: [12117.032351] Registered led device:
iwl-phy0::TX
This happens every 10 minutes.
Jan.
--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
Zitat von reinette chatre <[email protected]>:
> On Tue, 2009-02-10 at 03:19 -0800, Jan Schneider wrote:
>> Zitat von Jan Schneider <[email protected]>:
>>
>> > Zitat von Jan Schneider <[email protected]>:
>> >
>> >> Zitat von G=C3=A1bor Stefanik <[email protected]>:
>> >>
>> >>> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <[email protected]> wr=
ote:
>> >>>> Zitat von reinette chatre <[email protected]>:
>> >>>>
>> >>>>> On Fri, 2009-02-06 at 14:31 -0800, Jan Schneider wrote:
>> >>>>>>
>> >>>>>> I've seen in a post from January that someone already had =20
>> 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 kern=
el
>> >>>>>> 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 =
support.
>> >>>>> You can confirm that by looking at the version number of the d=
river
>> >>>>> printed when it loads ... it should have a "d" in it like "1.2=
=2E26kds".
>> >>>>> Could you please recompile the driver with debug support =20
>> (IWLWIFI_DEBUG)
>> >>>>> and rerun your test? This will provide us with a complete =20
>> event log of
>> >>>>> the uCode error.
>> >>>>
>> >>>> Enabling debug didn't help:
>> >>>>
>> >>>> Feb 7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(R) =20
>> Wireless 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 =20
>> 0000:0c:00.0: Microcode
>> >>>> SW er
>> >>>> ror detected. Restarting 0x2000000.
>> >>>> Feb 8 18:40:53 tank kernel: [77585.029747] Registered led devi=
ce:
>> >>>> iwl-phy0::rad
>> >>>> io
>> >>>> Feb 8 18:40:53 tank kernel: [77585.030765] Registered led devi=
ce:
>> >>>> iwl-phy0::ass
>> >>>> oc
>> >>>> Feb 8 18:40:53 tank kernel: [77585.031602] Registered led devi=
ce:
>> >>>> iwl-phy0::RX
>> >>>> Feb 8 18:40:53 tank kernel: [77585.032467] Registered led devi=
ce:
>> >>>> iwl-phy0::TX
>> >>>
>> >>> No - enable IWLWIFI_DEBUG in your kernel config, then rebuild th=
e
>> >>> 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
>> > "1.3.27kds".
>>
>> Anything else I can try to provide more information?
>
> Which hardware are you running? If it is a member of the 5k series th=
en
> you need to use the debug50 parameter.
Yeah, it is, a 5300. I'll try that and get back to you.
Jan.
--=20
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
Zitat von reinette chatre <[email protected]>:
> On Wed, 2009-02-11 at 18:22 -0800, reinette chatre wrote:
>> On Wed, 2009-02-11 at 15:09 -0800, Jan Schneider wrote:
>> > Zitat von Jan Schneider <[email protected]>:
>> >
>> > > Zitat von reinette chatre <[email protected]>:
>> > >
>> > >> On Tue, 2009-02-10 at 03:19 -0800, Jan Schneider wrote:
>> > >>> Zitat von Jan Schneider <[email protected]>:
>> > >>>
>> > >>>> Zitat von Jan Schneider <[email protected]>:
>> > >>>>
>> > >>>>> Zitat von G=C3=A1bor Stefanik <[email protected]>:
>> > >>>>>
>> > >>>>>> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider =20
>> <[email protected]> wrote:
>> > >>>>>>> Zitat von reinette chatre <[email protected]>:
>> > >>>>>>>
>> > >>>>>>>> On Fri, 2009-02-06 at 14:31 -0800, Jan Schneider wrote:
>> > >>>>>>>>>
>> > >>>>>>>>> I've seen in a post from January that someone already ha=
d
>> > >>>>>>>>> this problem
>> > >>>>>>>>> but couldn't reproduce it.
>> > >>>>>>>>> I can't reliably reproduce, but I see this more often =20
>> than I like.
>> > >>>>>>>>> When this happens, it usually doesn't help to reload the=
kernel
>> > >>>>>>>>> module. Sometimes it helps to use the rfkill switch thou=
gh.
>> > >>>>>>>>>
>> > >>>>>>>>> Here's a log with debug=3D0x43fff:
>> > >>>>>>>>
>> > >>>>>>>> It does not seem as though your driver is compiled with =20
>> debug support.
>> > >>>>>>>> You can confirm that by looking at the version number of =
=20
>> the driver
>> > >>>>>>>> printed when it loads ... it should have a "d" in it =20
>> 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 complet=
e
>> > >>>>>>>> event log of
>> > >>>>>>>> the uCode error.
>> > >>>>>>>
>> > >>>>>>> Enabling debug didn't help:
>> > >>>>>>>
>> > >>>>>>> Feb 7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(=
R)
>> > >>>>>>> Wireless 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=
device:
>> > >>>>>>> iwl-phy0::rad
>> > >>>>>>> io
>> > >>>>>>> Feb 8 18:40:53 tank kernel: [77585.030765] Registered led=
device:
>> > >>>>>>> iwl-phy0::ass
>> > >>>>>>> oc
>> > >>>>>>> Feb 8 18:40:53 tank kernel: [77585.031602] Registered led=
device:
>> > >>>>>>> iwl-phy0::RX
>> > >>>>>>> Feb 8 18:40:53 tank kernel: [77585.032467] Registered led=
device:
>> > >>>>>>> iwl-phy0::TX
>> > >>>>>>
>> > >>>>>> No - enable IWLWIFI_DEBUG in your kernel config, then rebui=
ld 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
>> > >>>> "1.3.27kds".
>> > >>>
>> > >>> Anything else I can try to provide more information?
>> > >>
>> > >> Which hardware are you running? If it is a member of the 5k ser=
ies then
>> > >> you need to use the debug50 parameter.
>> > >
>> > > Yeah, it is, a 5300. I'll try that and get back to you.
>> >
>> > Now, this was was fun. I was just reading this mailing list, wonde=
ring
>> > why the driver still didn't crashed. When I left this mail folder,=
it
>> > happened. :-) Did anybody sneak some semantic analysis into the la=
test
>> > code? ;-) And how it crashed! I had to reboot and it keeps crashin=
g
>> > now after a few seconds activity at most.
>> >
>> > Anyway, here is the log, I hope the attachment makes it to the lis=
t.
>> > If you need more, I have more, but I figured this should contain a=
ll
>> > important information.
>>
>> Thank you very much for this log. Do you perhaps have a log that sho=
ws a
>> bit what is going on _before_ the SYSASSERT occurs?
>>
>> I passed this log on to our hardware folks for some information. At =
this
>> time, please consider opening a bug in
>> http://www.intellinuxwireless.org/bugzilla/ with your debug logs.
>>
>
> I got an answer back promptly because you encountered a problem that =
was
> fixed recently. Could you please try with the latest wireless-testing=
?
> Patch f50f70bb8d10fa407d7d0e6f4421b928f62357e3 "iwlwifi: fix FAT chan=
nel
> config for 5000 series" should fix this problem.
Unfortunately not. I created a ticket.
Jan.
--=20
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
Zitat von Jan Schneider <[email protected]>:
> Zitat von reinette chatre <[email protected]>:
>
>> On Tue, 2009-02-10 at 03:19 -0800, Jan Schneider wrote:
>>> Zitat von Jan Schneider <[email protected]>:
>>>
>>>> Zitat von Jan Schneider <[email protected]>:
>>>>
>>>>> Zitat von Gábor Stefanik <[email protected]>:
>>>>>
>>>>>> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <[email protected]> wrote:
>>>>>>> Zitat von reinette chatre <[email protected]>:
>>>>>>>
>>>>>>>> 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.
>>>>>>>
>>>>>>> Enabling debug didn't help:
>>>>>>>
>>>>>>> Feb 7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(R)
>>>>>>> Wireless WiFi
>>>>>>> Link
>>>>>>> AGN driver for Linux, 1.3.27kds
>>>>>>>
>>>>>>>
>>>>>>> /etc/modprobe.d/iwlagn:
>>>>>>>
>>>>>>> options iwlagn debug=0x43fff
>>>>>>>
>>>>>>>
>>>>>>> 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 device:
>>>>>>> iwl-phy0::rad
>>>>>>> io
>>>>>>> Feb 8 18:40:53 tank kernel: [77585.030765] Registered led device:
>>>>>>> iwl-phy0::ass
>>>>>>> oc
>>>>>>> Feb 8 18:40:53 tank kernel: [77585.031602] Registered led device:
>>>>>>> iwl-phy0::RX
>>>>>>> Feb 8 18:40:53 tank kernel: [77585.032467] Registered led device:
>>>>>>> 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
>>>> "1.3.27kds".
>>>
>>> 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.
>
> Yeah, it is, a 5300. I'll try that and get back to you.
Now, this was was fun. I was just reading this mailing list, wondering
why the driver still didn't crashed. When I left this mail folder, it
happened. :-) Did anybody sneak some semantic analysis into the latest
code? ;-) And how it crashed! I had to reboot and it keeps crashing
now after a few seconds activity at most.
Anyway, here is the log, I hope the attachment makes it to the list.
If you need more, I have more, but I figured this should contain all
important information.
Jan.
--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
Zitat von Jan Schneider <[email protected]>:
> Zitat von G=E1bor Stefanik <[email protected]>:
>
>> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <[email protected]> wrote:
>>> Zitat von reinette chatre <[email protected]>:
>>>
>>>> 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 pr=
oblem
>>>>> but couldn't reproduce it.
>>>>> I can't reliably reproduce, but I see this more often than I like=
=2E
>>>>> 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=3D0x43fff:
>>>>
>>>> It does not seem as though your driver is compiled with debug supp=
ort.
>>>> You can confirm that by looking at the version number of the drive=
r
>>>> printed when it loads ... it should have a "d" in it like "1.2.26k=
ds".
>>>> Could you please recompile the driver with debug support (IWLWIFI_=
DEBUG)
>>>> and rerun your test? This will provide us with a complete event l=
og of
>>>> the uCode error.
>>>
>>> Enabling debug didn't help:
>>>
>>> Feb 7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(R) Wirele=
ss 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: Mi=
crocode
>>> SW er
>>> ror detected. Restarting 0x2000000.
>>> Feb 8 18:40:53 tank kernel: [77585.029747] Registered led device:
>>> iwl-phy0::rad
>>> io
>>> Feb 8 18:40:53 tank kernel: [77585.030765] Registered led device:
>>> iwl-phy0::ass
>>> oc
>>> Feb 8 18:40:53 tank kernel: [77585.031602] Registered led device:
>>> iwl-phy0::RX
>>> Feb 8 18:40:53 tank kernel: [77585.032467] Registered led device:
>>> 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".
Jan.
--=20
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
On Tue, 2009-02-10 at 03:19 -0800, Jan Schneider wrote:
> Zitat von Jan Schneider <[email protected]>:
>=20
> > Zitat von Jan Schneider <[email protected]>:
> >
> >> Zitat von G=C3=A1bor Stefanik <[email protected]>:
> >>
> >>> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <[email protected]> wro=
te:
> >>>> Zitat von reinette chatre <[email protected]>:
> >>>>
> >>>>> 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
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
On Wed, 2009-02-11 at 18:22 -0800, reinette chatre wrote:
> On Wed, 2009-02-11 at 15:09 -0800, Jan Schneider wrote:
> > Zitat von Jan Schneider <[email protected]>:
> >=20
> > > Zitat von reinette chatre <[email protected]>:
> > >
> > >> On Tue, 2009-02-10 at 03:19 -0800, Jan Schneider wrote:
> > >>> Zitat von Jan Schneider <[email protected]>:
> > >>>
> > >>>> Zitat von Jan Schneider <[email protected]>:
> > >>>>
> > >>>>> Zitat von G=C3=A1bor Stefanik <[email protected]>:
> > >>>>>
> > >>>>>> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <[email protected]=
> wrote:
> > >>>>>>> Zitat von reinette chatre <[email protected]>:
> > >>>>>>>
> > >>>>>>>> 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 tha=
n I like.
> > >>>>>>>>> When this happens, it usually doesn't help to reload the =
kernel
> > >>>>>>>>> module. Sometimes it helps to use the rfkill switch thoug=
h.
> > >>>>>>>>>
> > >>>>>>>>> Here's a log with debug=3D0x43fff:
> > >>>>>>>>
> > >>>>>>>> It does not seem as though your driver is compiled with de=
bug support.
> > >>>>>>>> You can confirm that by looking at the version number of t=
he 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.
> > >>>>>>>
> > >>>>>>> Enabling debug didn't help:
> > >>>>>>>
> > >>>>>>> Feb 7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(R=
)
> > >>>>>>> Wireless 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 =
device:
> > >>>>>>> iwl-phy0::rad
> > >>>>>>> io
> > >>>>>>> Feb 8 18:40:53 tank kernel: [77585.030765] Registered led =
device:
> > >>>>>>> iwl-phy0::ass
> > >>>>>>> oc
> > >>>>>>> Feb 8 18:40:53 tank kernel: [77585.031602] Registered led =
device:
> > >>>>>>> iwl-phy0::RX
> > >>>>>>> Feb 8 18:40:53 tank kernel: [77585.032467] Registered led =
device:
> > >>>>>>> iwl-phy0::TX
> > >>>>>>
> > >>>>>> No - enable IWLWIFI_DEBUG in your kernel config, then rebuil=
d 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
> > >>>> "1.3.27kds".
> > >>>
> > >>> Anything else I can try to provide more information?
> > >>
> > >> Which hardware are you running? If it is a member of the 5k seri=
es then
> > >> you need to use the debug50 parameter.
> > >
> > > Yeah, it is, a 5300. I'll try that and get back to you.
> >=20
> > Now, this was was fun. I was just reading this mailing list, wonder=
ing
> > why the driver still didn't crashed. When I left this mail folder, =
it
> > happened. :-) Did anybody sneak some semantic analysis into the lat=
est
> > code? ;-) And how it crashed! I had to reboot and it keeps crashing
> > now after a few seconds activity at most.
> >=20
> > Anyway, here is the log, I hope the attachment makes it to the list=
=2E
> > If you need more, I have more, but I figured this should contain al=
l
> > important information.
>=20
> Thank you very much for this log. Do you perhaps have a log that show=
s a
> bit what is going on _before_ the SYSASSERT occurs?=20
>=20
> I passed this log on to our hardware folks for some information. At t=
his
> time, please consider opening a bug in
> http://www.intellinuxwireless.org/bugzilla/ with your debug logs.
>=20
I got an answer back promptly because you encountered a problem that wa=
s
fixed recently. Could you please try with the latest wireless-testing?
Patch f50f70bb8d10fa407d7d0e6f4421b928f62357e3 "iwlwifi: fix FAT channe=
l
config for 5000 series" should fix this problem.
Reinette
Zitat von reinette chatre <[email protected]>:
> 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.
Enabling debug didn't help:
Feb 7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(R) Wireless
WiFi Link
AGN driver for Linux, 1.3.27kds
/etc/modprobe.d/iwlagn:
options iwlagn debug=0x43fff
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 device:
iwl-phy0::rad
io
Feb 8 18:40:53 tank kernel: [77585.030765] Registered led device:
iwl-phy0::ass
oc
Feb 8 18:40:53 tank kernel: [77585.031602] Registered led device:
iwl-phy0::RX
Feb 8 18:40:53 tank kernel: [77585.032467] Registered led device:
iwl-phy0::TX
Jan.
--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <[email protected]> wrote:
> Zitat von reinette chatre <[email protected]>:
>
>> 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.
>
> Enabling debug didn't help:
>
> Feb 7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(R) Wireless WiFi
> Link
> AGN driver for Linux, 1.3.27kds
>
>
> /etc/modprobe.d/iwlagn:
>
> options iwlagn debug=0x43fff
>
>
> 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 device:
> iwl-phy0::rad
> io
> Feb 8 18:40:53 tank kernel: [77585.030765] Registered led device:
> iwl-phy0::ass
> oc
> Feb 8 18:40:53 tank kernel: [77585.031602] Registered led device:
> iwl-phy0::RX
> Feb 8 18:40:53 tank kernel: [77585.032467] Registered led device:
> iwl-phy0::TX
>
> Jan.
>
> --
> Do you need professional PHP or Horde consulting?
> http://horde.org/consulting/
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
No - enable IWLWIFI_DEBUG in your kernel config, then rebuild the
kernel (or at least the iwlwifi modules).
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
On Wed, 2009-02-11 at 15:09 -0800, Jan Schneider wrote:
> Zitat von Jan Schneider <[email protected]>:
>=20
> > Zitat von reinette chatre <[email protected]>:
> >
> >> On Tue, 2009-02-10 at 03:19 -0800, Jan Schneider wrote:
> >>> Zitat von Jan Schneider <[email protected]>:
> >>>
> >>>> Zitat von Jan Schneider <[email protected]>:
> >>>>
> >>>>> Zitat von G=C3=A1bor Stefanik <[email protected]>:
> >>>>>
> >>>>>> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <[email protected]> =
wrote:
> >>>>>>> Zitat von reinette chatre <[email protected]>:
> >>>>>>>
> >>>>>>>> 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 ke=
rnel
> >>>>>>>>> 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 debu=
g 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=
=2E2.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.
> >>>>>>>
> >>>>>>> Enabling debug didn't help:
> >>>>>>>
> >>>>>>> Feb 7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(R)
> >>>>>>> Wireless 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 de=
vice:
> >>>>>>> iwl-phy0::rad
> >>>>>>> io
> >>>>>>> Feb 8 18:40:53 tank kernel: [77585.030765] Registered led de=
vice:
> >>>>>>> iwl-phy0::ass
> >>>>>>> oc
> >>>>>>> Feb 8 18:40:53 tank kernel: [77585.031602] Registered led de=
vice:
> >>>>>>> iwl-phy0::RX
> >>>>>>> Feb 8 18:40:53 tank kernel: [77585.032467] Registered led de=
vice:
> >>>>>>> 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
> >>>> "1.3.27kds".
> >>>
> >>> 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.
> >
> > Yeah, it is, a 5300. I'll try that and get back to you.
>=20
> Now, this was was fun. I was just reading this mailing list, wonderin=
g
> why the driver still didn't crashed. When I left this mail folder, it
> happened. :-) Did anybody sneak some semantic analysis into the lates=
t
> code? ;-) And how it crashed! I had to reboot and it keeps crashing
> now after a few seconds activity at most.
>=20
> Anyway, here is the log, I hope the attachment makes it to the list.
> If you need more, I have more, but I figured this should contain all
> important information.
Thank you very much for this log. Do you perhaps have a log that shows =
a
bit what is going on _before_ the SYSASSERT occurs?=20
I passed this log on to our hardware folks for some information. At thi=
s
time, please consider opening a bug in
http://www.intellinuxwireless.org/bugzilla/ with your debug logs.
Thank you
Reinette
Zitat von G=E1bor Stefanik <[email protected]>:
> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <[email protected]> wrote:
>> Zitat von reinette chatre <[email protected]>:
>>
>>> 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 pro=
blem
>>>> 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=3D0x43fff:
>>>
>>> It does not seem as though your driver is compiled with debug suppo=
rt.
>>> 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.26kd=
s".
>>> Could you please recompile the driver with debug support (IWLWIFI_D=
EBUG)
>>> and rerun your test? This will provide us with a complete event lo=
g of
>>> the uCode error.
>>
>> Enabling debug didn't help:
>>
>> Feb 7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(R) Wireles=
s 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: Mic=
rocode
>> SW er
>> ror detected. Restarting 0x2000000.
>> Feb 8 18:40:53 tank kernel: [77585.029747] Registered led device:
>> iwl-phy0::rad
>> io
>> Feb 8 18:40:53 tank kernel: [77585.030765] Registered led device:
>> iwl-phy0::ass
>> oc
>> Feb 8 18:40:53 tank kernel: [77585.031602] Registered led device:
>> iwl-phy0::RX
>> Feb 8 18:40:53 tank kernel: [77585.032467] Registered led device:
>> 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.
Jan.
--=20
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
Zitat von Jan Schneider <[email protected]>:
> Zitat von Jan Schneider <[email protected]>:
>
>> Zitat von G=E1bor Stefanik <[email protected]>:
>>
>>> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <[email protected]> wrote=
:
>>>> Zitat von reinette chatre <[email protected]>:
>>>>
>>>>> 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 p=
roblem
>>>>>> but couldn't reproduce it.
>>>>>> I can't reliably reproduce, but I see this more often than I lik=
e.
>>>>>> 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=3D0x43fff:
>>>>>
>>>>> It does not seem as though your driver is compiled with debug sup=
port.
>>>>> You can confirm that by looking at the version number of the driv=
er
>>>>> printed when it loads ... it should have a "d" in it like "1.2.26=
kds".
>>>>> 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.
>>>>
>>>> Enabling debug didn't help:
>>>>
>>>> Feb 7 00:04:40 tank kernel: [ 2769.084395] iwlagn: Intel(R) Wirel=
ess 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: M=
icrocode
>>>> SW er
>>>> ror detected. Restarting 0x2000000.
>>>> Feb 8 18:40:53 tank kernel: [77585.029747] Registered led device:
>>>> iwl-phy0::rad
>>>> io
>>>> Feb 8 18:40:53 tank kernel: [77585.030765] Registered led device:
>>>> iwl-phy0::ass
>>>> oc
>>>> Feb 8 18:40:53 tank kernel: [77585.031602] Registered led device:
>>>> iwl-phy0::RX
>>>> Feb 8 18:40:53 tank kernel: [77585.032467] Registered led device:
>>>> 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".
Anything else I can try to provide more information?
Jan.
--=20
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/