2018-11-17 02:56:23

by Tom Gutteridge

[permalink] [raw]
Subject: Intel 8260 Firmware Init Failure

What can I do about this? My wireless card is unusable. Seems to be a
spontaneous failure. This is the output of dmesg | grep iwlwifi:

[ 7.206387] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[ 7.215066] iwlwifi 0000:02:00.0: loaded firmware version
36.7596afd4.0 op_mode iwlmvm
[ 7.686950] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band
Wireless AC 8260, REV=0x208
[ 7.769839] iwlwifi 0000:02:00.0: base HW address: 14:ab:c5:7c:5e:a2
[ 7.770427] iwlwifi 0000:02:00.0: Microcode SW error detected.
Restarting 0x2000000.
[ 7.770555] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[ 7.770557] iwlwifi 0000:02:00.0: Status: 0x00000100, count: 6
[ 7.770559] iwlwifi 0000:02:00.0: Loaded firmware version: 36.7596afd4.0
[ 7.770561] iwlwifi 0000:02:00.0: 0x00001392 | ADVANCED_SYSASSERT
[ 7.770562] iwlwifi 0000:02:00.0: 0x000002F2 | trm_hw_status0
[ 7.770564] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
[ 7.770565] iwlwifi 0000:02:00.0: 0x000124BE | branchlink2
[ 7.770566] iwlwifi 0000:02:00.0: 0x0001C1E2 | interruptlink1
[ 7.770568] iwlwifi 0000:02:00.0: 0x00000000 | interruptlink2
[ 7.770569] iwlwifi 0000:02:00.0: 0x0000010B | data1
[ 7.770570] iwlwifi 0000:02:00.0: 0x00000000 | data2
[ 7.770572] iwlwifi 0000:02:00.0: 0xDEADBEEF | data3
[ 7.770573] iwlwifi 0000:02:00.0: 0x00000000 | beacon time
[ 7.770574] iwlwifi 0000:02:00.0: 0x0000169F | tsf low
[ 7.770576] iwlwifi 0000:02:00.0: 0x00000000 | tsf hi
[ 7.770577] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[ 7.770578] iwlwifi 0000:02:00.0: 0x0000169F | time gp2
[ 7.770580] iwlwifi 0000:02:00.0: 0x00000009 | uCode revision type
[ 7.770581] iwlwifi 0000:02:00.0: 0x00000024 | uCode version major
[ 7.770583] iwlwifi 0000:02:00.0: 0x7596AFD4 | uCode version minor
[ 7.770584] iwlwifi 0000:02:00.0: 0x00000201 | hw version
[ 7.770585] iwlwifi 0000:02:00.0: 0x00489008 | board version
[ 7.770587] iwlwifi 0000:02:00.0: 0x0010016A | hcmd
[ 7.770588] iwlwifi 0000:02:00.0: 0x02322080 | isr0
[ 7.770589] iwlwifi 0000:02:00.0: 0x00000000 | isr1
[ 7.770591] iwlwifi 0000:02:00.0: 0x28201802 | isr2
[ 7.770592] iwlwifi 0000:02:00.0: 0x004000C0 | isr3
[ 7.770593] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[ 7.770595] iwlwifi 0000:02:00.0: 0x0010016A | last cmd Id
[ 7.770596] iwlwifi 0000:02:00.0: 0x00000000 | wait_event
[ 7.770598] iwlwifi 0000:02:00.0: 0x0000E45C | l2p_control
[ 7.770599] iwlwifi 0000:02:00.0: 0x00001420 | l2p_duration
[ 7.770600] iwlwifi 0000:02:00.0: 0x00000000 | l2p_mhvalid
[ 7.770602] iwlwifi 0000:02:00.0: 0x00000000 | l2p_addr_match
[ 7.770603] iwlwifi 0000:02:00.0: 0x0000000D | lmpm_pmg_sel
[ 7.770604] iwlwifi 0000:02:00.0: 0x22040707 | timestamp
[ 7.770606] iwlwifi 0000:02:00.0: 0x00000818 | flow_handler
[ 7.770669] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[ 7.770670] iwlwifi 0000:02:00.0: Status: 0x00000100, count: 7
[ 7.770672] iwlwifi 0000:02:00.0: 0x00000070 | ADVANCED_SYSASSERT
[ 7.770673] iwlwifi 0000:02:00.0: 0x00000000 | umac branchlink1
[ 7.770674] iwlwifi 0000:02:00.0: 0xC0086AA4 | umac branchlink2
[ 7.770675] iwlwifi 0000:02:00.0: 0xC0083CB0 | umac interruptlink1
[ 7.770677] iwlwifi 0000:02:00.0: 0xC0083C90 | umac interruptlink2
[ 7.770678] iwlwifi 0000:02:00.0: 0x00000800 | umac data1
[ 7.770679] iwlwifi 0000:02:00.0: 0xC0083C90 | umac data2
[ 7.770682] iwlwifi 0000:02:00.0: 0xDEADBEEF | umac data3
[ 7.770683] iwlwifi 0000:02:00.0: 0x00000024 | umac major
[ 7.770684] iwlwifi 0000:02:00.0: 0x7596AFD4 | umac minor
[ 7.770686] iwlwifi 0000:02:00.0: 0xC088628C | frame pointer
[ 7.770687] iwlwifi 0000:02:00.0: 0xC088628C | stack pointer
[ 7.770688] iwlwifi 0000:02:00.0: 0x0010016A | last host cmd
[ 7.770690] iwlwifi 0000:02:00.0: 0x00000000 | isr status reg
[ 7.770697] iwlwifi 0000:02:00.0: Failed to run INIT calibrations: -5
[ 7.770699] iwlwifi 0000:02:00.0: Failed to run INIT ucode: -5

