ipw2200 kernel module fails in intrepid

[przemo24555]

When system starts everything works perfect.
After a while my Intel® PRO/Wireless 2200BG starts losing sinal (5% or less).
Sometimes the connection fails and it's not possible to reconnect (network manager asks for a
wpa password and tries to reconnect). After reloading ipw2200 everything works fine (network manager
DOESN'T ask for password and connects with network).

It occures when many ip connections are established !

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.10
Release: 8.10
Codename: intrepid

dmesg |tail -n 14
[42641.709930] ipw2200: Unable to load firmware: -12
[42641.710005] ipw2200: Unable to load firmware: -12
[42641.710011] ipw2200: Failed to up device
[42876.688715] ipw2200 0000:02:04.0: PCI INT A disabled
[42882.142095] ieee80211: 802.11 data/management/control stack, git-1.1.13
[42882.142110] ieee80211: Copyright (C) 2004-2005 Intel Corporation <email address hidden>
[42882.177855] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
[42882.177871] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[42882.180613] ipw2200 0000:02:04.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[42882.183151] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[42882.185239] firmware: requesting ipw2200-bss.fw
[42882.413591] ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)
[42896.608022] eth1: no IPv6 routers present
[43091.034331] CCMP: decrypt failed: STA=00:21:29:b6:1a:56

uname -r
2.6.27-7-generic

lsmod |grep ipw2200
ipw2200 151244 0
ieee80211 38088 1 ipw2200

 lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03)
02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
02:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
02:06.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
02:0e.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)

[Anthony Noto (angusthefuzz)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, as attachments, as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Anthony Noto (angusthefuzz)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[przemo24555 (przemo2)]

I've compiled a custom kernel using sources from kernel.org and it looks fine, signal strength keeps between 73-90%. Any suggestions?

[Oliver Joos (oliver-joos)]

@przemo24555: I think I have the same problem. What did you customize in your kernel?

Could you please check if your bug is a duplicate of one of these:
https://bugs.launchpad.net/bugs/264104
https://bugs.launchpad.net/bugs/293426
https://bugs.launchpad.net/bugs/295414 (see my comments there)

[przemo24555 (przemo2)]

It's not a duplicate

[Launchpad Janitor (janitor)]

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.

[Jonatan Schroeder (jonatanschroeder)]

I have also been having this problem occasionally (I haven't identified the situations for which it happens). This normally happens when I resume from suspend, but it is doesn't happen every time. Actually, when it happens after I resume from suspend, I just suspend and resume again, and the network is back. I haven't tried to reload ipw2200, will try next time it happens.

$ uname -a
Linux ubuntujs 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 19:49:51 UTC 2009 i686 GNU/Linux

Using Ubuntu Jaunty 9.04.

By the way, any news on this bug? Nobody assigned to it for almost 7 months, no new activity, is anyone working on it?

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.