dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[PATCH] Add framebuffer max width/height fields to drm_mode_config
by Jeykumar Sankaran 29 Sep '19

29 Sep '19

Below two discussion threads will provide the context behind this patch. https://www.spinics.net/lists/dri-devel/msg229070.html https://lore.kernel.org/linux-arm-msm/db26145b-3f64-a334-f698-76f972332881@… Seperating out the core framework patch from vendor implementation. Jeykumar Sankaran (1): drm: add fb max width/height fields to drm_mode_config drivers/gpu/drm/drm_framebuffer.c | 17 +++++++++++++---- include/drm/drm_mode_config.h | 3 +++ 2 files changed, 16 insertions(+), 4 deletions(-) -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project

2 2

[Bug 111747] [CI][DRMTIP] igt@ - incomplete - Jenkins gives up
by bugzilla-daemon＠freedesktop.org 28 Sep '19

28 Sep '19

1 0

[Bug 111747] [CI][DRMTIP] igt@ - incomplete - Jenkins gives up
by bugzilla-daemon＠freedesktop.org 28 Sep '19

28 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=111747 --- Comment #10 from CI Bug Log <cibuglog(a)gmail.com> --- A CI Bug Log filter associated to this bug has been updated: {- TGL: igt@* -incomplete - Abort requested by .* terminating children -} {+ TGL: igt@* -incomplete - Abort requested by .* terminating children +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6964/shard-tglb4/igt@kms_bu… * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6967/re-tgl1-display/igt@km… * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6967/re-tgl1-display/igt@km… * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6967/re-tgl1-display/igt@km… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 109955] amdgpu [RX Vega 64] system freeze while gaming
by bugzilla-daemon＠freedesktop.org 28 Sep '19

28 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=109955 --- Comment #110 from Rodney A Morris <rodamorris(a)gmail.com> --- (In reply to Rodney A Morris from comment #104) > (In reply to Mauro Gaspari from comment #103) > > (In reply to Rodney A Morris from comment #101) > > > (In reply to Rodney A Morris from comment #99) > > > > Created attachment 145366 [details] > > > > apitrace of Hearts of Iron IV hard lock > > > > > > > > Apitrace from hard lock playing Hearts of Iron IV without Steam. The replay > > > > from this trace will hard lock the computer, though inconsistently. I've > > > > replayed the trace three times. The replay hard locked computer one time. > > > > > > neofetch from hardlock: > > > > > > /:-------------:\ > > > :-------------------:: -------------------------------- > > > :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x86_64 > > > /-----------omMMMNNNMMD ---: Kernel: 5.2.13-200.fc30.x86_64 > > > :-----------sMMMMNMNMP. ---: Uptime: 25 mins > > > :-----------:MMMdP------- ---\ Packages: 2202 (rpm), 27 (flatpak) > > > ,------------:MMMd-------- ---: Shell: bash 5.0.7 > > > :------------:MMMd------- .---: Resolution: 2560x1440 > > > :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2 > > > :-- .+shhhMMMmhhy++ .------/ WM: GNOME Shell > > > :- -------:MMMd--------------: WM Theme: Adwaita > > > :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3] > > > :- ------/hMMMy------------: Icons: Adwaita [GTK2/3] > > > :-- :dMNdhhdNMMNo------------; Terminal: tilix > > > :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000GHz > > > :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/64 > > > :---------------------:// Memory: 2478MiB / 32084MiB > > > > > > OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6 > > > > > > Note: hard lock replayed occurred when the Discord flatpak is also running. > > > > I also noticed some errors that pointed to discord in my logs. In my case > > discord was installed via .deb package. > > Could you please try and disable hardware acceleration in discord settings - > > appearance menu? Please let me know if it helps or changes anything. > > Thanks! > > I have disabled hardware acceleration in discord settings to see if that > improves my experience and report back my results. I am doubtful that it > will help much. At least on the 5.2.11 kernel, I had lockups with or > without discord running. Discord running just seemed to make the problem > appear more consistently. Another lockup and crash last night of Stellaris with identical dmesg kernel information as comment 105. Kernel for this crash: 5.2.17. Unlike previous attempts, I also had cpupower configured to run the cpu in performance mode and was running feral gamemode. Although I still wonder if my hardware has an issue, I am able to run Stellaris without issue under Windows. Final Note: Getting an apitrace of my crash under Stellaris is not feasible for two reasons. First, the crash typically happens between 30 minutes and 40 minutes of game play, resulting in a monster trace file. Second, i cannot get apitrace to run correctly with Steam and a 64-bit game, which is necessary since the crashes happen most frequently in multiplayer. I am happy to provide more data if someone can point me in the direction to capture it. Aside from trying the amdgpu-pro drivers, is there anything else I can try? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 109955] amdgpu [RX Vega 64] system freeze while gaming
by bugzilla-daemon＠freedesktop.org 28 Sep '19

