Hi Stefan,
On Mon, Nov 08, 2021 at 02:35:16PM +0100, Stefan Sperling wrote:
| Unfortunately, I cannot make any sense of this.
|
| There were no new changes in iwx(4) since Oct 15. If the Oct 31 snap
| was working fine then your problem is not related to driver-side changes.
Hmm, I may have gotten lucky with the previous snap. Will do more
testing.
| Also in the regular code flow there is no way that non-QoS data frames
| end up on the list processed in iwx_release_frames(). And QoS data frames
| always have a sequence number so this assertion simply should not trigger.
|
| I guess there could be some kind of memory corruption, where either an
| mbuf or the mbuf list maintained by the driver is garbage?
|
| Please try to bisect kernels from source and see whether you can find
| a commit which started this. I don't have a better answer for now.
Thanks for the feedback, I'll try bisecting and report what I find.
Paul
--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
http://www.weirdnet.nl/
