You are not logged in.

#26 2020-12-02 11:31:29

davc0n
Member
Registered: 2020-02-01
Posts: 50

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

Tested it, but didn't solve the problem for me. Still getting the microcode error.

[41108.967124] iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.
[41109.063116] ------------[ cut here ]------------
[41109.063131] WARNING: CPU: 0 PID: 343 at drivers/net/wireless/intel/iwlwifi/mvm/../iwl-trans.h:1360 iwl_mvm_dump_lmac_error_log+0x537/0x590 [iwlmvm]
[41109.063132] Modules linked in: tun hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid ccm xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc joydev mousedev overlay uvcvideo videobuf2_vmalloc amdgpu videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc edac_mce_amd iwlmvm wmi_bmof kvm_amd snd_hda_codec_realtek snd_hda_codec_generic gpu_sched mac80211 i2c_algo_bit kvm ttm snd_hda_codec_hdmi nls_iso8859_1 libarc4 irqbypass crct10dif_pclmul snd_hda_intel nls_cp437 crc32_pclmul snd_intel_dspcfg ghash_clmulni_intel vfat drm_kms_helper snd_rn_pci_acp3x fat snd_hda_codec aesni_intel iwlwifi tpm_crb crypto_simd cryptd glue_helper thinkpad_acpi r8169 snd_hda_core tpm_tis sp5100_tco snd_hwdep cfg80211 psmouse rapl input_leds pcspkr tpm_tis_core realtek nvram snd_pcm ipmi_devintf k10temp i2c_piix4 ledtrig_audio cec snd_pci_acp3x
[41109.063165]  mdio_devres ucsi_acpi of_mdio ccp rc_core snd_timer typec_ucsi tpm fixed_phy ipmi_msghandler rfkill syscopyarea snd sysfillrect sysimgblt typec fb_sys_fops libphy rng_core wmi soundcore battery ac i2c_scmi evdev pinctrl_amd mac_hid acpi_cpufreq drm crypto_user agpgart ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 serio_raw atkbd libps2 crc32c_intel xhci_pci xhci_pci_renesas xhci_hcd ehci_pci ehci_hcd i8042 serio
[41109.063185] CPU: 0 PID: 343 Comm: irq/89-iwlwifi: Tainted: G        W         5.9.11-arch2-1 #1
[41109.063186] Hardware name: LENOVO 20NJCTO1WW/20NJCTO1WW, BIOS R12ET55W(1.25 ) 07/06/2020
[41109.063192] RIP: 0010:iwl_mvm_dump_lmac_error_log+0x537/0x590 [iwlmvm]
[41109.063194] Code: 3b 31 d2 31 f6 44 8b 84 24 9c 00 00 00 48 c7 c1 45 67 51 c1 e8 2a 7c 7b ff e9 5e fb ff ff 49 c7 c1 32 64 51 c1 e9 ac fc ff ff <0f> 0b 48 8b 7d 38 48 c7 c1 f0 ab 51 c1 31 d2 31 f6 e8 03 7c 7b ff
[41109.063195] RSP: 0018:ffffb4cc018c7cf0 EFLAGS: 00010286
[41109.063197] RAX: 00000000fffffff0 RBX: ffffa0fd525d1ec8 RCX: 0000000000000000
[41109.063197] RDX: 0000000000000001 RSI: 0000000000000246 RDI: 00000000ffffffff
[41109.063198] RBP: ffffa0fd57f20018 R08: 0000000000003a98 R09: ffffffffc151642f
[41109.063199] R10: 0000000000000000 R11: ffffb4cc018c7b4d R12: 0000000000813cc4
[41109.063199] R13: 0000000000000000 R14: ffffb4cc018c7cf8 R15: ffffa0fd57f22544
[41109.063201] FS:  0000000000000000(0000) GS:ffffa0fd68a00000(0000) knlGS:0000000000000000
[41109.063202] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[41109.063203] CR2: 00007fba4607f000 CR3: 000000051fd42000 CR4: 00000000003506f0
[41109.063204] Call Trace:
[41109.063213]  iwl_mvm_dump_nic_error_log+0x35/0x3b0 [iwlmvm]
[41109.063222]  ? __iwl_err.cold+0x28/0x2d [iwlwifi]
[41109.063228]  iwl_mvm_nic_error+0x2d/0x40 [iwlmvm]
[41109.063234]  iwl_pcie_irq_handle_error+0x97/0xe0 [iwlwifi]
[41109.063240]  iwl_pcie_irq_msix_handler+0x19c/0x590 [iwlwifi]
[41109.063243]  ? disable_irq_nosync+0x10/0x10
[41109.063245]  irq_thread_fn+0x20/0x60
[41109.063246]  irq_thread+0xf5/0x1a0
[41109.063248]  ? irq_finalize_oneshot.part.0+0xe0/0xe0
[41109.063250]  ? irq_thread_check_affinity+0xd0/0xd0
[41109.063252]  kthread+0x142/0x160
[41109.063253]  ? __kthread_bind_mask+0x60/0x60
[41109.063256]  ret_from_fork+0x22/0x30
[41109.063258] ---[ end trace 831e481f04e90bd5 ]---
[41109.063261] iwlwifi 0000:01:00.0: HW error, resetting before reading
[41109.070315] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[41109.070320] iwlwifi 0000:01:00.0: Status: 0x00000040, count: 2105498100
[41109.070322] iwlwifi 0000:01:00.0: Loaded firmware version: 46.4d093a30.0 9260-th-b0-jf-b0-46.ucode
[41109.070324] iwlwifi 0000:01:00.0: 0x6B32FB29 | ADVANCED_SYSASSERT          
[41109.070327] iwlwifi 0000:01:00.0: 0xE3BC5146 | trm_hw_status0
[41109.070328] iwlwifi 0000:01:00.0: 0xADBDF8A5 | trm_hw_status1
[41109.070329] iwlwifi 0000:01:00.0: 0x116DC927 | branchlink2
[41109.070330] iwlwifi 0000:01:00.0: 0x60B3E877 | interruptlink1
[41109.070332] iwlwifi 0000:01:00.0: 0x6F7FF395 | interruptlink2
[41109.070333] iwlwifi 0000:01:00.0: 0xF8DF665C | data1
[41109.070334] iwlwifi 0000:01:00.0: 0xE3465DCF | data2
[41109.070335] iwlwifi 0000:01:00.0: 0xEDB7DBE0 | data3
[41109.070336] iwlwifi 0000:01:00.0: 0x059D2BD9 | beacon time
[41109.070337] iwlwifi 0000:01:00.0: 0x337F17D5 | tsf low
[41109.070338] iwlwifi 0000:01:00.0: 0x00A76268 | tsf hi
[41109.070339] iwlwifi 0000:01:00.0: 0x041AEBB1 | time gp1
[41109.070340] iwlwifi 0000:01:00.0: 0x97DBF981 | time gp2
[41109.070341] iwlwifi 0000:01:00.0: 0x3A5DF7CE | uCode revision type
[41109.070342] iwlwifi 0000:01:00.0: 0xD7A1A61E | uCode version major
[41109.070343] iwlwifi 0000:01:00.0: 0xF2C9598E | uCode version minor
[41109.070344] iwlwifi 0000:01:00.0: 0x75ED5B5F | hw version
[41109.070345] iwlwifi 0000:01:00.0: 0x253477B2 | board version
[41109.070346] iwlwifi 0000:01:00.0: 0xF8CBFDBF | hcmd
[41109.070347] iwlwifi 0000:01:00.0: 0xF47ACBB6 | isr0
[41109.070348] iwlwifi 0000:01:00.0: 0x78313B87 | isr1
[41109.070349] iwlwifi 0000:01:00.0: 0x2D9B1EBE | isr2
[41109.070350] iwlwifi 0000:01:00.0: 0x3FD776E4 | isr3
[41109.070351] iwlwifi 0000:01:00.0: 0x93EB66EE | isr4
[41109.070351] iwlwifi 0000:01:00.0: 0x67B815B8 | last cmd Id
[41109.070353] iwlwifi 0000:01:00.0: 0xE23AC6F4 | wait_event
[41109.070354] iwlwifi 0000:01:00.0: 0xAB360DCF | l2p_control
[41109.070355] iwlwifi 0000:01:00.0: 0x431991FC | l2p_duration
[41109.070356] iwlwifi 0000:01:00.0: 0x021AB723 | l2p_mhvalid
[41109.070357] iwlwifi 0000:01:00.0: 0xC1D149CB | l2p_addr_match
[41109.070358] iwlwifi 0000:01:00.0: 0xB8C2B1CA | lmpm_pmg_sel
[41109.070358] iwlwifi 0000:01:00.0: 0x837B3A97 | timestamp
[41109.070359] iwlwifi 0000:01:00.0: 0x68BD323F | flow_handler
[41109.070461] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[41109.070462] iwlwifi 0000:01:00.0: Status: 0x00000040, count: -550814268
[41109.070463] iwlwifi 0000:01:00.0: 0x5DB013FD | ADVANCED_SYSASSERT
[41109.070464] iwlwifi 0000:01:00.0: 0x06BBF592 | umac branchlink1
[41109.070466] iwlwifi 0000:01:00.0: 0x6F951D6F | umac branchlink2
[41109.070466] iwlwifi 0000:01:00.0: 0xD3DDF7F7 | umac interruptlink1
[41109.070468] iwlwifi 0000:01:00.0: 0x5620F8DF | umac interruptlink2
[41109.070469] iwlwifi 0000:01:00.0: 0x6D90F31E | umac data1
[41109.070470] iwlwifi 0000:01:00.0: 0x854AEA7F | umac data2
[41109.070471] iwlwifi 0000:01:00.0: 0xF346AA3D | umac data3
[41109.070472] iwlwifi 0000:01:00.0: 0x934AAFBD | umac major
[41109.070473] iwlwifi 0000:01:00.0: 0x51C33D9A | umac minor
[41109.070474] iwlwifi 0000:01:00.0: 0xA0337B9A | frame pointer
[41109.070476] iwlwifi 0000:01:00.0: 0xFCB9D924 | stack pointer
[41109.070477] iwlwifi 0000:01:00.0: 0xF129E2BF | last host cmd
[41109.070478] iwlwifi 0000:01:00.0: 0xE8EFA222 | isr status reg
[41109.070555] iwlwifi 0000:01:00.0: Fseq Registers:
[41109.070658] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_ERROR_CODE
[41109.070793] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_TOP_INIT_VERSION
[41109.070928] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_CNVIO_INIT_VERSION
[41109.071062] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_OTP_VERSION
[41109.071197] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_TOP_CONTENT_VERSION
[41109.071332] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_ALIVE_TOKEN
[41109.071466] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_CNVI_ID
[41109.071601] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | FSEQ_CNVR_ID
[41109.071736] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | CNVI_AUX_MISC_CHIP
[41109.071871] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP
[41109.072005] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[41109.072139] iwlwifi 0000:01:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[41109.072160] iwlwifi 0000:01:00.0: WRT: Collecting data: ini trigger 4 fired.
[41109.072166] ieee80211 phy0: Hardware restart was requested
[41113.041083] [drm] Fence fallback timer expired on ring gfx
[41113.577723] [drm] Fence fallback timer expired on ring gfx
[41114.244392] [drm] Fence fallback timer expired on ring gfx
[41114.751055] [drm] Fence fallback timer expired on ring gfx
[41115.787734] [drm] Fence fallback timer expired on ring gfx
[41116.644369] [drm] Fence fallback timer expired on ring gfx
[41117.841062] [drm] Fence fallback timer expired on ring gfx
[41118.374385] [drm] Fence fallback timer expired on ring gfx
[41118.881051] [drm] Fence fallback timer expired on ring gfx
[41119.924364] [drm] Fence fallback timer expired on ring sdma0
[41120.431032] [drm] Fence fallback timer expired on ring gfx
[41120.431033] [drm] Fence fallback timer expired on ring sdma0
[41120.937688] [drm] Fence fallback timer expired on ring gfx
[41120.937698] [drm] Fence fallback timer expired on ring sdma0
[41121.447689] [drm] Fence fallback timer expired on ring gfx
[41121.447691] [drm] Fence fallback timer expired on ring sdma0
[41121.947706] [drm] Fence fallback timer expired on ring sdma0
[41121.947708] [drm] Fence fallback timer expired on ring gfx
[41122.454352] [drm] Fence fallback timer expired on ring sdma0
[41122.457687] [drm] Fence fallback timer expired on ring gfx
[41122.961023] [drm] Fence fallback timer expired on ring gfx
[41122.961025] [drm] Fence fallback timer expired on ring sdma0
[41123.471015] [drm] Fence fallback timer expired on ring gfx
[41123.471019] [drm] Fence fallback timer expired on ring sdma0
[41123.981022] [drm] Fence fallback timer expired on ring gfx
[41124.484344] [drm] Fence fallback timer expired on ring gfx
[41124.987681] [drm] Fence fallback timer expired on ring gfx
[41125.691004] [drm] Fence fallback timer expired on ring sdma0
[41126.313432] iwlwifi 0000:01:00.0: Failing on timeout while stopping DMA channel 8 [0xa5a5a5a2]

