http://bugzilla.kernel.org/show_bug.cgi?id=15276
--- Comment #10 from Michał Witkowski <ne...@o2.pl> 2010-02-13 07:41:38 --- (In reply to comment #8) > (In reply to comment #7) > > Curious thing is, that these crashes didn't happen in vanilla 2.6.33-rc6. > > They > > started appearing in a kernel built with the patch for bug 15186. It still > > happens in kernel 2.6.33-rc7 (one crash in Hex Empire, one in present > > windows). > > Any chance you can use git bisect to track down the problematic commit? Could you please clarify how this should be done? A small howto would be nice, as I'm not good with git. I presume this means building numerous kernels at various git points, right? Is there a way to narrow it down to only the radeon patches so that the number of kernels rebuilt will be lower? The problem is, I can't find a 100% reproducible case. The closest I got is the flash Hex Empire get which crashes after 2-5 minutes. Testing it that way would be problematic though. Just a question: If I revert to vanilla 2.6.33rc6 and see that there are no hard-locks, would that be enough to pinpoint the problem to the bug 15186 fix? I started encountering problems after applying the fix to vanilla 2.6.33rc-6. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
