[Bug 271979] bsdinstall(8): iwlwifi(4): system crash when authenticating for Wi-Fi: panic: lkpi_sta_auth_to_scan: lsta 0x... state not NONE: 0, nstate 1 arg 1
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 09 Oct 2023 00:55:04 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271979 rkoberman@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rkoberman@gmail.com --- Comment #20 from rkoberman@gmail.com --- I just tried another "service netif restart wlan0" and my system froze. No panic. Nothing logged. No core dump. Display froze after "Starting wpa_supplicant." Nothing abnormal until that point. After a reboot I tried again without X running. This time I got a panic: ptavv dumped core - see /var/crash/vmcore.5 Sun Oct 8 17:37:18 PDT 2023 FreeBSD ptavv 15.0-CURRENT FreeBSD 15.0-CURRENT #7 main-n265807-04c8bfc17610: Sat Oct 7 23:34:33 PDT 2023 root@ptavv:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 panic: lkpi_sta_auth_to_scan: lsta 0xfffff8000bb92000 state not NONE: 0, nstate 1 arg 1 I can attach the full file if it looks useful. One oddity is that I see several drm items in the stack dump: KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe015adc8330 vpanic() at vpanic+0x132/frame 0xfffffe015adc8460 panic() at panic+0x43/frame 0xfffffe015adc84c0 trap_fatal() at trap_fatal+0x40c/frame 0xfffffe015adc8520 calltrap() at calltrap+0x8/frame 0xfffffe015adc8520 --- trap 0x9, rip = 0xffffffff831d25d0, rsp = 0xfffffe015adc85f0, rbp = 0xfffffe015adc8630 --- intel_atomic_get_global_obj_state() at intel_atomic_get_global_obj_state+0x90/frame 0xfffffe015adc8630 skl_compute_wm() at skl_compute_wm+0xaec/frame 0xfffffe015adc8850 intel_atomic_check() at intel_atomic_check+0xeff/frame 0xfffffe015adc8920 drm_atomic_check_only() at drm_atomic_check_only+0x4a3/frame 0xfffffe015adc8990 drm_atomic_commit() at drm_atomic_commit+0x13/frame 0xfffffe015adc89b0 drm_client_modeset_commit_atomic() at drm_client_modeset_commit_atomic+0x158/frame 0xfffffe015adc8a20 drm_client_modeset_commit_locked() at drm_client_modeset_commit_locked+0x74/frame 0xfffffe015adc8a70 drm_client_modeset_commit() at drm_client_modeset_commit+0x21/frame 0xfffffe015adc8a90 drm_fb_helper_restore_fbdev_mode_unlocked() at drm_fb_helper_restore_fbdev_mode_unlocked+0x83/frame 0xfffffe015adc8ac0 vt_kms_postswitch() at vt_kms_postswitch+0x181/frame 0xfffffe015adc8af0 vt_window_switch() at vt_window_switch+0x25e/frame 0xfffffe015adc8b30 vtterm_cngrab() at vtterm_cngrab+0x4f/frame 0xfffffe015adc8b50 cngrab() at cngrab+0x26/frame 0xfffffe015adc8b70 vpanic() at vpanic+0xd1/frame 0xfffffe015adc8ca0 panic() at panic+0x43/frame 0xfffffe015adc8d00 This crash occurred after I had terminated the X session and was in text mode on vty0. Let me know what else I might be able to provide. -- You are receiving this mail because: You are on the CC list for the bug.