dri-devel November 2018

dri-devel@lists.freedesktop.org

297 participants
2005 discussions

[Bug 85469] New: Brightness too high on internal AMD/ATI graphics device, but fine with external AMD/ATI graphics card
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=85469 Bug ID: 85469 Summary: Brightness too high on internal AMD/ATI graphics device, but fine with external AMD/ATI graphics card Product: DRI Version: XOrg CVS Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: paulepanter(a)users.sourceforge.net Created attachment 108433 --> https://bugs.freedesktop.org/attachment.cgi?id=108433&action=edit output of `radeonreg regs dce4` built from radeontool-1.6.3-10-g6b5e7c6 As reported on the list dri-devel [1], the brightness of the internal graphics card is too high on the ASRock E350M1 [2]. Please find the output of `radeonreg regs dce4` attached and I’ll attach the Linux kernel 3.16.5 messages and the Video BIOS too. [1] Brightness too high on internal AMD/ATI graphics device, but fine with external AMD/ATI graphics card http://lists.freedesktop.org/archives/dri-devel/2014-July/thread.html#63006 [2] http://www.asrock.com/mb/amd/e350m1/ -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 108309] Raven Ridge 2700U system lock-up on multiple games
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108309 Bug ID: 108309 Summary: Raven Ridge 2700U system lock-up on multiple games Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: samantham(a)posteo.net 05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev d0) System locks up partially with Plague Inc. (native Linux game). With Path of Exile (wine) it fully locks up, not able to respond to sysrq. I haven't gotten any output from the full lockup, but for the partial lock-up, nothing showed up in the logs. Let me know what steps I can take to help diagnose the issue here. Happens on 4.18.12 and 4.19.0-rc7+ ( v4.19-rc7-15-g64c5e530ac2c) -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 85180] New: [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=85180 Bug ID: 85180 Summary: [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD) Product: DRI Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: wrgcpp(a)gmail.com Created attachment 108036 --> https://bugs.freedesktop.org/attachment.cgi?id=108036&action=edit dmesg I'm using Debian Jessie, kernel 3.16.3, my graphic card is 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] System is booting normally, but GPU acceleration can't start. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 108302] High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108302 Bug ID: 108302 Summary: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: caravena(a)gmail.com Hello, Open bug in launchpad.net https://bugs.launchpad.net/bugs/1796720 "Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High.." Best regards, -- Cristian Aravena Romero (caravena) -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 108294] Turning off monitor via DisplayPort causes Kernel warning + stack trace
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108294 Bug ID: 108294 Summary: Turning off monitor via DisplayPort causes Kernel warning + stack trace 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: jamespharvey20(a)gmail.com Created attachment 141955 --> https://bugs.freedesktop.org/attachment.cgi?id=141955&action=edit kernel warning + stack trace - from when HDMI monitor is turned off and back on Up to date Arch Linux, including: linux 4.18.12.arch1-1, xf86-video-amdgpu 18.1.0-1, mesa 18.2.2-1, opencl-mesa 18.2.2-1, xorg-server 1.20.1-1, and plasma-desktop 5.13.5-1. (Recently installed system that STARTED with: linux 4.18.9.arch1-1, mesa 18.2.1-1, and opencl-mesa 18.2.1-1.) It was also doing this then. $ lspci -k | grep VGA 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] (rev e7) Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] Kernel driver in use: amdgpu Kernel modules: amdgpu It's the: XFX AMD Radeon RX 580 GTS Black Edition 8GB GDDR5 PCI Express 3.0 I have (5) Acer K272HUL bmiidp monitors hooked up via DisplayPort. Left 2 are chained, and right 2 are chained. ASRock EP2C602 Motherboard w/ P1.90 BIOS. (2) Intel Xeon E5-2690 (v1). Anytime a monitor turns off, it causes a couple of kernel warnings and stack traces. Usually 2-3 warnings each time. When the monitor turns back on, it just logs what are I think are (3) expected "[drm]" lines about the "new" connection. See attached file for a sample of the kernel warnings/stack traces. The first part is when a monitor turned off, and the last part is when it turned back on. By turned off/on, I mean regardless of if I press its power button on the monitor, pull the plug and plug it back in, or if a graphics issue somewhere in a driver or graphics API turns off a monitor until I cycle it. The only time I'm having this now is occasionally a few programs that use OpenGL graphics. (Monitors turning off/back on was happening a lot with the Acer-provided DisplayPort cables, but replacing them with certified Accell UltraAV DisplayPort cables fixed that.) When I turn it back on, KDE/Plasma properly re-adds it, gives it the right resolution, rotation, and alignment next to the other monitors. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 108107] The GPU Vega 56 randomly hang while I playing in the "Injustice: Gods Among Us Ultimate Edition" game under steam play
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108107 Bug ID: 108107 Summary: The GPU Vega 56 randomly hang while I playing in the "Injustice: Gods Among Us Ultimate Edition" game under steam play Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: mikhail.v.gavrilov(a)gmail.com Created attachment 141815 --> https://bugs.freedesktop.org/attachment.cgi?id=141815&action=edit dmesg $ inxi -bM System: Host: localhost.localdomain Kernel: 4.19.0-0.rc5.git0.1.fc30.x86_64 x86_64 bits: 64 Desktop: Gnome 3.30.0 Distro: Fedora release 30 (Rawhide) Machine: Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-I GAMING v: Rev 1.xx serial: <root required> UEFI: American Megatrends v: 0901 date: 07/23/2018 CPU: 8-Core: AMD Ryzen 7 2700X type: MT MCP speed: 2383 MHz min/max: 2200/3700 MHz Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] driver: amdgpu v: kernel Display: wayland server: Fedora Project X.org 11.0 driver: amdgpu resolution: 3840x2160~60Hz OpenGL: renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-0.rc5.git0.1.fc30.x86_64 LLVM 7.0.0) v: 4.5 Mesa 18.2.1 Network: Device-1: Intel I211 Gigabit Network driver: igb Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter driver: r8822be Drives: Local Storage: total: 11.35 TiB used: 5.33 TiB (47.0%) Info: Processes: 551 Uptime: 1h 11m Memory: 31.34 GiB used: 28.42 GiB (90.7%) Shell: bash inxi: 3.0.24 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 84500] New: [radeonsi] radeon 0000:01:00.0: Packet0 not allowed!
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=84500 Priority: medium Bug ID: 84500 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] radeon 0000:01:00.0: Packet0 not allowed! Severity: normal Classification: Unclassified OS: All Reporter: alexandre.f.demers(a)gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI On a 7950, I keep getting this error from time to time in dmesg: radeon 0000:01:00.0: Packet0 not allowed! I have associated this error with playing either html5 or flash videos. It may happen when playing offline movies, but I can't tell since I haven't tested it. When the error happens, there is a slight "stuttering" (from a fraction of second to a few seconds). And then it continues. There is nothing in Xorg.0.log about it, and no other message than "radeon 0000:01:00.0: Packet0 not allowed!" in dmesg. -- You are receiving this mail because: You are the assignee for the bug.

