You are not logged in.

Pages: 1

#1 2026-05-19 20:21:06

DinoSaar
Member
Registered: 2026-05-19
Posts: 8

iwlwifi started failing consistently, trying to determine root cause

Hello everyone, first post here.

I have an old Dell mini PC that I use as a little homelab running Arch Linux.
I've been running it for about 3 years without issues, but in the last few weeks I've been having an issue where it disconnects from the network a day or two after booting, with what looks like a failure in iwlwifi.
This is what I see in journalctl at the time of failure:

May 16 22:46:44 saarver kernel: ------------[ cut here ]------------
May 16 22:46:44 saarver kernel: Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff)
May 16 22:46:44 saarver kernel: WARNING: drivers/net/wireless/intel/iwlwifi/pcie/gen1_2/trans.c:2387 at _iwl_trans_pcie_grab_nic_access+0x16b/0x1e0 [iwlwifi], CPU#2: swapper/2/0
May 16 22:46:44 saarver kernel: Modules linked in: nf_conntrack_netlink xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE bridge stp llc xfrm_user xfrm_algo xt_set ip_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat x_tables nf_tables wireguard libcurve25519 ip6_udp_tunnel udp_tunnel ccm overlay vfat fat intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp snd_ctl_led iwlmvm kvm_intel mac80211 snd_hda_codec_alc269 kvm snd_hda_codec_realtek_lib snd_hda_scodec_component snd_hda_codec_intelhdmi snd_hda_codec_generic libarc4 snd_hda_codec_hdmi irqbypass snd_hda_intel ghash_clmulni_intel iwlwifi btusb platform_profile aesni_intel snd_hda_codec btmtk snd_hda_core rapl btrtl at24 btbcm dell_wmi mei_wdt mei_pxp mei_hdcp snd_intel_dspcfg i2c_i801 btintel intel_cstate snd_intel_sdw_acpi dell_smbios i2c_smbus cfg80211 snd_hwdep dcdbas bluetooth sparse_keymap e1000e intel_uncore wmi_bmof pcspkr i2c_mux mei_me intel_oc_wdt dell_wmi_descriptor snd_pcm spi_nor iTCO_wdt mei snd_timer
May 16 22:46:44 saarver kernel:  rfkill mtd ptp intel_pmc_bxt snd pps_core soundcore mac_hid squashfs loop nfnetlink dm_mod ses enclosure scsi_transport_sas ata_generic pata_acpi uas usb_storage i915 spi_intel_platform spi_intel i2c_algo_bit drm_buddy ttm intel_gtt drm_display_helper video ata_piix cec wmi lpc_ich
May 16 22:46:44 saarver kernel: CPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted 7.0.3-arch1-2 #1 PREEMPT(full)  88a2c8f55a128ad9505b4014386291e7c04d5e88
May 16 22:46:44 saarver kernel: Hardware name: Dell Inc. OptiPlex 9020M/0Y5DDC, BIOS A19 05/30/2019
May 16 22:46:44 saarver kernel: RIP: 0010:_iwl_trans_pcie_grab_nic_access+0x171/0x1e0 [iwlwifi]
May 16 22:46:44 saarver kernel: Code: 15 3c 83 d9 48 8b 5c 24 08 4c 8b 64 24 18 4c 8b 74 24 28 4c 8b 7c 24 30 e9 b8 fe ff ff 48 8d 3d c5 fb 56 00 89 c6 89 44 24 04 <67> 48 0f b9 3a 48 8b b3 88 1a 00 00 48 89 df e8 fb 05 ff ff 83 7c
May 16 22:46:44 saarver kernel: RSP: 0018:ffffd4d280160dc8 EFLAGS: 00010246
May 16 22:46:44 saarver kernel: RAX: 00000000ffffffff RBX: ffff8d78872b8028 RCX: 00000000ffffffff
May 16 22:46:44 saarver kernel: RDX: 0000000000004e34 RSI: 00000000ffffffff RDI: ffffffffc12876d0
May 16 22:46:44 saarver kernel: RBP: 0000000000000000 R08: 0000000000004df3 R09: 0000000000000002
May 16 22:46:44 saarver kernel: R10: 00000000000000a9 R11: 0000000000000000 R12: 0000000000000011
May 16 22:46:44 saarver kernel: R13: ffffffffc0d0e730 R14: 0000000000000008 R15: 0000000000000001
May 16 22:46:44 saarver kernel: FS:  0000000000000000(0000) GS:ffff8d79fa667000(0000) knlGS:0000000000000000
May 16 22:46:44 saarver kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 16 22:46:44 saarver kernel: CR2: 00007f7543d4be64 CR3: 000000020fc24004 CR4: 00000000001726f0
May 16 22:46:44 saarver kernel: Call Trace:
May 16 22:46:44 saarver kernel:  <IRQ>
May 16 22:46:44 saarver kernel:  iwl_trans_pcie_grab_nic_access+0x1f/0x50 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  ? enqueue_task_fair+0x596/0xbe0
May 16 22:46:44 saarver kernel:  iwl_read_prph+0x1b/0x60 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  ? psi_task_change+0xf5/0x100
May 16 22:46:44 saarver kernel:  iwl_txq_log_scd_error+0x148/0x230 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  ? __pfx_iwl_txq_stuck_timer+0x10/0x10 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  iwl_txq_stuck_timer+0x3c/0x60 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  ? __pfx_iwl_txq_stuck_timer+0x10/0x10 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  call_timer_fn+0x2a/0x140
May 16 22:46:44 saarver kernel:  __run_timers+0x269/0x330
May 16 22:46:44 saarver kernel:  run_timer_softirq+0x86/0xf0
May 16 22:46:44 saarver kernel:  ? irqtime_account_irq+0x30/0xc0
May 16 22:46:44 saarver kernel:  handle_softirqs+0xe8/0x2c0
May 16 22:46:44 saarver kernel:  __irq_exit_rcu+0xc9/0xf0
May 16 22:46:44 saarver kernel:  sysvec_apic_timer_interrupt+0x71/0x90
May 16 22:46:44 saarver kernel:  </IRQ>
May 16 22:46:44 saarver kernel:  <TASK>
May 16 22:46:44 saarver kernel:  asm_sysvec_apic_timer_interrupt+0x1a/0x20
May 16 22:46:44 saarver kernel: RIP: 0010:cpuidle_enter_state+0xbb/0x440
May 16 22:46:44 saarver kernel: Code: 00 00 e8 98 fc ec fe e8 93 ee ff ff 48 89 c5 0f 1f 44 00 00 31 ff e8 d4 50 eb fe 45 84 ff 0f 85 74 01 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 cb 01 00 00 44 89 f1 48 2b 2c 24 48 6b d1 68 48 89
May 16 22:46:44 saarver kernel: RSP: 0018:ffffd4d2800e7e70 EFLAGS: 00000246
May 16 22:46:44 saarver kernel: RAX: ffff8d79fa667000 RBX: 0000000000000005 RCX: 0000000000000000
May 16 22:46:44 saarver kernel: RDX: 00009ff2f41865a6 RSI: fffffffbfca06ce7 RDI: 0000000000000000
May 16 22:46:44 saarver kernel: RBP: 00009ff2f41865a6 R08: 0000000000000005 R09: ffff8d7996b21820
May 16 22:46:44 saarver kernel: R10: ffff8d7996b217c0 R11: 0000000000000004 R12: ffff8d7996b3adc0
May 16 22:46:44 saarver kernel: R13: ffffffff9ba0cb20 R14: 0000000000000005 R15: 0000000000000000
May 16 22:46:44 saarver kernel:  cpuidle_enter+0x31/0x50
May 16 22:46:44 saarver kernel:  do_idle+0x14b/0x2a0
May 16 22:46:44 saarver kernel:  cpu_startup_entry+0x29/0x30
May 16 22:46:44 saarver kernel:  start_secondary+0x119/0x150
May 16 22:46:44 saarver kernel:  common_startup_64+0x13e/0x141
May 16 22:46:44 saarver kernel:  </TASK>
May 16 22:46:44 saarver kernel: ---[ end trace 0000000000000000 ]---
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: iwlwifi transaction failed, dumping registers
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: iwlwifi device config registers:
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000000: 08b18086 00100000 028000bb 00000000 00000004 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000020: 00000000 00000000 00000000 c4708086 00000000 000000c8 00000000 00000100
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000040: 00020010 10008ec0 001b0c10 0006ec11 10110000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000060: 00000000 00080812 00000005 00000000 00010001 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000080: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 000000a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 000000c0: 00000000 00000000 c823d001 0d000000 00804005 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 000000e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000100: 14010001 00100000 00000000 00462031 000031c1 00002000 00000014 40000001
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000120: 0000000f f7c00460 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000140: 14c10003 ffc3371e cc3d82ff 15410018 00000000 0001000b 0141cafe 00f01e1f
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: iwlwifi device memory mapped registers:
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: iwlwifi device AER capability structure:
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000000: 14010001 00100000 00000000 00462031 000031c1 00002000 00000014 40000001
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000020: 0000000f f7c00460 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: iwlwifi parent port (0000:00:1c.3) config registers:
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000000: 8c168086 00100507 060400d4 00810010 00000000 00000000 00020200 200000f0
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000020: f7c0f7c0 0001fff1 00000000 00000000 00000000 00000040 00000000 0012040a
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000040: 01428010 00008000 00110000 04323c12 30110c42 001cb200 01480000 00000008
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000060: 00000000 00000817 00000000 00000000 00010002 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000080: 00019005 fee00258 00000000 00000000 0000a00d 06691028 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000000a0: c8030001 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000000c0: 00000000 00000000 00000000 00000000 01000000 00001842 0b118008 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000000e0: 00000300 88aa88aa 00000001 00000000 00000050 0c000040 08060fb1 04002800
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000100: 00000000 00000000 00000000 00060011 000011c1 00002000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000120: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000140: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000160: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000180: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000001a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000001c0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000001e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000200: 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [83, 104] HW [90, 90] FH TRB=0x05a5a5a5a

