> Two questions: > > Can you check with current upstream kernels, ideally 6.13-rc2 or the > versions available in Debian 6.12.5-1 (freshly uploaded, so has to > pass NEW) or 6.12.3-1 to verify the bahaviour is not present there? > > If this is the case there might be some requirements in the backports > which got missing. > > Samewise, if you have the resources, can you bisect upstream versions > between 6.1.112 and 6.1.115 specifically to identify which commit > causes the regression? > > Knowing though if the issue is present as well in mainline or most > recent stable series upstream would be good to get some more > datapoint.
Will do, thanks for the pointers.