1 56

[Bug 108100] RX480: HDMI display unavailable with amdgpu.dc=1, boot error drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:1721
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108100 Bug ID: 108100 Summary: RX480: HDMI display unavailable with amdgpu.dc=1, boot error drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resou rce.c:1721 Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: jlp.bugs(a)gmail.com Created attachment 141796 --> https://bugs.freedesktop.org/attachment.cgi?id=141796&action=edit dmesg-4.18.8 I have just upgraded my kernel on openSUSE Tumbleweed from 4.17.14 to 4.18.8 and my display that is a Panasonic 4K/UHD TV (TX-55CX400E) is not detected anymore and not available after boot. I have to pass amdgpu.dc=0 kernel paramater to get it available again. If I check dmesg I can see a lot of lines like the following repeated: [ 195.633367] WARNING: CPU: 0 PID: 1979 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_resource.c:1721 dc_validate_stream+0xd5/0x100 [amdgpu] [ 195.633368] Modules linked in: fuse ccm af_packet iscsi_ibft iscsi_boot_sysfs bluetooth ecdh_generic msr nct6775 hwmon_vid intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm nls_iso8859_1 nls_cp437 vfat fat irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel arc4 iTCO_wdt eeepc_wmi asus_wmi aes_x86_64 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi iTCO_vendor_support mxm_wmi mt7601u sparse_keymap wmi_bmof snd_hda_intel mac80211 snd_hda_codec crypto_simd cryptd pcspkr snd_hda_core joydev glue_helper cfg80211 rfkill snd_hwdep snd_pcm snd_timer snd fan soundcore e1000e ptp pps_core wmi thermal mei_me pcc_cpufreq video i2c_i801 mei button acpi_pad btrfs libcrc32c xor zstd_decompress zstd_compress xxhash hid_logitech_hidpp hid_logitech_dj hid_generic [ 195.633403] usbhid raid6_pq amdkfd amd_iommu_v2 amdgpu crc32c_intel sr_mod cdrom chash i2c_algo_bit gpu_sched drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci xhci_hcd ttm drm usbcore sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs [ 195.633418] CPU: 0 PID: 1979 Comm: X Tainted: G W 4.18.8-1-default #1 openSUSE Tumbleweed (unreleased) [ 195.633418] Hardware name: System manufacturer System Product Name/H170 PRO GAMING, BIOS 3805 05/16/2018 [ 195.633459] RIP: 0010:dc_validate_stream+0xd5/0x100 [amdgpu] [ 195.633461] Code: aa aa c1 e2 04 89 d0 f7 e1 c1 ea 04 89 93 68 02 00 00 e9 74 ff ff ff 5b b8 06 00 00 00 5d 41 5c c3 d1 ea eb c1 83 f9 02 74 e2 <0f> 0b 89 c2 eb dc 6b d2 1e b9 ab aa aa aa 89 d0 f7 e1 c1 ea 04 eb [ 195.633490] RSP: 0018:ffffb004c8fbbb78 EFLAGS: 00010297 [ 195.633491] RAX: 0000000000091050 RBX: ffff97358c10f400 RCX: 0000000000000005 [ 195.633492] RDX: 0000000000091050 RSI: ffff97358c10f400 RDI: ffff9735915a0080 [ 195.633493] RBP: ffff97353c118e00 R08: 0000000000000000 R09: 00000000000004b0 [ 195.633494] R10: ffff97358c10f400 R11: 0000000000000780 R12: ffff97358fe1b600 [ 195.633495] R13: ffff972f0cd88a10 R14: 0000000000000000 R15: ffff972f0cd88800 [ 195.633496] FS: 00007fcb3d8ab940(0000) GS:ffff9735b6c00000(0000) knlGS:0000000000000000 [ 195.633497] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 195.633498] CR2: 000056287912f3b8 CR3: 00000007ee834005 CR4: 00000000003606f0 [ 195.633499] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 195.633500] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 195.633500] Call Trace: [ 195.633545] amdgpu_dm_connector_mode_valid+0x6d/0x1d0 [amdgpu] [ 195.633551] drm_helper_probe_single_connector_modes+0x47f/0x690 [drm_kms_helper] [ 195.633565] drm_mode_getconnector+0x3af/0x3d0 [drm] [ 195.633577] ? drm_mode_connector_property_set_ioctl+0x30/0x30 [drm] [ 195.633586] drm_ioctl_kernel+0x81/0xd0 [drm] [ 195.633595] drm_ioctl+0x1da/0x360 [drm] [ 195.633604] ? drm_mode_connector_property_set_ioctl+0x30/0x30 [drm] [ 195.633633] amdgpu_drm_ioctl+0x49/0x80 [amdgpu] [ 195.633636] do_vfs_ioctl+0x90/0x5e0 [ 195.633638] ? __fget+0x6e/0xa0 [ 195.633641] ksys_ioctl+0x60/0x90 [ 195.633644] __x64_sys_ioctl+0x16/0x20 [ 195.633646] do_syscall_64+0x60/0x110 [ 195.633649] entry_SYSCALL_64_after_hwframe+0x49/0xbe [ 195.633650] RIP: 0033:0x7fcb3c27baa7 [ 195.633650] Code: 00 00 90 48 8b 05 f1 83 2c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c1 83 2c 00 f7 d8 64 89 01 48 [ 195.633679] RSP: 002b:00007ffff09eb918 EFLAGS: 00003246 ORIG_RAX: 0000000000000010 [ 195.633682] RAX: ffffffffffffffda RBX: 00005575382a36c0 RCX: 00007fcb3c27baa7 [ 195.633683] RDX: 00007ffff09eb950 RSI: 00000000c05064a7 RDI: 000000000000000d [ 195.633683] RBP: 00007ffff09eb950 R08: 00005575382a2ac0 R09: 0000000000000007 [ 195.633684] R10: 00007fcb3c2dee90 R11: 0000000000003246 R12: 00000000c05064a7 [ 195.633685] R13: 000000000000000d R14: 000000000000000d R15: 00007ffff09eb950 [ 195.633688] ---[ end trace a58eb9c235a952c1 ]--- I also have another LCD monitor (Samsung SyncMaster 215TW) connected via DVI to the MSI Radeon RX 480 Gaming X 8G graphics card and that one works just fine. I tried older kernels and it looks like the problem is here since 4.18.0. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 108098] Acer Swift 3 Ryzen 7 2700U, amdgpu, graphics freezes on 4.15.0-34
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108098 Bug ID: 108098 Summary: Acer Swift 3 Ryzen 7 2700U, amdgpu, graphics freezes on 4.15.0-34 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: antonio.chirizzi(a)gmail.com Created attachment 141794 --> https://bugs.freedesktop.org/attachment.cgi?id=141794&action=edit dmesg gzipped Just bought and installed a new Acer Swift 3 (From kern.log: Acer Swift SF315-41/Becks_RR, BIOS V2.03 06/15/2018) # uname -a Linux antonioRyzen 4.15.0-34-generic #37~16.04.1-Ubuntu SMP Tue Aug 28 10:44:06 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Device 15dd Display Server: X.org 1.18.4 drivers: ati (unloaded: fbdev,vesa,radeon,amdgpu) tty size: 156x48 Advanced Data: N/A for root Running linux mint 18.3 with KDE, fully updated. After a few hours using it I get the screen freeze. Still able to connect via ssh, but impossible to fully shutdown (systemd reports timeouts after 2 minutes waiting on some processes) This is what is logged at the moment of the freeze: Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337272] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:7 pas_id:0) Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337279] amdgpu 0000:02:00.0: at page 0x0000000104a4c000 from 27 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337283] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00701031 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337290] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:7 pas_id:0) Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337292] amdgpu 0000:02:00.0: at page 0x0000000104a4e000 from 27 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337295] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337301] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:7 pas_id:0) Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337304] amdgpu 0000:02:00.0: at page 0x0000000104a51000 from 27 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337306] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337312] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:7 pas_id:0) Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337314] amdgpu 0000:02:00.0: at page 0x0000000104a53000 from 27 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337316] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337323] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:7 pas_id:0) Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337325] amdgpu 0000:02:00.0: at page 0x0000000104a56000 from 27 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337327] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337333] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:7 pas_id:0) Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337336] amdgpu 0000:02:00.0: at page 0x0000000104a58000 from 27 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337338] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337344] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:7 pas_id:0) Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337346] amdgpu 0000:02:00.0: at page 0x0000000104a4f000 from 27 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337348] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337354] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:7 pas_id:0) Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337357] amdgpu 0000:02:00.0: at page 0x0000000104a50000 from 27 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337358] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337365] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:7 pas_id:0) Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337367] amdgpu 0000:02:00.0: at page 0x0000000104a54000 from 27 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337369] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337375] amdgpu 0000:02:00.0: [gfxhub] VMC page fault (src_id:0 ring:24 vm_id:7 pas_id:0) Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337377] amdgpu 0000:02:00.0: at page 0x0000000104a55000 from 27 Sep 29 15:21:13 antonioRyzen kernel: [ 7156.337379] amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00000000 This is what I can see at boot time in the kern.log: [ 3.392314] usb 3-2.2: new high-speed USB device number 4 using xhci_hcd [ 3.436384] [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 1us * 100 tries - tgn10_lock line:566 [ 3.436449] WARNING: CPU: 1 PID: 291 at /build/linux-hwe-On9fm7/linux-hwe-4.15.0/drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:190 generic_reg_wai t+0xf5/0x110 [amdgpu] [ 3.436450] Modules linked in: dm_mirror dm_region_hash dm_log hid_logitech_hidpp hid_logitech_dj usbhid amdkfd amd_iommu_v2 amdgpu chash i2c_algo_bit tt m drm_kms_helper syscopyarea sysfillrect sysimgblt ahci fb_sys_fops libahci drm video wmi i2c_hid hid [ 3.436468] CPU: 1 PID: 291 Comm: plymouthd Not tainted 4.15.0-34-generic #37~16.04.1-Ubuntu [ 3.436469] Hardware name: Acer Swift SF315-41/Becks_RR, BIOS V2.03 06/15/2018 [ 3.436507] RIP: 0010:generic_reg_wait+0xf5/0x110 [amdgpu] [ 3.436508] RSP: 0018:ffffb749c1913900 EFLAGS: 00010297 [ 3.436509] RAX: 0000000000000001 RBX: 0000000000000065 RCX: ffffffffb02626e8 [ 3.436510] RDX: 0000000000000000 RSI: 0000000000000082 RDI: 0000000000000246 [ 3.436511] RBP: ffffb749c1913940 R08: 000000000006a8a0 R09: 0000000000000383 [ 3.436512] R10: 0000000000000002 R11: ffffffffb075380d R12: 0000000000000001 [ 3.436513] R13: 0000000000000064 R14: ffff93089a3e6680 R15: 0000000000000100 [ 3.436514] FS: 00007fa393f96740(0000) GS:ffff9308a7640000(0000) knlGS:0000000000000000 [ 3.436515] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3.436516] CR2: 0000557d22ffc680 CR3: 000000021aa98000 CR4: 00000000003406e0 [ 3.436517] Call Trace: [ 3.436561] tgn10_lock+0xa2/0xb0 [amdgpu] [ 3.436601] program_all_pipe_in_tree+0x80d/0x8c0 [amdgpu] [ 3.436641] ? amdgpu_cgs_write_register+0x14/0x20 [amdgpu] [ 3.436679] ? amdgpu_cgs_read_register+0x14/0x20 [amdgpu] [ 3.436718] dcn10_apply_ctx_for_surface+0x413/0x510 [amdgpu] [ 3.436755] dc_commit_state+0x265/0x550 [amdgpu] [ 3.436797] amdgpu_dm_atomic_commit_tail+0x2c4/0xae0 [amdgpu] [ 3.436828] ? amdgpu_bo_pin_restricted+0x9f/0x290 [amdgpu] [ 3.436868] ? dm_plane_helper_prepare_fb+0x1d3/0x260 [amdgpu] [ 3.436879] commit_tail+0x42/0x70 [drm_kms_helper] [ 3.436885] drm_atomic_helper_commit+0x116/0x120 [drm_kms_helper] [ 3.436900] ? drm_atomic_check_only+0x456/0x570 [drm] [ 3.436939] amdgpu_dm_atomic_commit+0x91/0xa0 [amdgpu] [ 3.436951] drm_atomic_commit+0x51/0x60 [drm] [ 3.436956] restore_fbdev_mode_atomic+0x17b/0x1e0 [drm_kms_helper] [ 3.436962] restore_fbdev_mode+0x32/0x130 [drm_kms_helper] [ 3.436967] drm_fb_helper_restore_fbdev_mode_unlocked.part.31+0x28/0x70 [drm_kms_helper] [ 3.436972] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x30 [drm_kms_helper] [ 3.437003] amdgpu_fbdev_restore_mode+0x1f/0x50 [amdgpu] [ 3.437032] amdgpu_driver_lastclose_kms+0x12/0x20 [amdgpu] [ 3.437041] drm_lastclose+0x3c/0xf0 [drm] [ 3.437050] drm_release+0x2cf/0x390 [drm] [ 3.437056] __fput+0xea/0x220 [ 3.437058] ____fput+0xe/0x10 [ 3.437062] task_work_run+0x8a/0xb0 [ 3.437066] exit_to_usermode_loop+0xc4/0xd0 [ 3.437068] do_syscall_64+0xf4/0x130 [ 3.437073] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 3.437074] RIP: 0033:0x7fa3936978f0 [ 3.437075] RSP: 002b:00007ffd115bb108 EFLAGS: 00000246 ORIG_RAX: 0000000000000003 [ 3.437076] RAX: 0000000000000000 RBX: 00000000020c3dc0 RCX: 00007fa3936978f0 [ 3.437077] RDX: 00000000020b1290 RSI: 00007fa393964b28 RDI: 0000000000000009 [ 3.437078] RBP: 0000000000000009 R08: 00000000020c3dc0 R09: 0000000000000000 [ 3.437079] R10: 00007fa393964b78 R11: 0000000000000246 R12: 000000000000e200 [ 3.437079] R13: 00007fa39397d650 R14: 0000000000000000 R15: 00000000020c66f0 [ 3.437081] Code: 18 31 f6 45 89 e8 44 89 e1 48 c7 c7 7a c1 71 c0 89 45 d4 52 48 c7 c2 f8 46 71 c0 e8 26 85 dd ff 41 83 7e 20 01 58 8b 45 d4 74 02 <0f> 0b 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 2f [ 3.437106] ---[ end trace fce3b3b89c93a318 ]--- [ 3.437277] [drm] DC: Cursor address is 0! [ 3.437447] [drm] DC: Cursor address is 0! [ 3.437488] [drm] {1920x1080, 2230x1140@152600Khz} [ 3.449512] [drm] HBRx2 pass VS=1, PE=0 -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 108094] [CI][BAT] KBL-G: Test assertion failure function amdgpu_command_submission_compute_nop
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108094 Bug ID: 108094 Summary: [CI][BAT] KBL-G: Test assertion failure function amdgpu_command_submission_compute_nop Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: tomi.p.sarvela(a)intel.com >From CI_DRM_4904 on Hades Canyon (KBL-G): https://intel-gfx-ci.01.org/tree/drm-tip/igt@amdgpu_amd_basic@cs-compute.ht… Starting subtest: cs-compute (amd_basic:3890) CRITICAL: Test assertion failure function amdgpu_command_submission_compute_nop, file ../tests/amdgpu/amd_basic.c:722: (amd_basic:3890) CRITICAL: Failed assertion: r == 0 (amd_basic:3890) CRITICAL: Last errno: 22, Invalid argument (amd_basic:3890) CRITICAL: error: -22 != 0 Subtest cs-compute failed. -- You are receiving this mail because: You are the assignee for the bug.

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel November 2018