dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 55416] [R600g] Torchlight gives GPU lockup
Date: Sat, 29 Sep 2012 09:05:46 +0000	[thread overview]
Message-ID: <bug-55416-502-vx0dJwMFTJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-55416-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1992 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=55416

--- Comment #4 from Krzysztof A. Sobiecki <sobkas@gmail.com> ---
I'm no longer able to reproduce this bug on
mesa:bb7ecb29fb6358a4c65278c2fe88936c578074cd. 

Can someone confirm this? 

I only had that bug, when I was using R600_LLVM=1(R600_LLVM=0 was safe). 
There was a small visual difference between this two settings. R600_LLVM=1
caused rendering errors on main menu(not the missing face). 


./configure --prefix=/usr --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc
--libdir=${prefix}/lib/x86_64-linux-gnu --localstatedir=/v
ar --build=x86_64-linux-gnu --with-driver=dri --enable-r600-llvm-compiler
--with-dri-drivers= --with-dri-driverdir=/usr/lib/x86_64-linux-gnu/dri
--with-dri-searchpath
=/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri --enable-glx-tls
--enable-shared-glapi --enable-texture-float --enable-xa --enable-driglx-direct
--with-eg
l-platforms=x11 drm --enable-gallium-llvm --with-gallium-drivers= nouveau r600
r300 svga swrast --enable-gles1 --enable-gles2 --enable-openvg
--enable-gallium-egl --d
isable-glu CFLAGS=-Wall -g -O2 CXXFLAGS=-Wall -g -O2

OpenGL renderer string: Gallium 0.4 on AMD JUNIPER
OpenGL version string: 3.0 Mesa 9.1-devel
OpenGL shading language version string: 1.30

Linux solis 3.6.0-rc6+ #2 SMP Wed Sep 19 11:56:23 CEST 2012 x86_64 GNU/Linux

wheezy/sid
llvm-3.1:
  Installed: 3.1-3~exp4
  Candidate: 3.1-3~exp4


  Version table:
 *** 3.1-3~exp4 0
        501 http://ftp.pl.debian.org/debian/ experimental/main amd64 Packages
        500 /var/lib/dpkg/status
     3.1-2 0
        501 http://ftp.pl.debian.org/debian/ unstable/main amd64 Packages
     3.1-1 0
        500 http://ftp.pl.debian.org/debian/ testing/main amd64 Packages

torchlight:
  Installed: 1.0.20120924-1
  Candidate: 1.0.20120924-1
  Version table:
 *** 1.0.20120924-1 0
        500 /var/lib/dpkg/status

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2884 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

  parent reply	other threads:[~2012-09-29  9:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28 12:56 [Bug 55416] New: [R600g] Torchlight gives GPU lockup bugzilla-daemon
2012-09-28 13:47 ` [Bug 55416] " bugzilla-daemon
2012-09-28 14:05 ` bugzilla-daemon
2012-09-29  2:28 ` bugzilla-daemon
2012-09-29  9:05 ` bugzilla-daemon [this message]
2012-09-29 17:50 ` bugzilla-daemon
2012-09-29 22:03 ` bugzilla-daemon
2012-09-30  8:15 ` bugzilla-daemon
2012-10-01 15:51 ` bugzilla-daemon
2012-10-03  2:42 ` bugzilla-daemon
2012-12-11  5: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-55416-502-vx0dJwMFTJ@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