[Bug 290636] kernel panic in linuxkpi_ieee80211_next_txq
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 290636] kernel panic in linuxkpi_ieee80211_next_txq"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 08 Dec 2025 00:44:34 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290636
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> ---
Hi,
it's been a bit but I just wanted to let you know that I got a similar/same
panic (I have a debug kernel on so an assert might have caught it; and I have
local modifications):
/sys/compat/linuxkpi/common/src/linux_80211.c:8723:
linuxkpi_ieee80211_next_txq: Bad link elm 0xfffff800036fa300 prev->next != elm
cpuid = 2
time = 1765156399
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0069e87a40
vpanic() at vpanic+0x136/frame 0xfffffe0069e87b70
panic() at panic+0x43/frame 0xfffffe0069e87bd0
linuxkpi_ieee80211_next_txq() at linuxkpi_ieee80211_next_txq+0xe6/frame
0xfffffe0069e87bf0
...
I'll try to work through this during the week.
--
You are receiving this mail because:
You are the assignee for the bug.