uname -a gives:
Linux tomg-p5510 4.19.1-1-MANJARO #1 SMP PREEMPT Sun Nov 4 16:05:34
UTC 2018 x86_64 GNU/Linux

This happened once before, about a year ago. It resolved itself when I
tried installing Windows 10 and running an update. Now when I try a
clean install of Windows 10 it bluescreens on startup with probable
cause Netwtw06.sys.

Thanks,
Tom.


2018-11-17 20:15:44

by Emmanuel Grumbach

[permalink] [raw]
Subject: Re: Intel 8260 Firmware Init Failure

>
> What can I do about this? My wireless card is unusable. Seems to be a
> spontaneous failure. This is the output of dmesg | grep iwlwifi:
>
> [ 7.206387] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
> [ 7.215066] iwlwifi 0000:02:00.0: loaded firmware version
> 36.7596afd4.0 op_mode iwlmvm
> [ 7.686950] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band
> Wireless AC 8260, REV=0x208
> [ 7.769839] iwlwifi 0000:02:00.0: base HW address: 14:ab:c5:7c:5e:a2
> [ 7.770427] iwlwifi 0000:02:00.0: Microcode SW error detected.
> Restarting 0x2000000.
> [ 7.770555] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
> [ 7.770557] iwlwifi 0000:02:00.0: Status: 0x00000100, count: 6
> [ 7.770559] iwlwifi 0000:02:00.0: Loaded firmware version: 36.7596afd4.0
> [ 7.770561] iwlwifi 0000:02:00.0: 0x00001392 | ADVANCED_SYSASSERT
> [ 7.770562] iwlwifi 0000:02:00.0: 0x000002F2 | trm_hw_status0
> [ 7.770564] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
> [ 7.770565] iwlwifi 0000:02:00.0: 0x000124BE | branchlink2
> [ 7.770566] iwlwifi 0000:02:00.0: 0x0001C1E2 | interruptlink1
> [ 7.770568] iwlwifi 0000:02:00.0: 0x00000000 | interruptlink2
> [ 7.770569] iwlwifi 0000:02:00.0: 0x0000010B | data1
> [ 7.770570] iwlwifi 0000:02:00.0: 0x00000000 | data2
> [ 7.770572] iwlwifi 0000:02:00.0: 0xDEADBEEF | data3

Report of bug on bugzilla.kernel.org as explained here:
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging

From what I see this is a bug in calibrations. Not fun.

>
> This happened once before, about a year ago. It resolved itself when I
> tried installing Windows 10 and running an update. Now when I try a
> clean install of Windows 10 it bluescreens on startup with probable
> cause Netwtw06.sys.
>

Even less fun. When you want to compare this to any other problem you have seen,
please check the ASSERT number. In this case, you have ASSERT 1392.