https://bugs.freedesktop.org/show_bug.cgi?id=34313 --- Comment #14 from eric <e.durmin@xxxxxxx> 2011-04-11 06:00:55 PDT --- This happens also with r300g + linux-2.6.38.2 + KMS. I can not always reproduce this GPU lockup, but working (scrolling, opening a new tab) with big or fullscreen windows seems to trigger this lockup... but not right after a reboot... so it's difficult to reproduce. Hopefully someone finds a better way to reproduce this lockup. When the lockup starts the display disappears (turns to black) for 1 or 2 seconds, then the next will happen: 1) display will return and everything will work again, but the next lockup will happen soon; 2) display will return but only mouse and keyboard are working, the display will be frozen except the mouse pointer can move around; I have to exit all running applications (alt+f4) blindly because the changes will not be seen, go to console (ctrl+alt+f1) and from there reboot the system. Switching to console (ctrl+alt+f1) usually works and there the display is working again, but killing and restarting X will not work, the only way to get X back is to reboot. During the lockup the kernel.log will be full of: kernel: [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! kernel: [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1). These lines are going for ever until I kill X. Some lockups looking like mine were solved by turning off 'EnablePageFlip' in xorg.conf or setting 'agpmode' to -1, 1 or 4 in modprobe.conf or exporting 'LIBGL_ALWAYS_INDIRECT=1'... none of these solutions worked for me. Maybe turning off KMS works, but without KMS certain things won't work/are different, so I try to keep using KMS. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
