2.6.24-rc8: iwl3945 gets stuck

2.6.24-rc8: iwl3945 gets stuck

[Harald Dunkel]

Hi folks,

I've got some problem with iwl3945: If I run

	xset dpms force off

for the local display while some network traffic is running, then
the iwl3945 gets stuck. Syslog says:

Jan 23 19:29:41 daffy kernel: iwl3945: Microcode SW error detected.  Restarting 0x2000008.
Jan 23 19:29:43 daffy kernel: iwl3945: Can't stop Rx DMA.

The same happens if the Xserver runs into the configured timeout.
If the network is idle, then there is no such problem, as it seems.
If the Xserver is not running, and if the console runs into dpms,
then iwl3945 seems to stay alive, too, but to be sure I would need
some command similar to the xset shown above.

If the net is stuck (and if I am lucky), then I can rmmod iwl3945 and
load it again, but sometimes I have to reboot.

The machine is a Dell laptop xps m1330 running 64bit kernel 2.6.24-rc8.
Encryption is wpa/psk. iwl3945 is loaded without any special options.
At boot time there were no unusual call traces or something like this.

The configured XWindow driver is "nv", but I could reproduce this with
NVidia's proprietary "nvidia" driver, too. The vga device is a "nVidia
Corporation GeForce 8400M GS".

I would be glad to help to track this down.


Regards

Harri

RE: 2.6.24-rc8: iwl3945 gets stuck

[Chatre, Reinette]

On ,  Harald Dunkel wrote:

> I've got some problem with iwl3945: If I run
> 
> 	xset dpms force off
> 
> for the local display while some network traffic is running, then
> the iwl3945 gets stuck. Syslog says:
> 
> Jan 23 19:29:41 daffy kernel: iwl3945: Microcode SW error
> detected.  Restarting 0x2000008.
> Jan 23 19:29:43 daffy kernel: iwl3945: Can't stop Rx DMA.
> 

Very strange. Would it be possible to load the module with
"debug=0x43fff"? This will capture a detailed event log and error log
from uCode, so we can see what caused the uCode error.

Also, could you please open a bug in our bug tracker
(http://www.bughost.org/bugzilla/) - this will make it easier to keep
all info together and get the right people to take a look at it.

Thanks

Reinette

Re: 2.6.24-rc8: iwl3945 gets stuck

[Harald Dunkel]

Chatre, Reinette wrote:
> 
> Very strange. Would it be possible to load the module with
> "debug=0x43fff"? This will capture a detailed event log and error log
> from uCode, so we can see what caused the uCode error.
> 

I will try. Is there some way to turn debug on and off after
the module has been loaded, e.g. by running

	echo 0x43fff >/proc/some/fancy/path

?


Regards

Harri

Re: 2.6.24-rc8: iwl3945 gets stuck

[Joonwoo Park]

On Sat, Jan 26, 2008 at 03:54:30PM +0100, Harald Dunkel wrote:
>
> I will try. Is there some way to turn debug on and off after
> the module has been loaded, e.g. by running
>
> 	echo 0x43fff >/proc/some/fancy/path
>
> ?

please build kernel with CONFIG_IWLWIFI_DEBUG=y
mount sysfs on /sys
echo 0x43fff > /sys/bus/pci/drivers/iwl3945/debug_level

Thanks,
Joonwoo

Re: 2.6.24-rc8: iwl3945 gets stuck

[Harald Dunkel]

Chatre, Reinette wrote:
> 
> Very strange. Would it be possible to load the module with
> "debug=0x43fff"? This will capture a detailed event log and error log
> from uCode, so we can see what caused the uCode error.
> 
> Also, could you please open a bug in our bug tracker
> (http://www.bughost.org/bugzilla/) - this will make it easier to keep
> all info together and get the right people to take a look at it.
> 

moving to bug tracker, see http://bughost.org/bugzilla/show_bug.cgi?id=1577 .
The requested debug output has been posted there, too.


Regards

Harri