https://bugzilla.kernel.org/show_bug.cgi?id=46161

--- Comment #1 from Michel Dänzer michel@daenzer.net 2012-09-03 14:04:11 --- (In reply to comment #0)

This started happening in 3.6-rc1 and is still in rc2. It does happen on 3.5.1 and 3.5.2 if the radeon module is manually loaded a second time after boot.

So, do I understand this correctly: With 3.5.x it only happens after the radeon kernel module was loaded a second time, but with 3.6-rc* it even happens after it was loaded for the first time? If so, can you bisect what introduced the change in behaviour for 3.6-rc*?