[Gutsy] IPW2200 driver 100% CPU usage

[tlvince]

I am having problems with my wireless connection (IPW2200) after upgrading to Gutsy (it was fine in Feisty)

Sometimes the computer will boot fine, but the wireless doesn't connect

Sometimes the computer will boot slowly and the wireless will appear connected, but have no connectivity and the IPW2200/0 process will use 80-100% CPU usage

Other times it will work fine. A reboot *sometimes* solves the problem, although it can be many reboots and cold power off's until the wireless works correctly.

I don't know how I can log this problem, but if someone can explain to me how to, I will.

[Pádraig Brady (p-draigbrady)]

I notice this with ipw2200 on Fedora 7 also.
If you unload the ipw2200 module and reload it,
the cpu spinning stops.

[Pádraig Brady (p-draigbrady)]

Looks like an upstream issue alright. See also:
https://bugzilla.novell.com/show_bug.cgi?id=220790

[tlvince (tlvince)]

At the moment, I "unload and reload the modules" at boot time by turning off/on the wireless using the button on the front of the laptop.

The novell bugzilla shows the issue has been solved in a new version of ipw2200 driver. How can I update on Ubuntu?

[Michael Nagel (nailor)]

its marked resolved in the mentioned bugtracker. have you still problems?

[tlvince (tlvince)]

It seems to affect me sporadically, though I haven't noticed it for a while. Has the driver been updated in the Ubuntu Packages?

[Leann Ogasawara (leannogasawara)]

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.

[Ken Arnold (kenneth-arnold)]

I got this today on intrepid 2.6.27-6-generic. First time I've seen it, but same symptoms: I get the usual (for me, after upgrading to intrepid)

 ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.

followed by the unusual (but mentioned in the bug report):

 ipw2200: Failed to send ASSOCIATE: Already sending a command.

And it's busy-looping. Removing the module stops it, and reloading the module makes everything work fine.

[cyphax (r-elemans2)]

Occasionally (every few minutes), I see this process ("ipw2200/0") hog resources for 20 or so seconds. Everything becomes choppy (mouse movement, any sound that's playing) so this is unfortunately very much noticeable.
It's a fresh 8.10 install, kernel 2.6.27-7-generic
This issue started showing up some days ago in 8.04.
I'm not connected to a WiFi-network by the way.

[Leann Ogasawara (leannogasawara)]

Hi Guys,

Can you try installing the linux-backports-modules-intrepid package? It contains and updated compat-wireless stack and I'm curious if they may help with the issue you are seeing. If it still occurs after installing the linux-backports-modules-intrepid package, then per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

It would also be good to wait to capture the dmesg output until after you witness the bug. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[Michael Nagel (nailor)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!