Bug 608425 - iwlagn 0000:03:00.0: Microcode SW error detected. Restarting 0x2000000.
Summary: iwlagn 0000:03:00.0: Microcode SW error detected. Restarting 0x2000000.
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iwl6000-firmware
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: John W. Linville
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-27 13:37 UTC by David Kovalsky
Modified: 2014-03-31 23:45 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-06-29 19:59:57 UTC


Attachments (Terms of Use)

Description David Kovalsky 2010-06-27 13:37:43 UTC
This messages appeared in syslog:

kernel: iwlagn 0000:03:00.0: Microcode SW error detected.  Restarting 0x2000000.
kernel: Registered led device: iwl-phy0::radio
kernel: Registered led device: iwl-phy0::assoc
kernel: Registered led device: iwl-phy0::RX
kernel: Registered led device: iwl-phy0::TX

I haven't noticed any service degradation, I'm not even sure what triggered this, since I connected through SSH to the machine, but it had no traffic.

kernel-2.6.32-37.el6.x86_64

00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 06)
03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)


If relevant, the machine is Lenovo W510.

Comment 2 RHEL Product and Program Management 2010-06-27 14:02:53 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 John W. Linville 2010-06-29 19:59:57 UTC
Sounds like the firmware from Intel crashed and we recovered -- what else could we do?

Comment 4 David Kovalsky 2010-06-30 09:37:05 UTC
I though there might be a firmware update or adjustments how communication is done. If there's nothing that can be done, then I agree with CANTFIX :)

Thanks Jon!


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