Hi Paul, On Thu, May 30, 2024 at 12:58:45PM +0100, Ben Hutchings wrote: > On Thu, 2024-05-16 at 08:09 +0200, Paul Gevers wrote: > > Hi Ben (and all the rest), > > > > On 15-05-2024 9:56 p.m., Ben Hutchings wrote: > > > Apologies for leaving this bug for so long. > > > > NP, part of live I guess. > > > > > Is this bug still occurring? > > > > I don't know. The problem was severe enough for us to abandon the idea > > of running the backport kernels on our arm64 hosts, so we went back to > > the stable kernel there. > > > > > I had a look for possibly related fixes, > > > and found: > > > > > > commit 22e111ed6c83dcde3037fc81176012721bc34c0b > > > > [...] > > > > > The fix went into > > > 6.8-rc1 and was backported to 6.6.15, so Debian versions 6.6.15-1 > > > onward should have it. > > > > > commit a8b0026847b8c43445c921ad2c85521c92eb175f > > > > [...] > > > > > which went into 6.8 but was *not* backported. > > > > If you think it worth enough knowing if either is the case, I can > > install the backports kernel again on the arm64 hosts, but obviously > > that will be annoying for us. Please let me know if I should pursue this > > (I would be expecting a bit quicker turn around on this bug if you say > > yes now ;) ). > > If you can test with the unstable kernel that would be great. If you > are limited to only stable and backports, then you should probably wait > until 6.8 is in backports rather than testing the current 6.7 backport > that has only one of the fixes.
In the last weekly kernel team meeting we discussed about some of the open issues, and we wondered if you were able to test again with either a unstable kernel, or if that's not possible with the current versions available trough backports? Unfortunately for the 6.8.y series though the package is not yet out of backports-new. Regards, Salvatore
