On 2011.12.05 at 14:11 -0500, Jerome Glisse wrote: > On Mon, Dec 05, 2011 at 07:15:49PM +0100, Markus Trippelsdorf wrote: > > On 2011.12.05 at 12:10 -0500, Jerome Glisse wrote: > > > On Sun, Dec 04, 2011 at 02:02:00AM +0100, Markus Trippelsdorf wrote: > > > > On 2011.12.03 at 14:31 -0500, Jerome Glisse wrote: > > > > > On Sat, Dec 3, 2011 at 7:29 AM, Markus Trippelsdorf > > > > > <markus@xxxxxxxxxxxxxxx> wrote: > > > > > > On 2011.12.03 at 12:20 +0000, Dave Airlie wrote: > > > > > >> >> > > > > FIX idr_layer_cache: Marking all objects used > > > > > >> >> > > > > > > > > >> >> > > > Yesterday I couldn't reproduce the issue at all. But today I've hit > > > > > >> >> > > > exactly the same spot again. (CCing the drm list) > > > > > >> > > > > > >> If I had to guess it looks like 0 is getting written back to some > > > > > >> random page by the GPU maybe, it could be that the GPU is in some half > > > > > >> setup state at boot or on a reboot does it happen from a cold boot or > > > > > >> just warm boot or kexec? > > > > > > > > > > > > Only happened with kexec thus far. Cold boot seems to be fine. > > > > > > > > > > > > > > > > Can you add radeon.no_wb=1 to your kexec kernel paramater an see if > > > > > you can reproduce. > > > > > > > > No, I cannot reproduce the issue with radeon.no_wb=1. (I write this > > > > after 700 successful kexec iterations...) > > > > > > > > > > Can you try if attached patch fix the issue when you don't pass the > > > radeon.no_wb=1 option ? > > > > Yes the patch finally fixes the issue for me (tested with 120 kexec > > iterations). > > Thanks Jerome! > > > > -- > > Markus > > Can you do a kick run on the modified patch ? This one is also OK after ~60 iterations. -- Markus -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>