From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 104854] smu7_populate_single_firmware_entry fails to load powerplay firmware. Date: Sat, 23 Jun 2018 21:19:51 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0826002656==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 6037E6E007 for ; Sat, 23 Jun 2018 21:19:51 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0826002656== Content-Type: multipart/alternative; boundary="15297887910.Cae4e66D.27256" Content-Transfer-Encoding: 7bit --15297887910.Cae4e66D.27256 Date: Sat, 23 Jun 2018 21:19:51 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D104854 --- Comment #10 from Jos=C3=A9 Pekkarinen --- Created attachment 140293 --> https://bugs.freedesktop.org/attachment.cgi?id=3D140293&action=3Dedit dri config to work it around. I spent some more time toying this around and I found that, building the drm inside the kernel like in this extract of the config, and provided that you still blacklist the amdgpu module: BOOT_IMAGE=3D/kernel-genkernel-x86_64-4.17.2+ root=3D/dev/mapper/bee-root r= o dolvm crypt_root=3D/dev/sda3 real_root=3D/dev/bee/root resume=3D/dev/bee/swap iom= mu=3Dpt intel_iommu=3Don kvm-intel.nested=3D1 apparmor=3D1 zswap.enabled=3D1 securi= ty=3Dapparmor crashkernel=3D256M modprobe.blacklist=3Damdgpu The kernel booting will ignore my evil purposes: # dmesg|grep amdgpu [ 0.000000] Command line: BOOT_IMAGE=3D/kernel-genkernel-x86_64-4.17.2+ root=3D/dev/mapper/bee-root ro dolvm crypt_root=3D/dev/sda3 real_root=3D/de= v/bee/root resume=3D/dev/bee/swap iommu=3Dpt intel_iommu=3Don kvm-intel.nested=3D1 app= armor=3D1 zswap.enabled=3D1 security=3Dapparmor crashkernel=3D256M modprobe.blacklist= =3Damdgpu [ 0.000000] Kernel command line: BOOT_IMAGE=3D/kernel-genkernel-x86_64-4= .17.2+ root=3D/dev/mapper/bee-root ro dolvm crypt_root=3D/dev/sda3 real_root=3D/de= v/bee/root resume=3D/dev/bee/swap iommu=3Dpt intel_iommu=3Don kvm-intel.nested=3D1 app= armor=3D1 zswap.enabled=3D1 security=3Dapparmor crashkernel=3D256M modprobe.blacklist= =3Damdgpu [ 0.755913] [drm] amdgpu kernel modesetting enabled. [ 0.756304] amdgpu 0000:01:00.0: enabling device (0400 -> 0403) [ 0.772792] amdgpu 0000:01:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) [ 0.773338] amdgpu 0000:01:00.0: GTT: 256M 0x0000000000000000 - 0x000000000FFFFFFF [ 0.777463] [drm] amdgpu: 2048M of VRAM memory ready [ 0.778060] [drm] amdgpu: 3072M of GTT memory ready. [ 0.798170] amdgpu: [powerplay] can't get the mac of 5 [ 0.809732] [drm] Initialized amdgpu 3.25.0 20150101 for 0000:01:00.0 on minor 0 [ 6.112759] amdgpu: [powerplay] VI should always have 2 performance leve= ls [ 6.144432] amdgpu 0000:01:00.0: GPU pci config reset [ 22.024297] amdgpu: [powerplay] can't get the mac of 5 resulting in a properly booted machine that is able to use the amd gpu: $ DRI_PRIME=3D1 glxinfo |grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) R7 M360 (ICELAND, DRM 3.25.0, 4.17.= 2+, LLVM 6.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.1.2 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.1.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.1.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 OpenGL ES profile extensions: Technically it seems to be a weird workaround and I don't know if that may light your bulbs in any way, but hey, I hope it helps. Jos=C3=A9. --=20 You are receiving this mail because: You are the assignee for the bug.= --15297887910.Cae4e66D.27256 Date: Sat, 23 Jun 2018 21:19:51 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 10 on bug 10485= 4 from Jos=C3=A9 Pekkarinen 
Created attachment=
 140293 [details]
dri config to work it around.

I spent some more time toying this around and I found that, building
the drm inside the kernel like in this extract of the config, and
provided that you still blacklist the amdgpu module:

BOOT_IMAGE=3D/kernel-genkernel-x86_64-4.17.2+ root=3D/dev/mapper/bee-root r=
o dolvm
crypt_root=3D/dev/sda3 real_root=3D/dev/bee/root resume=3D/dev/bee/swap iom=
mu=3Dpt
intel_iommu=3Don kvm-intel.nested=3D1 apparmor=3D1 zswap.enabled=3D1 securi=
ty=3Dapparmor
crashkernel=3D256M modprobe.blacklist=3Damdgpu

The kernel booting will ignore my evil purposes:

# dmesg|grep amdgpu
[    0.000000] Command line: BOOT_IMAGE=3D/kernel-genkernel-x86_64-4.17.2+
root=3D/dev/mapper/bee-root ro dolvm crypt_root=3D/dev/sda3 real_root=3D/de=
v/bee/root
resume=3D/dev/bee/swap iommu=3Dpt intel_iommu=3Don kvm-intel.nested=3D1 app=
armor=3D1
zswap.enabled=3D1 security=3Dapparmor crashkernel=3D256M modprobe.blacklist=
=3Damdgpu
[    0.000000] Kernel command line: BOOT_IMAGE=3D/kernel-genkernel-x86_64-4=
.17.2+
root=3D/dev/mapper/bee-root ro dolvm crypt_root=3D/dev/sda3 real_root=3D/de=
v/bee/root
resume=3D/dev/bee/swap iommu=3Dpt intel_iommu=3Don kvm-intel.nested=3D1 app=
armor=3D1
zswap.enabled=3D1 security=3Dapparmor crashkernel=3D256M modprobe.blacklist=
=3Damdgpu
[    0.755913] [drm] amdgpu kernel modesetting enabled.
[    0.756304] amdgpu 0000:01:00.0: enabling device (0400 -> 0403)
[    0.772792] amdgpu 0000:01:00.0: VRAM: 2048M 0x000000F400000000 -
0x000000F47FFFFFFF (2048M used)
[    0.773338] amdgpu 0000:01:00.0: GTT: 256M 0x0000000000000000 -
0x000000000FFFFFFF
[    0.777463] [drm] amdgpu: 2048M of VRAM memory ready
[    0.778060] [drm] amdgpu: 3072M of GTT memory ready.
[    0.798170] amdgpu: [powerplay] can't get the mac of 5
[    0.809732] [drm] Initialized amdgpu 3.25.0 20150101 for 0000:01:00.0 on
minor 0
[    6.112759] amdgpu: [powerplay] VI should always have 2 performance leve=
ls
[    6.144432] amdgpu 0000:01:00.0: GPU pci config reset
[   22.024297] amdgpu: [powerplay] can't get the mac of 5

resulting in a properly booted machine that is able to use the amd gpu:

$ DRI_PRIME=3D1 glxinfo |grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: AMD Radeon (TM) R7 M360 (ICELAND, DRM 3.25.0, 4.17.=
2+,
LLVM 6.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.1.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 18.1.2
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.1.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

Technically it seems to be a weird workaround and I don't know if that may
light your bulbs in any way, but hey, I hope it helps.

Jos=C3=A9.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15297887910.Cae4e66D.27256-- --===============0826002656== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0826002656==--