Hi Ralf, On Wed, Dec 17, 2025 at 02:05:41PM +0100, Ralf Jung wrote: > Hi all, > > By trying out various snapshot kernels, I now got it nailed down to a single > major version bump: > > 6.13.11-1~exp1 is still good. > 6.14.6-1~exp1 has the problem.
While I understand from the context you gave that might not be the easiiest thing to make possible, but I think the most effective next step would be now to try upstream 6.13 and upstream 6.14.6 and then bisect. If you have a second device available maybe it is enough to join with that to the call and trigger the problem? In particular if you can take off work the device which exposes the problem. I do realize this is much we ask, but you are as well the only one able to reproduce the problem on the particular hardware, so actually in the best position to find the offending change. Regards, Salvatore
