Bug 34643 - ut2004/doom3 looping in submenu on r300g/PageFlip
Summary: ut2004/doom3 looping in submenu on r300g/PageFlip
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r300 (show other bugs)
Version: git
Hardware: Other Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-23 17:10 UTC by Chistopher Krakowiak
Modified: 2016-03-19 18:50 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
gdb/ut2k4 output and backraces. (63.88 KB, text/plain)
2011-02-23 17:10 UTC, Chistopher Krakowiak
Details
kernel dmesg from running ut2004(and doom3, but tail is from UT for sure) (61.16 KB, text/plain)
2011-02-23 17:12 UTC, Chistopher Krakowiak
Details
xorg.log. nothing surprising there (91.01 KB, text/plain)
2011-02-23 17:13 UTC, Chistopher Krakowiak
Details
kernel dmesg from running Doom3(and ut2k4, but tail is from Doom3 for sure) (61.17 KB, text/plain)
2011-02-23 17:15 UTC, Chistopher Krakowiak
Details

Description Chistopher Krakowiak 2011-02-23 17:10:39 UTC
Created attachment 43736 [details]
gdb/ut2k4 output and backraces.

ut2004(32/64bit) and doom3(32bit) are looping everytime in submenu on r300g/PageFlip. I believe that bug occured during last two weeks, but bisecting would be hard, because I was bisecting for:
https://bugs.freedesktop.org/show_bug.cgi?id=34418

And everytime supertuxkart wasnt working, ut2k4 also and vice versa, altough bugs were definitely different. Now previous bug is fixed(which affected only 64bit apps), but ut2004/doom3 got very similar behaviour(like looped video tape or something, moving forward and back), similar spam in console, but a bit different at output.
Disabling PageFLip fixes this problem definitely, but I was happpy pflip user from a long time.
Kernel is fresh D-R-T, DDX/DRM/Mesa from master.


--- UT2004 dmesg ---
[...]
[drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xe
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
[drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x1f
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
[drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xe
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
[drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x1f
[drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
[...]
--- EOF UT2004 dmesg ---


--- UT2004 gdb output/backtrace ---
[...]
[Thread 0x7fffe50cd700 (LWP 5934) exited]
[New Thread 0x7fffe50cd700 (LWP 5935)]
[Thread 0x7fffe50cd700 (LWP 5935) exited]
[New Thread 0x7fffe50cd700 (LWP 5936)]
[...]
[Thread 0x7fffe50cd700 (LWP 6540) exited]
[New Thread 0x7fffe50cd700 (LWP 6541)]
radeon: The kernel rejected CS, see dmesg for more information.
[Thread 0x7fffe50cd700 (LWP 6541) exited]
[...]
Program received signal SIGINT, Interrupt.
0x00007ffff6e0a1f3 in poll () from /lib64/libc.so.6
(gdb) bt
#0  0x00007ffff6e0a1f3 in poll () from /lib64/libc.so.6
#1  0x00007ffff65eac6a in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007ffff65ec2ff in xcb_wait_for_reply () from /usr/lib64/libxcb.so.1
#3  0x00007ffff684392d in _XReply () from /usr/lib64/libX11.so.6
#4  0x00007fffe6c1748c in DRI2GetBuffersWithFormat () from /opt/xorg/lib64/libGL.so.1
#5  0x00007fffe6c14bf9 in dri2GetBuffersWithFormat () from /opt/xorg/lib64/libGL.so.1
#6  0x00007fffe56de4d8 in dri2_allocate_textures () from /opt/xorg/lib64/dri/gallium/r300_dri.so
#7  0x00007fffe56dfb77 in dri_st_framebuffer_validate () from /opt/xorg/lib64/dri/gallium/r300_dri.so
#8  0x00007fffe573f132 in st_framebuffer_validate () from /opt/xorg/lib64/dri/gallium/r300_dri.so
#9  0x00007fffe5740916 in st_manager_validate_framebuffers () from /opt/xorg/lib64/dri/gallium/r300_dri.so
#10 0x00007fffe58e3c1e in st_validate_state () from /opt/xorg/lib64/dri/gallium/r300_dri.so
#11 0x00007fffe58ebb3a in st_Clear () from /opt/xorg/lib64/dri/gallium/r300_dri.so
#12 0x0000000000d291d9 in FOpenGLRenderInterface::Clear(int, FColor, int, float, int, unsigned int) ()
#13 0x000000000069d234 in UGameEngine::Draw(UViewport*, int, unsigned char*, int*) ()
#14 0x0000000000d1d106 in USDLViewport::Repaint(int) ()
#15 0x0000000000d1ab09 in USDLClient::Tick() ()
#16 0x00000000006a0f54 in UGameEngine::Tick(float) ()
#17 0x000000000053d2a3 in CMainLoop::RunLoop() ()
#18 0x000000000053344f in ?? ()
#19 0x000000000052f1a0 in main ()
--- UT2004 gdb output/backtrace ---


--- Doom3 output ---
[...]
radeon: The kernel rejected CS, see dmesg for more information.
radeon: The kernel rejected CS, see dmesg for more information
[...]
--- EOF Doom3 output ---

TIP:
For full logs, look into attachements (but nothing special in xorg.log)
Comment 1 Chistopher Krakowiak 2011-02-23 17:12:33 UTC
Created attachment 43737 [details]
kernel dmesg from running ut2004(and doom3, but tail is from UT for sure)
Comment 2 Chistopher Krakowiak 2011-02-23 17:13:57 UTC
Created attachment 43738 [details]
xorg.log. nothing surprising there
Comment 3 Chistopher Krakowiak 2011-02-23 17:15:40 UTC
Created attachment 43739 [details]
kernel dmesg from running Doom3(and ut2k4, but tail is from Doom3 for sure)
Comment 4 Chistopher Krakowiak 2011-04-05 14:42:57 UTC
Not sure when it was fixed, but no problem at d-r-t 2.6.38rc8 or drm-fixes 2.6.39rc1


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.