I can't think of any changes in the network or to the computer that should have affected anything.
I think it could be a hardware issue since this computer is relatively old (i5 4th gen), but I don't know how I would verify this.
Does this log suggest anything for sure? What else can I do to find the root cause?

Offline

#2 2026-05-20 02:21:22

clfarron4
Member
From: London, UK
Registered: 2013-06-28
Posts: 2,174
Website

Re: iwlwifi started failing consistently, trying to determine root cause

Did it happen after an update? If so, what happens if you roll back to before the update? You should be able to test this using the Arch Linux Archive: https://wiki.archlinux.org/title/Arch_Linux_Archive

Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository

Offline

#3 2026-05-20 04:56:04

DinoSaar
Member
Registered: 2026-05-19
Posts: 8

Re: iwlwifi started failing consistently, trying to determine root cause

clfarron4 wrote:

Did it happen after an update? If so, what happens if you roll back to before the update? You should be able to test this using the Arch Linux Archive: https://wiki.archlinux.org/title/Arch_Linux_Archive

I don't  remember exactly, but it could be related to an update. iwlwifi is part of the kernel, so would I need to roll back the kernel, right?

Offline

#4 2026-05-20 06:33:33

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,838

Re: iwlwifi started failing consistently, trying to determine root cause

Smells like power saving, does it happen if you keep a life-line (eternal ping to your _gateway or google.com) on the NIC?
https://wiki.archlinux.org/title/Power_ … interfaces (obviously try the opposite of saving, iwlmvm.power_scheme=1) and also pcie_aspm=off (can't tell whether the system supports aspm from that log-bit)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2026-05-21 10:04:19

DinoSaar
Member
Registered: 2026-05-19
Posts: 8

Re: iwlwifi started failing consistently, trying to determine root cause

seth wrote:

Smells like power saving, does it happen if you keep a life-line (eternal ping to your _gateway or google.com) on the NIC?
https://wiki.archlinux.org/title/Power_ … interfaces (obviously try the opposite of saving, iwlmvm.power_scheme=1) and also pcie_aspm=off (can't tell whether the system supports aspm from that log-bit)

It is connected to a wireguard server, shouldn't the handshakes be enough to keep it alive?

Last edited by DinoSaar (2026-05-21 10:05:40)

