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] New: [r600] Unreal Engine 4 demo crashed kernel
Date: Tue, 08 Jul 2014 12:04:35 +0000	[thread overview]
Message-ID: <bug-81045-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 81045
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [r600] Unreal Engine 4 demo crashed kernel
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: nikoli@gmx.us
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 102434
  --> https://bugs.freedesktop.org/attachment.cgi?id=102434&action=edit
kernel messages

Tried running Unreal Engine 4 demos from
https://wiki.unrealengine.com/Linux_Demos
'Mobile Temple Demo' started, worked bad (image was too dark, possible to see
almost nothing), but did not crash anything.
Next tried 'Effects Cave Demo': in a few seconds after first start of demo X
server became not responding (not even possible to switch with ctrl+alt+f1), it
was flickering between grey fill and normal desktop (seems kernel tried to
restart GPU), then system became fully unresponsive: ssh did not work, power
button did not send system to suspend. Attached kernel messages saved by
syslog.

I never had GPU related stability problems with 3.12.x-3.14.x kernels before:
several opengl 3d games worked fine, opengl based mpv video output worked fine,
glxgears and stellarium worked fine too.

Did unreal engine try to use some non implemented or unstable features? Why
kernel allowed to crash itself instead of killing userspace app?

Hardware: Radeon HD 6770
Software: Gentoo hardened amd64 stable, kernel-3.14.10, libdrm-2.4.54,
mesa-10.2.2, llvm-3.3, xf86-video-ati-7.3.0, xorg-server-1.15.0

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

[-- Attachment #1.2: Type: text/html, Size: 3256 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-08 12:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 12:04 bugzilla-daemon [this message]
2014-07-09  8:32 ` [Bug 81045] [r600] Unreal Engine 4 demo crashed kernel bugzilla-daemon
2014-07-09  8:51 ` 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@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).