dri-devel November 2018

dri-devel@lists.freedesktop.org

297 participants
2005 discussions

[Bug 88464] booting with radeon.test=1 with radeon3850hd and lockdep validation causes lock-up
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=88464 Bug ID: 88464 Summary: booting with radeon.test=1 with radeon3850hd and lockdep validation causes lock-up Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: arthur.marsh(a)internode.on.net I tried booting with radeon.test=1 Full dmesg output attached. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 108599] No vaapi / vdpau H264 decoding available on GCN 1.0 AMDGPU
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108599 Bug ID: 108599 Summary: No vaapi / vdpau H264 decoding available on GCN 1.0 AMDGPU 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: darkbasic(a)linuxsystems.it Distro is Arch Linux. $ vainfo vainfo: VA-API version: 1.3 (libva 2.3.0) vainfo: Driver version: Mesa Gallium driver 18.2.3 for AMD Radeon HD 7900 Series (TAHITI, DRM 3.26.0, 4.18.16-arch1-1-ARCH, LLVM 7.0.0) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc $ vdpauinfo display: :0 screen: 0 API version: 1 Information string: G3DVL VDPAU Driver Shared Library version 1.0 Video surface: name width height types ------------------------------------------- 420 16384 16384 NV12 YV12 422 16384 16384 UYVY YUYV 444 16384 16384 Y8U8V8A8 V8U8Y8A8 Decoder capabilities: name level macbs width height ---------------------------------------------------- MPEG1 0 1048576 16384 16384 MPEG2_SIMPLE 3 1048576 16384 16384 MPEG2_MAIN 3 1048576 16384 16384 H264_BASELINE --- not supported --- H264_MAIN --- not supported --- H264_HIGH --- not supported --- VC1_SIMPLE --- not supported --- VC1_MAIN --- not supported --- VC1_ADVANCED --- not supported --- MPEG4_PART2_SP --- not supported --- MPEG4_PART2_ASP --- not supported --- DIVX4_QMOBILE --- not supported --- DIVX4_MOBILE --- not supported --- DIVX4_HOME_THEATER --- not supported --- DIVX4_HD_1080P --- not supported --- DIVX5_QMOBILE --- not supported --- DIVX5_MOBILE --- not supported --- DIVX5_HOME_THEATER --- not supported --- DIVX5_HD_1080P --- not supported --- H264_CONSTRAINED_BASELINE --- not supported --- H264_EXTENDED --- not supported --- H264_PROGRESSIVE_HIGH --- not supported --- H264_CONSTRAINED_HIGH --- not supported --- H264_HIGH_444_PREDICTIVE --- not supported --- HEVC_MAIN --- not supported --- HEVC_MAIN_10 --- not supported --- HEVC_MAIN_STILL --- not supported --- HEVC_MAIN_12 --- not supported --- HEVC_MAIN_444 --- not supported --- Output surface: name width height nat types ---------------------------------------------------- B8G8R8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8 R8G8B8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8 R10G10B10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8 B10G10R10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8 Bitmap surface: name width height ------------------------------ B8G8R8A8 16384 16384 R8G8B8A8 16384 16384 R10G10B10A2 16384 16384 B10G10R10A2 16384 16384 A8 16384 16384 Video mixer: feature name sup ------------------------------------ DEINTERLACE_TEMPORAL y DEINTERLACE_TEMPORAL_SPATIAL - INVERSE_TELECINE - NOISE_REDUCTION y SHARPNESS y LUMA_KEY y HIGH QUALITY SCALING - L1 y HIGH QUALITY SCALING - L2 - HIGH QUALITY SCALING - L3 - HIGH QUALITY SCALING - L4 - HIGH QUALITY SCALING - L5 - HIGH QUALITY SCALING - L6 - HIGH QUALITY SCALING - L7 - HIGH QUALITY SCALING - L8 - HIGH QUALITY SCALING - L9 - parameter name sup min max ----------------------------------------------------- VIDEO_SURFACE_WIDTH y 48 16384 VIDEO_SURFACE_HEIGHT y 48 16384 CHROMA_TYPE y LAYERS y 0 4 attribute name sup min max ----------------------------------------------------- BACKGROUND_COLOR y CSC_MATRIX y NOISE_REDUCTION_LEVEL y 0.00 1.00 SHARPNESS_LEVEL y -1.00 1.00 LUMA_KEY_MIN_LUMA y LUMA_KEY_MAX_LUMA y -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 108574] Screens do not turn on if xorg start when they are off
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108574 Bug ID: 108574 Summary: Screens do not turn on if xorg start when they are off 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: coolo1mc(a)gmail.com Created attachment 142229 --> https://bugs.freedesktop.org/attachment.cgi?id=142229&action=edit errors in dmesg If xorg is started while screens are off or disconnected, ugly messages get printed into dmesg and the screens do not get activated if they are then turned on. Also seems to kill x11vnc if that was started. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 108573] Cannot set pstate values with under-voltage values for Vega M
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108573 Bug ID: 108573 Summary: Cannot set pstate values with under-voltage values for Vega M 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: rstrube(a)gmail.com There are some folks on the Windows side of the fence that have had great success under-volting their Vega M chips to improve thermals (and because TDP is shared between the CPU and GPU on Kaby Lake G, also their overall performance). Following information from the amdgpu kernel documentation I applied the following kernel boot parameters: amdgpu.runpm=0 amdgpu.ppfeaturemask=0xffffffff Note: I needed the runpm=0 so that the Vega M is active at all times, otherwise it powers down and I'm unable to make any changes to the pstates using the sysfs API. Then doing the following I was able to see the current pstates: cat /sys/bus/pci/drivers/amdgpu/0000:01:00.0/pp_od_clk_voltage OD_SCLK: 0: 225MHz 750mV 1: 400MHz 750mV 2: 535MHz 750mV 3: 715MHz 750mV 4: 850MHz 750mV 5: 960MHz 750mV 6: 985MHz 750mV 7: 1011MHz 750mV OD_MCLK: 0: 300MHz 750mV 1: 500MHz 750mV 2: 700MHz 750mV OD_RANGE: SCLK: 225MHz 1011MHz MCLK: 300MHz 700MHz VDDC: 750mV 750mV Then this to support updating the pstates: echo "manual" > /sys/bus/pci/drivers/amdgpu/0000:01:00.0/power_dpm_force_performance_level Then I could push in new pstates values, provided the voltage was *exactly* 750mV. I could set a higher clock speed for a pstate, but I was unable to make any changes to the voltage. echo "s 0 226 750" > /sys/bus/pci/drivers/amdgpu/0000:01:00.0/pp_od_clk_voltage works and increases the MHz from 225 -> 226 for pstate 0, but echo "s 0 226 749" > /sys/bus/pci/drivers/amdgpu/0000:01:00.0/pp_od_clk_voltage -bash: echo: write error: Invalid argument Checking dmesg I see that the voltage range is constrained between 750 and 750. [ 4362.487021] amdgpu: [powerplay] OD voltage is out of range [750 - 750] mV Would it be possible to add support for under-volting Vega M using the sysfs API? I also noticed that it's not possible to set any pstate higher than 1011 MHz, perhaps that's a harder sell, but it might also be nice to be able to overclock the Vega M a little! P.S. I tried finding these values in the kernel source code, but I was extremely confused about the way they are defined. I figured worse case scenario I could manually modify these limits and recompile the kernel. Thanks! Rob -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 88364] Xorg hangs after videocard switching
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=88364 Bug ID: 88364 Summary: Xorg hangs after videocard switching Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: lissamour(a)gmail.com Created attachment 112158 --> https://bugs.freedesktop.org/attachment.cgi?id=112158&action=edit dmesg log steps to reproduce: 1. launch anything through discrete videocard e. g. DRI_PRIME=1 glxgears I expected that program will run through discrete videocard, but after little time xorg hanged. Ubuntu 14.10 64-bit, kernel 3.18.1, lastest mesa and drivers from oibaf ppa. 0a:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun LE [Radeon HD 8550M / R5 M230] (rev ff) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr:0000:00:02.0 1:DIS: :DynOff:0000:0a:00.0 -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 108563] Kernel hangs up when no amdgpu.dc=0 (if DC not disabled) kernel parameter supplied and when GCN 1.1 and GCN 1.2/1.4 (very likely) device will be handled by AMDGPU
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108563 Bug ID: 108563 Summary: Kernel hangs up when no amdgpu.dc=0 (if DC not disabled) kernel parameter supplied and when GCN 1.1 and GCN 1.2/1.4 (very likely) device will be handled by AMDGPU 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: matszpk(a)interia.pl In my Arch Linux installation, I compiled and installed new fresh kernel 4.19. I have non-standard hardware configuration where are: Radeon R7 360 (Bonaire), Radeon RX 480 (Ellesmere) and Radeon RX VEGA 56 (GFX900) graphics card. If Radeon R7 360 was handled by Radeon driver (not AMDGPU) then system has been started properly without that errors. I solved temporarily trouble by supplying kernel parameter 'amdgpu.dc=0' (just disable DC). I have connetected monitor to Intel IGP (in the motherboard DVI port) and I am not using any Radeon graphics card to display screen. After run and loading AMDGPU driver module kernel print errors (if all Radeon graphics cards are handled by AMDGPU driver and if no amdgpu.dc=0 parameter): [ 18.371385] WARNING: CPU: 1 PID: 289 at drivers/gpu/drm/drm_plane.c:182 drm_universal_plane_init+0x55b/0x5f0 [drm] [ 18.371386] Modules linked in: mousedev input_leds joydev led_class amdkfd intel_rapl x86_pkg_temp_thermal intel_powerclamp amd_iommu_v2 coretemp amdgpu(+) kvm_intel crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 radeon crypto_simd cryptd gpio_ich iTCO_wdt iTCO_vendor_support glue_helper intel_cstate chash gpu_sched snd_hda_codec_realtek ttm pcspkr intel_uncore snd_hda_codec_generic evdev intel_rapl_perf i2c_i801 snd_hda_codec_hdmi alx mei_me mei mdio ie31200_edac lpc_ich mac_hid snd_hda_intel snd_hda_codec snd_hda_core rtc_cmos snd_hwdep snd_pcm snd_timer snd soundcore pcc_cpufreq sg crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 fscrypto sr_mod sd_mod cdrom uas usb_storage hid_generic ata_generic pata_acpi usbhid hid ata_piix xhci_pci libata [ 18.371446] ehci_pci xhci_hcd ehci_hcd crc32c_intel scsi_mod usbcore usb_common i915 kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass intel_gtt i2c_algo_bit cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm agpgart [ 18.371470] CPU: 1 PID: 289 Comm: systemd-udevd Not tainted 4.19.0extratemps #1 [ 18.371471] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77-DS3H, BIOS F8 08/21/2012 [ 18.371488] RIP: 0010:drm_universal_plane_init+0x55b/0x5f0 [drm] [ 18.371490] Code: e8 da e4 ff ff 48 8b b3 b8 04 00 00 31 d2 4c 89 ff e8 c9 e4 ff ff e9 08 fd ff ff 0f 0b c7 44 24 2c ea ff ff ff e9 06 fd ff ff <0f> 0b e9 2c fb ff ff bf 04 00 00 00 48 c7 c6 b0 f6 05 c0 e8 dd 21 [ 18.371492] RSP: 0018:ffffafa001f4f938 EFLAGS: 00010246 [ 18.371494] RAX: ffffffffc1206780 RBX: ffff9ffd092a1000 RCX: ffffffffc00e8ba0 [ 18.371496] RDX: 0000000000000000 RSI: ffff9ffd0a84a800 RDI: ffff9ffd092a1000 [ 18.371497] RBP: ffffafa001f4f9e8 R08: ffffffffc00e9120 R09: 0000000000000002 [ 18.371498] R10: ffff9ffd1bbc74a0 R11: 0000000000000024 R12: 0000000000000002 [ 18.371500] R13: 0000000000000000 R14: ffff9ffd0a84a800 R15: ffffffffc00e8ba0 [ 18.371502] FS: 00007fe3e78b7480(0000) GS:ffff9ffd1f280000(0000) knlGS:0000000000000000 [ 18.371504] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 18.371505] CR2: 00005610c22080b8 CR3: 0000000458860003 CR4: 00000000001606e0 [ 18.371507] Call Trace: [ 18.371524] ? drm_crtc_init+0x2a/0xb0 [drm_kms_helper] [ 18.371534] drm_crtc_init+0x60/0xb0 [drm_kms_helper] [ 18.371631] dce_v8_0_sw_init+0x17d/0x3b0 [amdgpu] [ 18.371723] amdgpu_device_init.cold.14+0xd5f/0x1253 [amdgpu] [ 18.371730] ? kmalloc_order+0x14/0x40 [ 18.371799] amdgpu_driver_load_kms+0x86/0x2c0 [amdgpu] [ 18.371816] drm_dev_register+0x109/0x140 [drm] [ 18.371885] amdgpu_pci_probe+0x13c/0x1c0 [amdgpu] [ 18.371892] ? _raw_spin_unlock_irqrestore+0x20/0x40 [ 18.371896] local_pci_probe+0x41/0x90 [ 18.371900] pci_device_probe+0x189/0x1a0 [ 18.371906] really_probe+0x235/0x3a0 [ 18.371910] driver_probe_device+0xb3/0xf0 [ 18.371913] __driver_attach+0xdd/0x110 [ 18.371916] ? driver_probe_device+0xf0/0xf0 [ 18.371919] ? driver_probe_device+0xf0/0xf0 [ 18.371921] bus_for_each_dev+0x76/0xc0 [ 18.371924] bus_add_driver+0x152/0x230 [ 18.371927] ? 0xffffffffc15ca000 [ 18.371930] driver_register+0x6b/0xb0 [ 18.371932] ? 0xffffffffc15ca000 [ 18.371936] do_one_initcall+0x46/0x1f5 [ 18.371942] ? kmem_cache_alloc_trace+0x176/0x1d0 [ 18.371945] ? do_init_module+0x22/0x210 [ 18.371947] do_init_module+0x5a/0x210 [ 18.371950] load_module+0x2451/0x25f0 [ 18.371957] ? __se_sys_init_module+0x10a/0x170 [ 18.371959] __se_sys_init_module+0x10a/0x170 [ 18.371965] do_syscall_64+0x5b/0x170 [ 18.371969] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 18.371971] RIP: 0033:0x7fe3eac4456e [ 18.371973] Code: 48 8b 0d f5 18 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c2 18 0c 00 f7 d8 64 89 01 48 [ 18.371975] RSP: 002b:00007fffe22ba348 EFLAGS: 00000246 ORIG_RAX: 00000000000000af [ 18.371978] RAX: ffffffffffffffda RBX: 00005604f506e070 RCX: 00007fe3eac4456e [ 18.371979] RDX: 00005604f5067b00 RSI: 00000000006111e8 RDI: 00005604f5bb7760 [ 18.371980] RBP: 00005604f5067b00 R08: 0000000000000007 R09: 0000000000000006 [ 18.371982] R10: 00005604f504a010 R11: 0000000000000246 R12: 00005604f5bb7760 [ 18.371983] R13: 00005604f5060be0 R14: 0000000000020000 R15: 00005604f506e070 [ 18.371986] ---[ end trace e549c6398b2ff21b ]--- ------------------------- These errors encountered many times in dmesg output. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 108562] Radeon R5 M330 freezes when dpm enabled
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108562 Bug ID: 108562 Summary: Radeon R5 M330 freezes when dpm enabled Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: masterxakep(a)gmail.com Radeon R5 M330 gpu hungs when dpm enabled and running gpu intensive programs with DRI_PRIME=1. If amdgpu.dpm disabled no freezes happens, but gpu always on same clock speed. This happens on every linux ditro I tried. Oldest kernel I tryed was 4.9, now I'm using amd-staging-drm-next kernel and still have problem. Also this happens with radeon module with radeon.dpm=1 but just before hung lot of texture/shader artifacts appears on screen -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 88183] radeonsi: R9 280X hangs with SuperTuxKart
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=88183 Bug ID: 88183 Summary: radeonsi: R9 280X hangs with SuperTuxKart Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: alexandre.f.demers(a)gmail.com In SuperTuxKart, upon loading the first track of the story mode, the display freezes. The GPU resets but when it comes back everything is messed up and it keeps resetting continuously. I'm using latest kernel 3.19-rc3 with the "drm/radeon: fix VM flush..." patches (also tested without it), latest mesa from git, latest drm from git. I'll see a journald dump outputs something interesting. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 108558] RX460: Screen corrupt after resume (from suspend to RAM)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108558 Bug ID: 108558 Summary: RX460: Screen corrupt after resume (from suspend to RAM) Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: anto.cuni(a)gmail.com Created attachment 142212 --> https://bugs.freedesktop.org/attachment.cgi?id=142212&action=edit picture of the corrupted screen I'm using Ubuntu 18.04.1 and amdgpu 18.40-676022. After resume to RAM, my screen was corrupted, showing big black horizontal bands: I attach a picture to show better. After moving the mouse on the bands, the windows were refreshed and they went back to normality. I also attach a bunch of logs as explained here: https://amdgpu-install.readthedocs.io/en/latest/install-bugrep.html -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 108542] hdmi issues with kernel 4.18
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=108542 Bug ID: 108542 Summary: hdmi issues with kernel 4.18 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: davide26079(a)gmail.com - since 4.18, the hdmi output says "12 bit" - since 4.18.8 there's no video output !! You can find more details in this thread https://bbs.archlinux.org/viewtopic.php?id=241212 I did a bisection to find the bad commit for the first regression already, and that's the result: e03fd3f300f6184c1264186a4c815e93bf658abb is the first bad commit commit e03fd3f300f6184c1264186a4c815e93bf658abb Author: Mikita Lipski <mikita.lipski(a)amd.com> Date: Wed May 16 16:46:18 2018 -0400 drm/amd/display: Do not limit color depth to 8bpc Delete if statement that would force any display's color depth higher than 8 bpc to 8 Signed-off-by: Mikita Lipski <mikita.lipski(a)amd.com> Reviewed-by: Harry Wentland <Harry.Wentland(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> :040000 040000 57c7a743a10059addbfdd1a122f90c4053d377fa 13139317e62ef56db1748bf48f31f81eb986c7f8 M drivers -- You are receiving this mail because: You are the assignee for the bug.

1 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel November 2018