Bug 268878

Summary: After installing the system, the system crashes when setting wifi
Product: Base System Reporter: ice051 <405032354>
Component: wirelessAssignee: freebsd-wireless (Nobody) <wireless>
Status: Open ---    
Severity: Affects Only Me CC: bz, grahamperrin, rwells772003, stoneab, yklaxds
Priority: --- Keywords: crash
Version: CURRENT   
Hardware: amd64   
OS: Any   
See Also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266570
Bug Depends on:    
Bug Blocks: 273620    
Attachments:
Description Flags
panic dump none

Description ice051 2023-01-11 05:16:43 UTC
The cpu is 13600kf, the main board is TUF GAMING B660M-PLUS WIFI D4, the system is FreeBSD-14.0-CURRENT-amd64-20230108-11b5b9e8a520-259967-memstick.img, After installing the system, before rebooting, and when setting up the wireless network, the system will crash after entering the wifi password.
Comment 1 Bjoern A. Zeeb freebsd_committer freebsd_triage 2023-01-11 22:46:29 UTC
It's an Intel card in that system?
Do you by any chance have the pciconf -lv output for it?

Do you have any further information on crash?  A backtrace?  A panic message?
Comment 2 ykla 2023-01-12 03:33:24 UTC
(In reply to ice051 from comment #0)
Show the output from pciconf -lv and take a photo about the kernel panic please.
Comment 3 Hitch 2023-07-04 04:36:35 UTC
I am running 13.2 STABLE, and the system crashes when attempting to setup wifi during installation.  I have successfully installed the system by bypassing the network setup and configuring after install.  I am running this on a Lenovo ThinkPad P15 Gen 1 with iwlwifi driver.  Install recognizes my wificard and the network, but after entering ssid and psk the system immediately crashes.
Comment 4 Ryan Wells 2023-07-14 22:30:24 UTC
Created attachment 243397 [details]
panic dump

crash screen after entering wifi password
Comment 5 Graham Perrin 2024-11-24 17:36:10 UTC
Reproducible with yesterday's 14.2-RC1?
Comment 6 Bjoern A. Zeeb freebsd_committer freebsd_triage 2024-11-24 21:55:30 UTC
This seems similar to what 266570 was.
The fixes listed in 263613 and related will likely have fixed this.

Just leaving it here as comments given this wasn't categorized.