dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93911] Radeon rv635 with KMS and no dpm, intermittent/random GPU lockup
Date: Tue, 02 Feb 2016 04:23:27 +0000	[thread overview]
Message-ID: <bug-93911-502-DQObbxQff0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93911-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 580 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=93911

--- Comment #8 from David Breese <dabreese00@gmail.com> ---
Thank you very much for pointing me to that, it looks right.  I didn't manage
to find it when searching the bug tracker.

I've now upgraded to kernel 4.4 which contains the relevant commit.  No more
crashes so far after 3 days of heavy use -- normally I would have expected a
crash sometime.

I'll post back if I do see the crash again, but provisionally I'll say this did
the trick.

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1436 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

  parent reply	other threads:[~2016-02-02  4:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 21:51 [Bug 93911] Radeon rv635 with KMS and no dpm, intermittent/random GPU lockup bugzilla-daemon
2016-01-28 21:54 ` bugzilla-daemon
2016-01-28 21:54 ` bugzilla-daemon
2016-01-28 21:55 ` bugzilla-daemon
2016-01-28 21:55 ` bugzilla-daemon
2016-01-28 21:56 ` bugzilla-daemon
2016-01-28 22:15 ` bugzilla-daemon
2016-01-29  2:42 ` bugzilla-daemon
2016-02-02  4:23 ` bugzilla-daemon [this message]
2016-02-25 22:35 ` bugzilla-daemon
2016-03-22 15:54 ` 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-93911-502-DQObbxQff0@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