Offline

#6 2026-05-21 13:26:28

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,838

Re: iwlwifi started failing consistently, trying to determine root cause

At what frequency do those happen?
Have you tried perma-pinging something?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2026-05-21 14:56:15

DinoSaar
Member
Registered: 2026-05-19
Posts: 8

Re: iwlwifi started failing consistently, trying to determine root cause

seth wrote:

At what frequency do those happen?
Have you tried perma-pinging something?

Over the last few weeks it happened usually a day or two after boot. Today it happened again about 15 minutes after boot, but hasn't happened again since.
I'll try a permanent ping to see if it helps.

Offline

#8 2026-05-21 15:12:58

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,838

Re: iwlwifi started failing consistently, trying to determine root cause

No, I meant how frequent you run a wireguard handshake w/ the VPN - once a day won't help much, even once an hour isn't enough itr.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2026-05-21 15:22:43

DinoSaar
Member
Registered: 2026-05-19
Posts: 8

Re: iwlwifi started failing consistently, trying to determine root cause

seth wrote:

No, I meant how frequent you run a wireguard handshake w/ the VPN - once a day won't help much, even once an hour isn't enough itr.

Ah, my bad. It's configured with persistent keepalive every 25 seconds.

Offline

#10 2026-05-21 19:47:43

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,838

Re: iwlwifi started failing consistently, trying to determine root cause

