linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Dunkel <harald.dunkel@t-online.de>
To: linux-wireless@vger.kernel.org
Cc: linville@tuxdriver.com, dhazelton@enter.net
Subject: 2.6.24-rc8: iwl3945 gets stuck
Date: Wed, 23 Jan 2008 20:45:16 +0100	[thread overview]
Message-ID: <4797994C.1090900@t-online.de> (raw)

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



             reply	other threads:[~2008-01-23 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23 19:45 Harald Dunkel [this message]
2008-01-25 17:04 ` 2.6.24-rc8: iwl3945 gets stuck Chatre, Reinette
2008-01-26 14:54   ` Harald Dunkel
2008-01-26 15:29     ` Joonwoo Park
2008-01-26 17:14   ` Harald Dunkel

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=4797994C.1090900@t-online.de \
    --to=harald.dunkel@t-online.de \
    --cc=dhazelton@enter.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).