All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 113341] GPU Lockup on AMD Kaveri
Date: Mon, 07 Mar 2016 14:11:48 +0000	[thread overview]
Message-ID: <bug-113341-2300-lbbNaHEYfm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-113341-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=113341

--- Comment #7 from Bernd Steinhauser <linux@bernd-steinhauser.de> ---
I tried to build LLVM/clang scm, but it failed (have to check why and if I can
get around that).

I've had several freezes over the last few weeks (most of them when I bisected
that other bug mentioned above (so could be unrelated), but only a few after
staying on 4.4.x), but this one was the only one I could relate to a specific
event, starting an application (thunderbird here).
The other ones seemed to happen out of nowhere, so it could be that it was just
coincidence that it happened when I started that application.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-03-07 14:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 20:18 [Bug 113341] New: GPU Lockup on AMD Kaveri bugzilla-daemon
2016-02-29  1:25 ` [Bug 113341] " bugzilla-daemon
2016-02-29  5:33 ` bugzilla-daemon
2016-02-29  5:37 ` bugzilla-daemon
2016-03-05 11:47 ` bugzilla-daemon
2016-03-05 11:48 ` bugzilla-daemon
2016-03-07  9:27 ` bugzilla-daemon
2016-03-07 14:11 ` bugzilla-daemon [this message]
2016-03-08  1:50 ` bugzilla-daemon
2016-03-11 18:14 ` bugzilla-daemon
2016-03-30 17:46 ` bugzilla-daemon
2016-06-03  5:22 ` 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-113341-2300-lbbNaHEYfm@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.