[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6D8AEFD@saturn3.aculab.com>
Date: Mon, 5 Dec 2011 10:44:33 -0000
From: "David Laight" <David.Laight@...LAB.COM>
To: "Markus Trippelsdorf" <markus@...ppelsdorf.de>,
"Dave Airlie" <airlied@...il.com>
Cc: "Jerome Glisse" <j.glisse@...il.com>,
"Christoph Lameter" <cl@...ux.com>,
"Alex, Shi" <alex.shi@...el.com>,
"Eric Dumazet" <eric.dumazet@...il.com>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
"Pekka Enberg" <penberg@...nel.org>, <linux-mm@...ck.org>,
"Matt Mackall" <mpm@...enic.com>, <tj@...nel.org>,
"Alex Deucher" <alexander.deucher@....com>
Subject: RE: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413
> > 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.
Sounds like the GPU is writing to physical memory from the
old mappings.
This can happen to other devices if they aren't completely
disabled - which may not happen since the kexec case probably
avoids some of the hardware resets that occurr diring a normal
reboot.
I remember an ethernet chip writing into its rx ring/buffer
area following a reboot (and reinstall!) when connected
to a quiet lan.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists