From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82019] Unreal Engine Effects Cave demo lockup HD 7970M
Date: Thu, 14 Aug 2014 18:19:21 +0000 [thread overview]
Message-ID: <bug-82019-502-QXn7ohiZUA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82019-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 806 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=82019
Christoph Haag <haagch@frickel.club> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |MOVED
--- Comment #5 from Christoph Haag <haagch@frickel.club> ---
(In reply to comment #4)
Good news: It has nothing to do with nine.
I think it's caused by the GALLIUM_HUD and so I opened bug 82628.
On second thought I could have seen that the hang is actually the same I had in
the first place and probably this bug would have been perfectly fine to post in
too, but now it's too late.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2464 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
prev parent reply other threads:[~2014-08-14 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 17:18 [Bug 82019] New: Unreal Engine Effects Cave demo lockup HD 7970M bugzilla-daemon
2014-08-01 17:37 ` [Bug 82019] " bugzilla-daemon
2014-08-01 17:49 ` bugzilla-daemon
2014-08-13 10:19 ` bugzilla-daemon
2014-08-14 17:23 ` bugzilla-daemon
2014-08-14 18:19 ` bugzilla-daemon [this message]
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-82019-502-QXn7ohiZUA@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