On Tue, 24 Aug 2010 00:55:54 +0100 Chris Wilson <chris at chris-wilson.co.uk> wrote:
> In threes. Hmm, one for primary, cursor and self-refresh. drm.debug=0xe > would be interesting to see what the pixel clock is. > > Can you grab one before the bad commit and one after? If there is a change > that may help pin-point the mistake. Or indicate further problems... OK, three files attached; drm.good is from 2.6.35, drm.bad is from 2.6.36-rc2. I also stripped the times and did a diff, in case that's useful. If you'd like output from right around the bad commit, say the word; that will take a bit of building time (I didn't keep all those bisect kernels around) but I can do it. Thanks, jon -------------- next part -------------- A non-text attachment was scrubbed... Name: drm.good Type: application/octet-stream Size: 32898 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20100824/43973a5d/attachment-0002.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: drm.bad Type: application/octet-stream Size: 34704 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20100824/43973a5d/attachment-0003.obj> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: drm.diff URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20100824/43973a5d/attachment-0001.txt>
