Date: Sat, 10 Feb 2024 21:13:45 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 274382] iwlwifi Invalid TXQ id Message-ID: <bug-274382-21060-KgHPxxVHgo@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 #28 from rkoberman@gmail.com --- (In reply to Ed Maste from comment #26) This was a problem I was seeing with the lkpi prior to the update from drm-515-kmod to drm-61-kmod. I see nothing likely to be involved between the two. I was seeing this problem while running n266789-06c083f79dd7 and drm-515-kmod from Dec. 22 and n267556-69748e62e82a drm-61-kmod from Jan. 15. Aside from fixing the serious limitations of running my Alder Lake graphics= on 515, it also fixed the invalid TXQ and crashing issues I was seeing prior to the update to 61. I had previously noted that the stack backtraces from the many panics tied = to the invalid TXQ always included drm items near the top of the stack. Have you tried drm-61-kmod? It looks like using drm-66 (I assume from git a= s it is not in ports yet) has likely led to the return to the issues I had with drm-515. I have looked at commits to iwlwifi and the lkpi in the relevant time period and I see nothing that looks likely in either place. I am now running a sys= tem from Feb. 6 with no issues with either drm-61 or iwlwifi. --=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-KgHPxxVHgo>