From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86357] [RadeonSI] GPU lockup with mesa 10.3.3 / kernel 3.17.2
Date: Sun, 02 Aug 2015 11:18:06 +0000 [thread overview]
Message-ID: <bug-86357-502-JslxI6nryD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-86357-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 797 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=86357
--- Comment #4 from Marek Olšák <maraeo@gmail.com> ---
(In reply to madcatx from comment #3)
> I haven't tried any of the fixes suggested there yet. I did however updated
> to 3.17.3 and the box survived yesteday without crashing. Is there anything
> in 3.17.3 that could have fixed or at least partially mitigagted the
> problem? Should I stick with 3.17.2 until you have save more definitive clue
> as to what is causing this?
>
> It usually takes a few hours for the crash to happen so I might just have
> been lucky though. I'll keep an eye on this report my findings in the "BUG
> 85647" thread.
>
> Thanks...
Does the GPU still lock up?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1700 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-02 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 22:42 [Bug 86357] [RadeonSI] GPU lockup with mesa 10.3.3 / kernel 3.17.2 bugzilla-daemon
2014-11-17 21:16 ` bugzilla-daemon
2014-11-18 7:15 ` bugzilla-daemon
2014-11-18 12:15 ` bugzilla-daemon
2015-08-02 11:18 ` bugzilla-daemon [this message]
2015-08-02 12:17 ` bugzilla-daemon
2015-08-02 12:57 ` 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-86357-502-JslxI6nryD@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