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 106466] GPU recovery fails on Vega 64
Date: Thu, 10 May 2018 20:24:34 +0000	[thread overview]
Message-ID: <bug-106466-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 106466
           Summary: GPU recovery fails on Vega 64
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: bas@basnieuwenhuizen.nl

Created attachment 139474
  --> https://bugs.freedesktop.org/attachment.cgi?id=139474&action=edit
dmesg

Reproduce:

1) boot
2) Start X
3) Stop X
4) cat /sys/kernel/debug/dri/2/amdgpu_gpu_recovery
5) Wait till finished
6) Start X
7) Notice slowness
8) Stop X

The dmesg says that the reset failed, but the screen comes back with some
artifacts. drawing in X is very slow event though pp_dpm_sclk seems to be
indicating reasonable speeds.

I use amd-staging-drm-next as of today with as last commit

commit 905aa01b240f9216b6dbba3226bf10b2d96eebb7 (origin/amd-staging-drm-next)
Author: Colin Ian King <colin.king@canonical.com>
Date:   Wed May 2 15:43:16 2018 +0100

    drm/amd/display: clean up assignment of amdgpu_crtc

    The declaration of pointer amdgpu_crtc has a redundant assignment to
    amdgpu_crtc. Clean this up by removing it.

    Detected by CoverityScan, CID#1460299 ("Evaluation order violation")

    Reviewed-by: Harry Wentland <harry.wentland@amd.com>
    Signed-off-by: Colin Ian King <colin.king@canonical.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>


plus a patch of my own adding some more dev_info messages to the reset process.

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

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

             reply	other threads:[~2018-05-10 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10 20:24 bugzilla-daemon [this message]
2019-11-19  8:38 ` [Bug 106466] GPU recovery fails on Vega 64 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-106466-502@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