Comment 31 for bug 330460

Revision history for this message
In , Martin Olsson (mnemo) wrote :

The error I get when using this stress testing tool is what looks like a CPU spin inside drm_intel_gem_bo_alloc_internal (I put break points on all functions in stack and ran it for a pretty long time and it didn't hit them):

#0 0x00007f2867bc6887 in drm_intel_gem_bo_alloc_internal (bufmgr=0x1bcd4c0, name=0x7f2867e3e872 "pixmap", size=1140615168,
    alignment=<value optimized out>, for_render=1) at ../../../libdrm/intel/intel_bufmgr_gem.c:205
#1 0x00007f2867e17cad in i830_uxa_create_pixmap (screen=0x1bccd70, w=16877, h=16877, depth=<value optimized out>, usage=0)
    at ../../src/i830_exa.c:966
#2 0x0000000000449b8a in ProcCreatePixmap (client=0x6155570) at ../../dix/dispatch.c:1299
#3 0x000000000044e354 in Dispatch () at ../../dix/dispatch.c:437
#4 0x0000000000433ddd in main (argc=10, argv=0x7fff74080a88, envp=<value optimized out>) at ../../dix/main.c:397

The original stack I got earlier in this bug report was a "chip hung" stack so X.org wasn't spinning. I get the CPU spin above also using the stress tool with --hw-only parameter.