Sorry for the bump, is there anything else we can try to debug this issue, or shall I start bisecting all the patches in the 6.5 -> 6.6 chain to find the problematic one? It sounds very tie consuming, but if it's my only option, I'll have to do it...