I was a bit short in the original description, but luckily we've since reached an understanding on how to try to reproduce this bug. Unfortunately he's not bee

I was a bit short in the original description, but luckily we've since reached an understanding on how to try to reproduce this bug. Unfortunately he's not been able to reproduce it, even though I can reproduce it on several machines here (and it's been independently reproduced by other people at Red Hat). We do know that it happens much less frequently on Intel hardware than AMD hardware (likely just because of subtle timing differences), and he's of course working at Intel.