That should™ keep it powered … do you have a complete journal for an occurrence?
(Maybe something builds up to it or there's noise on the bus from another device)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2026-05-23 17:30:13

DinoSaar
Member
Registered: 2026-05-19
Posts: 8

Re: iwlwifi started failing consistently, trying to determine root cause

seth wrote:

do you have a complete journal for an occurrence?
(Maybe something builds up to it or there's noise on the bus from another device)

Here is a complete journal.
By the way, I've changed the kernel to LTS to see if it helps. So far I haven't had issues but it's only been a day.

Offline

#12 2026-05-23 21:17:53

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,838

Re: iwlwifi started failing consistently, trying to determine root cause

May 16 20:01:00 saarver CROND[876419]: (root) CMD (run-parts /etc/cron.hourly)
May 16 20:01:00 saarver CROND[876418]: (root) CMDEND (run-parts /etc/cron.hourly)
May 16 20:38:47 saarver wpa_supplicant[491]: wlp2s0: RSN: Group rekeying completed with 3c:7c:3f:66:d2:8c [GTK=CCMP]
May 16 21:01:00 saarver CROND[895171]: (root) CMD (run-parts /etc/cron.hourly)
May 16 21:01:00 saarver CROND[895170]: (root) CMDEND (run-parts /etc/cron.hourly)
May 16 21:38:47 saarver wpa_supplicant[491]: wlp2s0: RSN: Group rekeying completed with 3c:7c:3f:66:d2:8c [GTK=CCMP]
May 16 21:58:00 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-BEACON-LOSS
May 16 21:58:01 saarver NetworkManager[460]: <info>  [1778957881.0092] device (wlp2s0): ip:dhcp4: restarting
May 16 21:58:01 saarver NetworkManager[460]: <info>  [1778957881.0092] dhcp4 (wlp2s0): canceled DHCP transaction
May 16 21:58:01 saarver NetworkManager[460]: <info>  [1778957881.0092] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
May 16 21:58:01 saarver NetworkManager[460]: <info>  [1778957881.0092] dhcp4 (wlp2s0): state changed no lease
May 16 21:58:01 saarver NetworkManager[460]: <info>  [1778957881.0093] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
May 16 21:58:01 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=3c:7c:3f:66:d2:8c reason=4 locally_generated=1
May 16 21:58:01 saarver wpa_supplicant[491]: wlp2s0: Added BSSID 3c:7c:3f:66:d2:8c into ignore list, ignoring for 10 seconds
May 16 21:58:01 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 16 21:58:01 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 16 21:58:01 saarver NetworkManager[460]: <info>  [1778957881.0593] device (wlp2s0): supplicant interface state: completed -> disconnected
May 16 21:58:01 saarver NetworkManager[460]: <info>  [1778957881.0594] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> disconnected
May 16 21:58:01 saarver NetworkManager[460]: <info>  [1778957881.1549] device (wlp2s0): supplicant interface state: disconnected -> scanning
May 16 21:58:01 saarver NetworkManager[460]: <info>  [1778957881.1550] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
May 16 21:58:04 saarver wpa_supplicant[491]: wlp2s0: Removed BSSID 3c:7c:3f:66:d2:8c from ignore list (clear)
May 16 21:58:04 saarver wpa_supplicant[491]: wlp2s0: SME: Trying to authenticate with 3c:7c:3f:66:d2:8c (SSID='Clyde' freq=5180 MHz)
May 16 21:58:04 saarver kernel: wlp2s0: authenticate with 3c:7c:3f:66:d2:8c (local address=cc:3d:82:c3:37:1e)
May 16 21:58:04 saarver kernel: wlp2s0: send auth to 3c:7c:3f:66:d2:8c (try 1/3)
May 16 21:58:04 saarver NetworkManager[460]: <info>  [1778957884.3656] device (wlp2s0): supplicant interface state: scanning -> authenticating
May 16 21:58:04 saarver NetworkManager[460]: <info>  [1778957884.3656] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
May 16 21:58:04 saarver kernel: wlp2s0: send auth to 3c:7c:3f:66:d2:8c (try 2/3)
May 16 21:58:04 saarver kernel: wlp2s0: send auth to 3c:7c:3f:66:d2:8c (try 3/3)
May 16 21:58:04 saarver kernel: wlp2s0: authentication with 3c:7c:3f:66:d2:8c timed out
May 16 21:58:04 saarver wpa_supplicant[491]: wlp2s0: Added BSSID 3c:7c:3f:66:d2:8c into ignore list, ignoring for 10 seconds
May 16 21:58:04 saarver NetworkManager[460]: <info>  [1778957884.5137] device (wlp2s0): supplicant interface state: authenticating -> disconnected
May 16 21:58:04 saarver NetworkManager[460]: <info>  [1778957884.5138] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> disconnected
May 16 21:58:05 saarver NetworkManager[460]: <info>  [1778957885.0144] device (wlp2s0): supplicant interface state: disconnected -> scanning
May 16 21:58:05 saarver NetworkManager[460]: <info>  [1778957885.0145] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
May 16 21:58:08 saarver wpa_supplicant[491]: wlp2s0: Removed BSSID 3c:7c:3f:66:d2:8c from ignore list (clear)
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.2270] dhcp4 (wlp2s0): state changed no lease
May 16 21:58:16 saarver NetworkManager[460]: <warn>  [1778957896.2769] device (wlp2s0): link timed out.
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.2799] device (wlp2s0): state change: activated -> failed (reason 'ssid-not-found', managed-type: 'full')
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.2907] device (wlp2s0): set-hw-addr: set MAC address to AA:2E:71:AE:04:22 (scanning)
May 16 21:58:16 saarver NetworkManager[460]: <warn>  [1778957896.2936] device (wlp2s0): Activation: failed for connection 'Clyde'
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.2952] device (wlp2s0): supplicant interface state: scanning -> disconnected
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.2952] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> disconnected
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.2958] device (wlp2s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
May 16 21:58:16 saarver wpa_supplicant[491]: wlp2s0: Reject scan trigger since one is already pending
May 16 21:58:16 saarver systemd[1]: Starting Network Manager Script Dispatcher Service...
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.3001] dhcp4 (wlp2s0): canceled DHCP transaction
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.3001] dhcp4 (wlp2s0): state changed no lease
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.3012] manager: NetworkManager state is now CONNECTED_LOCAL
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.3016] device (wlp2s0): supplicant interface state: disconnected -> scanning
May 16 21:58:16 saarver NetworkManager[460]: <info>  [1778957896.3017] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
May 16 21:58:16 saarver systemd[1]: Started Network Manager Script Dispatcher Service.
May 16 21:58:19 saarver NetworkManager[460]: <info>  [1778957899.4127] device (wlp2s0): supplicant interface state: scanning -> inactive
May 16 21:58:19 saarver NetworkManager[460]: <info>  [1778957899.4133] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> inactive
May 16 21:58:26 saarver systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3061] policy: auto-activating connection 'Clyde' (b3964eb0-4465-4c64-98b9-6ab0a587d43a)
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3072] device (wlp2s0): Activation: starting connection 'Clyde' (b3964eb0-4465-4c64-98b9-6ab0a587d43a)
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3075] device (wlp2s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3079] manager: NetworkManager state is now CONNECTING
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3223] device (wlp2s0): set-hw-addr: reset MAC address to CC:3D:82:C3:37:1E (preserve)
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3239] device (wlp2s0): state change: prepare -> config (reason 'none', managed-type: 'full')
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3241] device (wlp2s0): Activation: (wifi) access point 'Clyde' has security, but secrets are required.
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3241] device (wlp2s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3242] sup-iface[7ad79dc0c6bfe11b,0,wlp2s0]: wps: type pbc start...
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3253] device (wlp2s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3256] device (wlp2s0): state change: prepare -> config (reason 'none', managed-type: 'full')
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: WPS-PBC-ACTIVE
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: WPS-CANCEL
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3261] device (wlp2s0): Activation: (wifi) connection 'Clyde' has security, and secrets exist.  No new secrets needed.
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3261] Config: added 'ssid' value 'Clyde'
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3261] Config: added 'scan_ssid' value '1'
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3261] Config: added 'bgscan' value 'simple:30:-65:300'
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3261] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3261] Config: added 'auth_alg' value 'OPEN'
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3261] Config: added 'psk' value '<hidden>'
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3265] device (wlp2s0): supplicant interface state: inactive -> scanning
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3265] device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> scanning
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: SME: Trying to authenticate with 3c:7c:3f:66:d2:88 (SSID='Clyde' freq=2457 MHz)
May 16 21:58:37 saarver kernel: wlp2s0: authenticate with 3c:7c:3f:66:d2:88 (local address=cc:3d:82:c3:37:1e)
May 16 21:58:37 saarver kernel: wlp2s0: send auth to 3c:7c:3f:66:d2:88 (try 1/3)
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3521] device (wlp2s0): supplicant interface state: scanning -> authenticating
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3521] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: Trying to associate with 3c:7c:3f:66:d2:88 (SSID='Clyde' freq=2457 MHz)
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3536] device (wlp2s0): supplicant interface state: authenticating -> associating
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3536] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
May 16 21:58:37 saarver kernel: wlp2s0: authenticated
May 16 21:58:37 saarver kernel: wlp2s0: associate with 3c:7c:3f:66:d2:88 (try 1/3)
May 16 21:58:37 saarver kernel: wlp2s0: RX AssocResp from 3c:7c:3f:66:d2:88 (capab=0x1411 status=0 aid=19)
May 16 21:58:37 saarver kernel: wlp2s0: associated
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: Associated with 3c:7c:3f:66:d2:88
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3666] device (wlp2s0): supplicant interface state: associating -> associated
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3666] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> associated
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3727] device (wlp2s0): supplicant interface state: associated -> 4way_handshake
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3727] device (p2p-dev-wlp2s0): supplicant management interface state: associated -> 4way_handshake
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: WPA: Key negotiation completed with 3c:7c:3f:66:d2:88 [PTK=CCMP GTK=CCMP]
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 3c:7c:3f:66:d2:88 completed [id=0 id_str=]
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3922] device (wlp2s0): supplicant interface state: 4way_handshake -> completed
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3923] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Clyde"
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3923] device (p2p-dev-wlp2s0): supplicant management interface state: 4way_handshake -> completed
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3924] device (wlp2s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
May 16 21:58:37 saarver NetworkManager[460]: <info>  [1778957917.3929] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
May 16 21:58:38 saarver NetworkManager[460]: <info>  [1778957918.9259] dhcp4 (wlp2s0): state changed new lease, address=192.168.50.61, acd pending
May 16 21:58:39 saarver NetworkManager[460]: <info>  [1778957919.0950] dhcp4 (wlp2s0): state changed new lease, address=192.168.50.61
May 16 21:58:39 saarver NetworkManager[460]: <info>  [1778957919.0967] policy: set 'Clyde' (wlp2s0) as default for IPv4 routing and DNS
May 16 21:58:39 saarver NetworkManager[460]: <info>  [1778957919.1185] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
May 16 21:58:39 saarver systemd[1]: Starting Network Manager Script Dispatcher Service...
May 16 21:58:39 saarver systemd[1]: Started Network Manager Script Dispatcher Service.
May 16 21:58:39 saarver NetworkManager[460]: <info>  [1778957919.1472] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
May 16 21:58:39 saarver NetworkManager[460]: <info>  [1778957919.1474] device (wlp2s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
May 16 21:58:39 saarver NetworkManager[460]: <info>  [1778957919.1477] manager: NetworkManager state is now CONNECTED_SITE
May 16 21:58:39 saarver NetworkManager[460]: <info>  [1778957919.1488] device (wlp2s0): Activation: successful, device activated.
May 16 21:58:40 saarver NetworkManager[460]: <info>  [1778957920.5274] manager: NetworkManager state is now CONNECTED_GLOBAL
May 16 21:58:49 saarver systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
May 16 22:01:00 saarver CROND[913747]: (root) CMD (run-parts /etc/cron.hourly)
May 16 22:01:00 saarver CROND[913746]: (root) CMDEND (run-parts /etc/cron.hourly)
May 16 22:03:37 saarver wpa_supplicant[491]: wlp2s0: Reject scan trigger since one is already pending
May 16 22:08:37 saarver wpa_supplicant[491]: wlp2s0: Reject scan trigger since one is already pending
May 16 22:11:48 saarver systemd[1]: Starting Cleanup of Temporary Directories...
May 16 22:11:48 saarver systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
May 16 22:11:48 saarver systemd[1]: Finished Cleanup of Temporary Directories.
May 16 22:13:37 saarver wpa_supplicant[491]: wlp2s0: Reject scan trigger since one is already pending
May 16 22:18:37 saarver wpa_supplicant[491]: wlp2s0: Reject scan trigger since one is already pending
May 16 22:23:37 saarver wpa_supplicant[491]: wlp2s0: Reject scan trigger since one is already pending
May 16 22:28:37 saarver wpa_supplicant[491]: wlp2s0: Reject scan trigger since one is already pending
May 16 22:33:37 saarver wpa_supplicant[491]: wlp2s0: Reject scan trigger since one is already pending
May 16 22:38:37 saarver wpa_supplicant[491]: wlp2s0: Reject scan trigger since one is already pending
May 16 22:42:34 saarver wpa_supplicant[491]: wlp2s0: WNM: Preferred List Available
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: SME: Trying to authenticate with 3c:7c:3f:66:d2:8c (SSID='Clyde' freq=5260 MHz)
May 16 22:42:35 saarver kernel: wlp2s0: disconnect from AP 3c:7c:3f:66:d2:88 for new auth to 3c:7c:3f:66:d2:8c
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.0558] device (wlp2s0): ip:dhcp4: restarting
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.0559] dhcp4 (wlp2s0): canceled DHCP transaction
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.0559] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.0560] dhcp4 (wlp2s0): state changed no lease
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.0560] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
May 16 22:42:35 saarver kernel: wlp2s0: authenticate with 3c:7c:3f:66:d2:8c (local address=cc:3d:82:c3:37:1e)
May 16 22:42:35 saarver kernel: wlp2s0: send auth to 3c:7c:3f:66:d2:8c (try 1/3)
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.0805] device (wlp2s0): supplicant interface state: completed -> authenticating
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.0806] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> authenticating
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: Trying to associate with 3c:7c:3f:66:d2:8c (SSID='Clyde' freq=5260 MHz)
May 16 22:42:35 saarver kernel: wlp2s0: authenticated
May 16 22:42:35 saarver kernel: wlp2s0: associate with 3c:7c:3f:66:d2:8c (try 1/3)
May 16 22:42:35 saarver kernel: wlp2s0: RX ReassocResp from 3c:7c:3f:66:d2:8c (capab=0x1011 status=0 aid=22)
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: Associated with 3c:7c:3f:66:d2:8c
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
May 16 22:42:35 saarver kernel: wlp2s0: associated
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1022] device (wlp2s0): supplicant interface state: authenticating -> associating
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1023] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1024] device (wlp2s0): supplicant interface state: associating -> associated
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1024] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> associated
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: WPA: Key negotiation completed with 3c:7c:3f:66:d2:8c [PTK=CCMP GTK=CCMP]
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 3c:7c:3f:66:d2:8c completed [id=0 id_str=]
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1136] device (wlp2s0): supplicant interface state: associated -> completed
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1138] device (wlp2s0): ip:dhcp4: restarting
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1210] dhcp4 (wlp2s0): canceled DHCP transaction
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1211] dhcp4 (wlp2s0): state changed no lease
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1211] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1212] device (p2p-dev-wlp2s0): supplicant management interface state: associated -> completed
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1258] dhcp4 (wlp2s0): state changed new lease, address=192.168.50.61, acd pending
May 16 22:42:35 saarver NetworkManager[460]: <info>  [1778960555.1260] dhcp4 (wlp2s0): state changed new lease, address=192.168.50.61
May 16 22:42:35 saarver systemd[1]: Starting Network Manager Script Dispatcher Service...
May 16 22:42:35 saarver systemd[1]: Started Network Manager Script Dispatcher Service.
May 16 22:42:45 saarver systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
May 16 22:46:44 saarver kernel: ------------[ cut here ]------------
May 16 22:46:44 saarver kernel: Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff)
May 16 22:46:44 saarver kernel: WARNING: drivers/net/wireless/intel/iwlwifi/pcie/gen1_2/trans.c:2387 at _iwl_trans_pcie_grab_nic_access+0x16b/0x1e0 [iwlwifi], CPU#2: swapper/2/0
May 16 22:46:44 saarver kernel: Modules linked in: nf_conntrack_netlink xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE bridge stp llc xfrm_user xfrm_algo xt_set ip_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat x_tables nf_tables wireguard libcurve25519 ip6_udp_tunnel udp_tunnel ccm overlay vfat fat intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp snd_ctl_led iwlmvm kvm_intel mac80211 snd_hda_codec_alc269 kvm snd_hda_codec_realtek_lib snd_hda_scodec_component snd_hda_codec_intelhdmi snd_hda_codec_generic libarc4 snd_hda_codec_hdmi irqbypass snd_hda_intel ghash_clmulni_intel iwlwifi btusb platform_profile aesni_intel snd_hda_codec btmtk snd_hda_core rapl btrtl at24 btbcm dell_wmi mei_wdt mei_pxp mei_hdcp snd_intel_dspcfg i2c_i801 btintel intel_cstate snd_intel_sdw_acpi dell_smbios i2c_smbus cfg80211 snd_hwdep dcdbas bluetooth sparse_keymap e1000e intel_uncore wmi_bmof pcspkr i2c_mux mei_me intel_oc_wdt dell_wmi_descriptor snd_pcm spi_nor iTCO_wdt mei snd_timer
May 16 22:46:44 saarver kernel:  rfkill mtd ptp intel_pmc_bxt snd pps_core soundcore mac_hid squashfs loop nfnetlink dm_mod ses enclosure scsi_transport_sas ata_generic pata_acpi uas usb_storage i915 spi_intel_platform spi_intel i2c_algo_bit drm_buddy ttm intel_gtt drm_display_helper video ata_piix cec wmi lpc_ich
May 16 22:46:44 saarver kernel: CPU: 2 UID: 0 PID: 0 Comm: swapper/2 Not tainted 7.0.3-arch1-2 #1 PREEMPT(full)  88a2c8f55a128ad9505b4014386291e7c04d5e88
May 16 22:46:44 saarver kernel: Hardware name: Dell Inc. OptiPlex 9020M/0Y5DDC, BIOS A19 05/30/2019
May 16 22:46:44 saarver kernel: RIP: 0010:_iwl_trans_pcie_grab_nic_access+0x171/0x1e0 [iwlwifi]
May 16 22:46:44 saarver kernel: Code: 15 3c 83 d9 48 8b 5c 24 08 4c 8b 64 24 18 4c 8b 74 24 28 4c 8b 7c 24 30 e9 b8 fe ff ff 48 8d 3d c5 fb 56 00 89 c6 89 44 24 04 <67> 48 0f b9 3a 48 8b b3 88 1a 00 00 48 89 df e8 fb 05 ff ff 83 7c
May 16 22:46:44 saarver kernel: RSP: 0018:ffffd4d280160dc8 EFLAGS: 00010246
May 16 22:46:44 saarver kernel: RAX: 00000000ffffffff RBX: ffff8d78872b8028 RCX: 00000000ffffffff
May 16 22:46:44 saarver kernel: RDX: 0000000000004e34 RSI: 00000000ffffffff RDI: ffffffffc12876d0
May 16 22:46:44 saarver kernel: RBP: 0000000000000000 R08: 0000000000004df3 R09: 0000000000000002
May 16 22:46:44 saarver kernel: R10: 00000000000000a9 R11: 0000000000000000 R12: 0000000000000011
May 16 22:46:44 saarver kernel: R13: ffffffffc0d0e730 R14: 0000000000000008 R15: 0000000000000001
May 16 22:46:44 saarver kernel: FS:  0000000000000000(0000) GS:ffff8d79fa667000(0000) knlGS:0000000000000000
May 16 22:46:44 saarver kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 16 22:46:44 saarver kernel: CR2: 00007f7543d4be64 CR3: 000000020fc24004 CR4: 00000000001726f0
May 16 22:46:44 saarver kernel: Call Trace:
May 16 22:46:44 saarver kernel:  <IRQ>
May 16 22:46:44 saarver kernel:  iwl_trans_pcie_grab_nic_access+0x1f/0x50 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  ? enqueue_task_fair+0x596/0xbe0
May 16 22:46:44 saarver kernel:  iwl_read_prph+0x1b/0x60 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  ? psi_task_change+0xf5/0x100
May 16 22:46:44 saarver kernel:  iwl_txq_log_scd_error+0x148/0x230 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  ? __pfx_iwl_txq_stuck_timer+0x10/0x10 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  iwl_txq_stuck_timer+0x3c/0x60 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  ? __pfx_iwl_txq_stuck_timer+0x10/0x10 [iwlwifi 1fd91fa5056268c1c20053c996c5de21dc3baac7]
May 16 22:46:44 saarver kernel:  call_timer_fn+0x2a/0x140
May 16 22:46:44 saarver kernel:  __run_timers+0x269/0x330
May 16 22:46:44 saarver kernel:  run_timer_softirq+0x86/0xf0
May 16 22:46:44 saarver kernel:  ? irqtime_account_irq+0x30/0xc0
May 16 22:46:44 saarver kernel:  handle_softirqs+0xe8/0x2c0
May 16 22:46:44 saarver kernel:  __irq_exit_rcu+0xc9/0xf0
May 16 22:46:44 saarver kernel:  sysvec_apic_timer_interrupt+0x71/0x90
May 16 22:46:44 saarver kernel:  </IRQ>
May 16 22:46:44 saarver kernel:  <TASK>
May 16 22:46:44 saarver kernel:  asm_sysvec_apic_timer_interrupt+0x1a/0x20
May 16 22:46:44 saarver kernel: RIP: 0010:cpuidle_enter_state+0xbb/0x440
May 16 22:46:44 saarver kernel: Code: 00 00 e8 98 fc ec fe e8 93 ee ff ff 48 89 c5 0f 1f 44 00 00 31 ff e8 d4 50 eb fe 45 84 ff 0f 85 74 01 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 cb 01 00 00 44 89 f1 48 2b 2c 24 48 6b d1 68 48 89
May 16 22:46:44 saarver kernel: RSP: 0018:ffffd4d2800e7e70 EFLAGS: 00000246
May 16 22:46:44 saarver kernel: RAX: ffff8d79fa667000 RBX: 0000000000000005 RCX: 0000000000000000
May 16 22:46:44 saarver kernel: RDX: 00009ff2f41865a6 RSI: fffffffbfca06ce7 RDI: 0000000000000000
May 16 22:46:44 saarver kernel: RBP: 00009ff2f41865a6 R08: 0000000000000005 R09: ffff8d7996b21820
May 16 22:46:44 saarver kernel: R10: ffff8d7996b217c0 R11: 0000000000000004 R12: ffff8d7996b3adc0
May 16 22:46:44 saarver kernel: R13: ffffffff9ba0cb20 R14: 0000000000000005 R15: 0000000000000000
May 16 22:46:44 saarver kernel:  cpuidle_enter+0x31/0x50
May 16 22:46:44 saarver kernel:  do_idle+0x14b/0x2a0
May 16 22:46:44 saarver kernel:  cpu_startup_entry+0x29/0x30
May 16 22:46:44 saarver kernel:  start_secondary+0x119/0x150
May 16 22:46:44 saarver kernel:  common_startup_64+0x13e/0x141
May 16 22:46:44 saarver kernel:  </TASK>
May 16 22:46:44 saarver kernel: ---[ end trace 0000000000000000 ]---
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: iwlwifi transaction failed, dumping registers
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: iwlwifi device config registers:
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000000: 08b18086 00100000 028000bb 00000000 00000004 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000020: 00000000 00000000 00000000 c4708086 00000000 000000c8 00000000 00000100
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000040: 00020010 10008ec0 001b0c10 0006ec11 10110000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000060: 00000000 00080812 00000005 00000000 00010001 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000080: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 000000a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 000000c0: 00000000 00000000 c823d001 0d000000 00804005 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 000000e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000100: 14010001 00100000 00000000 00462031 000031c1 00002000 00000014 40000001
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000120: 0000000f f7c00460 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000140: 14c10003 ffc3371e cc3d82ff 15410018 00000000 0001000b 0141cafe 00f01e1f
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: iwlwifi device memory mapped registers:
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000000: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000020: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: iwlwifi device AER capability structure:
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000000: 14010001 00100000 00000000 00462031 000031c1 00002000 00000014 40000001
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: 00000020: 0000000f f7c00460 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: iwlwifi parent port (0000:00:1c.3) config registers:
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000000: 8c168086 00100507 060400d4 00810010 00000000 00000000 00020200 200000f0
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000020: f7c0f7c0 0001fff1 00000000 00000000 00000000 00000040 00000000 0012040a
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000040: 01428010 00008000 00110000 04323c12 30110c42 001cb200 01480000 00000008
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000060: 00000000 00000817 00000000 00000000 00010002 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000080: 00019005 fee00258 00000000 00000000 0000a00d 06691028 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000000a0: c8030001 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000000c0: 00000000 00000000 00000000 00000000 01000000 00001842 0b118008 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000000e0: 00000300 88aa88aa 00000001 00000000 00000050 0c000040 08060fb1 04002800
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000100: 00000000 00000000 00000000 00060011 000011c1 00002000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000120: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000140: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000160: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000180: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000001a0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000001c0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 000001e0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:00:1c.3: 00000200: 00000000 00000000 00000000
May 16 22:46:44 saarver kernel: iwlwifi 0000:02:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [83, 104] HW [90, 90] FH TRB=0x05a5a5a5a
May 16 22:46:49 saarver dockerd[537]: time="2026-05-16T22:46:49.213410890+03:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:192.168.50.61:47043" dns-server="udp:94.140.15.15:53" error="read udp 192.168.50.61:47043->94.140.15.15:53: i/o timeout" question=";grafana.com.\tIN\t A"
May 16 22:46:49 saarver dockerd[537]: time="2026-05-16T22:46:49.213465952+03:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:192.168.50.61:44773" dns-server="udp:94.140.15.15:53" error="read udp 192.168.50.61:44773->94.140.15.15:53: i/o timeout" question=";grafana.com.\tIN\t AAAA"
May 16 22:46:53 saarver dockerd[537]: time="2026-05-16T22:46:53.214824648+03:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:192.168.50.61:41816" dns-server="udp:192.168.50.1:53" error="read udp 192.168.50.61:41816->192.168.50.1:53: i/o timeout" question=";grafana.com.\tIN\t A"
May 16 22:46:53 saarver dockerd[537]: time="2026-05-16T22:46:53.214939448+03:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:192.168.50.61:41761" dns-server="udp:192.168.50.1:53" error="read udp 192.168.50.61:41761->192.168.50.1:53: i/o timeout" question=";grafana.com.\tIN\t AAAA"
May 16 22:46:54 saarver dockerd[537]: time="2026-05-16T22:46:54.214557709+03:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:192.168.50.61:60720" dns-server="udp:94.140.15.15:53" error="read udp 192.168.50.61:60720->94.140.15.15:53: i/o timeout" question=";grafana.com.\tIN\t AAAA"
May 16 22:46:54 saarver dockerd[537]: time="2026-05-16T22:46:54.214616068+03:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:192.168.50.61:37988" dns-server="udp:94.140.15.15:53" error="read udp 192.168.50.61:37988->94.140.15.15:53: i/o timeout" question=";grafana.com.\tIN\t A"
May 16 22:46:58 saarver dockerd[537]: time="2026-05-16T22:46:58.215307500+03:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:192.168.50.61:52678" dns-server="udp:192.168.50.1:53" error="read udp 192.168.50.61:52678->192.168.50.1:53: i/o timeout" question=";grafana.com.\tIN\t A"
May 16 22:46:58 saarver dockerd[537]: time="2026-05-16T22:46:58.215384678+03:00" level=error msg="[resolver] failed to query external DNS server" client-addr="udp:192.168.50.61:56630" dns-server="udp:192.168.50.1:53" error="read udp 192.168.50.61:56630->192.168.50.1:53: i/o timeout" question=";grafana.com.\tIN\t AAAA"
May 16 22:47:00 saarver kernel: iwlwifi 0000:02:00.0: Queue 11 is active on fifo 2 and stuck for 10000 ms. SW [2, 4] HW [90, 90] FH TRB=0x05a5a5a5a
May 16 22:47:01 saarver kernel: iwlwifi 0000:02:00.0: Error sending SCAN_OFFLOAD_ABORT_CMD: enqueue_hcmd failed: -5
May 16 22:47:07 saarver kernel: iwlwifi 0000:02:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5
May 16 22:47:13 saarver kernel: iwlwifi 0000:02:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5
May 16 22:47:19 saarver kernel: iwlwifi 0000:02:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5
May 16 22:47:25 saarver kernel: iwlwifi 0000:02:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5
May 16 22:47:31 saarver kernel: iwlwifi 0000:02:00.0: Error sending STATISTICS_CMD: enqueue_hcmd failed: -5
May 16 22:47:31 saarver kernel: iwlwifi 0000:02:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
May 16 22:47:31 saarver kernel: iwlwifi 0000:02:00.0: Scan failed! ret -5
…

