From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83319] New: [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730
Date: Sun, 31 Aug 2014 22:59:35 +0000 [thread overview]
Message-ID: <bug-83319-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1994 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=83319
Priority: medium
Bug ID: 83319
Assignee: dri-devel@lists.freedesktop.org
Summary: [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) -
RV730
Severity: critical
Classification: Unclassified
OS: Linux (All)
Reporter: Dieter@nuetzel-hh.de
Hardware: x86 (IA32)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 105518
--> https://bugs.freedesktop.org/attachment.cgi?id=105518&action=edit
dmesg-3.16.1-7.g90bc0f1-desktop-gsraytrace.log
GL_RENDERER = Gallium 0.4 on AMD RV730
GL_VERSION = 3.0 Mesa 10.4.0-devel (git-5598458)
GL_VENDOR = X.Org
GShader thing?
mesa-demos/glsl> ./vsraytrace
ATTENTION: default value of option vblank_mode overridden by environment.
GL_RENDERER = Gallium 0.4 on AMD RV730
47.590482 FPS (238 frames in 5.001000 seconds)
62.325210 FPS (312 frames in 5.006000 seconds)
65.407555 FPS (329 frames in 5.030000 seconds)
mesa-demos/glsl> ./fsraytrace
ATTENTION: default value of option vblank_mode overridden by environment.
GL_RENDERER = Gallium 0.4 on AMD RV730
503.000000 FPS (2515 frames in 5.000000 seconds)
626.800000 FPS (3134 frames in 5.000000 seconds)
577.600000 FPS (2888 frames in 5.000000 seconds)
mesa-demos/glsl> ./gsraytrace
ATTENTION: default value of option vblank_mode overridden by environment.
GL_RENDERER = Gallium 0.4 on AMD RV730
ESC = exit demo
left mouse + drag = rotate camera
0.044960 FPS (1 frames in 22.242000 seconds)
0.047201 FPS (1 frames in 21.186000 seconds)
ESC / CNTRL+C (several/hundred times)
=> 2 times switching between blank (black) full screen (console) and desktop
(KDE 4.13.3) before the system comes back
NO, no LLVM this time... (Michel?)
Maybe related: bug 76394
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3663 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-08-31 22:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 22:59 bugzilla-daemon [this message]
2014-08-31 23:00 ` [Bug 83319] [r600g] GPU lockup in gsraytrace (Mesa-demo-8.2.0) - RV730 bugzilla-daemon
2014-09-01 11:17 ` bugzilla-daemon
2014-09-01 11:37 ` bugzilla-daemon
2014-09-01 11:40 ` bugzilla-daemon
2014-09-01 11:40 ` bugzilla-daemon
2014-09-01 12:48 ` bugzilla-daemon
2014-10-23 18:34 ` bugzilla-daemon
2015-07-30 2:50 ` bugzilla-daemon
2015-09-02 18:23 ` bugzilla-daemon
2015-09-03 13:36 ` bugzilla-daemon
2015-11-25 1:46 ` bugzilla-daemon
2015-11-25 1:50 ` bugzilla-daemon
2015-11-25 6:34 ` bugzilla-daemon
2015-11-27 3:34 ` bugzilla-daemon
2016-01-14 10:10 ` bugzilla-daemon
2016-01-14 16:37 ` bugzilla-daemon
2016-01-14 21:58 ` bugzilla-daemon
2019-09-18 19:17 ` 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-83319-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