Hi,
I noticed some weird firmware restarts with iwl3945 lately.
-----------------
iwl3945: Microcode SW error detected. Restarting 0x82000008.
iwl3945: Error Reply type 0x00000005 cmd REPLY_SCAN_CMD (0x80) seq
0x4419 ser 0x0000004B
iwl3945: Can't stop Rx DMA.
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
iwl3945: Microcode SW error detected. Restarting 0x82000008.
iwl3945: Error Reply type 0x00000005 cmd REPLY_LEDS_CMD (0x48) seq
0x0408 ser 0x0000004B
iwl3945: Can't stop Rx DMA.
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
iwl3945: Microcode SW error detected. Restarting 0x82000008.
iwl3945: Error Reply type 0x00000005 cmd REPLY_LEDS_CMD (0x48) seq
0x0408 ser 0x0000004B
iwl3945: Can't stop Rx DMA.
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
iwl3945: Microcode SW error detected. Restarting 0x82000008.
iwl3945: Error Reply type 0x00000005 cmd REPLY_LEDS_CMD (0x48) seq
0x0407 ser 0x0000004B
iwl3945: Can't stop Rx DMA.
---------------
There seem to be random (can not reproduce them always) but the only
way to get the wireless working is to
1) unload the module
2) go to another room
3) load module
4) connect to AP
5) go back to the room and it works
If I stay in the same room after reloading the module the firmware
crashes happen again.
I have no output with the event log because they happen randomly and I
cannot reproduce them.
Any ideas?
Each bit enables a specific driver area/topic/type of debug messages ..=
=2E bits are defined by IWL_DL_ #defines in iwl-3945-debug.h ... 0x43ff=
f gives a nice cross section of debug messages without being *overly* v=
erbose.
-- Ben --
> -----Original Message-----
> From: [email protected]=20
> [mailto:[email protected]] On=20
> Behalf Of Stefanik G=E1bor
> Sent: Monday, July 14, 2008 2:11 PM
> To: Cahill, Ben M
> Cc: linux-wireless; ipw3945-devel
> Subject: Re: [ipw3945-devel] iwl3945 random firmware crashes
>=20
> On Mon, Jul 14, 2008 at 8:05 PM, Cahill, Ben M=20
> <[email protected]> wrote:
> > Try loading driver using module param:
> >
> > debug=3D0x43fff
> >
> > This will provide more information in the log, including an=20
> event log=20
> > (where you see "Microcode SW Error detected" in your log, you would=
=20
> > have captured Event Log if you had the debug=3D0x43fff setting).
> >
> > -- Ben --
>=20
> Just a question: Why are we using cryptic hex IDs for the=20
> debug setting? Is there a specific reason for this, or just=20
> noone has yet included proper modparams for the various=20
> debugging settings?
>=20
> --
> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
>=20
> --------------------------------------------------------------
> -----------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source=20
> project, along with a healthy diet, reduces your potential=20
> for chronic lameness and boredom. Vote Now at=20
> http://www.sourceforge.net/community/cca08
> _______________________________________________
> Ipw3945-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ipw3945-devel
>=20
On Mon, Jul 14, 2008 at 8:05 PM, Cahill, Ben M <[email protected]> wrote:
> Try loading driver using module param:
>
> debug=0x43fff
>
> This will provide more information in the log, including an event log
> (where you see "Microcode SW Error detected" in your log, you would have
> captured Event Log if you had the debug=0x43fff setting).
will try to capture the event log when it happens again.
On Mon, Jul 14, 2008 at 8:05 PM, Cahill, Ben M <[email protected]> wrote:
> Try loading driver using module param:
>
> debug=0x43fff
>
> This will provide more information in the log, including an event log
> (where you see "Microcode SW Error detected" in your log, you would have
> captured Event Log if you had the debug=0x43fff setting).
It happend again and this time I captured the log.
Debug output including event log is attached.
On Mon, Jul 14, 2008 at 8:05 PM, Cahill, Ben M <[email protected]> wrote:
> Try loading driver using module param:
>
> debug=0x43fff
>
> This will provide more information in the log, including an event log
> (where you see "Microcode SW Error detected" in your log, you would have
> captured Event Log if you had the debug=0x43fff setting).
>
> -- Ben --
Just a question: Why are we using cryptic hex IDs for the debug
setting? Is there a specific reason for this, or just noone has yet
included proper modparams for the various debugging settings?
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
Try loading driver using module param:
debug=0x43fff
This will provide more information in the log, including an event log
(where you see "Microcode SW Error detected" in your log, you would have
captured Event Log if you had the debug=0x43fff setting).
-- Ben --
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On
> Behalf Of drago01
> Sent: Monday, July 14, 2008 7:38 AM
> To: linux-wireless; ipw3945-devel
> Subject: [ipw3945-devel] iwl3945 random firmware crashes
>
> Hi,
> I noticed some weird firmware restarts with iwl3945 lately.
> -----------------
> iwl3945: Microcode SW error detected. Restarting 0x82000008.
> iwl3945: Error Reply type 0x00000005 cmd REPLY_SCAN_CMD (0x80) seq
> 0x4419 ser 0x0000004B
> iwl3945: Can't stop Rx DMA.
> Registered led device: iwl-phy0:radio
> Registered led device: iwl-phy0:assoc
> Registered led device: iwl-phy0:RX
> Registered led device: iwl-phy0:TX
> iwl3945: Microcode SW error detected. Restarting 0x82000008.
> iwl3945: Error Reply type 0x00000005 cmd REPLY_LEDS_CMD (0x48) seq
> 0x0408 ser 0x0000004B
> iwl3945: Can't stop Rx DMA.
> Registered led device: iwl-phy0:radio
> Registered led device: iwl-phy0:assoc
> Registered led device: iwl-phy0:RX
> Registered led device: iwl-phy0:TX
> iwl3945: Microcode SW error detected. Restarting 0x82000008.
> iwl3945: Error Reply type 0x00000005 cmd REPLY_LEDS_CMD (0x48) seq
> 0x0408 ser 0x0000004B
> iwl3945: Can't stop Rx DMA.
> Registered led device: iwl-phy0:radio
> Registered led device: iwl-phy0:assoc
> Registered led device: iwl-phy0:RX
> Registered led device: iwl-phy0:TX
> iwl3945: Microcode SW error detected. Restarting 0x82000008.
> iwl3945: Error Reply type 0x00000005 cmd REPLY_LEDS_CMD (0x48) seq
> 0x0407 ser 0x0000004B
> iwl3945: Can't stop Rx DMA.
> ---------------
> There seem to be random (can not reproduce them always) but
> the only way to get the wireless working is to
> 1) unload the module
> 2) go to another room
> 3) load module
> 4) connect to AP
> 5) go back to the room and it works
>
> If I stay in the same room after reloading the module the
> firmware crashes happen again.
>
> I have no output with the event log because they happen
> randomly and I cannot reproduce them.
>
> Any ideas?
>
> --------------------------------------------------------------
> -----------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source
> project, along with a healthy diet, reduces your potential
> for chronic lameness and boredom. Vote Now at
> http://www.sourceforge.net/community/cca08
> _______________________________________________
> Ipw3945-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ipw3945-devel
>