http://bugzilla.kernel.org/show_bug.cgi?id=13819
--- Comment #7 from Reinette Chatre <[email protected]> 2009-07-29 22:05:41 --- This problem has me very confused. I have tried bisecting it three times now and every time I end up with a patch from a merge of the 'drm-intel-next' branch, but I do not always get the same commit from that branch as the "first bad commit". I went ahead and "rolled my own" bisect by using rc4 and reverting all the patches from that branch merge. As expected, that gave me a working setup again. I then did a manual bisect and found that "drm/i915: enable error detection & state collection" was the bad commit. I wanted to confirm this with a sanity check, but could not revert it on its own, I had to revert the following to get a working setup based off the current linux-2.6 (4733fd328f14280900435d9dbae1487d110a4d56): drm/i915: Don't update display FIFO watermark on IGDNG drm/i915: add FIFO watermark support drm/i915: enable error detection & state collection -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
