Bug 497522 - iwlagn unresponsive and cpu hog
Summary: iwlagn unresponsive and cpu hog
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-24 12:57 UTC by Jean-Philippe Dionne
Modified: 2009-06-11 14:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-11 14:57:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jean-Philippe Dionne 2009-04-24 12:57:54 UTC
Description of problem:

After a fresh boot or a return from suspend, iwlagn consume all the cpu and continuously logs the following messages 

Apr 24 08:11:13 jpdionne kernel: iwlagn: Microcode SW error detected.  Restarting 0x82000000.
Apr 24 08:11:13 jpdionne kernel: iwlagn: Error setting new RXON (-5)
Apr 24 08:11:16 jpdionne kernel: Registered led device: iwl-phy0:radio
Apr 24 08:11:16 jpdionne kernel: Registered led device: iwl-phy0:assoc
Apr 24 08:11:16 jpdionne kernel: Registered led device: iwl-phy0:RX
Apr 24 08:11:16 jpdionne kernel: Registered led device: iwl-phy0:TX

Reloading the iwlagn module will fix the problem.

Version-Release number of selected component (if applicable):

Kernel: 2.6.27.21-170.2.56.fc10.x86_64
Wireless card: Intel Corporation Wireless WiFi Link 5100

How reproducible:

The problem is not 100% reproductible.  I have seen it happened on two kind of wireless networks: 802.11b unencrypted and 802.11n WPA .

Steps to Reproduce:
1. Return from suspend
2. When the NetworkManager will start the network scan, the computer will become unresponsive.

Comment 1 John W. Linville 2009-04-24 14:12:44 UTC
Can you reproduce this on a 2.6.29-based kernel?

   yum --enablerepo=updates-test update kernel

Comment 2 John W. Linville 2009-06-11 14:57:38 UTC
Closed due to lack of response...


Note You need to log in before you can comment on or make changes to this bug.