dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97123] [AMDGPU][CIK] Suspend to disk deadlocks system on resume always (Linus master + drm-next-4.9-wip)
Date: Wed, 24 Aug 2016 04:25:52 +0000	[thread overview]
Message-ID: <bug-97123-502-53DNoa6Arl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97123-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Shawn Starr <shawn.starr@rogers.com> ---
With latest patches: 
[PATCH 3/3] drm/amdgpu: reset the asic when hibernating v2

I am not noticing deadlock on resume, still continue to test.

When hibernating the first time, no corruption occurs on freeze state of
display, subsequent hibernations show same corruption pattern on freeze.

When resuming no such corruption shows once the GPU finishes init and we resume
successfully.

-- 
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: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-08-24  4:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  3:20 [Bug 97123] [AMDGPU][CIK] Suspend to disk deadlocks system on resume always (Linus master + drm-next-4.9-wip) bugzilla-daemon
2016-08-24  4:24 ` bugzilla-daemon
2016-08-24  4:25 ` bugzilla-daemon [this message]
2016-08-31  3:54 ` bugzilla-daemon
2016-09-04  6:07 ` bugzilla-daemon
2016-09-09 18:44 ` bugzilla-daemon
2016-10-31  5:51 ` 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-97123-502-53DNoa6Arl@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).