Bug 680456

Summary: Update for iwl5000-firmware version 8.83.5.1
Product: Red Hat Enterprise Linux 6 Reporter: John W. Linville <linville>
Component: iwl5000-firmwareAssignee: John W. Linville <linville>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: ajb, amyagi, mishu, phil, sgruszka, smooge, snagar, syeghiay, tpelka, vbenes, woodard
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 680457 680458 (view as bug list) Environment:
Last Closed: 2012-10-09 12:44:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 682742    
Bug Blocks: 709522    
Attachments:
Description Flags
messages output from kernel none

Description John W. Linville 2011-02-25 16:17:35 UTC
...or later...

Version 8.83.5.1 of maintenance release uCode for IntelĀ® 5000AGN Series
Wi-Fi Adapters is now available for download from
http://intellinuxwireless.org/?n=Downloads

This maintenance release should replace the current 5000 experimental
release uCode

Changes:

- Fix "tid mismatch" issue

Comment 1 Phil Perry 2011-05-20 20:29:58 UTC
Looks like this should have happened for the release of RHEL 6.1, but didn't.

https://bugzilla.redhat.com/show_bug.cgi?id=706533

Comment 2 John W. Linville 2011-05-24 13:54:39 UTC
*** Bug 706533 has been marked as a duplicate of this bug. ***

Comment 3 Alan Bartlett 2011-05-24 15:14:28 UTC
Note: REGRESSION.

(1) With 6.0, wireless operates correctly. 
(2) Once the OS is updated to 6.1, wireless connectivity is broken. 
(3) Using the f/w available from upstream resolves this issue.

This is a bug which requires fixing now and should not be left for the 6.2 release.

Stanislaw or John -- Do you require any further information?

Comment 4 Stanislaw Gruszka 2011-05-24 15:34:27 UTC
I just requested dmesg in bug 706533 (Note I have 5300 and 5100, both work quite well here with old firmware ...)

Comment 5 Stephen John Smoogen 2011-05-24 16:25:12 UTC
Created attachment 500644 [details]
messages output from kernel

Hardware is a Lenovo Thinkpad T500. (Standard issue). Network reloaded itself 600+ times in 24 hours and loses consistently 10% of the packets between it and the router after the update to 6.1

Comment 8 Vladimir Benes 2011-05-25 18:27:14 UTC
we have this card in house so granting ack
-> qa_ack

Comment 11 Stephen John Smoogen 2011-06-27 17:49:53 UTC
Hmmm update of the package fixed immediate error of looking for old ucode, but did not fix the network reloads with messages of:

iwlagn 0000:03:00.0: Microcode SW error detected.  Restarting 0x2000000.
iwlagn 0000:03:00.0: Start IWL Error Log Dump:
iwlagn 0000:03:00.0: Status: 0x000212E4, count: 5
iwlagn 0000:03:00.0: Desc                                  Time       data1      data2      line
iwlagn 0000:03:00.0: SYSASSERT                    (0x0005) 3029572349 0x0000008C 0x00000030 140
iwlagn 0000:03:00.0: pc      blink1  blink2  ilink1  ilink2  hcmd
iwlagn 0000:03:00.0: 0x1F650 0x1F790 0x1F790 0x008B2 0x00000 0x47B0010
iwlagn 0000:03:00.0: CSR values:
iwlagn 0000:03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
iwlagn 0000:03:00.0:        CSR_HW_IF_CONFIG_REG: 0X00480303

Comment 12 Stanislaw Gruszka 2011-06-28 05:33:41 UTC
Open new bug report for that problem. Provide messages with debug=0x47ffffff iwlagn module parameter from module load to first microcode error. (Note if dmesg will overrun messages, you'll need to configure syslog to log kernel debug messages, see "Configure syslog to log kernel debug messages" from https://fedoraproject.org/wiki/DebugWireless).

Comment 13 Stephen John Smoogen 2011-06-28 16:01:13 UTC
Will do so. Close this ticket?

Comment 14 John W. Linville 2011-06-28 17:42:46 UTC
Please don't change the state of the bug -- it is being handled by the proper RHEL process.

Comment 16 Jiri Pallich 2012-10-09 12:44:00 UTC
Since this is a parent bug of an issue that has already been released via Z-Stream (e.g. rhel-6.3.z), this bug is going to be CLOSED as CURRENTRELEASE.