https://bugs.freedesktop.org/show_bug.cgi?id=34313 --- Comment #22 from Bob Ham <rah@xxxxxxx> 2011-05-27 09:47:15 PDT --- I've done a bisect on GPU lockups with warzone 2100. During this bisect there were some kernels that displayed bad GL rendering (lots of artifacts, flickering textures, etc.), some of which locked up the GPU and some of which didn't. I've treated these kernels as 'good' if they do not lock up because bad rendering is not a problem with recent kernels so it's likely to have been a different issue. The last commit identified by the bisect caused the kernel to behave in a strange way with various bits timing out (particular on file system access) as soon as X was loaded, prior to any GL activity. The system is unusable and the time outs continue until the machine locks hard. I'll attached a log of the kernel's output. I'm not sure if this is the bug I'm chasing. Marking the commit as "skip" during the bisect unfortunately produces the following report: There are only 'skip'ped commits left to test. The first bad commit could be any of: b7ae5056c94a8191c1fd0b5697707377516c0c5d 5480f727dc4c049eb46b191bfaeb034067aa6835 We cannot bisect more! The possibilities are as follows: Merge branch 'drm-fixes' of /home/airlied/kernel/linux-2.6 into drm-core-next http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=b7ae5056c94a8191c1fd0b5697707377516c0c5d Revert "drm/radeon/kms: remove some pll algo flags" http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=5480f727dc4c049eb46b191bfaeb034067aa6835 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
