2010-07-27 22:38:41

by Perez-Gonzalez, Inaky

[permalink] [raw]
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card

On Tue, 2010-07-27 at 13:28 -0700, Alexey Shvetsov wrote:
> Hi all!

[apologies, I forgot to mention to CC the linux-wireless mailing list,
where the iwlagn guys lurk around -- done].

Guys, seems the wifi device is tripping in the 6250 when we switch on
WiMAX. Do you see anything interesting?

> Seems i fund bug on my 64bit system. I have installed 32bit version
> of wimax stack 1.5 and i'm running 2.6.35-rc6 kernel.
>
> After starting
> wimaxd at boot time iwlagn driver will crash when i try to scan or connect
> to any network. Stacktrace will be the following
>
> iwlagn 0000:02:00.0:
> RF_KILL bit toggled to enable radio.
> i2400m_usb 2-1.3:1.0: 'RF Control'
> (0x4602) command failed: -84 - invalid state (3)
> iwlagn 0000:02:00.0:
> Microcode SW error detected. Restarting 0x2000000.
> iwlagn 0000:02:00.0:
> Loaded firmware version: 9.201.4.1 build 24255
> iwlagn 0000:02:00.0: Start
> IWL Error Log Dump:
> iwlagn 0000:02:00.0: Status: 0x00020224, count: 5
> iwlagn
> 0000:02:00.0: Desc Time data1 data2
> line
> iwlagn 0000:02:00.0: SYSASSERT (#05) 0000012334
> 0x0000008D 0x8000000D 453
> iwlagn 0000:02:00.0: pc blink1 blink2
> ilink1 ilink2 hcmd
> iwlagn 0000:02:00.0: 0x1D074 0x1D066 0x1D066 0x009B2
> 0x00000 0x400005A
> iwlagn 0000:02:00.0: CSR values:
> iwlagn 0000:02:00.0: (2nd
> byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
> iwlagn 0000:02:00.0:
> CSR_HW_IF_CONFIG_REG: 0X00480303
> iwlagn 0000:02:00.0:
> CSR_INT_COALESCING: 0X0000ff40
> iwlagn 0000:02:00.0:
> CSR_INT: 0X00000000
> iwlagn 0000:02:00.0: CSR_INT_MASK:
> 0X00000000
> iwlagn 0000:02:00.0: CSR_FH_INT_STATUS:
> 0X00000000
> iwlagn 0000:02:00.0: CSR_GPIO_IN:
> 0X0000000f
> iwlagn 0000:02:00.0: CSR_RESET:
> 0X00000000
> iwlagn 0000:02:00.0: CSR_GP_CNTRL:
> 0X080403c5
> iwlagn 0000:02:00.0: CSR_HW_REV:
> 0X00000084
> iwlagn 0000:02:00.0: CSR_EEPROM_REG:
> 0Xe0a20ffd
> iwlagn 0000:02:00.0: CSR_EEPROM_GP:
> 0X90000801
> iwlagn 0000:02:00.0: CSR_OTP_GP_REG:
> 0X00030001
> iwlagn 0000:02:00.0: CSR_GIO_REG:
> 0X00080046
> iwlagn 0000:02:00.0: CSR_GP_UCODE_REG:
> 0X00000002
> iwlagn 0000:02:00.0: CSR_GP_DRIVER_REG:
> 0X00000004
> iwlagn 0000:02:00.0: CSR_UCODE_DRV_GP1:
> 0X00000000
> iwlagn 0000:02:00.0: CSR_UCODE_DRV_GP2:
> 0X00000000
> iwlagn 0000:02:00.0: CSR_LED_REG:
> 0X00000018
> iwlagn 0000:02:00.0: CSR_DRAM_INT_TBL_REG:
> 0X00000000
> iwlagn 0000:02:00.0: CSR_GIO_CHICKEN_BITS:
> 0X27800200
> iwlagn 0000:02:00.0: CSR_ANA_PLL_CFG:
> 0X00000000
> iwlagn 0000:02:00.0: CSR_HW_REV_WA_REG:
> 0X0001001a
> iwlagn 0000:02:00.0: CSR_DBG_HPET_MEM_REG:
> 0Xffff0000
> iwlagn 0000:02:00.0: FH register values:
> iwlagn 0000:02:00.0:
> FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0ffede00
> iwlagn 0000:02:00.0:
> FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00ffedf0
> iwlagn 0000:02:00.0:
> FH_RSCSR_CHNL0_WPTR: 0X00000000
> iwlagn 0000:02:00.0:
> FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
> iwlagn 0000:02:00.0:
> FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
> iwlagn 0000:02:00.0:
> FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
> iwlagn 0000:02:00.0:
> FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
> iwlagn 0000:02:00.0:
> FH_TSSR_TX_STATUS_REG: 0X07ff0001
> iwlagn 0000:02:00.0:
> FH_TSSR_TX_ERROR_REG: 0X00000000
> iwlagn 0000:02:00.0: Start IWL Event Log
> Dump: display last 20 entries
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004384:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004385:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004385:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004387:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004388:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004388:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004389:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004390:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004391:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004391:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004392:0x000000ff:1100
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004402:0x000003b1:0601
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004402:0x10000000:0600
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004403:0x000003c1:0660
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000004407:0x00000000:0661
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000012227:0x0400005a:0401
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000012228:0x0400005a:1513
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000012228:0x00000000:1513
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000012229:0x00000001:1523
> iwlagn 0000:02:00.0:
> EVT_LOGT:0000012344:0x00000000:0125
> iwlagn 0000:02:00.0: Command
> REPLY_PHY_CALIBRATION_CMD failed: FW Error
> iwlagn 0000:02:00.0: Error -5
> iteration 0
> usb 1-1.4: new full speed USB device using ehci_hcd and address
> 5
> iwlagn 0000:02:00.0: Error sending CALIBRATION_CFG_CMD: time out after
> 500ms.
> Bluetooth: Generic Bluetooth USB driver ver 0.6
> usbcore: registered
> new interface driver btusb
> Bluetooth: BNEP (Ethernet Emulation) ver
> 1.3
> Bluetooth: BNEP filters: protocol multicast
> Bluetooth: SCO (Voice Link)
> ver 0.6
> Bluetooth: SCO socket layer initialized
> iwlagn 0000:02:00.0:
> START_ALIVE timeout after 4000ms.
>
> initial state for defices are
>
> rfkill
> list
> 0: tpacpi_bluetooth_sw: Bluetooth
> Soft blocked: no
>
> Hard blocked: no
> 1: hci0: Bluetooth
> Soft blocked: no
> Hard
> blocked: no
> 2: i2400m-usb:2-1.3:1.0: WiMAX
> Soft blocked: yes
>
> Hard blocked: no
> 3: phy0: Wireless LAN
> Soft blocked: no
> Hard
> blocked: no
>





2010-07-28 18:10:08

by Inaky Perez-Gonzalez

[permalink] [raw]
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card

Hi Alexey

On Wed, 2010-07-28 at 21:53 +0400, Alexey Shvetsov wrote:
> Updated relevant part of logs for this bug
>

My concern here is that I am not seeing why the i2400m is failing to
initialize; there are no i2400m relevant messages. If I remember
correctly, over IRC you said that a grep of messages for i2400m only
turned:

Jul 22 16:20:03 x201 kernel: i2400m_usb: probe of 2-1.3:1.0 failed with
error -22

It that's the case, I missed to make the code properly report an error
condition, and we need to find out which one is it.

Can you enable debugging?:

1. unload the i2400m and i2400m-usb modules
2. $ modprobe i2400m debug='driver:8 control:3'
3. $ modprobe i2400m-usb debug='usb:8'

that should be printing way more logs to the console



2010-07-28 17:53:40

by Alexey Shvetsov

[permalink] [raw]
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card

Updated relevant part of logs for this bug

Jul 27 15:19:16 x201 wimaxd:
daemon starts
Jul 27 15:19:16 x201 wimaxd: pdifile is created
Jul 27
15:19:16 x201 wimaxd: wimaxd event: AppSrv is ready
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: Microcode SW error detected. Restarting
0x2000000.
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: Loaded firmware
version: 9.201.4.1 build 24255
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: Start IWL Error Log Dump:
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: Status: 0x000312E4, count: 5
Jul 27 15:19:27 x201 kernel:
iwlagn 0000:02:00.0: Desc Time data1
data2 line
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: SYSASSERT
(#05) 0000003432 0x000000BE 0x8000000D 453
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: pc blink1 blink2 ilink1
ilink2 hcmd
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: 0x1C548
0x1E674 0x1E674 0x009D6 0x00000 0x4360095
Jul 27 15:19:27 x201 kernel:
iwlagn 0000:02:00.0: CSR values:
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Jul
27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_HW_IF_CONFIG_REG:
0X00480303
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_INT_COALESCING: 0X00000040
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: CSR_INT: 0X00000000
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: CSR_INT_MASK: 0X00000000
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_FH_INT_STATUS:
0X00000000
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_GPIO_IN: 0X0000000f
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_RESET: 0X00000000
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: CSR_GP_CNTRL: 0X080403c5
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV: 0X00000084
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_EEPROM_REG:
0Xa0820ffd
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_EEPROM_GP: 0X90000801
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_OTP_GP_REG: 0X00030001
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: CSR_GIO_REG: 0X00080042
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: CSR_GP_UCODE_REG: 0X0000056a
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_GP_DRIVER_REG:
0X00000004
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_UCODE_DRV_GP1: 0X00000001
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: CSR_LED_REG: 0X00000058
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_DRAM_INT_TBL_REG:
0X880ffffe
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_GIO_CHICKEN_BITS: 0X27800200
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: CSR_ANA_PLL_CFG: 0X00000000
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_DBG_HPET_MEM_REG:
0Xffff0000
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: FH register
values:
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0ffede00
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00ffedf0
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_WPTR: 0X00000090
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
Jul 27 15:19:27 x201 kernel:
iwlagn 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
FH_TSSR_TX_ERROR_REG: 0X00000000
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: Start IWL Event Log Dump: display last 20 entries
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0001676513:0x00000196:0601
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0001676513:0xffffffff:0600
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0001676514:0x00000004:0600
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0001676514:0x0000019a:0606
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0001676515:0x000001f1:0615
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0001676567:0x000182f7:0615
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0001676568:0x00288000:0615
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0001676568:0xffffffff:0615
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0001676569:0x00000054:0601
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0001676570:0xffffffff:0615
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0001676576:0x0000006b:0601
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0001676591:0x000000e5:0628
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0001676591:0x00000000:0628
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0001676591:0x02288000:0628
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0001676591:0x02000000:0628
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0001676591:0x00000000:0628
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0001676591:0x00000800:0628
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0001676591:0x04000000:0628
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0001676594:0x0000025d:0601
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0001676684:0x00000000:0125
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: Command POWER_TABLE_CMD failed: FW Error
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: set power fail, ret = -5
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: Microcode SW error detected.
Restarting 0x2000000.
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
Loaded firmware version: 9.201.4.1 build 24255
Jul 27 15:19:27 x201 kernel:
iwlagn 0000:02:00.0: Start IWL Error Log Dump:
Jul 27 15:19:27 x201 kernel:
iwlagn 0000:02:00.0: Status: 0x00020224, count: 5
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: Desc Time
data1 data2 line
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
SYSASSERT (#05) 0000013122 0x0000008D 0x8000000D 453
Jul
27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: pc blink1 blink2 ilink1
ilink2 hcmd
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: 0x1EAB8
0x1EAA6 0x1EAA6 0x009D6 0x00000 0x400005A
Jul 27 15:19:27 x201 kernel:
iwlagn 0000:02:00.0: CSR values:
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Jul
27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_HW_IF_CONFIG_REG:
0X00480303
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_INT_COALESCING: 0X0000ff40
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: CSR_INT: 0X00000000
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: CSR_INT_MASK: 0X00000000
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_FH_INT_STATUS:
0X00000000
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_GPIO_IN: 0X0000000f
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_RESET: 0X00000000
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: CSR_GP_CNTRL: 0X080403c5
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV: 0X00000084
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_EEPROM_REG:
0Xa0820ffd
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_EEPROM_GP: 0X90000801
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_OTP_GP_REG: 0X00030001
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: CSR_GIO_REG: 0X00080046
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000002
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_GP_DRIVER_REG:
0X00000004
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_UCODE_DRV_GP1: 0X00000000
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: CSR_LED_REG: 0X00000018
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_DRAM_INT_TBL_REG:
0X880ffffe
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
CSR_GIO_CHICKEN_BITS: 0X27800200
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: CSR_ANA_PLL_CFG: 0X00000000
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0: CSR_DBG_HPET_MEM_REG:
0Xffff0000
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: FH register
values:
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0ffede00
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00ffedf0
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_WPTR: 0X00000000
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
Jul 27 15:19:27 x201 kernel:
iwlagn 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
FH_TSSR_TX_ERROR_REG: 0X00000000
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: Start IWL Event Log Dump: display last 20 entries
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005631:0x000000ff:1100
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005631:0x000000ff:1100
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005632:0x000000ff:1100
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005633:0x000000ff:1100
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005633:0x000000ff:1100
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005634:0x000000ff:1100
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005635:0x000000ff:1100
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005636:0x000000ff:1100
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005637:0x000000ff:1100
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005638:0x000000ff:1100
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005639:0x000000ff:1100
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005640:0x000000ff:1100
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005640:0x000000ff:1100
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005641:0x000000ff:1100
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005642:0x000000ff:1100
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000013014:0x0400005a:0401
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000013015:0x0400005a:1513
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000013016:0x00000000:1513
Jul 27
15:19:27 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000013017:0x00000001:1523
Jul 27 15:19:27 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000013132:0x00000000:0125
Jul 27 15:19:27 x201
kernel: iwlagn 0000:02:00.0: Command REPLY_PHY_CALIBRATION_CMD failed: FW
Error
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: Error -5 iteration
0
Jul 27 15:19:27 x201 kernel: iwlagn 0000:02:00.0: Error sending
TX_ANT_CONFIGURATION_CMD: time out after 500ms.
Jul 27 15:19:28 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_BT_CONFIG: time out after
500ms.
Jul 27 15:19:28 x201 kernel: iwlagn 0000:02:00.0: failed to send BT
Coex Config
Jul 27 15:19:28 x201 kernel: iwlagn 0000:02:00.0: Error sending
REPLY_RXON: time out after 500ms.
Jul 27 15:19:28 x201 kernel: iwlagn
0000:02:00.0: Error setting new RXON (-110)
Jul 27 15:19:29 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after
500ms.
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
REPLY_CT_KILL_CONFIG_CMD failed
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: queue 4 stuck 3 time. Fw reload.
Jul 27 15:19:29 x201 kernel:
iwlagn 0000:02:00.0: On demand firmware reload
Jul 27 15:19:29 x201 kernel:
iwlagn 0000:02:00.0: Error sending POWER_TABLE_CMD: time out after
500ms.
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0: set power fail, ret
= -110
Jul 27 15:19:29 x201 kernel: ------------[ cut here ]------------
Jul
27 15:19:29 x201 kernel: WARNING: at
drivers/net/wireless/iwlwifi/iwl-core.c:2068
iwl_mac_add_interface+0x127/0x150 [iwlcore]()
Jul 27 15:19:29 x201 kernel:
Hardware name: 3626W6E
Jul 27 15:19:29 x201 kernel: Modules linked in: ipv6
sco bnep rfcomm l2cap tp_smapi hdaps thinkpad_ec iwlagn btusb i2400m_usb
iwlcore bluetooth i2400m mac80211 joydev wimax i2c_i801 cfg80211 nfs lockd
sunrpc scsi_wait_scan usb_storage
Jul 27 15:19:29 x201 kernel: Pid: 18,
comm: events/3 Not tainted 2.6.35-rc6-tuxonice #2
Jul 27 15:19:29 x201
kernel: Call Trace:
Jul 27 15:19:29 x201 kernel: [<ffffffff8107737a>]
warn_slowpath_common+0x7a/0xb0
Jul 27 15:19:29 x201 kernel:
[<ffffffff810773c5>] warn_slowpath_null+0x15/0x20
Jul 27 15:19:29 x201
kernel: [<ffffffffa01e0077>] iwl_mac_add_interface+0x127/0x150 [iwlcore]
Jul
27 15:19:29 x201 kernel: [<ffffffffa0123454>] ieee80211_reconfig+0x84/0x460
[mac80211]
Jul 27 15:19:29 x201 kernel: [<ffffffffa0106bc0>] ?
ieee80211_restart_work+0x0/0x30 [mac80211]
Jul 27 15:19:29 x201 kernel:
[<ffffffffa0106bdd>] ieee80211_restart_work+0x1d/0x30 [mac80211]
Jul 27
15:19:29 x201 kernel: [<ffffffff8108b8ed>] worker_thread+0x16d/0x270
Jul 27
15:19:29 x201 kernel: [<ffffffff81090060>] ?
autoremove_wake_function+0x0/0x40
Jul 27 15:19:29 x201 kernel:
[<ffffffff8108b780>] ? worker_thread+0x0/0x270
Jul 27 15:19:29 x201 kernel:
[<ffffffff8108fa3e>] kthread+0x8e/0xa0
Jul 27 15:19:29 x201 kernel:
[<ffffffff8102cb54>] kernel_thread_helper+0x4/0x10
Jul 27 15:19:29 x201
kernel: [<ffffffff8108f9b0>] ? kthread+0x0/0xa0
Jul 27 15:19:29 x201 kernel:
[<ffffffff8102cb50>] ? kernel_thread_helper+0x0/0x10
Jul 27 15:19:29 x201
kernel: ---[ end trace f89060a8b6153bf5 ]---
Jul 27 15:19:29 x201 kernel:
iwlagn 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000.
Jul
27 15:19:29 x201 kernel: iwlagn 0000:02:00.0: Loaded firmware version:
9.201.4.1 build 24255
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
Start IWL Error Log Dump:
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
Status: 0x00020224, count: 5
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: Desc Time data1 data2
line
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0: SYSASSERT
(#05) 0000013599 0x0000008D 0x8000000D 453
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: pc blink1 blink2 ilink1 ilink2
hcmd
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0: 0x1EAB8 0x1EAA6
0x1EAA6 0x009D6 0x00000 0x400005A
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: CSR values:
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
(2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Jul 27 15:19:29
x201 kernel: iwlagn 0000:02:00.0: CSR_HW_IF_CONFIG_REG:
0X00480303
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
CSR_INT_COALESCING: 0X0000ff40
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: CSR_INT: 0X00000000
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: CSR_INT_MASK: 0X00000000
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0: CSR_FH_INT_STATUS:
0X00000000
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
CSR_GPIO_IN: 0X0000000f
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
CSR_RESET: 0X00000000
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: CSR_GP_CNTRL: 0X080403c5
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV: 0X00000084
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0: CSR_EEPROM_REG:
0Xa0820ffd
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
CSR_EEPROM_GP: 0X90000801
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
CSR_OTP_GP_REG: 0X00030001
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: CSR_GIO_REG: 0X00080046
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000002
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0: CSR_GP_DRIVER_REG:
0X00000004
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
CSR_UCODE_DRV_GP1: 0X00000000
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: CSR_LED_REG: 0X00000018
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0: CSR_DRAM_INT_TBL_REG:
0X880ffffe
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
CSR_GIO_CHICKEN_BITS: 0X27800200
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: CSR_ANA_PLL_CFG: 0X00000000
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0: CSR_DBG_HPET_MEM_REG:
0Xffff0000
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0: FH register
values:
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0ffede00
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00ffedf0
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_WPTR: 0X00000000
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
Jul 27 15:19:29 x201 kernel:
iwlagn 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
FH_TSSR_TX_ERROR_REG: 0X00000000
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: Start IWL Event Log Dump: display last 20 entries
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005630:0x000000ff:1100
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005630:0x000000ff:1100
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005631:0x000000ff:1100
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005632:0x000000ff:1100
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005632:0x000000ff:1100
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005633:0x000000ff:1100
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005634:0x000000ff:1100
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005635:0x000000ff:1100
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005636:0x000000ff:1100
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005637:0x000000ff:1100
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005638:0x000000ff:1100
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005638:0x000000ff:1100
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005639:0x000000ff:1100
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005640:0x000000ff:1100
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005641:0x000000ff:1100
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000013491:0x0400005a:0401
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000013492:0x0400005a:1513
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000013492:0x00000000:1513
Jul 27
15:19:29 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000013493:0x00000001:1523
Jul 27 15:19:29 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000013608:0x00000000:0125
Jul 27 15:19:29 x201
kernel: iwlagn 0000:02:00.0: Command REPLY_PHY_CALIBRATION_CMD failed: FW
Error
Jul 27 15:19:29 x201 kernel: iwlagn 0000:02:00.0: Error -5 iteration
0
Jul 27 15:19:30 x201 kernel: iwlagn 0000:02:00.0: Error sending
TX_ANT_CONFIGURATION_CMD: time out after 500ms.
Jul 27 15:19:30 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_BT_CONFIG: time out after
500ms.
Jul 27 15:19:30 x201 kernel: iwlagn 0000:02:00.0: failed to send BT
Coex Config
Jul 27 15:19:31 x201 kernel: iwlagn 0000:02:00.0: Error sending
REPLY_RXON: time out after 500ms.
Jul 27 15:19:31 x201 kernel: iwlagn
0000:02:00.0: Error setting new RXON (-110)
Jul 27 15:19:31 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after
500ms.
Jul 27 15:19:31 x201 kernel: iwlagn 0000:02:00.0:
REPLY_CT_KILL_CONFIG_CMD failed
Jul 27 15:19:31 x201 kernel: iwlagn
0000:02:00.0: queue 4 stuck 3 time. Fw reload.
Jul 27 15:19:32 x201 kernel:
iwlagn 0000:02:00.0: Error sending POWER_TABLE_CMD: time out after
500ms.
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0: set power fail, ret
= -110
Jul 27 15:19:32 x201 kernel: ------------[ cut here ]------------
Jul
27 15:19:32 x201 kernel: WARNING: at
drivers/net/wireless/iwlwifi/iwl-core.c:2068
iwl_mac_add_interface+0x127/0x150 [iwlcore]()
Jul 27 15:19:32 x201 kernel:
Hardware name: 3626W6E
Jul 27 15:19:32 x201 kernel: Modules linked in: ipv6
sco bnep rfcomm l2cap tp_smapi hdaps thinkpad_ec iwlagn btusb i2400m_usb
iwlcore bluetooth i2400m mac80211 joydev wimax i2c_i801 cfg80211 nfs lockd
sunrpc scsi_wait_scan usb_storage
Jul 27 15:19:32 x201 kernel: Pid: 16,
comm: events/1 Tainted: G W 2.6.35-rc6-tuxonice #2
Jul 27 15:19:32
x201 kernel: Call Trace:
Jul 27 15:19:32 x201 kernel: [<ffffffff8107737a>]
warn_slowpath_common+0x7a/0xb0
Jul 27 15:19:32 x201 kernel:
[<ffffffff810773c5>] warn_slowpath_null+0x15/0x20
Jul 27 15:19:32 x201
kernel: [<ffffffffa01e0077>] iwl_mac_add_interface+0x127/0x150 [iwlcore]
Jul
27 15:19:32 x201 kernel: [<ffffffffa0123454>] ieee80211_reconfig+0x84/0x460
[mac80211]
Jul 27 15:19:32 x201 kernel: [<ffffffffa0106bc0>] ?
ieee80211_restart_work+0x0/0x30 [mac80211]
Jul 27 15:19:32 x201 kernel:
[<ffffffffa0106bdd>] ieee80211_restart_work+0x1d/0x30 [mac80211]
Jul 27
15:19:32 x201 kernel: [<ffffffff8108b8ed>] worker_thread+0x16d/0x270
Jul 27
15:19:32 x201 kernel: [<ffffffff81090060>] ?
autoremove_wake_function+0x0/0x40
Jul 27 15:19:32 x201 kernel:
[<ffffffff8108b780>] ? worker_thread+0x0/0x270
Jul 27 15:19:32 x201 kernel:
[<ffffffff8108fa3e>] kthread+0x8e/0xa0
Jul 27 15:19:32 x201 kernel:
[<ffffffff8102cb54>] kernel_thread_helper+0x4/0x10
Jul 27 15:19:32 x201
kernel: [<ffffffff8108f9b0>] ? kthread+0x0/0xa0
Jul 27 15:19:32 x201 kernel:
[<ffffffff8102cb50>] ? kernel_thread_helper+0x0/0x10
Jul 27 15:19:32 x201
kernel: ---[ end trace f89060a8b6153bf6 ]---
Jul 27 15:19:32 x201 kernel:
iwlagn 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000.
Jul
27 15:19:32 x201 kernel: iwlagn 0000:02:00.0: Loaded firmware version:
9.201.4.1 build 24255
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
Start IWL Error Log Dump:
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
Status: 0x00020224, count: 5
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: Desc Time data1 data2
line
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0: SYSASSERT
(#05) 0000012798 0x0000008D 0x8000000D 453
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: pc blink1 blink2 ilink1 ilink2
hcmd
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0: 0x1EAB8 0x1EAA6
0x1EAA6 0x009D6 0x00000 0x400005A
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: CSR values:
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
(2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Jul 27 15:19:32
x201 kernel: iwlagn 0000:02:00.0: CSR_HW_IF_CONFIG_REG:
0X00480303
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
CSR_INT_COALESCING: 0X0000ff40
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: CSR_INT: 0X00000000
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: CSR_INT_MASK: 0X00000000
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0: CSR_FH_INT_STATUS:
0X00000000
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
CSR_GPIO_IN: 0X0000000f
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
CSR_RESET: 0X00000000
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: CSR_GP_CNTRL: 0X080403c5
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV: 0X00000084
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0: CSR_EEPROM_REG:
0Xa0820ffd
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
CSR_EEPROM_GP: 0X90000801
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
CSR_OTP_GP_REG: 0X00030001
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: CSR_GIO_REG: 0X00080046
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000002
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0: CSR_GP_DRIVER_REG:
0X00000004
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
CSR_UCODE_DRV_GP1: 0X00000000
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: CSR_LED_REG: 0X00000018
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0: CSR_DRAM_INT_TBL_REG:
0X880ffffe
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
CSR_GIO_CHICKEN_BITS: 0X27800200
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: CSR_ANA_PLL_CFG: 0X00000000
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0: CSR_DBG_HPET_MEM_REG:
0Xffff0000
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0: FH register
values:
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0ffede00
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00ffedf0
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_WPTR: 0X00000000
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
Jul 27 15:19:32 x201 kernel:
iwlagn 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
FH_TSSR_TX_ERROR_REG: 0X00000000
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: Start IWL Event Log Dump: display last 20 entries
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005629:0x000000ff:1100
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005630:0x000000ff:1100
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005631:0x000000ff:1100
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005632:0x000000ff:1100
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005632:0x000000ff:1100
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005633:0x000000ff:1100
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005634:0x000000ff:1100
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005635:0x000000ff:1100
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005636:0x000000ff:1100
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005637:0x000000ff:1100
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005638:0x000000ff:1100
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005638:0x000000ff:1100
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005639:0x000000ff:1100
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005640:0x000000ff:1100
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005640:0x000000ff:1100
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000012690:0x0400005a:0401
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000012691:0x0400005a:1513
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000012692:0x00000000:1513
Jul 27
15:19:32 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000012693:0x00000001:1523
Jul 27 15:19:32 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000012807:0x00000000:0125
Jul 27 15:19:32 x201
kernel: iwlagn 0000:02:00.0: Command REPLY_PHY_CALIBRATION_CMD failed: FW
Error
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0: Error -5 iteration
0
Jul 27 15:19:32 x201 kernel: iwlagn 0000:02:00.0: Error sending
TX_ANT_CONFIGURATION_CMD: time out after 500ms.
Jul 27 15:19:33 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_BT_CONFIG: time out after
500ms.
Jul 27 15:19:33 x201 kernel: iwlagn 0000:02:00.0: failed to send BT
Coex Config
Jul 27 15:19:33 x201 kernel: iwlagn 0000:02:00.0: Error sending
REPLY_RXON: time out after 500ms.
Jul 27 15:19:33 x201 kernel: iwlagn
0000:02:00.0: Error setting new RXON (-110)
Jul 27 15:19:34 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after
500ms.
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
REPLY_CT_KILL_CONFIG_CMD failed
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: queue 4 stuck 3 time. Fw reload.
Jul 27 15:19:34 x201 kernel:
iwlagn 0000:02:00.0: On demand firmware reload
Jul 27 15:19:34 x201 kernel:
iwlagn 0000:02:00.0: Error sending POWER_TABLE_CMD: time out after
500ms.
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0: set power fail, ret
= -110
Jul 27 15:19:34 x201 kernel: ------------[ cut here ]------------
Jul
27 15:19:34 x201 kernel: WARNING: at
drivers/net/wireless/iwlwifi/iwl-core.c:2068
iwl_mac_add_interface+0x127/0x150 [iwlcore]()
Jul 27 15:19:34 x201 kernel:
Hardware name: 3626W6E
Jul 27 15:19:34 x201 kernel: Modules linked in: ipv6
sco bnep rfcomm l2cap tp_smapi hdaps thinkpad_ec iwlagn btusb i2400m_usb
iwlcore bluetooth i2400m mac80211 joydev wimax i2c_i801 cfg80211 nfs lockd
sunrpc scsi_wait_scan usb_storage
Jul 27 15:19:34 x201 kernel: Pid: 17,
comm: events/2 Tainted: G W 2.6.35-rc6-tuxonice #2
Jul 27 15:19:34
x201 kernel: Call Trace:
Jul 27 15:19:34 x201 kernel: [<ffffffff8107737a>]
warn_slowpath_common+0x7a/0xb0
Jul 27 15:19:34 x201 kernel:
[<ffffffff810773c5>] warn_slowpath_null+0x15/0x20
Jul 27 15:19:34 x201
kernel: [<ffffffffa01e0077>] iwl_mac_add_interface+0x127/0x150 [iwlcore]
Jul
27 15:19:34 x201 kernel: [<ffffffffa0123454>] ieee80211_reconfig+0x84/0x460
[mac80211]
Jul 27 15:19:34 x201 kernel: [<ffffffffa0106bc0>] ?
ieee80211_restart_work+0x0/0x30 [mac80211]
Jul 27 15:19:34 x201 kernel:
[<ffffffffa0106bdd>] ieee80211_restart_work+0x1d/0x30 [mac80211]
Jul 27
15:19:34 x201 kernel: [<ffffffff8108b8ed>] worker_thread+0x16d/0x270
Jul 27
15:19:34 x201 kernel: [<ffffffff81090060>] ?
autoremove_wake_function+0x0/0x40
Jul 27 15:19:34 x201 kernel:
[<ffffffff8108b780>] ? worker_thread+0x0/0x270
Jul 27 15:19:34 x201 kernel:
[<ffffffff8108fa3e>] kthread+0x8e/0xa0
Jul 27 15:19:34 x201 kernel:
[<ffffffff8102cb54>] kernel_thread_helper+0x4/0x10
Jul 27 15:19:34 x201
kernel: [<ffffffff8108f9b0>] ? kthread+0x0/0xa0
Jul 27 15:19:34 x201 kernel:
[<ffffffff8102cb50>] ? kernel_thread_helper+0x0/0x10
Jul 27 15:19:34 x201
kernel: ---[ end trace f89060a8b6153bf7 ]---
Jul 27 15:19:34 x201 kernel:
iwlagn 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000.
Jul
27 15:19:34 x201 kernel: iwlagn 0000:02:00.0: Loaded firmware version:
9.201.4.1 build 24255
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
Start IWL Error Log Dump:
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
Status: 0x00020224, count: 5
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: Desc Time data1 data2
line
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0: SYSASSERT
(#05) 0000013662 0x0000008D 0x8000000D 453
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: pc blink1 blink2 ilink1 ilink2
hcmd
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0: 0x1EAB8 0x1EAA6
0x1EAA6 0x009D6 0x00000 0x400005A
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: CSR values:
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
(2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Jul 27 15:19:34
x201 kernel: iwlagn 0000:02:00.0: CSR_HW_IF_CONFIG_REG:
0X00480303
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
CSR_INT_COALESCING: 0X0000ff40
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: CSR_INT: 0X00000000
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: CSR_INT_MASK: 0X00000000
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0: CSR_FH_INT_STATUS:
0X00000000
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
CSR_GPIO_IN: 0X0000000f
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
CSR_RESET: 0X00000000
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: CSR_GP_CNTRL: 0X080403c5
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV: 0X00000084
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0: CSR_EEPROM_REG:
0Xa0820ffd
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
CSR_EEPROM_GP: 0X90000801
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
CSR_OTP_GP_REG: 0X00030001
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: CSR_GIO_REG: 0X00080046
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000002
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0: CSR_GP_DRIVER_REG:
0X00000004
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
CSR_UCODE_DRV_GP1: 0X00000000
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: CSR_LED_REG: 0X00000018
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0: CSR_DRAM_INT_TBL_REG:
0X880ffffe
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
CSR_GIO_CHICKEN_BITS: 0X27800200
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: CSR_ANA_PLL_CFG: 0X00000000
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0: CSR_DBG_HPET_MEM_REG:
0Xffff0000
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0: FH register
values:
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0ffede00
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00ffedf0
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_WPTR: 0X00000000
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
Jul 27 15:19:34 x201 kernel:
iwlagn 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
FH_TSSR_TX_ERROR_REG: 0X00000000
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: Start IWL Event Log Dump: display last 20 entries
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005629:0x000000ff:1100
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005630:0x000000ff:1100
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005631:0x000000ff:1100
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005632:0x000000ff:1100
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005632:0x000000ff:1100
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005633:0x000000ff:1100
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005634:0x000000ff:1100
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005635:0x000000ff:1100
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005636:0x000000ff:1100
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005637:0x000000ff:1100
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005638:0x000000ff:1100
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005638:0x000000ff:1100
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005639:0x000000ff:1100
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005640:0x000000ff:1100
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005640:0x000000ff:1100
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000013554:0x0400005a:0401
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000013555:0x0400005a:1513
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000013555:0x00000000:1513
Jul 27
15:19:34 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000013556:0x00000001:1523
Jul 27 15:19:34 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000013671:0x00000000:0125
Jul 27 15:19:34 x201
kernel: iwlagn 0000:02:00.0: Command REPLY_PHY_CALIBRATION_CMD failed: FW
Error
Jul 27 15:19:34 x201 kernel: iwlagn 0000:02:00.0: Error -5 iteration
0
Jul 27 15:19:35 x201 kernel: iwlagn 0000:02:00.0: Error sending
TX_ANT_CONFIGURATION_CMD: time out after 500ms.
Jul 27 15:19:35 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_BT_CONFIG: time out after
500ms.
Jul 27 15:19:35 x201 kernel: iwlagn 0000:02:00.0: failed to send BT
Coex Config
Jul 27 15:19:36 x201 kernel: iwlagn 0000:02:00.0: Error sending
REPLY_RXON: time out after 500ms.
Jul 27 15:19:36 x201 kernel: iwlagn
0000:02:00.0: Error setting new RXON (-110)
Jul 27 15:19:36 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after
500ms.
Jul 27 15:19:36 x201 kernel: iwlagn 0000:02:00.0:
REPLY_CT_KILL_CONFIG_CMD failed
Jul 27 15:19:36 x201 kernel: iwlagn
0000:02:00.0: queue 4 stuck 3 time. Fw reload.
Jul 27 15:19:37 x201 kernel:
iwlagn 0000:02:00.0: Error sending POWER_TABLE_CMD: time out after
500ms.
Jul 27 15:19:37 x201 kernel: iwlagn 0000:02:00.0: set power fail, ret
= -110
Jul 27 15:19:37 x201 kernel: iwlagn 0000:02:00.0: Error sending
REPLY_RXON: time out after 500ms.
Jul 27 15:19:37 x201 kernel: iwlagn
0000:02:00.0: Error setting new RXON (-110)
Jul 27 15:19:38 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_RXON: time out after 500ms.
Jul 27
15:19:38 x201 kernel: iwlagn 0000:02:00.0: Error setting new RXON (-110)
Jul
27 15:19:38 x201 kernel: iwlagn 0000:02:00.0: Error sending REPLY_RXON: time
out after 500ms.
Jul 27 15:19:38 x201 kernel: iwlagn 0000:02:00.0: Error
setting new RXON (-110)
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0:
Error sending REPLY_RXON: time out after 500ms.
Jul 27 15:19:39 x201 kernel:
iwlagn 0000:02:00.0: Error setting new RXON (-110)
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: Microcode SW error detected. Restarting
0x2000000.
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0: Loaded firmware
version: 9.201.4.1 build 24255
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: Start IWL Error Log Dump:
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: Status: 0x00020224, count: 5
Jul 27 15:19:39 x201 kernel:
iwlagn 0000:02:00.0: Desc Time data1
data2 line
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0: SYSASSERT
(#05) 0000013754 0x0000008D 0x8000000D 453
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0: pc blink1 blink2 ilink1
ilink2 hcmd
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0: 0x1EAB8
0x1EAA6 0x1EAA6 0x009D6 0x00000 0x400005A
Jul 27 15:19:39 x201 kernel:
iwlagn 0000:02:00.0: CSR values:
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
Jul
27 15:19:39 x201 kernel: iwlagn 0000:02:00.0: CSR_HW_IF_CONFIG_REG:
0X00480303
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0:
CSR_INT_COALESCING: 0X0000ff40
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: CSR_INT: 0X00000000
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: CSR_INT_MASK: 0X00000000
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0: CSR_FH_INT_STATUS:
0X00000000
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0:
CSR_GPIO_IN: 0X0000000f
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0:
CSR_RESET: 0X00000000Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: CSR_GP_CNTRL: 0X080403c5
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV: 0X00000084
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0: CSR_EEPROM_REG:
0Xa0820ffd
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0:
CSR_EEPROM_GP: 0X90000801
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0:
CSR_OTP_GP_REG: 0X00030001
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: CSR_GIO_REG: 0X00080046
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000002
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0: CSR_GP_DRIVER_REG:
0X00000004
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0:
CSR_UCODE_DRV_GP1: 0X00000000
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: CSR_LED_REG: 0X00000018
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0: CSR_DRAM_INT_TBL_REG:
0X880ffffe
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0:
CSR_GIO_CHICKEN_BITS: 0X27800200
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: CSR_ANA_PLL_CFG: 0X00000000
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0: CSR_DBG_HPET_MEM_REG:
0Xffff0000
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0: FH register
values:
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0ffede00
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00ffedf0
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
FH_RSCSR_CHNL0_WPTR: 0X00000000
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
Jul 27 15:19:39 x201 kernel:
iwlagn 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
FH_TSSR_TX_ERROR_REG: 0X00000000
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: Start IWL Event Log Dump: display last 20 entries
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005631:0x000000ff:1100
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005631:0x000000ff:1100
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005632:0x000000ff:1100
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005633:0x000000ff:1100
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005633:0x000000ff:1100
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005634:0x000000ff:1100
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005635:0x000000ff:1100
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005636:0x000000ff:1100
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005637:0x000000ff:1100
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005638:0x000000ff:1100
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005639:0x000000ff:1100
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005639:0x000000ff:1100
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000005640:0x000000ff:1100
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000005641:0x000000ff:1100
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000005642:0x000000ff:1100
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000013647:0x0400005a:0401
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000013648:0x0400005a:1513
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: EVT_LOGT:0000013648:0x00000000:1513
Jul 27
15:19:39 x201 kernel: iwlagn 0000:02:00.0:
EVT_LOGT:0000013650:0x00000001:1523
Jul 27 15:19:39 x201 kernel: iwlagn
0000:02:00.0: EVT_LOGT:0000013764:0x00000000:0125
Jul 27 15:19:39 x201
kernel: iwlagn 0000:02:00.0: Command REPLY_PHY_CALIBRATION_CMD failed: FW
Error
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0: Error -5 iteration
0
Jul 27 15:19:39 x201 kernel: iwlagn 0000:02:00.0: Error sending
TX_ANT_CONFIGURATION_CMD: time out after 500ms.
Jul 27 15:19:40 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_BT_CONFIG: time out after
500ms.
Jul 27 15:19:40 x201 kernel: iwlagn 0000:02:00.0: failed to send BT
Coex Config
Jul 27 15:19:40 x201 kernel: iwlagn 0000:02:00.0: Error sending
REPLY_RXON: time out after 500ms.
Jul 27 15:19:40 x201 kernel: iwlagn
0000:02:00.0: Error setting new RXON (-110)
Jul 27 15:19:41 x201 kernel:
iwlagn 0000:02:00.0: Error sending REPLY_CT_KILL_CONFIG_CMD: time out after
500ms.
Jul 27 15:19:41 x201 kernel: iwlagn 0000:02:00.0:
REPLY_CT_KILL_CONFIG_CMD failed
Jul 27 15:19:41 x201 kernel: iwlagn
0000:02:00.0: queue 4 stuck 3 time. Fw reload.
Jul 27 15:19:41 x201 kernel:
iwlagn 0000:02:00.0: On demand firmware reload
Jul 27 15:19:41 x201 kernel:
iwlagn 0000:02:00.0: Error sending POWER_TABLE_CMD: time out after
500ms.
Jul 27 15:19:41 x201 kernel: iwlagn 0000:02:00.0: set power fail, ret
= -110
Jul 27 15:19:41 x201 kernel: ------------[ cut here ]------------
Jul
27 15:19:41 x201 kernel: WARNING: at
drivers/net/wireless/iwlwifi/iwl-core.c:2068
iwl_mac_add_interface+0x127/0x150 [iwlcore]()
Jul 27 15:19:41 x201 kernel:
Hardware name: 3626W6E
Jul 27 15:19:41 x201 kernel: Modules linked in: ipv6
sco bnep rfcomm l2cap tp_smapi hdaps thinkpad_ec iwlagn btusb i2400m_usb
iwlcore bluetooth i2400m mac80211 joydev wimax i2c_i801 cfg80211 nfs lockd
sunrpc scsi_wait_scan usb_storage
Jul 27 15:19:41 x201 kernel: Pid: 16,
comm: events/1 Tainted: G W 2.6.35-rc6-tuxonice #2
Jul 27 15:19:41
x201 kernel: Call Trace:
Jul 27 15:19:41 x201 kernel: [<ffffffff8107737a>]
warn_slowpath_common+0x7a/0xb0
Jul 27 15:19:41 x201 kernel:
[<ffffffff810773c5>] warn_slowpath_null+0x15/0x20
Jul 27 15:19:41 x201
kernel: [<ffffffffa01e0077>] iwl_mac_add_interface+0x127/0x150 [iwlcore]
Jul
27 15:19:41 x201 kernel: [<ffffffffa0123454>] ieee80211_reconfig+0x84/0x460
[mac80211]
Jul 27 15:19:41 x201 kernel: [<ffffffffa0106bc0>] ?
ieee80211_restart_work+0x0/0x30 [mac80211]
Jul 27 15:19:41 x201 kernel:
[<ffffffffa0106bdd>] ieee80211_restart_work+0x1d/0x30 [mac80211]
Jul 27
15:19:41 x201 kernel: [<ffffffff8108b8ed>] worker_thread+0x16d/0x270
Jul 27
15:19:41 x201 kernel: [<ffffffff81090060>] ?
autoremove_wake_function+0x0/0x40
Jul 27 15:19:41 x201 kernel:
[<ffffffff8108b780>] ? worker_thread+0x0/0x270
Jul 27 15:19:41 x201 kernel:
[<ffffffff8108fa3e>] kthread+0x8e/0xa0
Jul 27 15:19:41 x201 kernel:
[<ffffffff8102cb54>] kernel_thread_helper+0x4/0x10
Jul 27 15:19:41 x201
kernel: [<ffffffff8108f9b0>] ? kthread+0x0/0xa0
Jul 27 15:19:41 x201 kernel:
[<ffffffff8102cb50>] ? kernel_thread_helper+0x0/0x10
Jul 27 15:19:41 x201
kernel: ---[ end trace f89060a8b6153bf8 ]---
Jul 27 15:19:41 x201 kernel:
iwlagn 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000.
Jul
27 15:19:41 x201 kernel: iwlagn 0000:02:00.0: Loaded firmware version:
9.201.4.1 build 24255
Jul 27 15:19:41 x201 kernel: iwlagn 0000:02:00.0:
Start IWL Error Log Dump:
Jul 27 15:19:41 x201 kernel: iwlagn 0000:02:00.0:
Status: 0x00020224, count: 5
Jul 27 15:19:41 x201 kernel: iwlagn
0000:02:00.0: Desc Time data1 data2
line
Jul 27 15:19:41 x201 kernel: iwlagn 0000:02:00.0: SYSASSERT
(#05) 0000012923 0x0000008D 0x8000000D 453
Jul 27 15:19:41 x201
kernel: iwlagn 0000:02:00.0: pc blink1 blink2 ilink1 ilink2
hcmd



--
Best Regards,
Alexey 'Alexxy' Shvetsov
Petersburg Nuclear
Physics Institute, Russia
Department of Molecular and Radiation
Biophysics
Gentoo Team Ru
Gentoo Linux
Dev
mailto:[email protected]
mailto:[email protected]
mailto:[email protected]
pi.spb.ru


Attachments:
signature.asc (198.00 B)
This is a digitally signed message part.

2010-07-28 20:21:54

by Perez-Gonzalez, Inaky

[permalink] [raw]
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card

On Wed, 2010-07-28 at 14:14 -0700, Dan Williams wrote:
...
> > ...
> > kernel: iwlagn 0000:02:00.0: RF_KILL bit toggled to enable radio.
> > NetworkManager: <info> WiFi now disabled by radio killswitch
> > kernel: i2400m_usb 2-1.3:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3)
> > NetworkManager: <info> (wlan0): bringing up device.
> > kernel: iwlagn 0000:02:00.0: Microcode SW error detected. Restarting
> > ...
> >
> > I say seemingly because I don't remember NetworkManager actually doing
> > that on WiMAX devices, but I could be wrong, as they expose an RFKILL
> > interface.
>
> NM doesn't do anything yet with wimax devices, though it'll look for
> wimax killswitches. But nothing is done with them yet upstream.
>
> So I guess my question here is whether Alexey is using a stock NM or a
> distro-patched one. Ubuntu used to patch NM to actually poke the rfkill
> bits, not sure if they still do that or not. Fedora does not, and I
> don't think Novell/SUSE does either.

Thanks for the clarification Dan, that eliminates a variable :)


2010-07-28 19:12:37

by Dan Williams

[permalink] [raw]
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card

On Wed, 2010-07-28 at 11:23 -0700, Inaky Perez-Gonzalez wrote:
> On Wed, 2010-07-28 at 11:09 -0700, Inaky Perez-Gonzalez wrote:
> > Hi Alexey
> >
> > On Wed, 2010-07-28 at 21:53 +0400, Alexey Shvetsov wrote:
> > > Updated relevant part of logs for this bug
> > >
>
> On the other side, I just went through the huge log file you sent me --
> thx for that.
>
> I don't see any i2400m errors in there -- the driver seems to at least
> be able to initialize right. WiFi's iwlagn gets toasted, but i2400m is
> not really complaining about anything -- except when NetworkManager
> seemingly tries to turn on/off the radio and a message about it being
> done while the device is not in the right state is popping up:

Stock NM actually doesn't poke rfkill for any device type yet. It
listens for killswitch changes, but it doesn't modify the switch state
at all. It will set the wifi device !IFF_UP though. At some point
we'll hook up rfkill to the "Wireless Enabled" checkbox, but rfkill is
such a tangled mess that it takes a bit of work to get the user
interaction right.

(there are platform and hardware switches, and sometimes the platform
switches control the hard/soft block on the hardware switches.
sometimes they don't. and you can't really tell. so you have to loop
through all switches, try turning them all off, and if any one fails to
turn off then you go through again until all of them turn off or until
it fails. but you can't tell it might fail before you try...)

> ...
> kernel: iwlagn 0000:02:00.0: RF_KILL bit toggled to enable radio.
> NetworkManager: <info> WiFi now disabled by radio killswitch
> kernel: i2400m_usb 2-1.3:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3)
> NetworkManager: <info> (wlan0): bringing up device.
> kernel: iwlagn 0000:02:00.0: Microcode SW error detected. Restarting
> ...
>
> I say seemingly because I don't remember NetworkManager actually doing
> that on WiMAX devices, but I could be wrong, as they expose an RFKILL
> interface.

NM doesn't do anything yet with wimax devices, though it'll look for
wimax killswitches. But nothing is done with them yet upstream.

So I guess my question here is whether Alexey is using a stock NM or a
distro-patched one. Ubuntu used to patch NM to actually poke the rfkill
bits, not sure if they still do that or not. Fedora does not, and I
don't think Novell/SUSE does either.

Dan

> So I am the more puzzled here, I guess I need to re-establish a baseline
> to curb confusion, please help me here:
>
> -- let's be in peace with the fact that wifi is not working at this
> point --
>
> (1) Does WiMAX work ok when iwlagn is unloaded? can you get to turn on
> the radio and scan?
>
> (2) Apparently the driver is up and running when iwlagn is loaded
> (according to your logs). Can you get the daemon to start? turn the
> radio on? scan?
>
> (3) when and how do you actually get that -22 error from the i2400m
> probe?
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html



2010-07-30 14:48:15

by Alexey Shvetsov

[permalink] [raw]
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card

Update with debug info on this bug
Log attached

2010/7/29 Inaky Perez-Gonzalez <[email protected]>
>
> On Wed, 2010-07-28 at 14:14 -0700, Dan Williams wrote:
> ...
> > > ...
> > > kernel: iwlagn 0000:02:00.0: RF_KILL bit toggled to enable radio.
> > > NetworkManager: <info>  WiFi now disabled by radio killswitch
> > > kernel: i2400m_usb 2-1.3:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3)
> > > NetworkManager: <info>  (wlan0): bringing up device.
> > > kernel: iwlagn 0000:02:00.0: Microcode SW error detected.  Restarting
> > > ...
> > >
> > > I say seemingly because I don't remember NetworkManager actually doing
> > > that on WiMAX devices, but I could be wrong, as they expose an RFKILL
> > > interface.
> >
> > NM doesn't do anything yet with wimax devices, though it'll look for
> > wimax killswitches.  But nothing is done with them yet upstream.
> >
> > So I guess my question here is whether Alexey is using a stock NM or a
> > distro-patched one.  Ubuntu used to patch NM to actually poke the rfkill
> > bits, not sure if they still do that or not.  Fedora does not, and I
> > don't think Novell/SUSE does either.
>
> Thanks for the clarification Dan, that eliminates a variable :)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



--
Best Regards,
Alexey 'Alexxy' Shvetsov
Petersburg Nuclear Physics Institute, Russia
Department of Molecular and Radiation Biophysics
Gentoo Team Ru
Gentoo Linux Dev
mailto:[email protected]
mailto:[email protected]
mailto:[email protected]


Attachments:
wimax_debug.log (68.02 kB)

2010-07-28 18:23:52

by Inaky Perez-Gonzalez

[permalink] [raw]
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card

On Wed, 2010-07-28 at 11:09 -0700, Inaky Perez-Gonzalez wrote:
> Hi Alexey
>
> On Wed, 2010-07-28 at 21:53 +0400, Alexey Shvetsov wrote:
> > Updated relevant part of logs for this bug
> >

On the other side, I just went through the huge log file you sent me --
thx for that.

I don't see any i2400m errors in there -- the driver seems to at least
be able to initialize right. WiFi's iwlagn gets toasted, but i2400m is
not really complaining about anything -- except when NetworkManager
seemingly tries to turn on/off the radio and a message about it being
done while the device is not in the right state is popping up:

...
kernel: iwlagn 0000:02:00.0: RF_KILL bit toggled to enable radio.
NetworkManager: <info> WiFi now disabled by radio killswitch
kernel: i2400m_usb 2-1.3:1.0: 'RF Control' (0x4602) command failed: -84 - invalid state (3)
NetworkManager: <info> (wlan0): bringing up device.
kernel: iwlagn 0000:02:00.0: Microcode SW error detected. Restarting
...

I say seemingly because I don't remember NetworkManager actually doing
that on WiMAX devices, but I could be wrong, as they expose an RFKILL
interface.

So I am the more puzzled here, I guess I need to re-establish a baseline
to curb confusion, please help me here:

-- let's be in peace with the fact that wifi is not working at this
point --

(1) Does WiMAX work ok when iwlagn is unloaded? can you get to turn on
the radio and scan?

(2) Apparently the driver is up and running when iwlagn is loaded
(according to your logs). Can you get the daemon to start? turn the
radio on? scan?

(3) when and how do you actually get that -22 error from the i2400m
probe?



2010-07-28 00:05:15

by Wey-Yi Guy

[permalink] [raw]
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card

Hi,

On Tue, 2010-07-27 at 15:38 -0700, Inaky Perez-Gonzalez wrote:
> On Tue, 2010-07-27 at 13:28 -0700, Alexey Shvetsov wrote:
> > Hi all!
>
> [apologies, I forgot to mention to CC the linux-wireless mailing list,
> where the iwlagn guys lurk around -- done].
>
> Guys, seems the wifi device is tripping in the 6250 when we switch on
> WiMAX. Do you see anything interesting?
>
> > Seems i fund bug on my 64bit system. I have installed 32bit version
> > of wimax stack 1.5 and i'm running 2.6.35-rc6 kernel.
> >
> > After starting
> > wimaxd at boot time iwlagn driver will crash when i try to scan or connect
> > to any network. Stacktrace will be the following
> >
> > iwlagn 0000:02:00.0:
> > RF_KILL bit toggled to enable radio.
> > i2400m_usb 2-1.3:1.0: 'RF Control'
> > (0x4602) command failed: -84 - invalid state (3)
> > iwlagn 0000:02:00.0:
> > Microcode SW error detected. Restarting 0x2000000.
> > iwlagn 0000:02:00.0:
> > Loaded firmware version: 9.201.4.1 build 24255
> > iwlagn 0000:02:00.0: Start
> > IWL Error Log Dump:
> > iwlagn 0000:02:00.0: Status: 0x00020224, count: 5
> > iwlagn
> > 0000:02:00.0: Desc Time data1 data2
> > line
> > iwlagn 0000:02:00.0: SYSASSERT (#05) 0000012334
> > 0x0000008D 0x8000000D 453
> > iwlagn 0000:02:00.0: pc blink1 blink2
> > ilink1 ilink2 hcmd
> > iwlagn 0000:02:00.0: 0x1D074 0x1D066 0x1D066 0x009B2
> > 0x00000 0x400005A
> > iwlagn 0000:02:00.0: CSR values:
> > iwlagn 0000:02:00.0: (2nd
> > byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
> > iwlagn 0000:02:00.0:
> > CSR_HW_IF_CONFIG_REG: 0X00480303
> > iwlagn 0000:02:00.0:
> > CSR_INT_COALESCING: 0X0000ff40
> > iwlagn 0000:02:00.0:
> > CSR_INT: 0X00000000
> > iwlagn 0000:02:00.0: CSR_INT_MASK:
> > 0X00000000
> > iwlagn 0000:02:00.0: CSR_FH_INT_STATUS:
> > 0X00000000
> > iwlagn 0000:02:00.0: CSR_GPIO_IN:
> > 0X0000000f
> > iwlagn 0000:02:00.0: CSR_RESET:
> > 0X00000000
> > iwlagn 0000:02:00.0: CSR_GP_CNTRL:
> > 0X080403c5
> > iwlagn 0000:02:00.0: CSR_HW_REV:
> > 0X00000084
> > iwlagn 0000:02:00.0: CSR_EEPROM_REG:
> > 0Xe0a20ffd
> > iwlagn 0000:02:00.0: CSR_EEPROM_GP:
> > 0X90000801
> > iwlagn 0000:02:00.0: CSR_OTP_GP_REG:
> > 0X00030001
> > iwlagn 0000:02:00.0: CSR_GIO_REG:
> > 0X00080046
> > iwlagn 0000:02:00.0: CSR_GP_UCODE_REG:
> > 0X00000002
> > iwlagn 0000:02:00.0: CSR_GP_DRIVER_REG:
> > 0X00000004
> > iwlagn 0000:02:00.0: CSR_UCODE_DRV_GP1:
> > 0X00000000
> > iwlagn 0000:02:00.0: CSR_UCODE_DRV_GP2:
> > 0X00000000
> > iwlagn 0000:02:00.0: CSR_LED_REG:
> > 0X00000018
> > iwlagn 0000:02:00.0: CSR_DRAM_INT_TBL_REG:
> > 0X00000000
> > iwlagn 0000:02:00.0: CSR_GIO_CHICKEN_BITS:
> > 0X27800200
> > iwlagn 0000:02:00.0: CSR_ANA_PLL_CFG:
> > 0X00000000
> > iwlagn 0000:02:00.0: CSR_HW_REV_WA_REG:
> > 0X0001001a
> > iwlagn 0000:02:00.0: CSR_DBG_HPET_MEM_REG:
> > 0Xffff0000
> > iwlagn 0000:02:00.0: FH register values:
> > iwlagn 0000:02:00.0:
> > FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0ffede00
> > iwlagn 0000:02:00.0:
> > FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00ffedf0
> > iwlagn 0000:02:00.0:
> > FH_RSCSR_CHNL0_WPTR: 0X00000000
> > iwlagn 0000:02:00.0:
> > FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
> > iwlagn 0000:02:00.0:
> > FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
> > iwlagn 0000:02:00.0:
> > FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
> > iwlagn 0000:02:00.0:
> > FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
> > iwlagn 0000:02:00.0:
> > FH_TSSR_TX_STATUS_REG: 0X07ff0001
> > iwlagn 0000:02:00.0:
> > FH_TSSR_TX_ERROR_REG: 0X00000000
> > iwlagn 0000:02:00.0: Start IWL Event Log
> > Dump: display last 20 entries
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004384:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004385:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004385:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004387:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004388:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004388:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004389:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004390:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004391:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004391:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004392:0x000000ff:1100
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004402:0x000003b1:0601
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004402:0x10000000:0600
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004403:0x000003c1:0660
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000004407:0x00000000:0661
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000012227:0x0400005a:0401
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000012228:0x0400005a:1513
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000012228:0x00000000:1513
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000012229:0x00000001:1523
> > iwlagn 0000:02:00.0:
> > EVT_LOGT:0000012344:0x00000000:0125
> > iwlagn 0000:02:00.0: Command
> > REPLY_PHY_CALIBRATION_CMD failed: FW Error
> > iwlagn 0000:02:00.0: Error -5
> > iteration 0
> > usb 1-1.4: new full speed USB device using ehci_hcd and address
> > 5
> > iwlagn 0000:02:00.0: Error sending CALIBRATION_CFG_CMD: time out after
> > 500ms.
> > Bluetooth: Generic Bluetooth USB driver ver 0.6
> > usbcore: registered
> > new interface driver btusb
> > Bluetooth: BNEP (Ethernet Emulation) ver
> > 1.3
> > Bluetooth: BNEP filters: protocol multicast
> > Bluetooth: SCO (Voice Link)
> > ver 0.6
> > Bluetooth: SCO socket layer initialized
> > iwlagn 0000:02:00.0:
> > START_ALIVE timeout after 4000ms.
> >
> >
Looks like iwlwifi driver stuck on loading uCode and performing
WiFi/WiMAX coex operation. I will forward the information to our uCode
team to look into it.

Thanks
Wey


2010-08-04 16:41:08

by Inaky Perez-Gonzalez

[permalink] [raw]
Subject: Re: [BUG] after starting wimaxd at boot iwlagn module will crash for intel 6250 card

On Fri, 2010-07-30 at 18:48 +0400, Alexey Shvetsov wrote:
> Update with debug info on this bug
> Log attached

This is now being tracked in bug #13.

Thank you!