Zitat von reinette chatre <reinette.chatre@xxxxxxxxx>:
On Tue, 2009-02-10 at 03:19 -0800, Jan Schneider wrote:
Zitat von Jan Schneider <jan@xxxxxxxxx>:
> Zitat von Jan Schneider <jan@xxxxxxxxx>:
>
>> Zitat von Gábor Stefanik <netrolller.3d@xxxxxxxxx>:
>>
>>> On Sun, Feb 8, 2009 at 7:23 PM, Jan Schneider <jan@xxxxxxxxx> wrote:
>>>> Zitat von reinette chatre <reinette.chatre@xxxxxxxxx>:
>>>>
>>>>> 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.
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
