From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91503] [r600g] regression: SB-related NI/Turks crash on 'gsraytrace'
Date: Fri, 28 Aug 2015 23:44:46 +0000 [thread overview]
Message-ID: <bug-91503-502-iMVbFrHgC6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91503-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 737 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91503
--- Comment #1 from Dieter Nützel <Dieter@nuetzel-hh.de> ---
Crash was FIXED by one of this:
36f1999a87258603b6720d55e6020d5d24c215c9
a830225adbb77073272961df409885cca6b861ee
a830225adbb77073272961df409885cca6b861ee
Now GPU hang on 'gsraytrace'.
See attached GALLIUM_DDEBUG dump log (gsraytrace_22964_00000000).
After reboot I found this in kernel log (dmesg):
[ 3.521069] [drm:btc_dpm_set_power_state [radeon]] *ERROR*
rv770_restrict_performance_levels_before_switch failed
R600_DEBUG=nosb
image corruption still there
see (new)
fsraytrace.png
gsraytrace.png
vsraytrace.png
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1549 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 prev parent reply other threads:[~2015-08-28 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 2:33 [Bug 91503] [r600g] regression: SB-related NI/Turks crash on 'gsraytrace' bugzilla-daemon
2015-08-28 23:44 ` bugzilla-daemon [this message]
2015-08-28 23:46 ` bugzilla-daemon
2015-08-28 23:48 ` bugzilla-daemon
2015-08-28 23:49 ` bugzilla-daemon
2015-08-28 23:49 ` bugzilla-daemon
2015-09-02 13:45 ` 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-91503-502-iMVbFrHgC6@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