FS#7709 - ipw3945 randomly breaks (no wireless extensions)

Attached to Project: Arch Linux
Opened by Christ Schlacta (aarcane) - Sunday, 29 July 2007, 23:13 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 22 April 2008, 03:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Critical
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Randomly during use, the device for ipw3945 (eth1) will suddenly decide to stop working. when this happens, the main symptom is that iwconfig eth1 reports no wireless extensions.

Additional info:
* package version(s)
* config and/or log files etc.
too many related packages to list, but I've run pacman -Syu within the last two days


Steps to reproduce:
use connection for a while, eth1 will die, and iwconfig will report no wireless extensions even though it did before
This task depends upon

Closed by  Aaron Griffin (phrakture)
Tuesday, 22 April 2008, 03:23 GMT
Reason for closing:  Deferred
Additional comments about closing:  Upstream bug. ipw3945 is deprecated
Comment by Thomas Bächler (brain0) - Tuesday, 31 July 2007, 14:04 GMT
Does this happen when you have lots of traffic? Can you look at what your logs said around the time it happened? Does reloading the ipw3945 module and restarting the ipw3945d fix the problem?
Comment by Christ Schlacta (aarcane) - Tuesday, 31 July 2007, 15:00 GMT
it can happen under lots of traffic, or under none at all (It happened last night while I was sleeping, there was little or no traffic)

also, the architecture should be changed, it happens under i686 as well.

Next time it happens I'll try reloading and restarting the daemon, but it's unpredictable.
Comment by Christ Schlacta (aarcane) - Tuesday, 31 July 2007, 15:05 GMT
Jul 31 07:27:09 ichigo ipw3945: Error sending cmd #07 to daemon: time out after 500ms.
Jul 31 07:27:11 ichigo ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
Jul 31 07:27:11 ichigo ipw3945: Error sending cmd #08 to daemon: time out after 500ms.
Jul 31 07:27:12 ichigo ipw3945: Error sending ADD_STA: time out after 500ms.
Jul 31 07:27:12 ichigo ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
Jul 31 07:28:11 ichigo ipw3945: Error sending LEDS_CMD: time out after 500ms.
Jul 31 07:28:12 ichigo ipw3945: Error sending LEDS_CMD: time out after 500ms.

The preceeding lines DID appear in my /var/log/everything.log durring the hours I was sleeping, they're the only ones, and I'm not sure they're related
Comment by Thomas Bächler (brain0) - Tuesday, 31 July 2007, 17:12 GMT
I got these messages earlier today under high traffic when my connection stopped working:

Jul 31 12:17:16 artin ipw3945: Error sending LEDS_CMD: time out after 500ms.
Jul 31 12:17:17 artin ipw3945: Microcode SW error detected. Restarting.
Jul 31 12:17:17 artin ipw3945: Can't stop Rx DMA.
Jul 31 12:17:17 artin ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
Jul 31 12:17:25 artin ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)

The last message was repeated until I stopped ipw3945d. I had to unload the module to make it work again.

I didn't check if iwconfig still showed the interface though, so this may be unrelated.

There is a new ipw3945 version out, I'll upload that later.
Comment by Witold Czaplewski (Witi) - Friday, 09 November 2007, 09:28 GMT
A month ago I had the same problem (and it still exists) with the new kernel module rtl8187 (I posted it in the german arch-forum [1]), which could be related to this issue.

I have a WPA encrypted WLAN and no problems under low/normal traffic (normal surfing and downloads). I can use it for hours.
My connection breaks after I start programs like rtorrent or amule, which open quite many parallel connections.

The most interesting part here is, that I can't unload the module (modprobe -r rtl8187). It freezes and I can see two other commands with a high load, which I can't kill:
4 root 15 -5 0 0 0 R 100 0.0 8:41.48 ksoftirqd/0
8160 root 20 0 3712 504 436 R 100 0.0 5:05.69 modprobe

I have to restart my system to solve this problem.

[1] http://forum.archlinux.de/?page=Postings;id=20;thread=7015
Comment by Juan Carlos Valero (eb3dgz) - Wednesday, 21 November 2007, 18:56 GMT
Apparently I'm affected by a variant of this bug. My equipment freeze using NFS mounted directory ONLY if I have the ipw3945 active (but not using, I'm connected to ethernet cable). This has been detected for anynone ?
Comment by Nathan Crandall (cactus.ed) - Friday, 04 January 2008, 01:28 GMT
I also had this problem with the ipw3945, swithching to iwlwifi fixed it. http://ipw3945.sourceforge.net/ says the ipw3945 project is deprecated, and development has been switched to the iwlwifi project - so it sounds like there won't be many bug fixes for ipw3945 from here on out.

Loading...