Discovered on HardenedBSD 15-CURRENT, and verified on the following FreeBSD 15-CURRENT build from FreeBSD-15.0-CURRENT-amd64-20250116-054c5ddf587a-274800-bootonly.iso Hardware Information: Dell Precision 7510 Laptop [1] CPU: Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz (2800.00-MHz K8-class CPU) [1] Origin="GenuineIntel" Id=0x506e3 Family=0x6 Model=0x5e Stepping=3 [1] Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> [1] Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND> [1] AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM> [1] AMD Features2=0x121<LAHF,ABM,Prefetch> [1] Structured Extended Features=0x29c6fbf<FSGSBASE,TSCADJ,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE> [1] Structured Extended Features3=0xbc002e00<MCUOPT,MD_CLEAR,TSXFA,IBPB,STIBP,L1DFL,ARCH_CAP,SSBD> [1] XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES> [1] IA32_ARCH_CAPS=0xc04<RSBA> [1] VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID [1] TSC: P-state invariant, performance statistics [1] real memory = 34359738368 (32768 MB) [1] avail memory = 33213587456 (31674 MB) [1] Event timer "LAPIC" quality 600 [1] ACPI APIC Table: <DELL CBX3 > [1] FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs [1] FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads [1] FreeBSD/SMP Online: 1 package(s) x 4 core(s) [8] iwlwifi0: <iwlwifi> mem 0xdc300000-0xdc301fff at device 0.0 on pci2 [8] iwlwifi0: Detected crf-id 0xbadcafe, cnv-id 0x3000000 wfpm id 0x80000000 [8] iwlwifi0: PCI dev 24f3/0050, rev=0x201, rfid=0xd55555d5 [8] iwlwifi0: Detected Intel(R) Dual Band Wireless AC 8260 [8] iwlwifi0: successfully loaded firmware image 'iwlwifi-8000C-36.ucode' [8] iwlwifi0: loaded firmware version 36.ca7b901d.0 8000C-36.ucode op_mode iwlmvm [8] iwlwifi0: base HW address: e4:b3:18:32:7f:8f, OTP minor version: 0x0 pciconf -lv hostb0@pci0:0:0:0: class=0x060000 rev=0x07 hdr=0x00 vendor=0x8086 device=0x1918 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 rev=0x07 hdr=0x01 vendor=0x8086 device=0x1901 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = '6th-10th Gen Core Processor PCIe Controller (x16)' class = bridge subclass = PCI-PCI none0@pci0:0:4:0: class=0x118000 rev=0x07 hdr=0x00 vendor=0x8086 device=0x1903 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem' class = dasp xhci0@pci0:0:20:0: class=0x0c0330 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa12f subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller' class = serial bus subclass = USB pchtherm0@pci0:0:20:2: class=0x118000 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa131 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family Thermal Subsystem' class = dasp none1@pci0:0:22:0: class=0x078000 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa13a subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family MEI Controller' class = simple comms ahci0@pci0:0:23:0: class=0x010400 rev=0x31 hdr=0x00 vendor=0x8086 device=0x2822 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = 'SATA Controller [RAID mode]' class = mass storage subclass = RAID pcib2@pci0:0:28:0: class=0x060400 rev=0xf1 hdr=0x01 vendor=0x8086 device=0xa111 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family PCI Express Root Port' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:2: class=0x060400 rev=0xf1 hdr=0x01 vendor=0x8086 device=0xa112 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family PCI Express Root Port' class = bridge subclass = PCI-PCI pcib4@pci0:0:28:4: class=0x060400 rev=0xf1 hdr=0x01 vendor=0x8086 device=0xa114 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family PCI Express Root Port' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa150 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = 'CM236 Chipset LPC/eSPI Controller' class = bridge subclass = PCI-ISA none2@pci0:0:31:2: class=0x058000 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa121 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family Power Management Controller' class = memory hdac1@pci0:0:31:3: class=0x040300 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa170 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family HD Audio Controller' class = multimedia subclass = HDA ichsmb0@pci0:0:31:4: class=0x0c0500 rev=0x31 hdr=0x00 vendor=0x8086 device=0xa123 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = '100 Series/C230 Series Chipset Family SMBus' class = serial bus subclass = SMBus em0@pci0:0:31:6: class=0x020000 rev=0x31 hdr=0x00 vendor=0x8086 device=0x15b7 subvendor=0x1028 subdevice=0x06d9 vendor = 'Intel Corporation' device = 'Ethernet Connection (2) I219-LM' class = network subclass = ethernet vgapci0@pci0:1:0:0: class=0x030000 rev=0xa2 hdr=0x00 vendor=0x10de device=0x13b0 subvendor=0x1028 subdevice=0x16d9 vendor = 'NVIDIA Corporation' device = 'GM107GLM [Quadro M2000M]' class = display subclass = VGA hdac0@pci0:1:0:1: class=0x040300 rev=0xa1 hdr=0x00 vendor=0x10de device=0x0fbc subvendor=0x1028 subdevice=0x16d9 vendor = 'NVIDIA Corporation' device = 'GM107 High Definition Audio Controller [GeForce 940MX]' class = multimedia subclass = HDA iwlwifi0@pci0:2:0:0: class=0x028000 rev=0x3a hdr=0x00 vendor=0x8086 device=0x24f3 subvendor=0x8086 subdevice=0x0050 vendor = 'Intel Corporation' device = 'Wireless 8260' class = network rtsx0@pci0:3:0:0: class=0xff0000 rev=0x01 hdr=0x00 vendor=0x10ec device=0x525a subvendor=0x1028 subdevice=0x06d9 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTS526A PCI Express Card Reader' Setup of network from rc.conf (note that iwm is blocked from loading) devmatch_blocklist="if_iwm" wlans_iwlwifi0="wlan0" ifconfig_wlan0="WPA SYNCDHCP" (also if I set a static IP address). wpa_supplicant with scan_ssid=1, network set to SSID and a fun passphrase (I have also tested with base wpa_supplicant and the port) Reproducing the issue: This is a laptop, and typically after starting the laptop, starting X11, I lock the laptop and close the lid typically accessing from another laptop (server laptop, its got Xeons in it). For a long time before iwlwifi, even with the iwm kernel module, the "wlan0" interface would just drop, pointing to another issue of a loss of a network connection. This would cause me to have to do "service netif restart" to bring the "wlan0" interface back online. Now with the push to using iwlwifi, I switched over and have found that when iwlwifi runs into an issue, stopping "netif" or running "ifconfig wlan0 down" will lead to the same panic as show below. As this was HardenedBSD, I fired up a live image of FreeBSD-15-CURRENT from 2025Jan16 and ran through the same wireless setup to block if_iwm, load wlan0 with the iwlwifi driver and found that eventually the same panic condition occurs NOTE FOR REPRODUCTION: I typically leave the laptop setup like this overnight so it may take a while to reproduce the panic. Log data from panic Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] wlan0: link state changed to DOWN Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Microcode SW error detected. Restarting 0x2000000. Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Start IWL Error Log Dump: Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Transport status: 0x0000004B, valid: 6 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Loaded firmware version: 36.ca7b901d.0 8000C-36.ucode Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x000021A0 | ADVANCED_SYSASSERT Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x000002A0 | trm_hw_status0 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | trm_hw_status1 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x0002438C | branchlink2 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00039C22 | interruptlink1 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | interruptlink2 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000030 | data1 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | data2 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | data3 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x1E007F14 | beacon time Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x75697806 | tsf low Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x000001A7 | tsf hi Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | time gp1 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x81841222 | time gp2 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000001 | uCode revision type Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000024 | uCode version major Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xCA7B901D | uCode version minor Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000201 | hw version Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x18489001 | board version Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x001C0118 | hcmd Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00022080 | isr0 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | isr1 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x08201802 | isr2 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x004150C0 | isr3 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | isr4 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x001B019F | last cmd Id Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | wait_event Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x000000C0 | l2p_control Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00018000 | l2p_duration Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x0000003F | l2p_mhvalid Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | l2p_addr_match Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x0000000D | lmpm_pmg_sel Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x10032207 | timestamp Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00005868 | flow_handler Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Start IWL Error Log Dump: Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Transport status: 0x0000004B, valid: 7 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000070 | NMI_INTERRUPT_LMAC_FATAL Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | umac branchlink1 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xC0086B3C | umac branchlink2 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xC0083D08 | umac interruptlink1 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xC0083D08 | umac interruptlink2 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000800 | umac data1 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xC0083D08 | umac data2 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xDEADBEEF | umac data3 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000024 | umac major Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xCA7B901D | umac minor Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xC088628C | frame pointer Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xC088628C | stack pointer Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x001C0118 | last host cmd Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000000 | isr status reg Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: IML/ROM dump: Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x0000388D | IML/ROM error/state Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x00000003 | IML/ROM data1 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Fseq Registers: Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xB53B3237 | FSEQ_ERROR_CODE Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xE1F88FF3 | FSEQ_TOP_INIT_VERSION Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x1178C508 | FSEQ_CNVIO_INIT_VERSION Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x0000A056 | FSEQ_OTP_VERSION Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xE7C9BF72 | FSEQ_TOP_CONTENT_VERSION Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x5FDFD166 | FSEQ_ALIVE_TOKEN Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xBA753032 | FSEQ_CNVI_ID Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x0F29E1C6 | FSEQ_CNVR_ID Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x03000000 | CNVI_AUX_MISC_CHIP Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x0BADCAFE | CNVR_AUX_MISC_CHIP Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x0DE0E006 | FSEQ_PREV_CNVIO_INIT_VERSION Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x3E7DA3F7 | FSEQ_WIFI_FSEQ_VERSION Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0x4BCF3FE2 | FSEQ_BT_FSEQ_VERSION Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: 0xAFBEB866 | FSEQ_CLASS_TP_VERSION Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Collecting data: trigger 2 fired. Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: FW error in SYNC CMD ADD_STA Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #0 0xffffffff80e3d4d6 at linux_dump_stack+0x26 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #1 0xffffffff842d483b at iwl_trans_pcie_send_hcmd+0x45b Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #2 0xffffffff842632c8 at iwl_trans_send_cmd+0x88 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #3 0xffffffff842b01a3 at iwl_mvm_send_cmd_status+0x53 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #4 0xffffffff842b02ba at iwl_mvm_send_cmd_pdu_status+0x5a Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #5 0xffffffff8429bf6a at iwl_mvm_sta_send_to_fw+0x37a Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #6 0xffffffff8429eb56 at iwl_mvm_add_sta+0x186 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #7 0xffffffff8427ec08 at iwl_mvm_mac_sta_state_common+0x658 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #8 0xffffffff80e37547 at lkpi_80211_mo_sta_state+0xa7 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #9 0xffffffff80e2c8da at lkpi_sta_scan_to_auth+0x55a Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #10 0xffffffff80e2ce5b at lkpi_sta_run_to_auth+0x1b Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #11 0xffffffff80e36800 at lkpi_iv_newstate+0x2d0 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #12 0xffffffff80d4c1ed at ieee80211_newstate_cb+0x2ad Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #13 0xffffffff80bf72d7 at taskqueue_run_locked+0x1c7 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #14 0xffffffff80bf8233 at taskqueue_thread_loop+0xd3 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #15 0xffffffff80b3ede7 at fork_exit+0x87 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] #16 0xffffffff810bfdae at fork_trampoline+0xe Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: lkpi_sta_scan_to_auth:1346: mo_sta_state(NONE) failed: -5 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: lkpi_iv_newstate: error -1 during state transition 5 (RUN) -> 2 (AUTH) Jan 21 14:08:18 15-CURRENT-HOST i3lock[39544]: in _pam_exec(): pam_sm_setcred: pam_get_authtok(): authentication token not available Jan 21 14:10:08 15-CURRENT-HOST syslogd: kernel boot file is /boot/kernel/kernel Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] iwlwifi0: lkpi_sta_auth_to_scan:1462: lvif 0xfffffe0143dfb000 vap 0xfffffe0143dfb010 iv_bss 0xfffffe0143e05000 lvif_bss 0 lvif_bss->ni 0 synched 0 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] panic: lkpi_sta_auth_to_scan: lsta 0 ni 0 lvif 0xfffffe0143dfb000 vap 0xfffffe0143dfb010 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] cpuid = 2 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] time = 1737486510 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] __HardenedBSD_version = 1500001 __FreeBSD_version = 1500029 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] version = FreeBSD 15.0-CURRENT-HBSD #0 : Wed Jan 1 10:44:22 UTC 2025 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] root@hbsd-os-build-01:/usr/obj/usr/src/amd64.amd64/sys/HARDENEDBSD Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] KDB: stack backtrace: Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] db_trace_self_wrapper() at db_trace_self_wrapper+0x36/frame 0xfffffe010671eb50 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] vpanic() at vpanic+0x13b/frame 0xfffffe010671ec80 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] panic() at panic+0x43/frame 0xfffffe010671ece0 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] lkpi_sta_auth_to_scan() at lkpi_sta_auth_to_scan+0x47c/frame 0xfffffe010671ed70 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] lkpi_iv_newstate() at lkpi_iv_newstate+0x2d0/frame 0xfffffe010671ede0 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] ieee80211_newstate_cb() at ieee80211_newstate_cb+0x2ad/frame 0xfffffe010671ee30 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] taskqueue_run_locked() at taskqueue_run_locked+0x1c7/frame 0xfffffe010671eec0 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] taskqueue_thread_loop() at taskqueue_thread_loop+0xd3/frame 0xfffffe010671eef0 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] fork_exit() at fork_exit+0x87/frame 0xfffffe010671ef30 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe010671ef30 Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] --- trap 0xc, rip = 0x9534f5f6ba, rsp = 0x7cd9b152aa78, rbp = 0x7cd9b152aa90 --- Jan 21 14:10:08 15-CURRENT-HOST kernel: [19378] KDB: enter: panic
Sorry to ask about this despite the description. So you left the laptop over night and then you typed in ifconfig wlan0 down and that immediately led to what's below in the log? I am asking to get the order of events clear (from that log): - interface goes down (link state event) - firmware crashes during ADD_STA (that means scan -> auth) - the backtrace and follwoing log says you were in RUN again and on the way from RUN to AUTH, which means the interface in between was UP again but I do not see that message in the log. Now it will not come up by itself if this was a manual ifconfig down or netif stop. So something else happened that very second or the crash was not produced by manual intervention. Did you by any chance run a netif wlan0 restart (not stop) or something else happened in parallel? Do you have wpa logs for that time (ideally let it log to console as well so we have a chance to see -- and remove sensitive information).
(In reply to Bjoern A. Zeeb from comment #1) >>>>>So you left the laptop over night and then you typed in ifconfig wlan0 down and that immediately led to what's below in the log? After a period of time, I come back and wlan0 has lost carrier with the wireless network, I will see "no carrier" under "status" when I do "ifconfig wlan0". When I do a netif restart or "ifconfig wlan0 down" or anything with the interface that is when the kernel will panic. >>>>Now it will not come up by itself if this was a manual ifconfig down or netif stop. So something else happened that very second or the crash was not produced by manual intervention. When I see the wlan0 interface is no longer connected to the network, everything else related to the OS or kernel are fine. >>>>>Did you by any chance run a netif wlan0 restart (not stop) or something else happened in parallel? Do you have wpa logs for that time (ideally let it log to console as well so we have a chance to see -- and remove sensitive information). I typically would do "service netif restart" and not specifically for wlan0. I will get wpa_supplicant setup so I will have more detailed logs. The only thing I see before I try to "service netif restart" is the following in /var/log/messages: Jan 21 08:45:58 15-CURRENT-HOST kernel: ---<<BOOT>>--- BEFORE THIS ENTRY system booted up, these are the first logs seen regarding wireless Jan 21 09:25:05 15-CURRENT-HOST kernel: [2373] iwlwifi0: linuxkpi_ieee80211_beacon_loss: vif 0xfffffe0143dfbe80 vap 0xfffffe0143dfb010 state RUN Jan 21 09:25:05 15-CURRENT-HOST syslogd: last message repeated 1 times Jan 21 09:25:05 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: CTRL-EVENT-DISCONNECTED bssid=BSSID-MAC reason=0 Jan 21 09:25:05 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: Added BSSID BSSID-MAC into ignore list, ignoring for 10 seconds Jan 21 09:25:05 15-CURRENT-HOST kernel: [2373] wlan0: link state changed to DOWN Jan 21 09:25:06 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: Trying to associate with BSSID-MAC-2 (SSID='AWESOME-SSID-NAME' freq=2417 MHz) Jan 21 09:25:06 15-CURRENT-HOST wpa_supplicant[75193]: FT: Invalid key management type (2) Jan 21 09:25:06 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: Associated with BSSID-MAC-2 Jan 21 09:25:06 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: WPA: Key negotiation completed with BSSID-MAC-2 [PTK=CCMP GTK=CCMP] Jan 21 09:25:06 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: CTRL-EVENT-CONNECTED - Connection to BSSID-MAC-2 completed [id=2 id_str=] Jan 21 09:25:06 15-CURRENT-HOST kernel: [2374] wlan0: link state changed to UP Jan 21 09:25:06 15-CURRENT-HOST dhclient[15178]: New IP Address (wlan0): 192.168.1.112 Jan 21 09:25:06 15-CURRENT-HOST dhclient[16695]: New Subnet Mask (wlan0): 255.255.255.0 Jan 21 09:25:06 15-CURRENT-HOST dhclient[17849]: New Broadcast Address (wlan0): 192.168.1.255 Jan 21 09:25:06 15-CURRENT-HOST dhclient[18673]: New Routers (wlan0): 192.168.1.1 Jan 21 12:50:56 15-CURRENT-HOST kernel: [14724] iwlwifi0: linuxkpi_ieee80211_beacon_loss: vif 0xfffffe0143dfbe80 vap 0xfffffe0143dfb010 state RUN Jan 21 12:51:01 15-CURRENT-HOST kernel: [14729] iwlwifi0: linuxkpi_ieee80211_beacon_loss: vif 0xfffffe0143dfbe80 vap 0xfffffe0143dfb010 state RUN Jan 21 12:51:01 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: CTRL-EVENT-DISCONNECTED bssid=BSSID-MAC-2 reason=0 Jan 21 12:51:01 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: Removed BSSID BSSID-MAC from ignore list (expired) Jan 21 12:51:01 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: Added BSSID BSSID-MAC-2 into ignore list, ignoring for 10 seconds Jan 21 12:51:01 15-CURRENT-HOST wpa_supplicant[75193]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign requested address Jan 21 12:51:01 15-CURRENT-HOST kernel: [14729] iwlwifi0: linuxkpi_ieee80211_connection_loss: vif 0xfffffe0143dfbe80 vap 0xfffffe0143dfb010 state RUN Jan 21 12:51:01 15-CURRENT-HOST kernel: [14729] wlan0: link state changed to DOWN Jan 21 12:51:01 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: Removed BSSID BSSID-MAC-2 from ignore list (clear) Jan 21 12:51:12 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: Trying to associate with BSSID-MAC-3 (SSID='AWESOME-SSID-NAME' freq=2417 MHz) Jan 21 12:51:12 15-CURRENT-HOST wpa_supplicant[75193]: FT: Invalid key management type (2) Jan 21 12:51:12 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: Associated with BSSID-MAC-3 Jan 21 12:51:12 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: WPA: Key negotiation completed with BSSID-MAC-3 [PTK=CCMP GTK=CCMP] Jan 21 12:51:12 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: CTRL-EVENT-CONNECTED - Connection to BSSID-MAC-3 completed [id=2 id_str=] Jan 21 12:51:12 15-CURRENT-HOST kernel: [14740] wlan0: link state changed to UP This IP is picked up from DHCPD running on a bridge interface I use for running bhyve VMs, the wireless connection is gone and wlan0 picks this up from localhost: Jan 21 12:51:13 15-CURRENT-HOST dhclient[40302]: New IP Address (wlan0): 172.16.66.142 Jan 21 12:51:13 15-CURRENT-HOST dhclient[42209]: New Subnet Mask (wlan0): 255.255.255.0 Jan 21 12:51:13 15-CURRENT-HOST dhclient[43952]: New Broadcast Address (wlan0): 172.16.66.255 Jan 21 12:51:13 15-CURRENT-HOST dhclient[46038]: New Routers (wlan0): 172.16.66.6 When I see the wireless is not working, I do "service netif restart" and these are the logs that follow. (matching what I already posted) Jan 21 12:56:39 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: CTRL-EVENT-DISCONNECTED bssid=BSSID-MAC-3 reason=0 Jan 21 12:56:39 15-CURRENT-HOST wpa_supplicant[75193]: wlan0: Added BSSID BSSID-MAC-3 into ignore list, ignoring for 10 seconds Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] wlan0: link state changed to DOWN Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Microcode SW error detected. Restarting 0x2000000. Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Start IWL Error Log Dump: Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Transport status: 0x0000004B, valid: 6 Jan 21 12:56:39 15-CURRENT-HOST kernel: [15067] iwlwifi0: Loaded firmware version: 36.ca7b901d.0 8000C-36.ucode ... same logs from before
(In reply to Shirkdog from comment #2) > After a period of time, I come back and wlan0 has lost carrier with the wireless network, ... Right, and why is that? What happened before? I see beacon misses in the log below. Crowded spectrum? Low signal? ..? If instead of doing a netif restart wlan0, can you simply try: ifconfig wlan0 down ifconfig wlan0 up ifconfig wlan0 scan and see if that helps to get you associated again without the panic when this happens?
Okay, took me 20 hours on this one: iwlwifi1@pci0:9:0:0: class=0x028000 rev=0x78 hdr=0x00 vendor=0x8086 device=0x24fd subvendor=0x8086 subdevice=0x1010 vendor = 'Intel Corporation' device = 'Wireless 8265 / 8275' class = network Came out of the blue without any other logging and the AX200 and AX210 survived that timeframe in case it would have been the AP. iwlwifi1: Microcode SW error detected. Restarting 0x2000000. iwlwifi1: Start IWL Error Log Dump: iwlwifi1: Transport status: 0x0000004B, valid: 6 iwlwifi1: Loaded firmware version: 36.ca7b901d.0 8265-36.ucode iwlwifi1: 0x000021A0 | ADVANCED_SYSASSERT iwlwifi1: 0x000002A0 | trm_hw_status0 iwlwifi1: 0x00000000 | trm_hw_status1 iwlwifi1: 0x00024A8C | branchlink2 iwlwifi1: 0x0003AC1E | interruptlink1 iwlwifi1: 0x00000000 | interruptlink2 iwlwifi1: 0x00000030 | data1 iwlwifi1: 0x00000000 | data2 iwlwifi1: 0x00000000 | data3 iwlwifi1: 0x94017589 | beacon time iwlwifi1: 0xA1210241 | tsf low iwlwifi1: 0x00000050 | tsf hi iwlwifi1: 0x00000000 | time gp1 iwlwifi1: 0x842B8E55 | time gp2 iwlwifi1: 0x00000001 | uCode revision type iwlwifi1: 0x00000024 | uCode version major iwlwifi1: 0xCA7B901D | uCode version minor iwlwifi1: 0x00000230 | hw version iwlwifi1: 0x00C89000 | board version iwlwifi1: 0x006B0118 | hcmd iwlwifi1: 0x00022080 | isr0 iwlwifi1: 0x00000000 | isr1 iwlwifi1: 0x08201802 | isr2 iwlwifi1: 0x004154C0 | isr3 iwlwifi1: 0x00000000 | isr4 iwlwifi1: 0x006A019F | last cmd Id iwlwifi1: 0x00000000 | wait_event iwlwifi1: 0x00000080 | l2p_control iwlwifi1: 0x00018000 | l2p_duration iwlwifi1: 0x0000003F | l2p_mhvalid iwlwifi1: 0x00000000 | l2p_addr_match iwlwifi1: 0x0000000D | lmpm_pmg_sel iwlwifi1: 0x10032209 | timestamp iwlwifi1: 0x000098A8 | flow_handler iwlwifi1: Start IWL Error Log Dump: iwlwifi1: Transport status: 0x0000004B, valid: 7 iwlwifi1: 0x00000070 | NMI_INTERRUPT_LMAC_FATAL iwlwifi1: 0x00000000 | umac branchlink1 iwlwifi1: 0xC008694C | umac branchlink2 iwlwifi1: 0xC0083B0C | umac interruptlink1 iwlwifi1: 0xC0083B0C | umac interruptlink2 iwlwifi1: 0x00000800 | umac data1 iwlwifi1: 0xC0083B0C | umac data2 iwlwifi1: 0xDEADBEEF | umac data3 iwlwifi1: 0x00000024 | umac major iwlwifi1: 0xCA7B901D | umac minor iwlwifi1: 0xC088628C | frame pointer iwlwifi1: 0xC088628C | stack pointer iwlwifi1: 0x006B0118 | last host cmd iwlwifi1: 0x00000000 | isr status reg iwlwifi1: IML/ROM dump: iwlwifi1: 0x000028A7 | IML/ROM error/state iwlwifi1: 0x00000003 | IML/ROM data1 iwlwifi1: Fseq Registers: iwlwifi1: 0xA885AEA6 | FSEQ_ERROR_CODE iwlwifi1: 0x5829A428 | FSEQ_TOP_INIT_VERSION iwlwifi1: 0x0108038E | FSEQ_CNVIO_INIT_VERSION iwlwifi1: 0x0000A10B | FSEQ_OTP_VERSION iwlwifi1: 0xCE341526 | FSEQ_TOP_CONTENT_VERSION iwlwifi1: 0xCE965EDB | FSEQ_ALIVE_TOKEN iwlwifi1: 0x40073100 | FSEQ_CNVI_ID iwlwifi1: 0x97D7D33E | FSEQ_CNVR_ID iwlwifi1: 0x00000010 | CNVI_AUX_MISC_CHIP iwlwifi1: 0x0BADCAFE | CNVR_AUX_MISC_CHIP iwlwifi1: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM iwlwifi1: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR iwlwifi1: 0x4F280E54 | FSEQ_PREV_CNVIO_INIT_VERSION iwlwifi1: 0xE819D9F4 | FSEQ_WIFI_FSEQ_VERSION iwlwifi1: 0x9D838E6A | FSEQ_BT_FSEQ_VERSION iwlwifi1: 0x4735F754 | FSEQ_CLASS_TP_VERSION iwlwifi1: Collecting data: trigger 2 fired. linuxkpi_ieee80211_restart_hw:3530: XXX LKPI80211 TODO iwlwifi1: FW error in SYNC CMD ADD_STA #0 0xffffffff80dfbc0b at linux_dump_stack+0x1b #1 0xffffffff82a9bd1b at iwl_trans_pcie_send_hcmd+0x43b #2 0xffffffff82a2b1f8 at iwl_trans_send_cmd+0x88 #3 0xffffffff82a768dd at iwl_mvm_send_cmd_status+0x4d #4 0xffffffff82a769ef at iwl_mvm_send_cmd_pdu_status+0x4f #5 0xffffffff82a6340e at iwl_mvm_sta_send_to_fw+0x35e #6 0xffffffff82a65e2e at iwl_mvm_add_sta+0x16e #7 0xffffffff82a45d97 at iwl_mvm_mac_sta_state_common+0x667 #8 0xffffffff80df5e38 at lkpi_80211_mo_sta_state+0xa8 #9 0xffffffff80de7ec5 at lkpi_sta_scan_to_auth+0x6d5 #10 0xffffffff80de844b at lkpi_sta_run_to_auth+0x1b #11 0xffffffff80df402b at lkpi_iv_newstate+0x2cb #12 0xffffffff80d0dc8c at ieee80211_newstate_cb+0x29c #13 0xffffffff80bc0332 at taskqueue_run_locked+0x1c2 #14 0xffffffff80bc11f3 at taskqueue_thread_loop+0xd3 #15 0xffffffff80b0ac02 at fork_exit+0x82 #16 0xffffffff810645fe at fork_trampoline+0xe iwlwifi1: lkpi_sta_scan_to_auth:1835: mo_sta_state(NONE) failed: -5 iwlwifi1: lkpi_iv_newstate: error -1 during state transition 5 (RUN) -> 2 (AUTH) But I didn't manage a follow-up panic. You mentioned that you had that problem with iwm(4) already? Did it just drop or did you get firmware crashes there as well?
Adjusting the subject as it's likely a pre-22000 chipsets problem to figure out.
I would really be interested on how this showed on iwm(8) given this seems to be related to older chipsets. I also reproduced it on another old one as well after another day (again no panic here). I'll contemplate how to do tracing for this in order to figure out what is going wrong; given the almost 24 hour timeframe to get to it this is a bit tricky but we'll see and hope that instrumentation will not make this go away. [155.105817] iwlwifi0: Detected crf-id 0x0, cnv-id 0x0 wfpm id 0x0 [155.110718] iwlwifi0: PCI dev 3165/4010, rev=0x210, rfid=0xd55555d5 [155.115870] iwlwifi0: Detected Intel(R) Dual Band Wireless AC 3165 [155.189453] iwlwifi0: successfully loaded firmware image 'iwlwifi-7265D-29.ucode' [155.196158] iwlwifi0: Found debug destination: EXTERNAL_DRAM [155.210617] iwlwifi0: Found debug configuration: 0 [155.216424] iwlwifi0: loaded firmware version 29.f2390aa8.0 7265D-29.ucode op_mode iwlmvm iwlwifi0: Microcode SW error detected. Restarting 0x2000000. iwlwifi0: Start IWL Error Log Dump: iwlwifi0: Transport status: 0x0000004B, valid: 6 iwlwifi0: Loaded firmware version: 29.f2390aa8.0 7265D-29.ucode iwlwifi0: 0x000021A0 | ADVANCED_SYSASSERT iwlwifi0: 0x000002A0 | trm_hw_status0 iwlwifi0: 0x00000000 | trm_hw_status1 iwlwifi0: 0x00043D6C | branchlink2 iwlwifi0: 0x0004B002 | interruptlink1 iwlwifi0: 0x00000000 | interruptlink2 iwlwifi0: 0x00000030 | data1 iwlwifi0: 0x00000000 | data2 iwlwifi0: 0x00000000 | data3 iwlwifi0: 0x6640C914 | beacon time iwlwifi0: 0xBEEE1EB5 | tsf low iwlwifi0: 0x00000064 | tsf hi iwlwifi0: 0x00000000 | time gp1 iwlwifi0: 0x7557917E | time gp2 iwlwifi0: 0x00000001 | uCode revision type iwlwifi0: 0x0000001D | uCode version major iwlwifi0: 0xF2390AA8 | uCode version minor iwlwifi0: 0x00000210 | hw version iwlwifi0: 0x00C89200 | board version iwlwifi0: 0x006B0118 | hcmd iwlwifi0: 0x00022080 | isr0 iwlwifi0: 0x00000000 | isr1 iwlwifi0: 0x0000000A | isr2 iwlwifi0: 0x004154C0 | isr3 iwlwifi0: 0x00000000 | isr4 iwlwifi0: 0x006A019F | last cmd Id iwlwifi0: 0x00000000 | wait_event iwlwifi0: 0x000000C0 | l2p_control iwlwifi0: 0x00018000 | l2p_duration iwlwifi0: 0x0000003F | l2p_mhvalid iwlwifi0: 0x00000000 | l2p_addr_match iwlwifi0: 0x00000005 | lmpm_pmg_sel iwlwifi0: 0x03031934 | timestamp iwlwifi0: 0x000098A8 | flow_handler iwlwifi0: Fseq Registers: iwlwifi0: 0x00000000 | FSEQ_ERROR_CODE iwlwifi0: 0x00000000 | FSEQ_TOP_INIT_VERSION iwlwifi0: 0x00000000 | FSEQ_CNVIO_INIT_VERSION iwlwifi0: 0x00000000 | FSEQ_OTP_VERSION iwlwifi0: 0x00000000 | FSEQ_TOP_CONTENT_VERSION iwlwifi0: 0x00000000 | FSEQ_ALIVE_TOKEN iwlwifi0: 0x00000000 | FSEQ_CNVI_ID iwlwifi0: 0x00000000 | FSEQ_CNVR_ID iwlwifi0: 0x00000000 | CNVI_AUX_MISC_CHIP iwlwifi0: 0x00000000 | CNVR_AUX_MISC_CHIP iwlwifi0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM iwlwifi0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR iwlwifi0: 0x00000000 | FSEQ_PREV_CNVIO_INIT_VERSION iwlwifi0: 0x00000000 | FSEQ_WIFI_FSEQ_VERSION iwlwifi0: 0x00000000 | FSEQ_BT_FSEQ_VERSION iwlwifi0: 0x00000000 | FSEQ_CLASS_TP_VERSION iwlwifi0: Collecting data: trigger 2 fired. linuxkpi_ieee80211_restart_hw:3530: XXX LKPI80211 TODO iwlwifi0: FW error in SYNC CMD ADD_STA #0 0xffffffff80dfbc0b at linux_dump_stack+0x1b #1 0xffffffff82a9bd1b at iwl_trans_pcie_send_hcmd+0x43b #2 0xffffffff82a2b1f8 at iwl_trans_send_cmd+0x88 #3 0xffffffff82a768dd at iwl_mvm_send_cmd_status+0x4d #4 0xffffffff82a769ef at iwl_mvm_send_cmd_pdu_status+0x4f #5 0xffffffff82a6340e at iwl_mvm_sta_send_to_fw+0x35e #6 0xffffffff82a65e2e at iwl_mvm_add_sta+0x16e #7 0xffffffff82a45d97 at iwl_mvm_mac_sta_state_common+0x667 #8 0xffffffff80df5e38 at lkpi_80211_mo_sta_state+0xa8 #9 0xffffffff80de7ec5 at lkpi_sta_scan_to_auth+0x6d5 #10 0xffffffff80de844b at lkpi_sta_run_to_auth+0x1b #11 0xffffffff80df402b at lkpi_iv_newstate+0x2cb #12 0xffffffff80d0dc8c at ieee80211_newstate_cb+0x29c #13 0xffffffff80bc0332 at taskqueue_run_locked+0x1c2 #14 0xffffffff80bc11f3 at taskqueue_thread_loop+0xd3 #15 0xffffffff80b0ac02 at fork_exit+0x82 #16 0xffffffff810645fe at fork_trampoline+0xe iwlwifi0: lkpi_sta_scan_to_auth:1835: mo_sta_state(NONE) failed: -5 iwlwifi0: lkpi_iv_newstate: error -1 during state transition 5 (RUN) -> 2 (AUTH)
I believe reporting this bug has caused the issue not to happen as much...and this is probably due to interacting with the laptop and not letting it sit idle for a long time. I will report back on this bug when I can provide answers to your questions. Specifically when it happens again I will tell you about this. >>>If instead of doing a netif restart wlan0, can you simply try: >>> ifconfig wlan0 down >>> ifconfig wlan0 up >>> ifconfig wlan0 scan >>>and see if that helps to get you associated again without the panic when this happens? I will load up the latest FreeBSD 15-CURRENT build, setting debug on wpa_supplicant over the weekend when I am not using this laptop to see if I can get the panic condition again. Now some responses to your other comments: >>>Right, and why is that? What happened before? >>>I see beacon misses in the log below. >>>Crowded spectrum? Low signal? ..? Crowded spectrum is interesting, as this has happened with different wireless routers (Netgear, TP_Link) at two different locations where there is definite overlap of wireless signals. For both locations, I had the laptop very close to the router. The Intel driver works negotiates on the 2.4GHz band with 802.11g. Of interest, the modulation does appear to change over time, from OFDM to DS, >>>But I didn't manage a follow-up panic. >>>You mentioned that you had that problem with iwm(4) already? >>>Did it just drop or did you get firmware crashes there as well? >>>I would really be interested on how this showed on iwm(8) given this seems to be related to older chipsets. The iwm driver acted the same way you have found, after a period of time, I would come back and find "no carrier" on "wlan0", but I would simply refresh the interface and get an IP address. I never got a panic with the iwm driver, this is something I have only seen with the iwlwifi driver. The laptop is getting old, but since intel wireless is pretty common, I wanted to raise this issue.
(In reply to Shirkdog from comment #7) >>>>I would really be interested on how this showed on iwm(8) given this seems to be related to older chipsets. > > The iwm driver acted the same way you have found, after a period of time, I would come back and find "no carrier" on "wlan0", but I would simply refresh the Do you also see firmware crashes there or just "no carrier" for no obvious reason?
(In reply to Bjoern A. Zeeb from comment #8) With just the iwm driver, the interface goes to "no carrier" status and there is no firmware crash (nothing in the logs). Log data just shows me restarting the interface with "service netif restart", and wpa_supplicant shows disconnecting logs from the BSSID like nothing is wrong.