Date: Wed, 14 Feb 2024 14:57:23 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 274382] iwlwifi Invalid TXQ id Message-ID: <bug-274382-21060-N6VzkDwtJ5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-274382-21060@https.bugs.freebsd.org/bugzilla/> References: <bug-274382-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=3D274382 --- Comment #29 from Cheng Cui <cc@FreeBSD.org> --- The patches from D43389, D43725, D43753 in combination seem to work and prevented the crash "panic: lkpi_sta_auth_to_assoc" from "service netif restart" or simply booting the kernel. The patches does not prevent "please report to PR 274382" from showing up. However, I observed this strange difference among my three freebsd VMs. vm1: Feb 12 main kernel, keeps hitting the crash without the patches vm2: Feb 12 main kernel, and never hit the crash vm3: Feb 14 main kernel, and never hit the crash, on a second physical host The only different between vm1 and vm2 (they are on the same physical host)= is that vm1 was created last November, 2023 with World rebuilt that time; but = vm2 was created last week using the Feb 8 freebsd-current ISO image without rebuilding the World. The vm3 was also created in Feb without rebuilding the World. But I can't explain why the old World but new kernel will cause the problem. And I suspect that is the drm-515-kmod (as rkoberman@gmail.com mentioned) t= he culprit? I remember Ed told me before that the ports tree has drm-kmod, but could somebody help explain my suspicion, before I rebuild the drm-kmod in vm1 to verify myself? --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-274382-21060-N6VzkDwtJ5>