Hi, On Mon, Mar 17, 2025 at 11:56:18AM +0000, Henrik Morsing via GLLUG wrote: > The previous kernel does seem to be stable, so will stick to that for now. > > Odd what's causing it though. And if no-one reports it, it won't get fixed.
Report it to Kali then. At this point if this were me on Debian and a bug report didn't result in a quick fix then I'd be building my own kernel from the source of the kernel package that fails, confirming that it fails and then doing a "git bisect" to go further back. I'd repeat this until I got a kernel that didn't fail at which point I'd be able to further bisect down to the exact commit that caused the problem for me. I'd then report that in the Debian bug. I don't know if you can do that with Kali. If you can't, it might be possible to find two upstream (i.e. kernel.org) source versions that are stable and fail respectively, and do the same bisect there. Knowing which upstream commit breaks it for you would still be useful information for your distribution. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting -- GLLUG mailing list [email protected] https://mailman.lug.org.uk/mailman/listinfo/gllug
