From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91527] 7870 radeon crashes after kernel msg drm:radeon_mn_invalidate_range_start
Date: Thu, 03 Sep 2015 14:43:14 +0000 [thread overview]
Message-ID: <bug-91527-502-1Oxer1FSlL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91527-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 945 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91527
JATothrim <jarmo.tiitto@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from JATothrim <jarmo.tiitto@gmail.com> ---
(In reply to Christian König from comment #6)
> Well have you tested this with the current upstream kernel? E.g. 4.1 or a
> recent rc of 4.2?
>
> That's usually the first thing you should to to figure out if newer kernels
> are already fixed.
Phew. I finally managed to compile/test newer kernel v4.2 and this bug is
fixed! :) Yay!
My tip for radeon 7870 owners: if your screen freezes and turns into a weird
rainbow mess try kernel v4.2.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2603 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:[~2015-09-03 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 3:36 [Bug 91527] 7870 radeon crashes after kernel msg drm:radeon_mn_invalidate_range_start bugzilla-daemon
2015-08-03 2:46 ` bugzilla-daemon
2015-08-03 14:06 ` bugzilla-daemon
2015-08-03 22:59 ` bugzilla-daemon
2015-08-03 23:08 ` bugzilla-daemon
2015-08-05 23:39 ` bugzilla-daemon
2015-08-13 17:41 ` bugzilla-daemon
2015-08-13 18:15 ` bugzilla-daemon
2015-09-03 14:43 ` 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-91527-502-1Oxer1FSlL@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