You are not logged in.

Pages: 1

#1 2011-02-09 21:39:28

piffey
Member
From: Sioux Falls, SD
Registered: 2009-10-07
Posts: 54

[SOLVED] iwlagn, 2.6.37-5 firmware crash, fallback image works fine

Solution:Install the latest firmware from intellinuxwireless.org since the firmware included with the kernel is over a year old.

Posted up on the intellinuxwireless.org bug list and figured I'd post here too in case there's already a solution or if someone else has seen it.

Situation: Home Wireless w/ WPA2 works fine, never a disconnect, with 2.6.37-5.
WPA2 PEAP/MSCHAPv2 produces the following firmware errors after a few minutes
of connectivity. Running my fallback image, no errors are produced
and I stay connected. Running Arch Linux x86_64, Intel Centrino Advanced N 6200
2x2 AGN is the card. A recent upgrade updated the firmware package to
20110201-1, changelogs just show adding of firmware images for devices other
than the 6200 so not sure if it is relevant, especially since the 2.6.37
fallback image uses the same firmware package...I believe, but am not positive.

/var/log/errors.log:

Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: Microcode SW error
detected.  Restarting 0x2000000.
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: Loaded firmware version:
9.193.4.1 build 19710
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: Start IWL Error Log
Dump:
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: Status: 0x000312E4,
count: 5
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: Desc                    
             Time       data1      data2      line
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: NMI_INTERRUPT_TRM       
    (0x0016) 1958834260 0x00000040 0x07030000 73376
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: pc      blink1  blink2 
ilink1  ilink2  hcmd
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: 0x007C0 0x00686 0x00852
0x009D6 0x0FA42 0x00000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: CSR values:
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: (2nd byte of
CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:       
CSR_HW_IF_CONFIG_REG: 0X00480303
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:         
CSR_INT_COALESCING: 0X0000ff40
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:                    
CSR_INT: 0X00000000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:               
CSR_INT_MASK: 0X00000000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:          
CSR_FH_INT_STATUS: 0X00000000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:                
CSR_GPIO_IN: 0X0000000f
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:                  
CSR_RESET: 0X00000000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:               
CSR_GP_CNTRL: 0X080403c5
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:                 
CSR_HW_REV: 0X00000074
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:             
CSR_EEPROM_REG: 0Xbb3f0ffd
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:              
CSR_EEPROM_GP: 0X90000001
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:             
CSR_OTP_GP_REG: 0X00030001
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:                
CSR_GIO_REG: 0X00080042
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:           
CSR_GP_UCODE_REG: 0X000011e2
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:          
CSR_GP_DRIVER_REG: 0X00000002
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:          
CSR_UCODE_DRV_GP1: 0X00000000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:          
CSR_UCODE_DRV_GP2: 0X00000000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:                
CSR_LED_REG: 0X00000058
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:       
CSR_DRAM_INT_TBL_REG: 0X88131afa
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:       
CSR_GIO_CHICKEN_BITS: 0X27800200
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:            
CSR_ANA_PLL_CFG: 0X00000000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:          
CSR_HW_REV_WA_REG: 0X0001001a
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:       
CSR_DBG_HPET_MEM_REG: 0Xffff0000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: FH register values:
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:        
FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X1331c000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:       
FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X0130e4f0
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:                 
FH_RSCSR_CHNL0_WPTR: 0X00000028
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:        
FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00819104
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:         
FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:           
FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:   
FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:               
FH_TSSR_TX_STATUS_REG: 0X07ff0001
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:                
FH_TSSR_TX_ERROR_REG: 0X00000000
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: Log capacity 1024 is
bogus, limit to 512 entries
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0: Start IWL Event Log
Dump: display last 20 entries
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017355875:0x000000d4:0303
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017355880:0x00000f4e:0217
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017355881:0x024d001c:0217
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356390:0x00000118:0106
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356392:0x00000000:0302
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356442:0x0000000e:0322
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356442:0x0000002c:0322
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356448:0x00000001:1332
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356449:0x000000d4:0322
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356479:0x006b7bbf:0310
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356681:0x00000001:1332
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356682:0x024e001c:0206
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356683:0x00000001:0204
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356688:0x00000001:0219
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356688:0x03000210:0211
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356697:0x00000000:0256
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356697:0x00000000:0256
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356698:0x01020084:0212
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356805:0x000000f0:0123
Feb  9 14:48:37 localhost kernel: iwlagn 0000:03:00.0:
EVT_LOGT:0017356832:0x00000000:0125

Edit: Didn't quite realize how fallback images were created. Thought it was 2.6.37-1 or the 2.6.36.2-3 cached on my system. Since the fallback image works is it a module issue from the autodetect hook? How can I see what modules differ? Something must not be loading in the regular image and that's causing an issue somewhere.

Edit 2: So, there's something that must be going wrong with the autodetect hook if that is all there is that is different between the two. Lsmod output on both images, ran through vimdiff, is near identical, with a few smaller "used" numbers for modules like nvidia and ipv6 on the fallback image. Is there any way to see what exactly autodetect removed when parsing the new kernel image?

Last edited by piffey (2011-02-13 16:57:11)

Twitter

Offline

#2 2011-02-13 13:39:59

JF
Member
From: France
Registered: 2009-03-27
Posts: 39

Re: [SOLVED] iwlagn, 2.6.37-5 firmware crash, fallback image works fine

Hello,

I just happened to do a fresh Arch install on a laptop equipped with the same Wifi card as yours and experienced the same problem since then.

But after having downloaded and installed the latest firmware available from intellinuxwireless.org (shown as "9.221.4.1 build 25532" by the kernel when loaded) the driver seems stable now.

Hope this helps, have a nice day,

JF

Offline

#3 2011-02-13 14:20:36

piffey
Member
From: Sioux Falls, SD
Registered: 2009-10-07
Posts: 54

Re: [SOLVED] iwlagn, 2.6.37-5 firmware crash, fallback image works fine

Thank you JF. I'm surprised the included firmware is so out of date since the build you reference was released June 2010 and the build on my machine is from 2009. I will install the latest image and give it another test run. Hopefully we can mark this as solved.

Twitter

Offline

#4 2011-02-13 16:56:05

piffey
Member
From: Sioux Falls, SD
Registered: 2009-10-07
Posts: 54

Re: [SOLVED] iwlagn, 2.6.37-5 firmware crash, fallback image works fine

Loaded the updated firmware and haven't had a problem yet. I will have an opportunity to test on a crowded network come Monday, when most of the errors seem to happen. I'm going to mark this as solved though since I've been on for hours and haven't had an issue yet.

Twitter

Offline

Pages: 1

Board footer

Powered by FluxBB