and then follow 3h and 50k lines of scan failure errros

You seem to be quickly roaming between 5.4 and 5 GHz 

May 16 20:38:47 saarver wpa_supplicant[491]: wlp2s0: RSN: Group rekeying completed with 3c:7c:3f:66:d2:8c [GTK=CCMP]
May 16 21:38:47 saarver wpa_supplicant[491]: wlp2s0: RSN: Group rekeying completed with 3c:7c:3f:66:d2:8c [GTK=CCMP]
May 16 21:58:01 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=3c:7c:3f:66:d2:8c reason=4 locally_generated=1
May 16 21:58:01 saarver wpa_supplicant[491]: wlp2s0: Added BSSID 3c:7c:3f:66:d2:8c into ignore list, ignoring for 10 seconds
May 16 21:58:04 saarver wpa_supplicant[491]: wlp2s0: Removed BSSID 3c:7c:3f:66:d2:8c from ignore list (clear)
May 16 21:58:04 saarver wpa_supplicant[491]: wlp2s0: SME: Trying to authenticate with 3c:7c:3f:66:d2:8c (SSID='Clyde' freq=5180 MHz)
May 16 21:58:04 saarver kernel: wlp2s0: authenticate with 3c:7c:3f:66:d2:8c (local address=cc:3d:82:c3:37:1e)
May 16 21:58:04 saarver kernel: wlp2s0: send auth to 3c:7c:3f:66:d2:8c (try 1/3)
May 16 21:58:04 saarver kernel: wlp2s0: send auth to 3c:7c:3f:66:d2:8c (try 2/3)
May 16 21:58:04 saarver kernel: wlp2s0: send auth to 3c:7c:3f:66:d2:8c (try 3/3)
May 16 21:58:04 saarver kernel: wlp2s0: authentication with 3c:7c:3f:66:d2:8c timed out
May 16 21:58:04 saarver wpa_supplicant[491]: wlp2s0: Added BSSID 3c:7c:3f:66:d2:8c into ignore list, ignoring for 10 seconds
May 16 21:58:08 saarver wpa_supplicant[491]: wlp2s0: Removed BSSID 3c:7c:3f:66:d2:8c from ignore list (clear)
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: SME: Trying to authenticate with 3c:7c:3f:66:d2:88 (SSID='Clyde' freq=2457 MHz)
May 16 21:58:37 saarver kernel: wlp2s0: authenticate with 3c:7c:3f:66:d2:88 (local address=cc:3d:82:c3:37:1e)
May 16 21:58:37 saarver kernel: wlp2s0: send auth to 3c:7c:3f:66:d2:88 (try 1/3)
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: Trying to associate with 3c:7c:3f:66:d2:88 (SSID='Clyde' freq=2457 MHz)
May 16 21:58:37 saarver kernel: wlp2s0: associate with 3c:7c:3f:66:d2:88 (try 1/3)
May 16 21:58:37 saarver kernel: wlp2s0: RX AssocResp from 3c:7c:3f:66:d2:88 (capab=0x1411 status=0 aid=19)
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: Associated with 3c:7c:3f:66:d2:88
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: WPA: Key negotiation completed with 3c:7c:3f:66:d2:88 [PTK=CCMP GTK=CCMP]
May 16 21:58:37 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 3c:7c:3f:66:d2:88 completed [id=0 id_str=]
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: SME: Trying to authenticate with 3c:7c:3f:66:d2:8c (SSID='Clyde' freq=5260 MHz)
May 16 22:42:35 saarver kernel: wlp2s0: disconnect from AP 3c:7c:3f:66:d2:88 for new auth to 3c:7c:3f:66:d2:8c
May 16 22:42:35 saarver kernel: wlp2s0: authenticate with 3c:7c:3f:66:d2:8c (local address=cc:3d:82:c3:37:1e)
May 16 22:42:35 saarver kernel: wlp2s0: send auth to 3c:7c:3f:66:d2:8c (try 1/3)
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: Trying to associate with 3c:7c:3f:66:d2:8c (SSID='Clyde' freq=5260 MHz)
May 16 22:42:35 saarver kernel: wlp2s0: associate with 3c:7c:3f:66:d2:8c (try 1/3)
May 16 22:42:35 saarver kernel: wlp2s0: RX ReassocResp from 3c:7c:3f:66:d2:8c (capab=0x1011 status=0 aid=22)
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: Associated with 3c:7c:3f:66:d2:8c
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: WPA: Key negotiation completed with 3c:7c:3f:66:d2:8c [PTK=CCMP GTK=CCMP]
May 16 22:42:35 saarver wpa_supplicant[491]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 3c:7c:3f:66:d2:8c completed [id=0 id_str=]

What if you pin a BSSID?
https://wiki.archlinux.org/title/Networ … ts_(Wi-Fi)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2026-05-25 17:41:44

DinoSaar
Member
Registered: 2026-05-19
Posts: 8

Re: iwlwifi started failing consistently, trying to determine root cause

The issue happened again with the LTS kernel so I think it's safe to rule out a regression in iwlwifi.

seth wrote:

What if you pin a BSSID?

I just pinned it to the 2.4 GHz band since the 5 GHz is a little borderline, we'll see if it helps.

Offline

#14 2026-06-05 08:30:17

DinoSaar
Member
Registered: 2026-05-19
Posts: 8

Re: iwlwifi started failing consistently, trying to determine root cause

seth wrote:

What if you pin a BSSID?

It's been more than 10 days and I haven't run into any issues, so pinning the BSSID probably solved it. Thanks for your help!

I noticed that my phone has been disconnecting and connecting quite a lot, even with strong signal. Maybe something is up with the 5GHz band.

Offline

Pages: 1

Board footer

Powered by FluxBB