Come to think of it, a more likely explanation is that this is part of radeon bug 1841718. Not sure why I didn't consider that before.
Come to think of it, a more likely explanation is that this is part of radeon bug 1841718. Not sure why I didn't consider that before.