(In reply to agapito from comment #184)
> (In reply to Michel D=C3=A4nzer from comment #182)
> > Can you bisect which commit in 3.18-rc2 fixed it for you?
>=20
> Sorry, I do not know how to do it. But these are the changes between R=
C1
> (still crashing) and RC2 (stable):
>=20
>  drm/radeon: reduce sparse false positive warnings
>  Revert "drm/radeon: drop btc_get_max_clock_from_voltage_dependen=
cy_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
>=20
> I am not an expert, but probably: drm/radeon: use gart memory for DMA =
ring
> tests; could be the good commit.
>=20
> (In reply to Aaron B from com=
ment #183)
> > 3.18 is still crashing for me, I doubt it is fixed.
>=20
> rc2 crashed for you? After 24 hours I am still stable.

https://wiki.ubu=
ntu.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 r=
un
"git bisect good", and recompile.
Continue to do so until no revisions are left to be tested