dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 100109] Graphics Lockup if monitor disconnected and then set into standby
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=100109 Bug ID: 100109 Summary: Graphics Lockup if monitor disconnected and then set into standby Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: kierangrant(a)linux.com Created attachment 130119 --> https://bugs.freedesktop.org/attachment.cgi?id=130119&action=edit Various log files I got a Kernel Oops from with AMDGPU-PRO for Ubuntu 16.04.2 LTS x86-64 version 16.60 after unplugging and plugging in my HDMI display... Computer was left on overnight to do some long IO operation... before I left it, I turned monitor off... at the time my MATE display settings was to put monitor to sleep after 30 minutes... so I guess it tried that after 30 minutes... Next day... I got no graphics response... after trying various F-n combos... I eventually tried some SysRq keys to force text console... but stock Ubuntu SysRq limit was in effect *doh*... That is when as a last resort thought to unplug and re-plug in monitor... in hopes that would magically do something... it did something alright... I got Kernel OOPS at that moment... it was early morning for me :| Attached is a snippet of my syslog plus various ls* outputs... I have a MSI Radeon RX480 8GB I will see if I can manually reproduce the bug to get a Xorg.log file... I forgot that one and old one is now gone :/ -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 97548] DPM states not working
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97548 Bug ID: 97548 Summary: DPM states not working Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: jarkko_korpi(a)hotmail.com I am using 4.6-staging because I need the audio driver it provides. I have been trying to lower the voltages of the card by bios editing and there seems to be no issues with windows, but I dont seem to get higher DPM states in use at linux. Something is broken. dmesg is spammed with these amdgpu-pro, mint 18, rx480. Latest 4.6 kernel from git (agd5f/linux). [ 1214.592256] VM fault (0x14, vmid 6) at page 1071080, write from 'CB0' (0x43423000) (96) [ 1214.592262] amdgpu 0000:01:00.0: GPU fault detected: 146 0x059aa504 [ 1214.592262] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057D2 [ 1214.592263] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0D0014 [ 1214.592264] VM fault (0x14, vmid 6) at page 1071058, write from 'CB7' (0x43423700) (208) [ 1214.592269] amdgpu 0000:01:00.0: GPU fault detected: 146 0x059a5504 [ 1214.592270] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057D8 [ 1214.592271] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D020014 [ 1214.592271] VM fault (0x14, vmid 6) at page 1071064, write from 'CB2' (0x43423200) (32) [ 1214.592642] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0f2ad014 [ 1214.592643] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057E9 [ 1214.592643] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C0D000C [ 1214.592644] VM fault (0x0c, vmid 6) at page 1071081, read from 'CB7' (0x43423700) (208) [ 1214.592650] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0f2aa014 [ 1214.592650] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057D8 [ 1214.592651] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C02000C [ 1214.592652] VM fault (0x0c, vmid 6) at page 1071064, read from 'CB2' (0x43423200) (32) [ 1214.592657] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0f60e00c [ 1214.592658] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057EC [ 1214.592659] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0E0014 [ 1214.592659] VM fault (0x14, vmid 6) at page 1071084, write from 'CB6' (0x43423600) (224) [ 1214.592665] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0f28a00c [ 1214.592666] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057D0 [ 1214.592666] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D0E0014 [ 1214.592667] VM fault (0x14, vmid 6) at page 1071056, write from 'CB6' (0x43423600) (224) [ 1214.592673] amdgpu 0000:01:00.0: GPU fault detected: 146 0x0ec25014 [ 1214.592673] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x001057D2 [ 1214.592674] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0D060014 [ 1214.592675] VM fault (0x14, vmid 6) at page 1071058, write from 'CB0' (0x43423000) (96) [ 1214.661835] steam[6544]: segfault at 4184ddd7 ip 00000000f72ea771 sp 00000000ff9ce690 error 4 in libc-2.23.so[f727d000+1af000] [ 1353.103633] failed to send pre message 200 ret is 0 [ 1353.317672] failed to send message 200 ret is 0 [ 1353.536394] failed to send pre message 201 ret is 0 [ 1353.754228] failed to send message 201 ret is 0 [ 1961.904046] failed to send pre message 200 ret is 0 [ 1962.120865] failed to send message 200 ret is 0 [ 1962.342261] failed to send pre message 201 ret is 0 [ 1962.560233] failed to send message 201 ret is 0 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 97221] monitor miss detection, philips 242G5
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97221 Bug ID: 97221 Summary: monitor miss detection, philips 242G5 Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: ken(a)kenjo.org Created attachment 125566 --> https://bugs.freedesktop.org/attachment.cgi?id=125566&action=edit dmesg This is a 144Hz display but that is not showing up in xrandr as an option for nay resolution. DisplayPort-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.00*+ 50.00 59.94 -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 97220] miss detect monitor. dell UP3214Q
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=97220 Bug ID: 97220 Summary: miss detect monitor. dell UP3214Q Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: ken(a)kenjo.org Created attachment 125565 --> https://bugs.freedesktop.org/attachment.cgi?id=125565&action=edit dmesg Dell UP3214Q is a MST Monitor and proper detection is needed for it to operate in 60HZ mode. It is miss detected and only show up as supporting 30Hz max. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 96906] OpenCL program causes steady stream of GPU fault detected errors
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=96906 Bug ID: 96906 Summary: OpenCL program causes steady stream of GPU fault detected errors Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu-pro Assignee: dri-devel(a)lists.freedesktop.org Reporter: jolan(a)jolan.org Hi, I have an OpenCL program which causes a steady stream of errors: kernel: amdgpu 0000:01:00.0: GPU fault detected: 147 0x03f84801 kernel: VM fault (0x01, vmid 6) at page 135290494, read from 'TC7' (0x54433700) (132) kernel: amdgpu 0000:05:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C084001 kernel: amdgpu 0000:05:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E7E kernel: amdgpu 0000:05:00.0: GPU fault detected: 147 0x03f08401 kernel: VM fault (0x01, vmid 3) at page 135290494, read from 'TC2' (0x54433200) (200) kernel: amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x060C8001 kernel: amdgpu 0000:04:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E7E kernel: amdgpu 0000:04:00.0: GPU fault detected: 147 0x03f0c801 kernel: VM fault (0x01, vmid 6) at page 135290495, read from 'TC1' (0x54433100) (4) kernel: amdgpu 0000:05:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0C004001 kernel: amdgpu 0000:05:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x08105E7F AMDGPU-Pro: 16.30.3.306809 Kernel: 4.7.0-rc6-mainline GPU: RX480 -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 109978] Unprivileged user mode program can cause GPU reset
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=109978 Bug ID: 109978 Summary: Unprivileged user mode program can cause GPU reset Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/amdkfd Assignee: dri-devel(a)lists.freedesktop.org Reporter: sudolskym(a)gmail.com https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/issues/72 Sample program which causes this (needs ROCm): > #include <hc.hpp> > int main() > { > parallel_for_each(hc::extent<1>(1), [=]() [[hc]] > { > asm("s_trap 2"); > }); > return 0; > } > hcc -hc main.cpp > ./a.out Process never ends and CTRL-C causes GPU reset which breaks all other processes actually using rocm on that GPU. Seems trap handler expects queue handle in s[0:1] which is set when using __builtin_trap() so without it trap handler causes another exceptions. System logs: [ 247.428727] qcm fence wait loop timeout expired [ 247.428730] The cp might be in an unrecoverable state due to an unsuccessful queues preemption [ 247.428736] amdgpu 0000:0b:00.0: GPU reset begin! [ 247.619440] amdgpu 0000:0b:00.0: GPU reset [ 248.152762] [drm] psp mode1 reset succeed [ 248.279461] amdgpu 0000:0b:00.0: GPU reset succeeded, trying to resume [ 248.279584] [drm] PCIE GART of 512M enabled (table at 0x000000F400900000). [ 248.279639] [drm:amdgpu_device_gpu_recover [amdgpu]] *ERROR* VRAM is lost! [ 248.279769] [drm] PSP is resuming... [ 248.428305] [drm] reserve 0x400000 from 0xf400d00000 for PSP TMR SIZE [ 248.472774] WARNING: CPU: 23 PID: 21634 at /build/linux-uQJ2um/linux-4.15.0/kernel/kthread.c:498 kthread_park+0x67/0x80 [ 248.472775] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs msr nls_utf8 cifs ccm fscache cmac bnep binfmt_misc nls_iso8859_1 edac_mce_amd arc4 snd_hda_codec_realtek snd_hda_codec_generic kvm_amd snd_hda_codec_hdmi kvm snd_seq_midi irqbypass snd_hda_intel snd_seq_midi_event snd_hda_codec btusb snd_hda_core btrtl wmi_bmof snd_rawmidi iwlmvm snd_hwdep btbcm btintel snd_pcm snd_seq bluetooth mac80211 snd_seq_device ecdh_generic snd_timer iwlwifi ccp snd cfg80211 soundcore k10temp shpchp mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nct6775 hwmon_vid parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 [ 248.472823] multipath linear raid0 amdgpu(OE) amdchash(OE) amdttm(OE) amd_sched(OE) mxm_wmi crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 amdkcl(OE) crypto_simd glue_helper amd_iommu_v2 cryptd drm_kms_helper syscopyarea sysfillrect sysimgblt igb fb_sys_fops drm dca nvme i2c_algo_bit i2c_piix4 nvme_core ptp ahci atlantic libahci pps_core gpio_amdpt wmi gpio_generic [ 248.472846] CPU: 23 PID: 21634 Comm: a.out Tainted: G OE 4.15.0-45-generic #48-Ubuntu [ 248.472847] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X399 Professional Gaming, BIOS P3.30 08/14/2018 [ 248.472849] RIP: 0010:kthread_park+0x67/0x80 [ 248.472850] RSP: 0018:ffffb44fc7e27ad0 EFLAGS: 00010202 [ 248.472852] RAX: 0000000000000004 RBX: ffff9ec63f49e480 RCX: 0000000000000000 [ 248.472853] RDX: ffff9ec63c717198 RSI: ffff9ec63ea0c0c0 RDI: ffff9ec63dd38000 [ 248.472854] RBP: ffffb44fc7e27ae0 R08: 0000000000000051 R09: 0000000000000000 [ 248.472855] R10: 0000000000000000 R11: 0000000000000056 R12: ffff9ec63ea0c0c0 [ 248.472855] R13: ffff9ec64f4f4200 R14: ffff9ec63c710000 R15: 0000000000000000 [ 248.472857] FS: 00007fd52a286c00(0000) GS:ffff9ec65cdc0000(0000) knlGS:0000000000000000 [ 248.472858] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 248.472859] CR2: 00007f0c07687a98 CR3: 000000081b5b6000 CR4: 00000000003406e0 [ 248.472860] Call Trace: [ 248.472865] amddrm_sched_entity_fini+0x44/0x1b0 [amd_sched] [ 248.472868] amddrm_sched_entity_destroy+0x1f/0x30 [amd_sched] [ 248.472907] amdgpu_vm_fini+0xbb/0x4f0 [amdgpu] [ 248.472942] amdgpu_driver_postclose_kms+0x15b/0x2b0 [amdgpu] [ 248.472952] drm_release+0x26b/0x390 [drm] [ 248.472955] __fput+0xea/0x220 [ 248.472957] ____fput+0xe/0x10 [ 248.472959] task_work_run+0x9d/0xc0 [ 248.472961] do_exit+0x2ec/0xb40 [ 248.472963] do_group_exit+0x43/0xb0 [ 248.472965] get_signal+0x27b/0x590 [ 248.472968] do_signal+0x37/0x730 [ 248.472971] ? __switch_to_asm+0x34/0x70 [ 248.472973] ? __switch_to_asm+0x40/0x70 [ 248.472976] ? do_vfs_ioctl+0xa8/0x630 [ 248.472978] ? __schedule+0x299/0x8a0 [ 248.472980] exit_to_usermode_loop+0x73/0xd0 [ 248.472982] do_syscall_64+0x115/0x130 [ 248.472984] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 248.472986] RIP: 0033:0x7fd528bdd5d7 [ 248.472987] RSP: 002b:00007ffe830d4778 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 248.472988] RAX: fffffffffffffffc RBX: 0000000000000001 RCX: 00007fd528bdd5d7 [ 248.472989] RDX: 00007ffe830d47d0 RSI: 00000000c0184b0c RDI: 0000000000000003 [ 248.472990] RBP: 00007ffe830d47d0 R08: 00007ffe830d4890 R09: 0000000000000001 [ 248.472990] R10: 0000000000c92010 R11: 0000000000000246 R12: 00000000c0184b0c [ 248.472991] R13: 0000000000000003 R14: 0000000000000000 R15: 00000000fffffffe [ 248.472992] Code: 0e e8 6e c0 00 00 48 8d 7b 18 e8 35 d2 8e 00 44 89 e0 5b 41 5c 5d c3 0f 0b 41 bc da ff ff ff 44 89 e0 5b 41 5c 5d c3 0f 0b eb af <0f> 0b 41 bc f0 ff ff ff eb da 0f 1f 44 00 00 66 2e 0f 1f 84 00 [ 248.473020] ---[ end trace 19649ddd4a6314f7 ]--- [ 248.648453] [drm] UVD and UVD ENC initialized successfully. [ 248.748509] [drm] VCE initialized successfully. [ 248.749616] [drm] recover vram bo from shadow start [ 248.749666] [drm] recover vram bo from shadow done [ 248.749680] amdgpu 0000:0b:00.0: GPU reset(1) succeeded! -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 107898] "kfd: Failed to resume IOMMU for device 1002:15dd" on Raven Ridge
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=107898 Bug ID: 107898 Summary: "kfd: Failed to resume IOMMU for device 1002:15dd" on Raven Ridge Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/amdkfd Assignee: dri-devel(a)lists.freedesktop.org Reporter: marvin.damschen(a)gullz.de Created attachment 141520 --> https://bugs.freedesktop.org/attachment.cgi?id=141520&action=edit dmesg 4.19-rc3 Hey, I wanted to try the newly-added support for Raven Ridge in amdkfd, but initialization fails at: "kfd: Failed to resume IOMMU for device 1002:15dd" on AMD Ryzen 5 2500U (Lenovo E485) with 4.19-rc3. IOMMU itself seems to initialize fine (As I understand, I can ignore the "AMD-Vi: Unable to write to IOMMU perf counter." msg). Full log is attached. Best regards Marvin -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 106571] Stoney [Radeon R5 Graphics] [1002:98E4] hangs on hibernate
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=106571 Bug ID: 106571 Summary: Stoney [Radeon R5 Graphics] [1002:98E4] hangs on hibernate Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: hagar(a)iinet.net.au Created attachment 139632 --> https://bugs.freedesktop.org/attachment.cgi?id=139632&action=edit Hardware Listing I have a laptop with "AMD A9-9420e RADEON R5, 5 COMPUTE CORES 2C+3G" Without the amdgpu module it always hibernates. With just the amdgou module (without amdkfd and amd_iommu_v2) it reboots instead. With all 3 loaded it hangs at "PM: Syncing filesystems ... " All I get in the logs is - May 19 08:32:53 diamond systemd[1]: Reached target Sleep. May 19 08:32:53 diamond systemd[1]: Starting Hibernate... May 19 08:32:53 diamond systemd-sleep[10963]: Suspending system... May 19 08:32:53 diamond kernel: PM: hibernation entry May 19 08:32:53 diamond kernel: PM: Syncing filesystems ... -- Reboot -- The device suspends just fine. I currently use the following module options - options amdgpu dc=0 si=0 cik=0 exp_hw_support=0 aspm=1 dpm=1 bapm=1 hw_i2c=1 radeon is not loaded (doesnt work on the card anyway) Kernels tried - arch 4.16.8 arch lts 4.14.41 arch mainline 4.17rc5 and a couple of others All showed the same symptoms and log entries. Thanks -- You are receiving this mail because: You are the assignee for the bug.

