FS#23404 - [inux-firmware] iwlagn firmware problems with each linux-firmware upgrade

Attached to Project: Arch Linux
Opened by Chad Anderson (piffey) - Wednesday, 23 March 2011, 13:56 GMT
Last edited by Allan McRae (Allan) - Friday, 16 November 2012, 11:43 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
With each upgrade of the linux-firmware package I've noticed that the iwlwifi firmware for the Advanced-N 6200 driver breaks for WPA Enterprise networks (PEAP/MSCHAPv2 is the one I use daily). The wireless will stay connected for several minutes, then disconnect with the following crash in /var/log/errors.log. Each time I can solve the problem by re-downloading the firmware from the iwlwifi website and copying the ucode into /lib/firmware. After that, everything functions normally.




Additional info:
/var/log/errors.log:

Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: Microcode SW error detected. Restarting 0x2000000.
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: Loaded firmware version: 9.193.4.1 build 19710
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: Start IWL Error Log Dump:
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: Status: 0x000212E4, count: 5
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: Desc Time data1 data2 line
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: NMI_INTERRUPT_TRM (0x0016) 1384022435 0x00000040 0x07030000 73376
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: pc blink1 blink2 ilink1 ilink2 hcmd
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: 0x007C0 0x00686 0x00852 0x009D6 0x0FA42 0x00000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR values:
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_HW_IF_CONFIG_REG: 0X00480303
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_INT_COALESCING: 0X0000ff40
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_INT: 0X00000000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_INT_MASK: 0X00000000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_FH_INT_STATUS: 0X00000000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_GPIO_IN: 0X0000000f
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_RESET: 0X00000000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_GP_CNTRL: 0X080403c5
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_HW_REV: 0X00000074
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_EEPROM_REG: 0Xbbbe0ffd
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_EEPROM_GP: 0X90000001
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_OTP_GP_REG: 0X00030001
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_GIO_REG: 0X00080042
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_GP_UCODE_REG: 0X0000c7e0
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_GP_DRIVER_REG: 0X00000002
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_UCODE_DRV_GP1: 0X00000000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_LED_REG: 0X00000058
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_DRAM_INT_TBL_REG: 0X8812d936
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_ANA_PLL_CFG: 0X00000000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_HW_REV_WA_REG: 0X0001001a
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: FH register values:
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X1321a600
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X01305010
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_WPTR: 0X000000b0
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00819104
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: Log capacity 1024 is bogus, limit to 512 entries
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: Log write index 644 is bogus, limit to 512
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: Start IWL Event Log Dump: display last 20 entries
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207205808:0x00000001:1332
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207205809:0x000000d4:0322
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207205839:0x006b7bbf:0310
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207209692:0x00000118:0106
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207209694:0x00000000:0302
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207220946:0x00000001:1332
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207220947:0x02cc001c:0206
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207220948:0x00000001:0204
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207220953:0x00000001:0219
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207220954:0x03000210:0211
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207221038:0x00000000:0212
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207221093:0x00000000:0215
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207221098:0x00000008:0220
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207221115:0x00000000:0302
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207221144:0x000000d4:0303
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207221149:0x000006cd:0217
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207221150:0x02cc001c:0217
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207221980:0x00000118:0106
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207221982:0x00000000:0302
Mar 23 08:42:15 localhost kernel: iwlagn 0000:03:00.0: EVT_LOGT:1207234268:0x00000118:0106


Steps to reproduce: Use WPA Enterprise network for 5-10 minutes, especially during peak traffic times.
This task depends upon

Closed by  Allan McRae (Allan)
Friday, 16 November 2012, 11:43 GMT
Reason for closing:  Upstream
Additional comments about closing:  Needs to be updated upstream
Comment by Thomas Bächler (brain0) - Friday, 25 March 2011, 08:11 GMT
Can you compare the checksums between our version and the one you downloaded? There might be a broken file in the linux-firmware tree.
Comment by Tobias Powalowski (tpowa) - Saturday, 26 March 2011, 21:24 GMT Comment by Paweł Paprota (yagood) - Thursday, 12 May 2011, 14:32 GMT
File /lib/firmware/iwlwifi-6000-4.ucode is still older than the one from http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-6000-ucode-9.221.4.1.tgz even with the latest linux-firmware package (version 20110512-1 from testing). Updating this file manually helped solve the above problem for me (I also have Advanced-N 6200 card).

Dmesg logs from before and after the update:

[16893.314259] iwlagn 0000:03:00.0: Loaded firmware version: 9.193.4.1 build 19710
[16985.189482] iwlagn 0000:03:00.0: loaded firmware version 9.221.4.1 build 25532
Comment by Greg (dolby) - Monday, 15 October 2012, 08:02 GMT
Solution: either grab the firmware from intel instead of the kernel git tree, or report to the kernel firmware maintainers.

Loading...