https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271979
Oleg <oleglelc...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |oleglelc...@gmail.com
--- Comment #7 from Oleg <oleglelc...@gmail.com> ---
I think I've been encountering the same panic with my Intel Wi-fi 6 AX201 card.
If I type "ifconfig wlan create wlandev iwlwifi0", "ifconfig wlan0 channel
153", "wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf &", "dhclient
wlan0", then I will be able to access the internet without encountering issues
and there will be no panic. However, if I type "ifconfig wlan0 up" right after
creating wlandev, there will be a panic after I type "wpa_supplicant -i wlan0
-c /etc/wpa_supplicant.conf &". I don't really have the need to type "ifconfig
wlan0 up" because I am still able to access the internet after typing the
commands I already mentioned; however, bsdinstall wants this "up" thing to be
available early, so, in bsdinstall, I will encounter this panic. Here's the
backtrace:
__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:59
59 __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct
pcpu,
(kgdb) #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:59
#1 doadump (textdump=textdump@entry=1)
at /usr/src/sys/kern/kern_shutdown.c:407
#2 0xffffffff80b4bb60 in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:528
#3 0xffffffff80b4c07d in vpanic (
fmt=0xffffffff811d6263 "%s: lsta %p state not NONE: %#x, nstate %d arg
%d\n", ap=ap@entry=0xfffffe01e9a94ce0) at /usr/src/sys/kern/kern_shutdown.c:972
#4 0xffffffff80b4be03 in panic (fmt=<unavailable>)
at /usr/src/sys/kern/kern_shutdown.c:896
#5 0xffffffff80dcbd0c in lkpi_sta_auth_to_scan (vap=0xfffffe01f95cd010,
nstate=IEEE80211_S_SCAN, arg=1)
at /usr/src/sys/compat/linuxkpi/common/src/linux_80211.c:1153
#6 0xffffffff80dd2963 in lkpi_iv_newstate (vap=0xfffffe01f95cd010,
nstate=IEEE80211_S_SCAN, arg=1)
at /usr/src/sys/compat/linuxkpi/common/src/linux_80211.c:2045
#7 0xffffffff80cf8937 in ieee80211_newstate_cb (xvap=0xfffffe01f95cd010,
npending=<optimized out>) at /usr/src/sys/net80211/ieee80211_proto.c:2548
#8 0xffffffff80bb055b in taskqueue_run_locked (
queue=queue@entry=0xfffff80001cc8e00)
at /usr/src/sys/kern/subr_taskqueue.c:514
#9 0xffffffff80bb1613 in taskqueue_thread_loop (
arg=arg@entry=0xfffffe01ea0de110)
at /usr/src/sys/kern/subr_taskqueue.c:826
#10 0xffffffff80b02500 in fork_exit (
callout=0xffffffff80bb1540 <taskqueue_thread_loop>,
arg=0xfffffe01ea0de110, frame=0xfffffe01e9a94f40)
at /usr/src/sys/kern/kern_fork.c:1131
#11 <signal handler called>
#12 0xdeadc0dedeadc0de in ?? ()
Backtrace stopped: Cannot access memory at address 0xdeadc0dedeadc0de
(kgdb)
--
You are receiving this mail because:
You are on the CC list for the bug.
