On Tue, May 5, 2009 at 12:38 PM, Alex Deucher <[email protected]> wrote: > On Tue, May 5, 2009 at 12:28 PM, Lowell Alleman > <[email protected]> wrote: >> Hello all, >> >> I've got my X server stuck in some kind of loop that is using up nearly %100 >> of the CPU. I have a remote ssh connection and I'm running gdb against it. >> I've very unfamiar with debugging at this level, but I really want to >> anything I can to help track down some X issues I'm been hitting. >> >> I turned on drm kernel debugging for awhile, and I see this group of errors >> repeated over and over again: >> >> [ 9812.879383] [drm:drm_ioctl] pid=3917, cmd=0x6444, nr=0x44, dev 0xe200, >> auth=1 >> [ 9812.879388] [drm:radeon_cp_idle] >> [ 9812.879390] [drm:radeon_do_cp_idle] >> [ 9813.035795] [drm:radeon_do_wait_for_idle] wait idle failed status : >> 0x80010140 0x00000000 >> [ 9813.035798] [drm:drm_ioctl] ret = fffffff0 > > Your GPU has locked up. The trick is finding what combination of > commands and state caused the lockup. > > Alex
So I take it there is no way to get to this information from my running X server? (using gdb, or strace, or something like that)? _______________________________________________ xorg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xorg
