* Microcode SW errors for Intel 7260
@ 2014-07-05 1:37 Larry Finger
2014-07-05 18:10 ` Emmanuel Grumbach
0 siblings, 1 reply; 5+ messages in thread
From: Larry Finger @ 2014-07-05 1:37 UTC (permalink / raw)
To: Johannes Berg, Emmanuel Grumbach; +Cc: Intel Linux Wireless, linux-wireless
The wireless device in my new Toshiba Tecra A50 reports the following when using
'lspci -nnv':
04:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1]
(rev 73)
Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4070]
Flags: bus master, fast devsel, latency 0, IRQ 48
Memory at e2400000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
My kernel is from the wireless-testing tree, and 'git describe' shows
master-2014-06-26-51-g956e5e6
The device seems to work OK, and is connected to channel 36 (5 GHz) with WPA2
encryption; however, it floods my logs with sequences as follows:
[367733.570361] iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting
0x2000000.
[367733.570372] iwlwifi 0000:04:00.0: CSR values:
[367733.570378] iwlwifi 0000:04:00.0: (2nd byte of CSR_INT_COALESCING is
CSR_INT_PERIODIC_REG)
[367733.570396] iwlwifi 0000:04:00.0: CSR_HW_IF_CONFIG_REG: 0X40489204
[367733.570413] iwlwifi 0000:04:00.0: CSR_INT_COALESCING: 0X80000040
[367733.570430] iwlwifi 0000:04:00.0: CSR_INT: 0X00000000
[367733.570448] iwlwifi 0000:04:00.0: CSR_INT_MASK: 0X00000000
[367733.570464] iwlwifi 0000:04:00.0: CSR_FH_INT_STATUS: 0X00000000
[367733.570480] iwlwifi 0000:04:00.0: CSR_GPIO_IN: 0X00000000
[367733.570496] iwlwifi 0000:04:00.0: CSR_RESET: 0X00000000
[367733.570512] iwlwifi 0000:04:00.0: CSR_GP_CNTRL: 0X080403c5
[367733.570529] iwlwifi 0000:04:00.0: CSR_HW_REV: 0X00000144
[367733.570581] iwlwifi 0000:04:00.0: CSR_EEPROM_REG: 0X00000000
[367733.570605] iwlwifi 0000:04:00.0: CSR_EEPROM_GP: 0X80000000
[367733.570633] iwlwifi 0000:04:00.0: CSR_OTP_GP_REG: 0X803a0000
[367733.570659] iwlwifi 0000:04:00.0: CSR_GIO_REG: 0X00080042
[367733.570678] iwlwifi 0000:04:00.0: CSR_GP_UCODE_REG: 0X00000000
[367733.570698] iwlwifi 0000:04:00.0: CSR_GP_DRIVER_REG: 0X00000000
[367733.570718] iwlwifi 0000:04:00.0: CSR_UCODE_DRV_GP1: 0X00000000
[367733.570738] iwlwifi 0000:04:00.0: CSR_UCODE_DRV_GP2: 0X00000000
[367733.570758] iwlwifi 0000:04:00.0: CSR_LED_REG: 0X00000060
[367733.570779] iwlwifi 0000:04:00.0: CSR_DRAM_INT_TBL_REG: 0X88220a0d
[367733.570804] iwlwifi 0000:04:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
[367733.570825] iwlwifi 0000:04:00.0: CSR_ANA_PLL_CFG: 0Xd55555d5
[367733.570845] iwlwifi 0000:04:00.0: CSR_MONITOR_STATUS_REG: 0X3c08019d
[367733.570864] iwlwifi 0000:04:00.0: CSR_HW_REV_WA_REG: 0X0001001a
[367733.570884] iwlwifi 0000:04:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0000
[367733.570892] iwlwifi 0000:04:00.0: FH register values:
[367733.570924] iwlwifi 0000:04:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG:
0X0c05ff00
[367733.570953] iwlwifi 0000:04:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG:
0X00c06000
[367733.570984] iwlwifi 0000:04:00.0: FH_RSCSR_CHNL0_WPTR:
0X00000028
[367733.571010] iwlwifi 0000:04:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG:
0X80801114
[367733.571036] iwlwifi 0000:04:00.0: FH_MEM_RSSR_SHARED_CTRL_REG:
0X000000fc
[367733.571063] iwlwifi 0000:04:00.0: FH_MEM_RSSR_RX_STATUS_REG:
0X07030000
[367733.571089] iwlwifi 0000:04:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV:
0X00000000
[367733.571116] iwlwifi 0000:04:00.0: FH_TSSR_TX_STATUS_REG:
0X07ff0001
[367733.571142] iwlwifi 0000:04:00.0: FH_TSSR_TX_ERROR_REG:
0X00000000
[367733.571281] iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
[367733.571286] iwlwifi 0000:04:00.0: Status: 0x00000000, count: 6
[367733.571290] iwlwifi 0000:04:00.0: Loaded firmware version: 23.214.9.0
[367733.571294] iwlwifi 0000:04:00.0: 0x0000277B | ADVANCED_SYSASSERT
[367733.571298] iwlwifi 0000:04:00.0: 0x000002B0 | uPc
[367733.571301] iwlwifi 0000:04:00.0: 0x00000000 | branchlink1
[367733.571305] iwlwifi 0000:04:00.0: 0x00000BA4 | branchlink2
[367733.571308] iwlwifi 0000:04:00.0: 0x000166A4 | interruptlink1
[367733.571312] iwlwifi 0000:04:00.0: 0x00DB0DD3 | interruptlink2
[367733.571316] iwlwifi 0000:04:00.0: 0x00000024 | data1
[367733.571319] iwlwifi 0000:04:00.0: 0x00000018 | data2
[367733.571323] iwlwifi 0000:04:00.0: 0xDEADBEEF | data3
[367733.571326] iwlwifi 0000:04:00.0: 0x003BE407 | beacon time
[367733.571330] iwlwifi 0000:04:00.0: 0x00041C14 | tsf low
[367733.571333] iwlwifi 0000:04:00.0: 0x00000000 | tsf hi
[367733.571337] iwlwifi 0000:04:00.0: 0x00000000 | time gp1
[367733.571340] iwlwifi 0000:04:00.0: 0x00041C14 | time gp2
[367733.571345] iwlwifi 0000:04:00.0: 0x00000000 | time gp3
[367733.571349] iwlwifi 0000:04:00.0: 0x000417D6 | uCode version
[367733.571353] iwlwifi 0000:04:00.0: 0x00000144 | hw version
[367733.571357] iwlwifi 0000:04:00.0: 0x40489204 | board version
[367733.571362] iwlwifi 0000:04:00.0: 0x0000001C | hcmd
[367733.571366] iwlwifi 0000:04:00.0: 0x00022000 | isr0
[367733.571370] iwlwifi 0000:04:00.0: 0x00000000 | isr1
[367733.571374] iwlwifi 0000:04:00.0: 0x00000002 | isr2
[367733.571378] iwlwifi 0000:04:00.0: 0x0040D0C0 | isr3
[367733.571382] iwlwifi 0000:04:00.0: 0x00000000 | isr4
[367733.571386] iwlwifi 0000:04:00.0: 0x00000110 | isr_pref
[367733.571390] iwlwifi 0000:04:00.0: 0x00000000 | wait_event
[367733.571394] iwlwifi 0000:04:00.0: 0x00000080 | l2p_control
[367733.571398] iwlwifi 0000:04:00.0: 0x00010000 | l2p_duration
[367733.571402] iwlwifi 0000:04:00.0: 0x0000003F | l2p_mhvalid
[367733.571406] iwlwifi 0000:04:00.0: 0x00000080 | l2p_addr_match
[367733.571410] iwlwifi 0000:04:00.0: 0x00000005 | lmpm_pmg_sel
[367733.571415] iwlwifi 0000:04:00.0: 0x18051651 | timestamp
[367733.571419] iwlwifi 0000:04:00.0: 0x00002830 | flow_handler
[367733.571428] ieee80211 phy0: Hardware restart was requested
[367733.572094] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
[367733.572457] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
Please inform me of any further info that is needed.
Thanks,
Larry
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: Microcode SW errors for Intel 7260
2014-07-05 1:37 Microcode SW errors for Intel 7260 Larry Finger
@ 2014-07-05 18:10 ` Emmanuel Grumbach
2014-07-06 4:29 ` Larry Finger
0 siblings, 1 reply; 5+ messages in thread
From: Emmanuel Grumbach @ 2014-07-05 18:10 UTC (permalink / raw)
To: Larry Finger
Cc: Johannes Berg, Emmanuel Grumbach, Intel Linux Wireless,
linux-wireless
> My kernel is from the wireless-testing tree, and 'git describe' shows
>
> master-2014-06-26-51-g956e5e6
>
> The device seems to work OK, and is connected to channel 36 (5 GHz) with
> WPA2 encryption; however, it floods my logs with sequences as follows:
>
> [367733.570361] iwlwifi 0000:04:00.0: Microcode SW error detected.
> Restarting 0x2000000.
> [367733.570372] iwlwifi 0000:04:00.0: CSR values:
> [367733.570378] iwlwifi 0000:04:00.0: (2nd byte of CSR_INT_COALESCING is
> CSR_INT_PERIODIC_REG)
> [367733.570396] iwlwifi 0000:04:00.0: CSR_HW_IF_CONFIG_REG:
> 0X40489204
> [367733.570413] iwlwifi 0000:04:00.0: CSR_INT_COALESCING:
> 0X80000040
> [367733.570430] iwlwifi 0000:04:00.0: CSR_INT:
> 0X00000000
> [367733.570448] iwlwifi 0000:04:00.0: CSR_INT_MASK:
> 0X00000000
> [367733.570464] iwlwifi 0000:04:00.0: CSR_FH_INT_STATUS:
> 0X00000000
> [367733.570480] iwlwifi 0000:04:00.0: CSR_GPIO_IN:
> 0X00000000
> [367733.570496] iwlwifi 0000:04:00.0: CSR_RESET:
> 0X00000000
> [367733.570512] iwlwifi 0000:04:00.0: CSR_GP_CNTRL:
> 0X080403c5
> [367733.570529] iwlwifi 0000:04:00.0: CSR_HW_REV:
> 0X00000144
> [367733.570581] iwlwifi 0000:04:00.0: CSR_EEPROM_REG:
> 0X00000000
> [367733.570605] iwlwifi 0000:04:00.0: CSR_EEPROM_GP:
> 0X80000000
> [367733.570633] iwlwifi 0000:04:00.0: CSR_OTP_GP_REG:
> 0X803a0000
> [367733.570659] iwlwifi 0000:04:00.0: CSR_GIO_REG:
> 0X00080042
> [367733.570678] iwlwifi 0000:04:00.0: CSR_GP_UCODE_REG:
> 0X00000000
> [367733.570698] iwlwifi 0000:04:00.0: CSR_GP_DRIVER_REG:
> 0X00000000
> [367733.570718] iwlwifi 0000:04:00.0: CSR_UCODE_DRV_GP1:
> 0X00000000
> [367733.570738] iwlwifi 0000:04:00.0: CSR_UCODE_DRV_GP2:
> 0X00000000
> [367733.570758] iwlwifi 0000:04:00.0: CSR_LED_REG:
> 0X00000060
> [367733.570779] iwlwifi 0000:04:00.0: CSR_DRAM_INT_TBL_REG:
> 0X88220a0d
> [367733.570804] iwlwifi 0000:04:00.0: CSR_GIO_CHICKEN_BITS:
> 0X27800200
> [367733.570825] iwlwifi 0000:04:00.0: CSR_ANA_PLL_CFG:
> 0Xd55555d5
> [367733.570845] iwlwifi 0000:04:00.0: CSR_MONITOR_STATUS_REG:
> 0X3c08019d
> [367733.570864] iwlwifi 0000:04:00.0: CSR_HW_REV_WA_REG:
> 0X0001001a
> [367733.570884] iwlwifi 0000:04:00.0: CSR_DBG_HPET_MEM_REG:
> 0Xffff0000
> [367733.570892] iwlwifi 0000:04:00.0: FH register values:
> [367733.570924] iwlwifi 0000:04:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG:
> 0X0c05ff00
> [367733.570953] iwlwifi 0000:04:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG:
> 0X00c06000
> [367733.570984] iwlwifi 0000:04:00.0: FH_RSCSR_CHNL0_WPTR:
> 0X00000028
> [367733.571010] iwlwifi 0000:04:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG:
> 0X80801114
> [367733.571036] iwlwifi 0000:04:00.0: FH_MEM_RSSR_SHARED_CTRL_REG:
> 0X000000fc
> [367733.571063] iwlwifi 0000:04:00.0: FH_MEM_RSSR_RX_STATUS_REG:
> 0X07030000
> [367733.571089] iwlwifi 0000:04:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV:
> 0X00000000
> [367733.571116] iwlwifi 0000:04:00.0: FH_TSSR_TX_STATUS_REG:
> 0X07ff0001
> [367733.571142] iwlwifi 0000:04:00.0: FH_TSSR_TX_ERROR_REG:
> 0X00000000
> [367733.571281] iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
> [367733.571286] iwlwifi 0000:04:00.0: Status: 0x00000000, count: 6
> [367733.571290] iwlwifi 0000:04:00.0: Loaded firmware version: 23.214.9.0
> [367733.571294] iwlwifi 0000:04:00.0: 0x0000277B | ADVANCED_SYSASSERT
> [367733.571298] iwlwifi 0000:04:00.0: 0x000002B0 | uPc
> [367733.571301] iwlwifi 0000:04:00.0: 0x00000000 | branchlink1
> [367733.571305] iwlwifi 0000:04:00.0: 0x00000BA4 | branchlink2
> [367733.571308] iwlwifi 0000:04:00.0: 0x000166A4 | interruptlink1
> [367733.571312] iwlwifi 0000:04:00.0: 0x00DB0DD3 | interruptlink2
> [367733.571316] iwlwifi 0000:04:00.0: 0x00000024 | data1
> [367733.571319] iwlwifi 0000:04:00.0: 0x00000018 | data2
> [367733.571323] iwlwifi 0000:04:00.0: 0xDEADBEEF | data3
> [367733.571326] iwlwifi 0000:04:00.0: 0x003BE407 | beacon time
> [367733.571330] iwlwifi 0000:04:00.0: 0x00041C14 | tsf low
> [367733.571333] iwlwifi 0000:04:00.0: 0x00000000 | tsf hi
> [367733.571337] iwlwifi 0000:04:00.0: 0x00000000 | time gp1
> [367733.571340] iwlwifi 0000:04:00.0: 0x00041C14 | time gp2
> [367733.571345] iwlwifi 0000:04:00.0: 0x00000000 | time gp3
> [367733.571349] iwlwifi 0000:04:00.0: 0x000417D6 | uCode version
> [367733.571353] iwlwifi 0000:04:00.0: 0x00000144 | hw version
> [367733.571357] iwlwifi 0000:04:00.0: 0x40489204 | board version
> [367733.571362] iwlwifi 0000:04:00.0: 0x0000001C | hcmd
> [367733.571366] iwlwifi 0000:04:00.0: 0x00022000 | isr0
> [367733.571370] iwlwifi 0000:04:00.0: 0x00000000 | isr1
> [367733.571374] iwlwifi 0000:04:00.0: 0x00000002 | isr2
> [367733.571378] iwlwifi 0000:04:00.0: 0x0040D0C0 | isr3
> [367733.571382] iwlwifi 0000:04:00.0: 0x00000000 | isr4
> [367733.571386] iwlwifi 0000:04:00.0: 0x00000110 | isr_pref
> [367733.571390] iwlwifi 0000:04:00.0: 0x00000000 | wait_event
> [367733.571394] iwlwifi 0000:04:00.0: 0x00000080 | l2p_control
> [367733.571398] iwlwifi 0000:04:00.0: 0x00010000 | l2p_duration
> [367733.571402] iwlwifi 0000:04:00.0: 0x0000003F | l2p_mhvalid
> [367733.571406] iwlwifi 0000:04:00.0: 0x00000080 | l2p_addr_match
> [367733.571410] iwlwifi 0000:04:00.0: 0x00000005 | lmpm_pmg_sel
> [367733.571415] iwlwifi 0000:04:00.0: 0x18051651 | timestamp
> [367733.571419] iwlwifi 0000:04:00.0: 0x00002830 | flow_handler
> [367733.571428] ieee80211 phy0: Hardware restart was requested
> [367733.572094] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
> [367733.572457] iwlwifi 0000:04:00.0: L1 Enabled; Disabling L0S
>
> Please inform me of any further info that is needed.
Please run with trace-cmd:
I need -e iwlwifi -e iwlwifi_msg
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Microcode SW errors for Intel 7260
2014-07-05 18:10 ` Emmanuel Grumbach
@ 2014-07-06 4:29 ` Larry Finger
2014-07-06 4:56 ` Emmanuel Grumbach
0 siblings, 1 reply; 5+ messages in thread
From: Larry Finger @ 2014-07-06 4:29 UTC (permalink / raw)
To: Emmanuel Grumbach
Cc: Johannes Berg, Emmanuel Grumbach, Intel Linux Wireless,
linux-wireless
On 07/05/2014 01:10 PM, Emmanuel Grumbach wrote:
>
> Please run with trace-cmd:
>
> I need -e iwlwifi -e iwlwifi_msg
>
Emmanuel,
I am obviously missing something. Neither iwlwifi nor iwlwifi_msg are listed in
/sys/kernel/debug/tracing/available_events/, thus trace-cmd cannot enable
logging those events. The output is as follows:
finger@linux-rcu3:~/wireless-testing> sudo trace-cmd record -e iwlwifi -e
iwlwifi_msg
/sys/kernel/debug/tracing/events/iwlwifi_msg/filter
/sys/kernel/debug/tracing/events/*/iwlwifi_msg/filter
trace-cmd: No such file or directory
No events enabled with iwlwifi_msg
finger@linux-rcu3:~/wireless-testing>
I compared my .config with one for the openSUSE kernel 3.11.10, and the kernel
hacking section has the same settings.
Do you have any suggestions?
Larry
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Microcode SW errors for Intel 7260
2014-07-06 4:29 ` Larry Finger
@ 2014-07-06 4:56 ` Emmanuel Grumbach
2014-07-06 16:11 ` Larry Finger
0 siblings, 1 reply; 5+ messages in thread
From: Emmanuel Grumbach @ 2014-07-06 4:56 UTC (permalink / raw)
To: Larry Finger
Cc: Johannes Berg, Emmanuel Grumbach, Intel Linux Wireless,
linux-wireless
Hi Larry,
> I am obviously missing something. Neither iwlwifi nor iwlwifi_msg are listed
> in /sys/kernel/debug/tracing/available_events/, thus trace-cmd cannot enable
> logging those events. The output is as follows:
>
> finger@linux-rcu3:~/wireless-testing> sudo trace-cmd record -e iwlwifi -e
> iwlwifi_msg
> /sys/kernel/debug/tracing/events/iwlwifi_msg/filter
> /sys/kernel/debug/tracing/events/*/iwlwifi_msg/filter
> trace-cmd: No such file or directory
> No events enabled with iwlwifi_msg
> finger@linux-rcu3:~/wireless-testing>
>
>
> I compared my .config with one for the openSUSE kernel 3.11.10, and the
> kernel hacking section has the same settings.
>
> Do you have any suggestions?
>
Do you have CONFIG_IWLWIFI_DEVICE_TRACING enabled?
If not, please enable it.
Note that I don't really need iwlwifi_msg. iwlwifi should be enough.
If you have CONFIG_IWLWIFI_DEBUG, then running with debug=0x00000800
as a module parameter should be enough if that can save you a kernel
compilation.
Thanks.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Microcode SW errors for Intel 7260
2014-07-06 4:56 ` Emmanuel Grumbach
@ 2014-07-06 16:11 ` Larry Finger
0 siblings, 0 replies; 5+ messages in thread
From: Larry Finger @ 2014-07-06 16:11 UTC (permalink / raw)
To: Emmanuel Grumbach
Cc: Johannes Berg, Emmanuel Grumbach, Intel Linux Wireless,
linux-wireless
On 07/05/2014 11:56 PM, Emmanuel Grumbach wrote:
> Hi Larry,
>
>> I am obviously missing something. Neither iwlwifi nor iwlwifi_msg are listed
>> in /sys/kernel/debug/tracing/available_events/, thus trace-cmd cannot enable
>> logging those events. The output is as follows:
>>
>> finger@linux-rcu3:~/wireless-testing> sudo trace-cmd record -e iwlwifi -e
>> iwlwifi_msg
>> /sys/kernel/debug/tracing/events/iwlwifi_msg/filter
>> /sys/kernel/debug/tracing/events/*/iwlwifi_msg/filter
>> trace-cmd: No such file or directory
>> No events enabled with iwlwifi_msg
>> finger@linux-rcu3:~/wireless-testing>
>>
>>
>> I compared my .config with one for the openSUSE kernel 3.11.10, and the
>> kernel hacking section has the same settings.
>>
>> Do you have any suggestions?
>>
>
> Do you have CONFIG_IWLWIFI_DEVICE_TRACING enabled?
> If not, please enable it.
> Note that I don't really need iwlwifi_msg. iwlwifi should be enough.
>
> If you have CONFIG_IWLWIFI_DEBUG, then running with debug=0x00000800
> as a module parameter should be enough if that can save you a kernel
> compilation.
Apparently, I was caught by a bug in the kernel configuration system. Using
'make xconfig', none of the entries under 'menu "Debugging Options"' in
drivers/net/wireless/iwlwifi/Kconfig appear. Using 'make menuconfig' reveals
them. I will report the problem to the appropriate persons - it does not seem to
be a wireless bug.
The rebuilt kernel is running with the appropriate trace turned on. Now it only
takes a retriggering of the original problem. I just hope that having debugging
enabled does not affect the timing enough to prevent the errors. :)
Thanks,
Larry
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-07-06 16:11 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-05 1:37 Microcode SW errors for Intel 7260 Larry Finger
2014-07-05 18:10 ` Emmanuel Grumbach
2014-07-06 4:29 ` Larry Finger
2014-07-06 4:56 ` Emmanuel Grumbach
2014-07-06 16:11 ` Larry Finger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).