All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91278] Tonga GPU lock/reset fail  with Unigine Valley
Date: Sun, 15 Nov 2015 15:11:54 +0000	[thread overview]
Message-ID: <bug-91278-502-VHqvSyY1Ff@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91278-502@http.bugs.freedesktop.org/>


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

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

--- Comment #47 from Andy Furniss <adf.lists@gmail.com> ---
Seems like you are using an old kernel - though what I call old may be current
for what's released.

The hanging for me stopped with 4.4, but 4.3 is release.

If you are using 4.3 maybe booting with the option -

amdgpu.enable_scheduler=1

will help.

If you are used to compiling your own kernels then using one from -

http://cgit.freedesktop.org/~agd5f/linux/

like drm-next-4.4 should be stable.

Or if you want to test/use the new powerplay try amdgpu-powerplay

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

[-- Attachment #1.2: Type: text/html, Size: 1469 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:[~2015-11-15 15:11 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 10:10 [Bug 91278] Tonga GPU lock/reset fail with Unigine Valley bugzilla-daemon
2015-07-09 10:11 ` bugzilla-daemon
2015-07-09 10:12 ` bugzilla-daemon
2015-07-17  9:30 ` bugzilla-daemon
2015-07-20 23:25 ` bugzilla-daemon
2015-08-17 19:25 ` bugzilla-daemon
2015-08-18  6:41 ` bugzilla-daemon
2015-08-28 10:45 ` bugzilla-daemon
2015-09-24 15:43 ` bugzilla-daemon
2015-09-25 17:30 ` bugzilla-daemon
2015-09-25 21:52 ` bugzilla-daemon
2015-09-28  9:08 ` bugzilla-daemon
2015-09-28 15:35 ` bugzilla-daemon
2015-09-28 21:27 ` bugzilla-daemon
2015-09-29 10:32 ` bugzilla-daemon
2015-09-29 15:47 ` bugzilla-daemon
2015-09-29 20:33 ` bugzilla-daemon
2015-09-30  9:38 ` bugzilla-daemon
2015-09-30 10:08 ` bugzilla-daemon
2015-09-30 19:59 ` bugzilla-daemon
2015-09-30 20:42 ` bugzilla-daemon
2015-09-30 21:15 ` bugzilla-daemon
2015-09-30 21:19 ` bugzilla-daemon
2015-09-30 21:51 ` bugzilla-daemon
2015-09-30 21:55 ` bugzilla-daemon
2015-10-04 20:34 ` bugzilla-daemon
2015-10-05  6:23 ` bugzilla-daemon
2015-10-05  8:54 ` bugzilla-daemon
2015-10-05 22:51 ` bugzilla-daemon
2015-10-06  1:25 ` bugzilla-daemon
2015-10-09 16:08 ` bugzilla-daemon
2015-10-10  7:49 ` bugzilla-daemon
2015-10-10  8:59 ` bugzilla-daemon
2015-10-10 10:33 ` bugzilla-daemon
2015-10-11 16:14 ` bugzilla-daemon
2015-10-11 16:26 ` bugzilla-daemon
2015-10-11 19:37 ` bugzilla-daemon
2015-10-11 20:50 ` bugzilla-daemon
2015-10-11 21:44 ` bugzilla-daemon
2015-10-12 11:58 ` bugzilla-daemon
2015-10-13 18:24 ` bugzilla-daemon
2015-10-15  9:45 ` bugzilla-daemon
2015-10-15 13:28 ` bugzilla-daemon
2015-10-15 13:51 ` bugzilla-daemon
2015-10-15 15:51 ` bugzilla-daemon
2015-11-15 11:24 ` bugzilla-daemon
2015-11-15 11:27 ` bugzilla-daemon
2015-11-15 15:11 ` bugzilla-daemon [this message]
2015-12-28 14:24 ` bugzilla-daemon
2016-09-15 17:04 ` bugzilla-daemon
2016-09-16  1:45 ` 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-91278-502-VHqvSyY1Ff@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 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.