Thanks for pointing out this policy. I did however want to share my workaround with people who might find this bug. And surely you'll agree that having one's bug report marked as a duplicate feels like it is being thrown away, it's not a good feeling for the reporter; and in this case it is clear that we're dealing with a duplicate.
3.4.17 (2012-10-31) works, as reported earlier, while 3.5.0-rc1 (2012-06-03) crashes (screen and keyboard frozen, no log files left). Further bisection would require delving into the git history. Newer kernels are also affected, right up to the latest 3.7.0-rc4 (2012-11-04). So the signs point to a problem upstream.
Red Hat users have hit the same issue, and have got further than we in debugging. Timothy Davis narrowed the problem down to changes made in radeon_kms.c between 3.4 and 3.5. Again, we need to send this upstream. https://bugzilla.redhat.com/show_bug.cgi?id=845745
Thanks for pointing out this policy. I did however want to share my workaround with people who might find this bug. And surely you'll agree that having one's bug report marked as a duplicate feels like it is being thrown away, it's not a good feeling for the reporter; and in this case it is clear that we're dealing with a duplicate.
By the way, I performed the bisection, using quantal kernels from http:// kernel. ubuntu. com/~kernel- ppa/mainline/
3.4.17 (2012-10-31) works, as reported earlier, while 3.5.0-rc1 (2012-06-03) crashes (screen and keyboard frozen, no log files left). Further bisection would require delving into the git history. Newer kernels are also affected, right up to the latest 3.7.0-rc4 (2012-11-04). So the signs point to a problem upstream.
Red Hat users have hit the same issue, and have got further than we in debugging. Timothy Davis narrowed the problem down to changes made in radeon_kms.c between 3.4 and 3.5. Again, we need to send this upstream. /bugzilla. redhat. com/show_ bug.cgi? id=845745
https:/