(In reply to Ana Guerrero from comment #10) > This seems to have appeared again with linux 6.4.11, full log attached. This is a different error handled in bug 1214391 now, right?