From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 112234] [REGRESSION] navi10: writing to pp_table fails (5.4-rc6 = working)
Date: Fri, 08 Nov 2019 16:47:01 +0000 [thread overview]
Message-ID: <bug-112234-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1265 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=112234
Bug ID: 112234
Summary: [REGRESSION] navi10: writing to pp_table fails
(5.4-rc6 = working)
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: not set
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: mcoffin13@gmail.com
Created attachment 145913
--> https://bugs.freedesktop.org/attachment.cgi?id=145913&action=edit
dmesg log (journalctl -k) for the failure.
On 5.4-rc6, with navi10, writing to the sysfs pp_table works, with the SMU
resetting successfully.
On amd-staging-drm-next (270209307880ec946cfe9b98a6a58d285dbc5a2e), this fails.
I can bisect, but unfortunately I'm not too sure on where to start, since the
amd-staging-drm-next branch is currently rebased off of an older version
(5.3-rcX I think?). Tips on where to start would be helpful and appreciated,
but my guess that this would be introduced in the big refactor to remove the
swSMU code layer.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2734 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-11-08 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 16:47 bugzilla-daemon [this message]
2019-11-08 20:51 ` [Bug 112234] [REGRESSION] navi10: writing to pp_table fails (5.4-rc6 = working) bugzilla-daemon
2019-11-11 23:27 ` 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-112234-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 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.