intel wireless ipw3945 randomly disconnects

Here's the relevant syslog. The addresses/SSIDs have been changed to protect the innocent.

same here....
im using ipw3945, and wireless connection is lost after few minutes and i cannot connect wireless network again unless i reboot orr reload the ipw3945 module.
dmesg show this:
[ 130.056000] ipw3945: Error sending DAEMON: Already sending a synchronous daemon command
[ 320.776000] ipw3945: Error sending DAEMON: Already sending a synchronous daemon command
[ 320.776000] ipw3945: Error sending DAEMON: Already sending a synchronous daemon command

some more dmesg outputs:

eyal@m:~$ dmesg | grep ipw3945
[ 18.264000] ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.2mp.ubuntu1
[ 18.264000] ipw3945: Copyright(c) 2003-2006 Intel Corporation
[ 18.268000] ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
[ 20.240000] ipw3945: Detected geography ABG (13 802.11bg channels, 23 802.11a channels)
[ 703.636000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[ 704.776000] ipw3945: Error sending cmd #07 to daemon: time out after 500ms.
[ 707.976000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
[ 708.476000] ipw3945: Error sending cmd #08 to daemon: time out after 500ms.
[ 708.976000] ipw3945: Error sending ADD_STA: time out after 500ms.
[ 709.476000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
[ 713.052000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[ 768.476000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[ 768.976000] ipw3945: Error sending LEDS_CMD: time out after 500ms.

I have the same problems, and a reasonably good way to get an error seems to be to either "get" or "put" a file using SFTP. Putting files on a server is especially risky -- I've had the network disconnect after uploading a single digital camera file (about a megabyte in size). Downloading ISO-files using SFTP "get" can also cause the problem. Can anyone else confirm this (if so, at least my problem could be related to bug 93581).

I get the same errors, intermittently, which can cause a complete or partial system freeze. At this point, things are pretty frustrating as I have no idea how to reproduce consistently the behaviour. It happens about once an hour or so.

Here is the message that pops up in syslog:

[10475.112000] ipw3945: Error sending DAEMON: Already sending a synchronous daemon command

Once I get the message, there is nothing I can do except reboot. :(

I have seemingly same issue. same dmsg as above. "link timed ou"t in daemon.log at the time of disconnection.

here's a reconnect script for ubuntu (remove/insert of the driver) that seems to work -- the sleep times are a bit random, doing it too quickly doesn't seem to work.

(see also also question https://answers.launchpad.net/ubuntu/+question/16550)

I have the same problem. It's a shame this bug couldn't be resolved prior to release of 7.10 or after the release. This is the only reason I have switched from Ubuntu 7.10 to Fedora 8. I will try Ubuntu again when 8.04 is released. This bug is important to me because I perform backups at night and can't rely on ipw3945 to work long enough for the backup to complete.

I have a friend with a Dell 1520 with this problem. I own a Lenovo X60s with the same wireless card and with no problems at all, so i don't understand what is happening. Today I've found the following page: http://linux.dell.com/wiki/index.php/Ubuntu_7.10/Issues/ipw3945_Wireless_Network_Module_Issues where they blacklist the module ipw3945 and load the iwl3945. I hope this solution fix the #@!%\&/ problem.

Thanks for that script, Franck. I got it to work on my system. It's nice because I can reconnect the wireless without rebooting which means I can keep all of my apps open. It's a nice workaround, but I still like to see a fix for this.

I couldn't get stock iwl3945 to work either with ubuntu 7.10's stock kernel, but the newer version in Ubuntu 8.04 (where it's the default) is working nicely so far, so now 8.04 is released upgrading is a solution for this bug.

I've been using the Hardy beta for a few weeks now and I haven't noticed any problems with the wireless connection. The random disconnecting seems to have stopped.

I am still having this issue (or at least I seem to be). I am using Hardy 64-bit, but I never had Gutsy installed on this machine.
Attaching a dmesg from right after it happened. I wanted to see if I could still suspend afterwards and I got a bunch of weird messages. Attaching a dmesg after resuming (which did not fix the issue). This happens completely randomly. Sometimes I'll go hours or days without it happening, other times, it seems to happen only a little while after booting. Let me know if you need more info from me.

03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)

dmesg after suspend/resume

As stated on http://ipw3945.sourceforge.net/, the ipw3945-driver is deprecated and all development has gone to the iwlwifi-project, found at http://intellinuxwireless.org/. So I think this issue won't be fixed anymore.

Hi All,

From the comments made here it seems this bug is resolved with the newer iwl3945 driver available in Hardy.

Jonathan, you commented that you are using the 4965 driver. If you could open a new bug report that would be great. It is helpful to the kernel team if bug reports target a specific issue against a specific set of hardware/drivers.

Finally against 2.6.22 this will be closed. It's unlikely that a fix for a deprecated set of ipw drivers will be made. And even though it looks like linux-ubuntu-modules-2.6.22 provides the iwlwifi drivers - the newer version of the iwlwifi drivers in Hardy will not likely be backported to Gutsy. Thanks.