dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 81045] [r600] Unreal Engine 4 demo crashed kernel
Date: Wed, 09 Jul 2014 08:32:00 +0000	[thread overview]
Message-ID: <bug-81045-502-f2hKweLF61@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-81045-502@http.bugs.freedesktop.org/>


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

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

--- Comment #1 from Thomas Rohloff <v10lator@myway.de> ---
I tried the Effects Cave Demo on a Radeon HD 6950: After it loaded the sound
played but the screen was going into standby and the system wasn't even
reacting to MagSysRq keys. Would love to give logs but they where wiped with
the system reset.

OpenGL renderer string: Gallium 0.4 on AMD CAYMAN
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.0-devel
(git-3c77d2a)

Kernel 3.15.3

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

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

  reply	other threads:[~2014-07-09  8:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 12:04 [Bug 81045] New: [r600] Unreal Engine 4 demo crashed kernel bugzilla-daemon
2014-07-09  8:32 ` bugzilla-daemon [this message]
2014-07-09  8:51 ` [Bug 81045] " bugzilla-daemon
2014-07-10 15:28 ` bugzilla-daemon
2014-07-10 15:28 ` bugzilla-daemon
2014-09-24  7:52 ` bugzilla-daemon
2014-10-07 14:21 ` bugzilla-daemon
2016-01-28 23:50 ` bugzilla-daemon
2016-01-29  2:29 ` bugzilla-daemon
2016-01-29 11:06 ` bugzilla-daemon
2016-02-05  8:47 ` bugzilla-daemon
2019-11-19  8:53 ` 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-81045-502-f2hKweLF61@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;
as well as URLs for NNTP newsgroup(s).