From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97801] [amdgpu SI] "drm/amd/amdgpu: Tidy up SI SMC code" prevents amdgpu loading with dpm=1
Date: Tue, 13 Sep 2016 22:02:40 +0000 [thread overview]
Message-ID: <bug-97801-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1251 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97801
Bug ID: 97801
Summary: [amdgpu SI] "drm/amd/amdgpu: Tidy up SI SMC code"
prevents amdgpu loading with dpm=1
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: arek.rusi@gmail.com
Created attachment 126501
--> https://bugs.freedesktop.org/attachment.cgi?id=126501&action=edit
dmesg log
This is quasi-bisected while I need apply patch newer than first bad commit.
So keep in mind that i always apply: drm/amd/amdgpu: Remove double lock from
gfx v6
see: https://bugs.freedesktop.org/show_bug.cgi?id=97594
kernel: drm-next-4.9-wip
boot with dpm=0 works,
dmesg is attached
"first" bad commit: drm/amd/amdgpu: Tidy up SI SMC code
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-4.9-wip&id=c4f7beed7017652ca39fb475a1f423084944975e
Due i cannot simple revert i don't know if it's only problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3075 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
next reply other threads:[~2016-09-13 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 22:02 bugzilla-daemon [this message]
2016-09-14 13:48 ` [Bug 97801] [amdgpu SI] "drm/amd/amdgpu: Tidy up SI SMC code" prevents amdgpu loading with dpm=1 bugzilla-daemon
2016-09-14 14:08 ` 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-97801-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