From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 50657] New: [Evergreen,GIT,Tiling?] Occasional invalid command stream and subsequent performance increase
Date: Sun, 03 Jun 2012 22:46:47 +0000 [thread overview]
Message-ID: <bug-50657-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=50657
Bug #: 50657
Summary: [Evergreen,GIT,Tiling?] Occasional invalid command
stream and subsequent performance increase
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: thomas.lindroth@gmail.com
Starting Warcraft 3 in Wine sometimes failes because of invalid command stream.
It happens in about 10% of all startup attempts.
After a failed startup Warcraft normally starts fine again and with improved
framerate. Normal framerate after clean reboot is 110fps and directly after
error it jumps to 150fps. Other applications also get improved framerate.
Street fighter 4 benchmark in wine goes from 50 to 61 and glxgears from 4,000
to 10,000. The increased performance lasts for about 2 min and drops back to
normal after that. It will jump again next time the error is triggered. No
rendering errors can be seen. No other applications besides war3 can trigger
the failed command stream.
Dmesg reports:
radeon 0000:01:00.0: evergreen_surface_value_conv_check:325 depth invalid array
mode 15
radeon 0000:01:00.0: evergreen_cs_track_validate_depth:645 depth invalid
(0xffffffff 0x00000000 0xffffffff)
radeon 0000:01:00.0: evergreen_packet3_check:2015 invalid cmd stream
Same message every time. No other error reported in dmesg or Xorg.log
Hardware is HD 6770. Using DDX,Mesa,libdrm from latest git. Kernel 3.4.0.
"ColorTiling" "true"
"ColorTiling2D" "true"
"SwapbuffersWait" "false"
"EnablePageFlip" "true"
radeon.pcie_gen2=1
War3 is invoked as "vblank_mode=0 WINEDEBUG=fps wine war3.exe -opengl" in a
wine virtual desktop.
The error might be build related. Building mesa with --enable-debug triggers
the error more often it seems. Pipeing the output of wine to file also triggers
the error.
Mesa built from gentoo ebuild
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu
--mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share
--sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking
--enable-dri --enable-glx --enable-texture-float --disable-debug --enable-egl
--disable-gbm --disable-gles1 --disable-gles2 --enable-glx-tls --disable-osmesa
--enable-asm --enable-shared-glapi --disable-xa --disable-xorg
--with-dri-drivers= --with-gallium-drivers=,swrast,r600
--with-egl-platforms=x11 --enable-gallium-egl --disable-d3d1x
--disable-gallium-g3dvl --enable-gallium-llvm --disable-openvg
--disable-r600-llvm-compiler --disable-vdpau --disable-xvmc
--
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:[~2012-06-03 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 22:46 bugzilla-daemon [this message]
2012-06-04 11:00 ` [Bug 50657] [Evergreen,GIT,Tiling?] Occasional invalid command stream and subsequent performance increase bugzilla-daemon
2012-06-04 11:03 ` bugzilla-daemon
2012-06-09 8:34 ` bugzilla-daemon
2012-06-09 14:36 ` bugzilla-daemon
2012-06-09 21:01 ` bugzilla-daemon
2012-06-13 13:56 ` bugzilla-daemon
2019-09-18 19:00 ` 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-50657-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.