ipw3945 hangs intermittently on Thinkpad T61

Thank you for taking the time to report this bug and helping to make Ubuntu better. There have been a couple of kernel updates since you initially reported this bug. Are you still having an issue? Thanks in advance.

Brian,
I just experienced it again a few minutes ago. I'm running linux-image-2.6.22-12-generic.

Same for my T61....

I have been running Feisty for about 3 months all without troubles, now I have updated to Gutsy
(2.6.22-14-generic) and now my ipw3945 lockups the ThinkPad completely every 4-6 hours.
After displaying those kernel messages (running tail -f on kern.log) laptop completely dies in 1-2 minutes.
(hardware lockup, can be only reset with holding power button for 5 secons)

I would change this bug Importance to High (if I could), because it makes my T61 total useless for me :(
I can't use it in everyday work now. I have 2 options - a) Re-intall back to Feisty b) Use that other evil "W" OS

Same problem here with my T61p and Gutsy. It locks up randomly every few hours or so.
There's a silly workaround in here:
https://bugs.launchpad.net/ipw3945/+bug/134515

But it's no fix.

I get this too on my T61 every now and then. I never had the patience to wait 1-2 minutes to see whether my laptop will freeze hard, but at this point (1) ifconfig/iwconfig hangs on startup, and (2) sudo hangs on startup without asking for a password, giving me no chance to rmmod or try to restart the ipw3945 daemon. The only cure is to reboot with Alt+SysRq, as regular reboots also hang.

I can confirm problems with gutsy and the 3945 on a T61. Some days it will stay connected the whole night.. others it will go into its weird state 3 times. Once it has done it, it seems to cause the whole machine to crash slowly if I attempt to reconnect. attempting to rmmod the ipw3945 hangs forever (+D state), new processes wont launch, etc. I'm forced to hold the power button down for 10 seconds to reboot.

This is a regression, wifi was working pretty well in feisty. (I installed feisty fresh, and then upgraded to gutsy)

I have confirmed the bug with WPA PSK, and WPA2 at work. I haven't connected to any open networks to confirm it in open mode.

I have all the IRQ's in the bios set to "auto" instead of factory default 11, which makes the laptop much more stable otherwise in linux.

Same problem here with a DELL Latitude D630 and gutsy Gibbon (Linux 2.6.22-14-generic with Intel Corporation PRO/Wireless 3945ABG)

After large file transfer (x GB) the interface gets disconnected and the following errors appears in dmesg (see attachment), I have to restart the computer to get the interface working.

I tried with and without encryption (WEP and open mode) the problem is the same.

interrupts

lshw

I have the same problem. I decided to wipe out ubuntu 7.10 and give Fedora 8 a try. It uses iwl3945 instead of ipw3945. After add options disable_hw_scan=1 to modprobe.conf, it worked to some extend.

My understanding is that ubuntu 7.10 shipped with both iwl3945 and ipw3945 but use iwl3945 as default. Can anybody still have ubuntu7.10 on their machine try to use iwl3945 see if it fixed the problem?

I've got the same with 7.10 on an Acer Aspire. Nothing further to add,except confirming that:

- I didn't notice any such problem on 7.04.

- Both iwl3945 and ipw3945 show the same behaviour.

I went back to Ubuntu 7.10 as Fedora doesn't feel as polished. I installed real time flavor of the kernel. It have been running for 4 days without a crash.

sudo apt-get install linux-rt

Then reboot, select the realtime kernel

Hardware encryption seems to improve stability for the iwl3945 module.

put
    options iwl3945 hwcrypto=1
in a file in /etc/modutils.d (ex create a file called iwl3945)

With default software-crypto my test-computer would hang randomly after transmitting anywhere between a few MB up to 1 or 2 GB. With hardware-crypto enabled I just completed a test-transfer of 40GB+

Funny it's not been mentioned yet in this thread, but the iwlwifi drivers in gutsy are rather old. Changelogs from intellinuxwireless.org describe heaps of serious bugs that have been squashed recently. Those fixes should IMHO make it into the next revision of the linux-ubuntu-modules package. There's also a lot of annoying bugs in gutsy's current kernel, so maybe there's a hope for an updated kernel and modules shortly.

I ended up building my own kernel and building the recent iwl drivers which seems to fix the hang up all together. Hopefully the latest iwl drivers will be incorporated into the latest kernel as I couldn't wait any longer.

Same problem with a Dell Inspiron 1520. It hangs the wireless every few hours and hungs the system afterwards.
My cards PCI ID is: 8086:4222

Same problem with Dell 1420n laptop after I installed Gutsy. The fix is to use the old iwl3945 and blacklist the ipw3945, this does fix the stability issue but it's slower. I was maxing out 8100kbps dowloads with the ipw3945 but then it drops connection after a few minutes. Now with the iwl3945 I'm only maxing 1204kbps but it's stable a trade off that's not noticed unless you update or apt while on wireless. Here's the fix from dells wiki http://linux.dell.com/wiki/index.php/Ubuntu_7.10/Issues/ipw3945_Wireless_Network_Module_Issues

I have the same problem on my Lenovo T61.

Same problem here. ipw3945 on Dell Latitude D830 Intel Corporation PRO/Wireless 3945ABG Network Connection

I have the same problem with a HP DV6500T

I have not had this problem since the move to the 'iwl3945' driver with the release of 8.04. I believe it is fixed.

Echo: ipw3945 and iwl3945 *are* *not* the same driver, so this is not fixed, you are using a different driver.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.