Date: Wed, 14 Feb 2024 15:29:08 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 274382] iwlwifi Invalid TXQ id Message-ID: <bug-274382-21060-3EE0VnbjEf@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 #30 from Bjoern A. Zeeb <bz@FreeBSD.org> --- (In reply to Cheng Cui from comment #29) > [..] The patches does not prevent "please report to PR 274382" from showi= ng up. Can you reliably reproduce it? There's some more debugging to be added to = see in which state we are with the sta. > However, I observed this strange difference among my three freebsd VMs. >=20 > 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 ho= st I think that basically explains the observations from a lot of people incl.= the problem which made it hard to track some of this down. Some people do see = the problems while others don't. Some people see if depending on timing and (radio) environment and others don't. This is why some people have been reporting "very happy" recently and others still saw crashes. It's not a deterministic setting and depends on many different things from user space = to radio. This is why the reproducer based on your observations last year was= so important. --=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-3EE0VnbjEf>