28 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=109955 --- Comment #109 from jeroenimo <freedesktop(a)jeroenimo.nl> --- (In reply to Wilko Bartels from comment #108) > Did u try the amdgpu-pro driver as well? > i just did four runs of glmark and it just went through for me. going up to > 1600mhz shader clock. tested both closed and opensource drivers. vega pulse > here. > Yes I did try all versions. I'm pretty sure it's not the driver, as all results in the same. Any higher clockspeed just crashed. Ik have NVIDIA 1030 installed now, which is also buggy but at least it doesn't crash. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[PATCH] gpu: drm: amd: amdgpu: Remove call to memset after dma_alloc_coherent
by Saurav Girepunje 28 Sep '19

28 Sep '19

dma_alloc_coherent has already zeroed the memory. So memset is not needed. Signed-off-by: Saurav Girepunje <saurav.girepunje(a)gmail.com> --- drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c index 6d8f05511aba..111a301ce878 100644 --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c @@ -66,7 +66,6 @@ int amdgpu_ih_ring_init(struct amdgpu_device *adev, struct amdgpu_ih_ring *ih, if (ih->ring == NULL) return -ENOMEM; - memset((void *)ih->ring, 0, ih->ring_size + 8); ih->gpu_addr = dma_addr; ih->wptr_addr = dma_addr + ih->ring_size; ih->wptr_cpu = &ih->ring[ih->ring_size / 4]; -- 2.20.1

1 0

[Bug 109955] amdgpu [RX Vega 64] system freeze while gaming
by bugzilla-daemon＠freedesktop.org 28 Sep '19

28 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=109955 --- Comment #108 from Wilko Bartels <me(a)jasondaigo.de> --- Did u try the amdgpu-pro driver as well? i just did four runs of glmark and it just went through for me. going up to 1600mhz shader clock. tested both closed and opensource drivers. vega pulse here. mesa result: ======================================================= glmark2 2014.03 ======================================================= OpenGL Information GL_VENDOR: X.Org GL_RENDERER: Radeon RX Vega (VEGA10, DRM 3.33.0, 5.3.1-arch1-1-ARCH, LLVM 8.0.1) GL_VERSION: 4.5 (Compatibility Profile) Mesa 19.1.7 ======================================================= [build] use-vbo=false: FPS: 8617 FrameTime: 0.116 ms [build] use-vbo=true: FPS: 10534 FrameTime: 0.095 ms [texture] texture-filter=nearest: FPS: 11214 FrameTime: 0.089 ms [texture] texture-filter=linear: FPS: 11274 FrameTime: 0.089 ms [texture] texture-filter=mipmap: FPS: 10197 FrameTime: 0.098 ms [shading] shading=gouraud: FPS: 9790 FrameTime: 0.102 ms [shading] shading=blinn-phong-inf: FPS: 10979 FrameTime: 0.091 ms [shading] shading=phong: FPS: 10167 FrameTime: 0.098 ms [shading] shading=cel: FPS: 9662 FrameTime: 0.103 ms [bump] bump-render=high-poly: FPS: 9830 FrameTime: 0.102 ms [bump] bump-render=normals: FPS: 10151 FrameTime: 0.099 ms [bump] bump-render=height: FPS: 10870 FrameTime: 0.092 ms libpng warning: iCCP: known incorrect sRGB profile [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 12008 FrameTime: 0.083 ms libpng warning: iCCP: known incorrect sRGB profile [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 10876 FrameTime: 0.092 ms [pulsar] light=false:quads=5:texture=false: FPS: 10232 FrameTime: 0.098 ms libpng warning: iCCP: known incorrect sRGB profile [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 6842 FrameTime: 0.146 ms libpng warning: iCCP: known incorrect sRGB profile [desktop] effect=shadow:windows=4: FPS: 7934 FrameTime: 0.126 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 1770 FrameTime: 0.565 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 2308 FrameTime: 0.433 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 1875 FrameTime: 0.533 ms [ideas] speed=duration: FPS: 4475 FrameTime: 0.223 ms [jellyfish] <default>: FPS: 9499 FrameTime: 0.105 ms [terrain] <default>: FPS: 2593 FrameTime: 0.386 ms [shadow] <default>: FPS: 9423 FrameTime: 0.106 ms [refract] <default>: FPS: 6008 FrameTime: 0.166 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 11364 FrameTime: 0.088 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 10816 FrameTime: 0.092 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 12000 FrameTime: 0.083 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 10932 FrameTime: 0.091 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 11690 FrameTime: 0.086 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 11119 FrameTime: 0.090 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 11003 FrameTime: 0.091 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 12886 FrameTime: 0.078 ms ======================================================= glmark2 Score: 9119 ======================================================= amdgpu-pro result: ======================================================= glmark2 2014.03 ======================================================= OpenGL Information GL_VENDOR: ATI Technologies Inc. GL_RENDERER: Radeon RX Vega GL_VERSION: 4.6.13572 Compatibility Profile Context ======================================================= [build] use-vbo=false: FPS: 3727 FrameTime: 0.268 ms [build] use-vbo=true: FPS: 9516 FrameTime: 0.105 ms [texture] texture-filter=nearest: FPS: 7346 FrameTime: 0.136 ms [texture] texture-filter=linear: FPS: 9236 FrameTime: 0.108 ms [texture] texture-filter=mipmap: FPS: 9161 FrameTime: 0.109 ms [shading] shading=gouraud: FPS: 9184 FrameTime: 0.109 ms [shading] shading=blinn-phong-inf: FPS: 9363 FrameTime: 0.107 ms [shading] shading=phong: FPS: 9424 FrameTime: 0.106 ms [shading] shading=cel: FPS: 9060 FrameTime: 0.110 ms [bump] bump-render=high-poly: FPS: 9047 FrameTime: 0.111 ms [bump] bump-render=normals: FPS: 8804 FrameTime: 0.114 ms [bump] bump-render=height: FPS: 9156 FrameTime: 0.109 ms libpng warning: iCCP: known incorrect sRGB profile [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 9121 FrameTime: 0.110 ms libpng warning: iCCP: known incorrect sRGB profile [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 8866 FrameTime: 0.113 ms [pulsar] light=false:quads=5:texture=false: FPS: 8286 FrameTime: 0.121 ms libpng warning: iCCP: known incorrect sRGB profile [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 3789 FrameTime: 0.264 ms libpng warning: iCCP: known incorrect sRGB profile [desktop] effect=shadow:windows=4: FPS: 4491 FrameTime: 0.223 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 1026 FrameTime: 0.975 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 2228 FrameTime: 0.449 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 1275 FrameTime: 0.784 ms [ideas] speed=duration: FPS: 4038 FrameTime: 0.248 ms [jellyfish] <default>: FPS: 7342 FrameTime: 0.136 ms [terrain] <default>: FPS: 790 FrameTime: 1.266 ms [shadow] <default>: FPS: 6002 FrameTime: 0.167 ms [refract] <default>: FPS: 4273 FrameTime: 0.234 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 9208 FrameTime: 0.109 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 8964 FrameTime: 0.112 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 8984 FrameTime: 0.111 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 9360 FrameTime: 0.107 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 9214 FrameTime: 0.109 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 8945 FrameTime: 0.112 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 9218 FrameTime: 0.108 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 9077 FrameTime: 0.110 ms ======================================================= glmark2 Score: 7197 ======================================================= -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 203781] New: AMDGPU Radeon VII crashes with dual monitors
by bugzilla-daemon＠bugzilla.kernel.org 28 Sep '19

28 Sep '19

https://bugzilla.kernel.org/show_bug.cgi?id=203781 Bug ID: 203781 Summary: AMDGPU Radeon VII crashes with dual monitors Product: Drivers Version: 2.5 Kernel Version: 5.2.0-rc2, 5.1.x Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: sehellion(a)gmail.com Regression: No Created attachment 283033 --> https://bugzilla.kernel.org/attachment.cgi?id=283033&action=edit dmesg with two monitors System information: Mainline kernel 5.2.0-rc2 Mesa 19.1.0_rc4 Card Radeon VII Monitors LG 24UD58-B via DP When using only one monitor, then everything works fine. But when using two, the system starts to hang and try reset gpu. -- You are receiving this mail because: You are watching the assignee of the bug.

1 12

[PATCH] Add framebuffer max width/height fields to drm_mode_config
by Jeykumar Sankaran 28 Sep '19

28 Sep '19

1 0

[PATCH] Add framebuffer max width/height fields to drm_mode_config
by Jeykumar Sankaran 28 Sep '19

28 Sep '19

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019