1 9

[PATCH 0/2] Support CMDQ interface and control flow
by Bibby Hsieh 18 Nov '19

18 Nov '19

The CMDQ (Command Queue) in MT8183 is used to help update all relevant display controller registers with critical time limation. These patched add CMDQ interface in ddp_comp interface and add CMDQ control flow. This patch depends on ptach: drm/mediatek: fixup cursor moving unsmooth issue (https://patchwork.kernel.org/cover/11123119/) add drm support for MT8183 (https://patchwork.kernel.org/cover/11121519/) support gce on mt8183 platform (https://patchwork.kernel.org/cover/11120153/) Bibby Hsieh (2): drm/mediatek: Support CMDQ interface in ddp component drm/mediatek: Apply CMDQ control flow drivers/gpu/drm/mediatek/mtk_disp_color.c | 7 +- drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 78 ++++---- drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 66 +++---- drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 190 +++++++++++++++++--- drivers/gpu/drm/mediatek/mtk_drm_crtc.h | 2 + drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 144 +++++++++++---- drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 55 ++++-- drivers/gpu/drm/mediatek/mtk_drm_plane.c | 4 + 8 files changed, 393 insertions(+), 153 deletions(-) -- 2.18.0

5 8

[Bug 109206] Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U
by bugzilla-daemon＠freedesktop.org 16 Nov '19

16 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=109206 Bug ID: 109206 Summary: Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: grakbug(a)gmail.com On Kernel 4.20.0-arch1, amdgpu psp fails to load firmware, crashing system during boot. modprobe.blacklist=amdgpu allowed system to boot, without dm. System is an HP Envy x360 Ryzen 5 2500U Laptop. Jan 01 08:36:42 mimisbrunnr kernel: Linux agpgart interface v0.103 Jan 01 08:36:42 mimisbrunnr kernel: AMD IOMMUv2 driver by Joerg Roedel <jroedel(a)suse.de> Jan 01 08:36:42 mimisbrunnr kernel: [drm] amdgpu kernel modesetting enabled. Jan 01 08:36:42 mimisbrunnr kernel: Parsing CRAT table with 1 nodes Jan 01 08:36:42 mimisbrunnr kernel: Ignoring ACPI CRAT on non-APU system Jan 01 08:36:42 mimisbrunnr kernel: Virtual CRAT table created for CPU Jan 01 08:36:42 mimisbrunnr kernel: Parsing CRAT table with 1 nodes Jan 01 08:36:42 mimisbrunnr kernel: Creating topology SYSFS entries Jan 01 08:36:42 mimisbrunnr kernel: Topology: Add CPU node Jan 01 08:36:42 mimisbrunnr kernel: Finished initializing topology Jan 01 08:36:42 mimisbrunnr kernel: checking generic (e0000000 7f0000) vs hw (e0000000 10000000) Jan 01 08:36:42 mimisbrunnr kernel: fb0: switching to amdgpudrmfb from EFI VGA Jan 01 08:36:42 mimisbrunnr kernel: Console: switching to colour dummy device 80x25 Jan 01 08:36:42 mimisbrunnr kernel: amdgpu 0000:03:00.0: enabling device (0006 -> 0007) Jan 01 08:36:42 mimisbrunnr kernel: [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x103C:0x83C6 0xC4). Jan 01 08:36:42 mimisbrunnr kernel: [drm] register mmio base: 0xFE000000 Jan 01 08:36:42 mimisbrunnr kernel: [drm] register mmio size: 524288 Jan 01 08:36:42 mimisbrunnr kernel: [drm] add ip block number 0 <soc15_common> Jan 01 08:36:42 mimisbrunnr kernel: [drm] add ip block number 1 <gmc_v9_0> Jan 01 08:36:42 mimisbrunnr kernel: [drm] add ip block number 2 <vega10_ih> Jan 01 08:36:42 mimisbrunnr kernel: [drm] add ip block number 3 <psp> Jan 01 08:36:42 mimisbrunnr kernel: [drm] add ip block number 4 <gfx_v9_0> Jan 01 08:36:42 mimisbrunnr kernel: [drm] add ip block number 5 <sdma_v4_0> Jan 01 08:36:42 mimisbrunnr kernel: [drm] add ip block number 6 <powerplay> Jan 01 08:36:42 mimisbrunnr kernel: [drm] add ip block number 7 <dm> Jan 01 08:36:42 mimisbrunnr kernel: [drm] add ip block number 8 <vcn_v1_0> Jan 01 08:36:42 mimisbrunnr kernel: [drm] VCN decode is enabled in VM mode Jan 01 08:36:42 mimisbrunnr kernel: [drm] VCN encode is enabled in VM mode Jan 01 08:36:42 mimisbrunnr kernel: [drm] VCN jpeg decode is enabled in VM mode Jan 01 08:36:42 mimisbrunnr kernel: ATOM BIOS: SWBRT25890.001 Jan 01 08:36:42 mimisbrunnr kernel: [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit Jan 01 08:36:42 mimisbrunnr kernel: amdgpu 0000:03:00.0: VRAM: 256M 0x000000F400000000 - 0x000000F40FFFFFFF (256M used) Jan 01 08:36:42 mimisbrunnr kernel: amdgpu 0000:03:00.0: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF Jan 01 08:36:42 mimisbrunnr kernel: amdgpu 0000:03:00.0: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF Jan 01 08:36:42 mimisbrunnr kernel: [drm] Detected VRAM RAM=256M, BAR=256M Jan 01 08:36:42 mimisbrunnr kernel: [drm] RAM width 128bits UNKNOWN Jan 01 08:36:42 mimisbrunnr kernel: [TTM] Zone kernel: Available graphics memory: 3964154 kiB Jan 01 08:36:42 mimisbrunnr kernel: [TTM] Zone dma32: Available graphics memory: 2097152 kiB Jan 01 08:36:42 mimisbrunnr kernel: [TTM] Initializing pool allocator Jan 01 08:36:42 mimisbrunnr kernel: [TTM] Initializing DMA pool allocator Jan 01 08:36:42 mimisbrunnr kernel: [drm] amdgpu: 256M of VRAM memory ready Jan 01 08:36:42 mimisbrunnr kernel: [drm] amdgpu: 3072M of GTT memory ready. Jan 01 08:36:42 mimisbrunnr kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144 Jan 01 08:36:42 mimisbrunnr kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F4007E9000). Jan 01 08:36:42 mimisbrunnr kernel: [drm] use_doorbell being set to: [true] Jan 01 08:36:42 mimisbrunnr kernel: [drm] Found VCN firmware Version: 1.73 Family ID: 18 Jan 01 08:36:42 mimisbrunnr kernel: [drm] PSP loading VCN firmware Jan 01 08:36:42 mimisbrunnr kernel: [drm] reserve 0x400000 from 0xf400b00000 for PSP TMR SIZE Jan 01 08:36:43 mimisbrunnr kernel: [drm:psp_cmd_submit_buf [amdgpu]] *ERROR* failed loading with status (-65530) and ucode id (19) Jan 01 08:36:43 mimisbrunnr kernel: [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed Jan 01 08:36:43 mimisbrunnr kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block <psp> failed -22 Jan 01 08:36:43 mimisbrunnr kernel: amdgpu 0000:03:00.0: amdgpu_device_ip_init failed Jan 01 08:36:43 mimisbrunnr kernel: amdgpu 0000:03:00.0: Fatal error during GPU init Jan 01 08:36:43 mimisbrunnr kernel: [drm] amdgpu: finishing device. Jan 01 08:36:43 mimisbrunnr kernel: amdgpu 0000:03:00.0: 00000000c149df08 unpin not necessary -- You are receiving this mail because: You are the assignee for the bug.

2 71

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019