From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34643] New: ut2004/doom3 looping in submenu on r300g/PageFlip
Date: Wed, 23 Feb 2011 17:10:40 -0800 (PST) [thread overview]
Message-ID: <bug-34643-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=34643
Summary: ut2004/doom3 looping in submenu on r300g/PageFlip
Product: Mesa
Version: git
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: krzysztof.krakowiak@gmail.com
Created an attachment (id=43736)
--> (https://bugs.freedesktop.org/attachment.cgi?id=43736)
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)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-02-24 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 1:10 bugzilla-daemon [this message]
2011-02-24 1:12 ` [Bug 34643] ut2004/doom3 looping in submenu on r300g/PageFlip bugzilla-daemon
2011-02-24 1:13 ` bugzilla-daemon
2011-02-24 1:15 ` bugzilla-daemon
2011-04-05 21:42 ` bugzilla-daemon
2016-03-19 18:50 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-34643-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox