Comment # 186
on bug 79980
from Jacob
(In reply to agapito from comment #184) > (In reply to Michel Dänzer from comment #182) > > Can you bisect which commit in 3.18-rc2 fixed it for you? > > Sorry, I do not know how to do it. But these are the changes between RC1 > (still crashing) and RC2 (stable): > > drm/radeon: reduce sparse false positive warnings > Revert "drm/radeon: drop btc_get_max_clock_from_voltage_dependency_table" > Revert "drm/radeon/dpm: drop clk/voltage dependency filters for SI" > drm/radeon: initialize sadb to NULL in the audio code > drm/radeon: fix speaker allocation setup > drm/radeon: use gart memory for DMA ring tests > drm/radeon: fix vm page table block size calculation > > I am not an expert, but probably: drm/radeon: use gart memory for DMA ring > tests; could be the good commit. > > (In reply to Aaron B from comment #183) > > 3.18 is still crashing for me, I doubt it is fixed. > > rc2 crashed for you? After 24 hours I am still stable. https://wiki.ubuntu.com/Kernel/KernelBisection This guide helped me. Might help you too. In short, you just have to clone the Linux repository, run "git bisect start <BAD> <GOOD>", then compile the kernel and test it. If it crashes, then run "git bisect bad", and recompile. If you think you've tested it long enough and the version is stable, then run "git bisect good", and recompile. Continue to do so until no revisions are left to be tested
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
