From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx159.postini.com [74.125.245.159]) by kanga.kvack.org (Postfix) with SMTP id D8B226B004F for ; Mon, 5 Dec 2011 14:07:14 -0500 (EST) Received: by qadc12 with SMTP id c12so865039qad.14 for ; Mon, 05 Dec 2011 11:07:13 -0800 (PST) Date: Mon, 5 Dec 2011 14:11:16 -0500 From: Jerome Glisse Subject: Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413 Message-ID: <20111205191116.GB4342@homer.localdomain> References: <20111124085040.GA1677@x4.trippels.de> <20111202230412.GB12057@homer.localdomain> <20111203092845.GA1520@x4.trippels.de> <20111203122900.GA1617@x4.trippels.de> <20111204010200.GA1530@x4.trippels.de> <20111205171046.GA4342@homer.localdomain> <20111205181549.GA1612@x4.trippels.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b5gNqxB1S1yM7hjW" Content-Disposition: inline In-Reply-To: <20111205181549.GA1612@x4.trippels.de> Sender: owner-linux-mm@kvack.org List-ID: To: Markus Trippelsdorf Cc: Dave Airlie , Christoph Lameter , "Alex, Shi" , Eric Dumazet , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , dri-devel@lists.freedesktop.org, Pekka Enberg , "linux-mm@kvack.org" , Matt Mackall , tj@kernel.org, Alex Deucher --b5gNqxB1S1yM7hjW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 > > > > 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 ? I believe this patch could go to stable too as it's low impact from my pov. Cheers, Jerome --b5gNqxB1S1yM7hjW Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="0001-drm-radeon-disable-possible-GPU-writeback-early-v2.patch" --b5gNqxB1S1yM7hjW--