From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107001] hard system freeze with mesa 18.1.x on AMD RX 580
Date: Tue, 11 Sep 2018 13:55:55 +0000 [thread overview]
Message-ID: <bug-107001-502-GLN6yOvuxT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107001-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 612 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107001
--- Comment #3 from claude@mathr.co.uk ---
So, I got some freezes with Linux 4.18.5 and Mesa 18.0.5 (the version of Mesa
that I assumed was bug free), and so far (24 hours uptime) no freezes with
Linux 4.18.7 and Mesa 18.1.7-1. The Linux change log mentions some fixes for
various deadlocks, perhaps I was just unlucky that some Mesa versions were more
likely than others to trigger these Linux bugs on my system. I'll leave this
open for another week or so of testing.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1393 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-11 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-107001-502@http.bugs.freedesktop.org/>
2018-06-22 14:40 ` [Bug 107001] hard system freeze with mesa 18.1.1 and 18.1.2 on AMD RX 580 bugzilla-daemon
2018-07-27 13:09 ` bugzilla-daemon
2018-08-08 22:25 ` bugzilla-daemon
2018-08-13 11:31 ` [Bug 107001] hard system freeze with mesa 18.1.x " bugzilla-daemon
2018-09-11 13:55 ` bugzilla-daemon [this message]
2018-09-19 16:37 ` 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-107001-502-GLN6yOvuxT@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).