https://bugzilla.kernel.org/show_bug.cgi?id=33912 --- Comment #10 from Vish <drkvi-a@xxxxxxxxx> 2011-06-10 07:50:02 --- (In reply to comment #9) > Can you bisect? I have never bisected a kernel, but I can try. Just have a few doubts. 1 * Can I do with the Ubuntu kernel as per Ubuntu instructions[0] as: $ git bisect start Ubuntu-2.6.35-1.1 Ubuntu-2.6.34-5.14 Which seems a saner incremental interval of Jun5 -> Jun 4. Whereas Mainline Kernel 2.6.35-020635rc1-generic #020635rc1[1] which is dated Jun 1 had the problem , but Kernel 2.6.34-02063407-generic #201009140905[2] dated Sep 14(!!!) did not have the problem. 2 * Are there any pointers to narrow down the kernel commit from the backtraces I have posted? Or is just looking for "drivers/gpu/drm/radeon/" the closest? 3 * Is there any specific command I need to run if I hit the bug? Or is gdb of X sufficient? Do I need to set any variables to get better logs of the freeze? (This is a very random bug which can sometimes take days, would be nice to know just to be prepared. And I dont know much about kernel, hence the Qs.. :D ) [0]<https://wiki.ubuntu.com/Kernel/KernelBisection> [1]<http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc1-lucid/> [2]<http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34.7-maverick/> [3]<http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commit;h=67a3e12b05e055c0415c556a315a3d3eb637e29e> -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
