From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105244] NULL dereference during startup of Cape Verde with AMDGPU and GPU passthrough
Date: Wed, 28 Feb 2018 22:49:54 +0000 [thread overview]
Message-ID: <bug-105244-502-EvOPnZt0TZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105244-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 612 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105244
--- Comment #3 from Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl> ---
Sorry for the delay, I can confirm this fixes the NULL issue.
pp_dpm_mclk / pp_dpm_sclk look empty to me, not sure though if that is just
because they are not hooked up yet for SI, but since I don't need DPM and this
now boots AMDGPU with the default config to an usable state I'd consider this
fixed.
(leaving open because I don't know if the patch landed yet, feel free to close
when you push it)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1460 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 prev parent reply other threads:[~2018-02-28 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 22:01 [Bug 105244] NULL dereference during startup of Cape Verde with AMDGPU and GPU passthrough bugzilla-daemon
2018-02-26 16:11 ` bugzilla-daemon
2018-02-27 14:13 ` bugzilla-daemon
2018-02-28 22:49 ` bugzilla-daemon [this message]
2018-03-01 2:03 ` bugzilla-daemon
2018-03-04 12:12 ` bugzilla-daemon
2018-03-05 13:28 ` bugzilla-daemon
2018-06-20 22:42 ` 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-105244-502-EvOPnZt0TZ@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