Date: Sat, 15 Oct 2022 18:34:36 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 267029] iwlwifi: Panic on initial network startup Message-ID: <bug-267029-21060-xggLbdgJ0R@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267029-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-267029-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267029 Bjoern A. Zeeb <bz@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Assignee|wireless@FreeBSD.org |bz@FreeBSD.org CC| |bz@FreeBSD.org --- Comment #1 from Bjoern A. Zeeb <bz@FreeBSD.org> --- Please try a ifconfig wlan0 down && sleep 1 && ifconfig wlan0 up insteadt of service restart. The core.txt seems to have a lot of log_in_vain bits in it but I cannot actually find the initial error anymore. You may have to increase your ker= nel message buffer. The line right before the kernel panic contains an error from the driver, w= hich would have been great in the bug report. I am also confused by the fact that you say a power cycle did not help and always panics on start given your crashdump was full of running firefox. Can you elaborate a bit more on when it worked and when it stopped working? Currently it sounds like you had a working machine, it lost assoc, you trie= d to fix that, it paniced, and after that it now always panics with the same ker= nel on every bootup despite having the laptop turned off even? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267029-21060-xggLbdgJ0R>