Created attachment 65768 [details] Kernel panic #1 I've got kernel panic two times in a row after opening http://apod.nasa.gov/apod/image/1207/orion_hubble_6000.jpg in firefox on vanilla kernel-3.5.2 with libdrm/mesa/xf86-video-ati from latest git.
Created attachment 65769 [details] Kernel panic #1
Created attachment 65770 [details] Karnel panic #2
Created attachment 65771 [details] Xorg.log
Created attachment 65772 [details] glxinfo
Created attachment 65773 [details] Kernel log, second panic
It also happens with default xorg.conf (without "ColorTiling2D" and "AccelDFS").
There is no crashes with 3.4 kernel, but messages "space check failed in flush".
Bisection leads me to (linux-stable tree) 8fbaa37e12d83fe586e593bba3af8bd907117d50 is the first bad commit commit 8fbaa37e12d83fe586e593bba3af8bd907117d50 Author: Jerome Glisse <jglisse@redhat.com> Date: Thu Jul 12 18:23:05 2012 -0400 drm/radeon: fix bo creation retry path commit d1c7871ddb1f588b8eb35affd9ee1a3d5e11cd0c upstream. Retry label was at wrong place in function leading to memory leak. Signed-off-by: Jerome Glisse <jglisse@redhat.com> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Dave Airlie <airlied@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> :040000 040000 5e9268680a97277b9560844799a6f70df12b97ff acb9847d2ea78612801e15b21063ae65b5dcf536 M drivers
Fixed in Linus tree commit 676bc2e1e4f9072f7a640d5b7c99ffdf9709a6e7 Author: Alex Deucher <alexander.deucher@amd.com> Date: Tue Aug 21 09:55:01 2012 -0400 Revert "drm/radeon: fix bo creation retry path" This reverts commit d1c7871ddb1f588b8eb35affd9ee1a3d5e11cd0c. ttm_bo_init() destroys the BO on failure. So this patch makes the retry path work with freed memory. This ends up causing kernel panics when this path is hit. Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Cc: stable@vger.kernel.org
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.