Offline

#27 2021-01-08 03:25:49

Kewl
Wiki Maintainer
From: UK
Registered: 2018-03-09
Posts: 21

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

Same issue here with kernel 5.10.5 and AC 9260 card.
I have tried the parameters:

options iwlwifi 11n_disable=1 swcrypto=0 bt_coex_active=0 power_save=0

but for some reason I don't manage to connect to the ac network any longer with these params. 11n is not activated at the router level and disabling 11n at the card level should not have any impact but it does.

Last edited by Kewl (2021-01-08 03:27:54)

Offline

#28 2021-01-08 08:28:15

seth
Member
Registered: 2012-09-03
Posts: 18,168

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

Connect how? Did you try "manually"? (Don't forget to stop your network managing service)
At which stage does it fail?
Can you scan for the station? (Don't forget to stop your network managing service)
Did you isolate "11n_disable=1" as the crucial parameter?

Offline

#29 2021-01-08 12:47:19

Kewl
Wiki Maintainer
From: UK
Registered: 2018-03-09
Posts: 21

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

Whenever I add

11n_disable=1

I can scan with iwctl: "station wlan0 get-networks" shows my 801.11ac network, but trying to connect to it returns "Operation failed". I have tried with another Intel card AC8260 and have the same issue: whenever I disable 11n I cannot connect to ac anymore (and to n but this is intended).

I have also tried with wpa_supplicant which gives a bit more information on the error: "CTRL-EVENT-ASSOC-REJECT status_code=104", then "SME: Deauth request to the driver failed". The error 104 does not seem to be a documented one according to the Cisco deauth codes.

In conclusion, I can associate with a 801.11g (2.4 GHz) network or a 801.11a (5 GHz) but not 801.11ac (nor 801.11n obviously) with 11n_disable=1.
Therefore, if 11n_disable=1 disables both "n" and "ac" and this is the only known way to avoid the crash this is too limiting and I will look for a more stable ac capable card.

Last edited by Kewl (2021-01-09 01:48:09)

Offline

#30 2021-01-09 07:18:56

agapito
Member
From: Spain
Registered: 2008-11-13
Posts: 512

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

This is my device: Network controller: Intel Corporation Wireless-AC 9260 (rev 29)

I´m not using a wifi network right now but i had the same problem in the past. My connection wasn´t stable when my router was on "N mode", the solution was to change the router to the slow but stable "G mode". What i can tell you is: this is not a Linux related problem because because i had the same behavior on Windows too. I found that this adapter is not compatible with some routers on 5 Ghz networks.

The same adaptor is working super stable when my phone is on wifi tethering mode using an AC network. So what I think is that the only way to solve this problem is changing the router or buying another wifi adaptor.


Excuse my poor English.

Offline

#31 2021-01-09 09:47:56

seth
Member
Registered: 2012-09-03
Posts: 18,168

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

801.11n actually covers 2.4GHz and 5GHz while 801.11ac is 5GHz only so if the problem is w/ the 5GHz band I'd try to set the router to allow 801.11n and try to connect on 2.4GHz

Since

parm:           11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: disable agg RX, 8 enable agg TX (uint)

and 11ac is an extension of 11n that makes use of those features it's reasonable to assume that blocking 11n in the driver will implicitly block 11ac

nb. that  those parameters "fix" the issue anecdotally - it's not certain why or how of by what, so trying 11n/2.4 instead of 11n/5 or 11ac/5 might suggest that the firmware crashes because of the used frequency…

Offline

#32 2021-01-09 11:15:31

davc0n
Member
Registered: 2020-02-01
Posts: 50

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

Kewl wrote:

In conclusion, I can associate with a 801.11g (2.4 GHz) network or a 801.11a (5 GHz) but not 801.11ac (nor 801.11n obviously) with 11n_disable=1.
Therefore, if 11n_disable=1 disables both "n" and "ac" and this is the only known way to avoid the crash this is too limiting and I will look for a more stable ac capable card.

How can I find the protocol in use ?

I use a 2.4 GHz network btw, with the same wireless device (AC 9260, rev 29), and disabling 11n didn't solve the issue though.

Offline

#33 2021-01-09 14:10:32

seth
Member
Registered: 2012-09-03
Posts: 18,168

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

iw dev <interface> link
iw dev <interface> station dump

If there's "MCS" it's 11n or 11ac, 20/40MHz is probably 11n, 80/160MHz is 11ac for sure
2.4GHz is 11n for sure, 5GHz could be 11n or 11ac

Notice that a bunch of module options are set by the people claiming them to be an effective mitigation and a different option or a combination could be the relevant one.

Offline

#34 2021-01-09 15:42:19

Kewl
Wiki Maintainer
From: UK
Registered: 2018-03-09
Posts: 21

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

Thanks seth for your help.
I am now testing the 9260NGW with LTS 5.4.87, iwlwifi has not crashed for the past 24 hours (which does not mean it will not), I am testing in ac mode without any parameter.

Otherwise I will switch to a Qualcomm card, I have a QCA9377 running in ac at 433Mbps which has never caused any issue and they have the QCA6174A with 2 streams (867Mbps) that would be worth testing, both cards have BT 5.0 and are supported by the ath10k driver. This is out of scope of this thread but to give some alternatives for the ones who would be really stuck with this crash.

Last edited by Kewl (2021-01-10 01:01:25)

Offline

#35 2021-01-12 18:22:08

davc0n
Member
Registered: 2020-02-01
Posts: 50

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

seth wrote:

Notice that a bunch of module options are set by the people claiming them to be an effective mitigation and a different option or a combination could be the relevant one.

Just tested with all the parameters proposed by sinatosk, and the issue still occurs.

Offline

#36 2021-01-12 18:47:59

Kewl
Wiki Maintainer
From: UK
Registered: 2018-03-09
Posts: 21

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

davc0n wrote:
seth wrote:

Notice that a bunch of module options are set by the people claiming them to be an effective mitigation and a different option or a combination could be the relevant one.

Just tested with all the parameters proposed by sinatosk, and the issue still occurs.

I suggest you try with Linux LTS, it has not crashed for a few days with LTS on my side then I am facing some new connection issues after suspend I did not have with the most recent kernel I have not resolved yet.

Offline

#37 2021-01-12 19:39:31

davc0n
Member
Registered: 2020-02-01
Posts: 50

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

Thanks for the suggestion. I already use LTS kernel, tried also on stable though and noticed no differences.

Offline

#38 2021-01-17 09:14:49

fartyg
Member
Registered: 2021-01-17
Posts: 1

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

I have this old USB drive that I think might soon be dying on me. When I plug it in it throws a few errors in journalctl, but always works in the end. However when I insert it into the usb slot I was able to produce this error multiple times:

jan 17 10:35:23 arch kernel: usb-storage 2-2:1.0: USB Mass Storage device detected
jan 17 10:35:23 arch kernel: scsi host2: usb-storage 2-2:1.0
jan 17 10:35:24 arch kernel: scsi 2:0:0:0: Direct-Access     WD       My Passport 259F 1004 PQ: 0 ANSI: 6
jan 17 10:35:24 arch kernel: scsi 2:0:0:1: Enclosure         WD       SES Device       1004 PQ: 0 ANSI: 6
jan 17 10:35:24 arch kernel: ses 2:0:0:1: Attached Enclosure device
jan 17 10:35:24 arch kernel: sd 2:0:0:0: [sdb] Spinning up disk...
jan 17 10:35:28 arch kernel: ses 2:0:0:1: Wrong diagnostic page; asked for 1 got 8
jan 17 10:35:28 arch kernel: ses 2:0:0:1: Failed to get diagnostic page 0x1
jan 17 10:35:28 arch kernel: ses 2:0:0:1: Failed to bind enclosure -19
jan 17 10:35:29 arch kernel: .ready
jan 17 10:35:29 arch kernel: sd 2:0:0:0: [sdb] 1953458176 512-byte logical blocks: (1.00 TB/931 GiB)
jan 17 10:35:29 arch kernel: sd 2:0:0:0: [sdb] Write Protect is off
jan 17 10:35:29 arch kernel: sd 2:0:0:0: [sdb] Mode Sense: 47 00 10 08
jan 17 10:35:29 arch kernel: sd 2:0:0:0: [sdb] No Caching mode page found
jan 17 10:35:29 arch kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
jan 17 10:35:30 arch kernel:  sdb: sdb1
jan 17 10:35:30 arch kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: Queue 11 is active on fifo 1 and stuck for 10000 ms. SW [171, 181] HW [171, 181] FH TRB=0x0c010b0b4
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: Status: 0x00000040, count: 6
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: Loaded firmware version: 29.198743027.0 7265D-29.ucode
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00800634 | trm_hw_status0
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00043D6C | branchlink2
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x0004AFD6 | interruptlink1
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x0000AD8C | interruptlink2
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | data1
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000080 | data2
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x07030000 | data3
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x28002E5B | beacon time
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x426471A4 | tsf low
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000004 | tsf hi
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | time gp1
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x141A0876 | time gp2
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000001 | uCode revision type
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x0000001D | uCode version major
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x0BD893F3 | uCode version minor
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000210 | hw version
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00489200 | board version
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x0BAB001C | hcmd
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0xA4022002 | isr0
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x01000000 | isr1
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x0000000A | isr2
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x004138C5 | isr3
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | isr4
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x008D019C | last cmd Id
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | wait_event
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000080 | l2p_control
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00012030 | l2p_duration
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x000000CE | l2p_addr_match
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000007 | lmpm_pmg_sel
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x14101241 | timestamp
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00348898 | flow_handler
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: Fseq Registers:
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_ERROR_CODE
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_TOP_INIT_VERSION
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVIO_INIT_VERSION
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_OTP_VERSION
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_TOP_CONTENT_VERSION
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_ALIVE_TOKEN
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVI_ID
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | FSEQ_CNVR_ID
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | CNVI_AUX_MISC_CHIP
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | CNVR_AUX_MISC_CHIP
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
jan 17 10:35:33 arch kernel: iwlwifi 0000:02:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR

I went into router + extender and set the channel width to 20Mhz instead of auto (20/40MHZ) and it doesn't happen now. The disk still errors (but works), but iwlwifi doesnt crash.

edit: Am using 11n_disable=8 as it gives me higher speeds.

Last edited by fartyg (2021-01-17 09:15:47)

Offline

#39 Yesterday 08:47:26

Convergence
Member
Registered: 2005-07-02
Posts: 377

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

Kewl wrote:

Thanks seth for your help.
I am now testing the 9260NGW with LTS 5.4.87, iwlwifi has not crashed for the past 24 hours (which does not mean it will not), I am testing in ac mode without any parameter.

Otherwise I will switch to a Qualcomm card, I have a QCA9377 running in ac at 433Mbps which has never caused any issue and they have the QCA6174A with 2 streams (867Mbps) that would be worth testing, both cards have BT 5.0 and are supported by the ath10k driver. This is out of scope of this thread but to give some alternatives for the ones who would be really stuck with this crash.

I have a I'd like to jump ship to a Qualcomm card, but I can't find one that fits my needs.  I need it to be PCIE, and really fast.  It seems like Intel kind of dominates in that category, but the cards are unreliable on Linux.  sad

If I search for QCA6174A on amazon, or anywhere, I either get m.2 type cards, or more Intel cards. Maybe Qualcomm wifi chips don't often make their way into Desktop parts?

PS:  I currently have a Wi-Fi 6 AX200, which is plenty fast, but it keeps crashing my computer.  This is my second Intel device, I replaced the old one thinking that it was a hardware problem, not a driver problem.  So I'd recommend just staying away from Intel chips if you need performance at 5ghz (if an appropriate non Intel part can be found)


It's a very deadly weapon to know what you're doing
---  William Murderface

Offline

#40 Yesterday 21:28:46

Kewl
Wiki Maintainer
From: UK
Registered: 2018-03-09
Posts: 21

Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x0.

Convergence wrote:
Kewl wrote:

Thanks seth for your help.
I am now testing the 9260NGW with LTS 5.4.87, iwlwifi has not crashed for the past 24 hours (which does not mean it will not), I am testing in ac mode without any parameter.

Otherwise I will switch to a Qualcomm card, I have a QCA9377 running in ac at 433Mbps which has never caused any issue and they have the QCA6174A with 2 streams (867Mbps) that would be worth testing, both cards have BT 5.0 and are supported by the ath10k driver. This is out of scope of this thread but to give some alternatives for the ones who would be really stuck with this crash.

I have a I'd like to jump ship to a Qualcomm card, but I can't find one that fits my needs.  I need it to be PCIE, and really fast.  It seems like Intel kind of dominates in that category, but the cards are unreliable on Linux.  sad

If I search for QCA6174A on amazon, or anywhere, I either get m.2 type cards, or more Intel cards. Maybe Qualcomm wifi chips don't often make their way into Desktop parts?

PS:  I currently have a Wi-Fi 6 AX200, which is plenty fast, but it keeps crashing my computer.  This is my second Intel device, I replaced the old one thinking that it was a hardware problem, not a driver problem.  So I'd recommend just staying away from Intel chips if you need performance at 5ghz (if an appropriate non Intel part can be found)

You could get a M.2 to PCIe adapter for about $15 (adapter and antennas) it could give you more choice of cards.
I gave up with the 9260NGW which started to crash with Linux LTS as well. I am testing 8260NGW which seems to be a bit more stable so far in 802.11ac (in 2 * 80MHz mode = 866mbps). The main difference is that it does not support 160MHz and has Bluetooth 4.2 vs 5.1.

Last edited by Kewl (Yesterday 21:49:07)

Offline

Board footer

Powered by FluxBB