Alex Deucher <alexdeucher@xxxxxxxxx> writes: >> In that case those are the already known problems with the scheduler >> changes, aren't they? > > Yes. Those changes went into 6.7 though, not 6.6 AFAIK. Maybe I'm > misunderstanding what the original report was actually testing. If it > was 6.7, then try reverting: > 56e449603f0ac580700621a356d35d5716a62ce5 > b70438004a14f4d0f9890b3297cd66248728546c At some point it was suggested that I file a gitlab issue, but I took this to mean it was already known and being worked on. -rc3 came out today and still has the problem. Is there a known issue I could track?
