[Bug 111482] Sapphire Pulse RX 5700 XT power consumption

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111482 --- Comment #25 from Eduardo --- I have a PowerColor RedDevil 5700XT and for me, Kernel 5.4-rc1 just works. Memory clocks always at 100Mhz when idle, even using KDE (Plasma 5.16). amdgpu-pci-0a00 Adapter: PCI adapter vddgfx: +0.72 V

[drm-tip:drm-tip 548/565] drivers/gpu/drm/i915/gem/i915_gem_context.c:813:29: sparse: sparse: incorrect type in argument 1 (different address spaces)

2019-10-05 Thread kbuild test robot
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip head: f99065c68952afc90504325a19125d95e6b84abc commit: a4e7ccdac38ec8335d9e4e2656c1a041c77feae1 [548/565] drm/i915: Move context management under GEM reproduce: # apt-get install sparse # sparse version:

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-05 Thread Keith Packard
Robert Foss writes: > Hey Keith, > > Thanks for setting this up, and picking a descriptive project name :) > > How is liboutput going to relate to the libliftoff[1] project? We heard about libliftoff at XDC. It sounds like it does the plane selection stuff, including searching for

[Bug 205093] [amdgpu] resume of IP block failed -110

2019-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205093 --- Comment #1 from Marcin P (kat.zygf...@gmail.com) --- Created attachment 285361 --> https://bugzilla.kernel.org/attachment.cgi?id=285361=edit Full dmesg on 5.2.8 -- You are receiving this mail because: You are watching the assignee of the

[Bug 205093] New: [amdgpu] resume of IP block failed -110

2019-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205093 Bug ID: 205093 Summary: [amdgpu] resume of IP block failed -110 Product: Drivers Version: 2.5 Kernel Version: 5.2.13 Hardware: x86-64 OS: Linux Tree:

[Bug 111481] AMD Navi GPU frequent freezes on both Manjaro/Ubuntu with kernel 5.3 and mesa 19.2 -git/llvm9

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111481 --- Comment #75 from Marko Popovic --- (In reply to ans.belfodil from comment #73) > According to this > https://www.phoronix.com/scan.php?page=news_item=AMDGPU-Bulk-Moves-Lands > and my tests (Linux 5.3.1 and packages from >

[Bug 111229] Unable to unbind GPU from amdgpu

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111229 --- Comment #10 from Eugene Shatsky --- I confirm that on on 5.3-rc7 I could unbind/bind RX470 multiple times and shut the system down cleanly afterwards. Got some warning with a trace in dmesg, now going to check if this does affect system

Re: liboutput: thoughts about shared library on top of DRM/KMS

2019-10-05 Thread Robert Foss
Hey Keith, Thanks for setting this up, and picking a descriptive project name :) How is liboutput going to relate to the libliftoff[1] project? [1] https://github.com/emersion/libliftoff Rob. On 05.10.19 18:09, Keith Packard wrote: During XDC this year, we heard a few presentations and

Re: [PATCH] drm/amdkfd: add missing void argument to function kgd2kfd_init

2019-10-05 Thread Colin Ian King
On 05/10/2019 19:10, Randy Dunlap wrote: > On 10/5/19 10:58 AM, Colin King wrote: >> From: Colin Ian King >> >> Function kgd2kfd_init is missing a void argument, add it >> to clean up the non-ANSI function declaration. >> >> Signed-off-by: Colin Ian King > > Acked-by: Randy Dunlap > > sparse

Re: [PATCH] backlight: lm3630a: fix module aliases

2019-10-05 Thread Andreas Kemnade
Hi, hmm, this bugfix has not arrived in -next or any -fixes branch I am aware of yet. I hope it is not forgotten... so a friendly ping. Regards, Andreas On Wed, 11 Sep 2019 11:51:48 +0100 Daniel Thompson wrote: > On Tue, Sep 10, 2019 at 05:23:59PM +0200, Andreas Kemnade wrote: > > Devicetree

[PATCH] drm/amdkfd: add missing void argument to function kgd2kfd_init

2019-10-05 Thread Colin King
From: Colin Ian King Function kgd2kfd_init is missing a void argument, add it to clean up the non-ANSI function declaration. Signed-off-by: Colin Ian King --- drivers/gpu/drm/amd/amdkfd/kfd_module.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[Bug 111481] AMD Navi GPU frequent freezes on both Manjaro/Ubuntu with kernel 5.3 and mesa 19.2 -git/llvm9

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111481 --- Comment #74 from ans.belfo...@gmail.com --- Woops copied the wrong link from Phoronix: https://www.phoronix.com/scan.php?page=news_item=RADV-Navi-Random-Hangs-19.3 -- You are receiving this mail because: You are the assignee for the

[Bug 111481] AMD Navi GPU frequent freezes on both Manjaro/Ubuntu with kernel 5.3 and mesa 19.2 -git/llvm9

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111481 --- Comment #73 from ans.belfo...@gmail.com --- According to this https://www.phoronix.com/scan.php?page=news_item=AMDGPU-Bulk-Moves-Lands and my tests (Linux 5.3.1 and packages from https://pkgbuild.com/~lcarlier/mesa-git/x86_64/), the hangs

[PATCH 4/5] drm/amd/display: Remove set but not used variable 'pixel_width'

2019-10-05 Thread zhengbin
Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/amd/display/dc/dcn20/dcn20_dpp.c: In function dpp2_get_optimal_number_of_taps: drivers/gpu/drm/amd/display/dc/dcn20/dcn20_dpp.c:359:11: warning: variable pixel_width set but not used [-Wunused-but-set-variable] It is not used since

[PATCH 0/6] drm/msm/dpu: Remove some set but not used variables

2019-10-05 Thread zhengbin
zhengbin (6): drm/msm/dpu: Remove set but not used variable 'priv' in dpu_kms.c drm/msm/dpu: Remove set but not used variable 'priv' in dpu_encoder_phys_vid.c drm/msm/dpu: Remove set but not used variable 'priv' in dpu_core_irq.c drm/msm/dpu: Remove set but not used variables

[PATCH 3/5] drm/amd/display: Remove set but not used variables 'h_ratio_chroma', 'v_ratio_chroma'

2019-10-05 Thread zhengbin
Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/amd/display/dc/dcn20/dcn20_dwb_scl.c: In function dwb_program_horz_scalar: drivers/gpu/drm/amd/display/dc/dcn20/dcn20_dwb_scl.c:725:11: warning: variable h_ratio_chroma set but not used [-Wunused-but-set-variable]

[PATCH] drm/amd/display: Make some functions static

2019-10-05 Thread zhengbin
Fix sparse warnings: drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_hdcp.c:32:6: warning: symbol 'lp_write_i2c' was not declared. Should it be static? drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_hdcp.c:42:6: warning: symbol 'lp_read_i2c' was not declared. Should it be

[PATCH] drm/amd/display: Fix typo in some comments

2019-10-05 Thread Christophe JAILLET
p and g are switched in 'amdpgu_dm' Signed-off-by: Christophe JAILLET --- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c

[PATCH 3/6] drm/msm/dpu: Remove set but not used variable 'priv' in dpu_core_irq.c

2019-10-05 Thread zhengbin
Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/msm/disp/dpu1/dpu_core_irq.c: In function dpu_core_irq_preinstall: drivers/gpu/drm/msm/disp/dpu1/dpu_core_irq.c:354:26: warning: variable priv set but not used [-Wunused-but-set-variable]

[PATCH 1/6] drm/msm/dpu: Remove set but not used variable 'priv' in dpu_kms.c

2019-10-05 Thread zhengbin
Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c: In function _dpu_danger_signal_status: drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c:80:26: warning: variable priv set but not used [-Wunused-but-set-variable] drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c: In function

[PATCH 4/6] drm/msm/dpu: Remove set but not used variables 'dpu_cstate', 'priv'

2019-10-05 Thread zhengbin
Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/msm/disp/dpu1/dpu_core_perf.c: In function dpu_core_perf_crtc_release_bw: drivers/gpu/drm/msm/disp/dpu1/dpu_core_perf.c:248:25: warning: variable dpu_cstate set but not used [-Wunused-but-set-variable]

[PATCH 6/6] drm/msm/dpu: Remove set but not used variables 'mode', 'dpu_kms', 'priv'

2019-10-05 Thread zhengbin
Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c: In function dpu_encoder_virt_disable: drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c:1199:27: warning: variable mode set but not used [-Wunused-but-set-variable] drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c:

[PATCH v19 0/2] PS8640 MIPI-to-eDP bridge

2019-10-05 Thread Ulrich Hecht
Hi! This driver seems to have fallen by the wayside because, while otherwise fine, it has a firmware update feature that requires a blob that is not in the linux-firmware repo.[1] Whatever the cause for that may be, the update code is entirely optional (my chip works fine with whatever firmware

[PATCH v19 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

2019-10-05 Thread Ulrich Hecht
From: Jitao Shi This patch adds drm_bridge driver for parade DSI to eDP bridge chip. Signed-off-by: Jitao Shi Reviewed-by: Daniel Kurtz Reviewed-by: Enric Balletbo i Serra [uli: followed API changes, removed FW update feature] Signed-off-by: Ulrich Hecht --- Changes since v18: - followed

[PATCH 2/6] drm/msm/dpu: Remove set but not used variable 'priv' in dpu_encoder_phys_vid.c

2019-10-05 Thread zhengbin
Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_vid.c: In function dpu_encoder_phys_vid_disable: drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_vid.c:566:26: warning: variable priv set but not used [-Wunused-but-set-variable] It is not used since

[PATCH 1/5] drm/amd/display: Make function wait_for_alt_mode static

2019-10-05 Thread zhengbin
Fix sparse warnings: drivers/gpu/drm/amd/display/dc/core/dc_link.c:687:6: warning: symbol 'wait_for_alt_mode' was not declared. Should it be static? Reported-by: Hulk Robot Signed-off-by: zhengbin --- drivers/gpu/drm/amd/display/dc/core/dc_link.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v19 1/2] Documentation: bridge: Add documentation for ps8640 DT properties

2019-10-05 Thread Ulrich Hecht
From: Jitao Shi Add documentation for DT properties supported by ps8640 DSI-eDP converter. Signed-off-by: Jitao Shi Acked-by: Rob Herring Reviewed-by: Philipp Zabel Signed-off-by: Ulrich Hecht --- Changes since v18: - No change. Changes since v17: - No change. Changes since v16: - No

Re: linux-next: Tree for Oct 4 (amdgpu)

2019-10-05 Thread Randy Dunlap
On 10/3/19 10:59 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20191003: > on x86_64: CONFIG_DRM_AMDGPU=y # CONFIG_DRM_AMDGPU_SI is not set # CONFIG_DRM_AMDGPU_CIK is not set CONFIG_DRM_AMDGPU_USERPTR=y CONFIG_DRM_AMDGPU_GART_DEBUGFS=y ld:

[PATCH 5/5] drm/amd/display: Remove set but not used variables 'pp_smu', 'old_pipe'

2019-10-05 Thread zhengbin
Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/amd/display/dc/dce110/dce110_hw_sequencer.c: In function dce110_enable_audio_stream: drivers/gpu/drm/amd/display/dc/dce110/dce110_hw_sequencer.c:949:23: warning: variable pp_smu set but not used [-Wunused-but-set-variable]

[PATCH 5/6] drm/msm/dpu: Remove set but not used variables 'cmd_enc', 'priv'

2019-10-05 Thread zhengbin
Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c: In function dpu_encoder_phys_cmd_ctl_start_irq: drivers/gpu/drm/msm/disp/dpu1/dpu_encoder_phys_cmd.c:136:31: warning: variable cmd_enc set but not used [-Wunused-but-set-variable]

[PATCH 2/5] drm/amd/display: Remove set but not used variable 'source_bpp'

2019-10-05 Thread zhengbin
Fixes gcc '-Wunused-but-set-variable' warning: drivers/gpu/drm/amd/display/dc/dsc/rc_calc.c: In function calc_rc_params: drivers/gpu/drm/amd/display/dc/dsc/rc_calc.c:180:6: warning: variable source_bpp set but not used [-Wunused-but-set-variable] It is not used since commit 97bda0322b8a

[PATCH 0/5] drm/amd/display: some fixes for gcc warning

2019-10-05 Thread zhengbin
zhengbin (5): drm/amd/display: Make function wait_for_alt_mode static drm/amd/display: Remove set but not used variable 'source_bpp' drm/amd/display: Remove set but not used variables 'h_ratio_chroma','v_ratio_chroma' drm/amd/display: Remove set but not used variable 'pixel_width'

Re: [PATCH 03/11] drm/amdgpu: convert amdgpu_vm_it to half closed intervals

2019-10-05 Thread Michel Lespinasse
On Fri, Oct 04, 2019 at 06:54:54AM +, Koenig, Christian wrote: > Am 03.10.19 um 22:18 schrieb Davidlohr Bueso: > > The amdgpu_vm interval tree really wants [a, b) intervals, > > NAK, we explicitly do need an [a, b[ interval here. Hi Christian, Just wanted to confirm where you stand on this

liboutput: thoughts about shared library on top of DRM/KMS

2019-10-05 Thread "Keith Packard"
During XDC this year, we heard a few presentations and had a lot of hallway talk about sharing code for driving DRM/KMS for display. I think the general consensus is that there is enough shared functionality between all of the various DRM/KMS clients that we can start thinking about building a

Re: [PATCH] drm/imx: fix memory leak in imx_pd_bind

2019-10-05 Thread Markus Elfring
> In imx_pd_bind, the duplicated memory for imxpd->edid via kmemdup should > be released in drm_of_find_panel_or_bridge or imx_pd_register fail. Please improve this change description. > +++ b/drivers/gpu/drm/imx/parallel-display.c > @@ -227,14 +227,18 @@ static int imx_pd_bind(struct device

[DO NOT MERGE] [PATCH v10 6/6] arm64: dts: allwinner: bananapi-m64: Enable Bananapi S070WV20-CT16 DSI panel

2019-10-05 Thread Jagan Teki
This patch add support for Bananapi S070WV20-CT16 DSI panel to BPI-M64 board. DSI panel connected via board DSI port with, - DLDO1 as VCC-DSI supply - DCDC1 as VDD supply - PD7 gpio for lcd enable pin - PD6 gpio for lcd reset pin - PD5 gpio for backlight enable pin Signed-off-by: Jagan Teki ---

[PATCH v10 5/6] arm64: dts: allwinner: a64: Add MIPI DSI pipeline

2019-10-05 Thread Jagan Teki
Add MIPI DSI pipeline for Allwinner A64. - dsi node, with A64 compatible since it doesn't support DSI_SCLK gating unlike A33 - dphy node, with A64 compatible with A33 fallback since DPHY on A64 and A33 is similar - finally, attach the dsi_in to tcon0 for complete MIPI DSI Signed-off-by:

[PATCH v10 3/6] drm/sun4i: dsi: Add has_mod_clk quirk

2019-10-05 Thread Jagan Teki
As per the user manual, look like mod clock is not mandatory for all Allwinner MIPI DSI controllers, it is connected to CLK_DSI_SCLK for A31 and not available in A64. So add has_mod_clk quirk and process the clk accordingly. Tested-by: Merlijn Wajer Signed-off-by: Jagan Teki ---

[PATCH v10 4/6] drm/sun4i: dsi: Add Allwinner A64 MIPI DSI support

2019-10-05 Thread Jagan Teki
The MIPI DSI controller in Allwinner A64 is similar to A33. But unlike A33, A64 doesn't have DSI_SCLK gating so add compatible for Allwinner A64 with uninitialized has_mod_clk driver. Signed-off-by: Jagan Teki Tested-by: Merlijn Wajer --- drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c | 7 +++ 1

[PATCH v10 2/6] dt-bindings: sun6i-dsi: Add A64 DPHY compatible (w/ A31 fallback)

2019-10-05 Thread Jagan Teki
The MIPI DSI PHY controller on Allwinner A64 is similar on the one on A31. Add A64 compatible and append A31 compatible as fallback. Signed-off-by: Jagan Teki --- .../bindings/phy/allwinner,sun6i-a31-mipi-dphy.yaml | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH v10 0/6] drm/sun4i: Allwinner A64 MIPI-DSI support

2019-10-05 Thread Jagan Teki
This is v10 version for Allwinner A64 MIPI-DSI support and here is the previous version set[1]. This series on top of drm-misc/for-linux-next along with video start delay fix [2] Changes for v10: - updated dt-bindings as per .yaml format - rebased on drm-misc/for-linux-next Changes for v9: -

[PATCH v10 1/6] dt-bindings: sun6i-dsi: Add A64 MIPI-DSI compatible

2019-10-05 Thread Jagan Teki
The MIPI DSI controller in Allwinner A64 is similar to A33. But unlike A33, A64 doesn't have DSI_SCLK gating so it is valid to with separate compatible for A64 on the same driver. Signed-off-by: Jagan Teki --- .../bindings/display/allwinner,sun6i-a31-mipi-dsi.yaml| 4 +++- 1 file

[Bug 201539] AMDGPU R9 390 automatic fan speed control in Linux 4.19/4.20/5.0

2019-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201539 --- Comment #20 from artheg (art...@gmail.com) --- To anyone who's still struggling with this, perhaps this would be of help: I'm using this script (https://github.com/grmat/amdgpu-fancontrol) as a service, with these params: TEMPS=( 65000

[Bug 111232] 3200 Memory Crash My System

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111232 --- Comment #11 from bibitocarlos --- Any idea ? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org

[Bug 111482] Sapphire Pulse RX 5700 XT power consumption

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111482 --- Comment #24 from Sylvain BERTRAND --- Hi, popping to say it may be the same on southern islands (tahiti xt). -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 109955] amdgpu [RX Vega 64] system freeze while gaming

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109955 --- Comment #113 from Jason Playne --- As others have noted, with powerplay doing its thing we get system freezes. Just had a successful 6+ hour gaming session on a kernel 5.3.2-050302-generic with the following being done: * Forcing high

[Bug 111482] Sapphire Pulse RX 5700 XT power consumption

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111482 --- Comment #23 from Andrew Sheldon --- @Leon I suspect there is more than one bug occurring. The main Navi-specific issue has been fixed with newer kernels (that affected everyone), but there is another issue relating to high resolution and

[Bug 204725] black screen

2019-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204725 --- Comment #53 from Dmitri Seletski (drj...@gmail.com) --- made minor error. compiled 5.4r1 compiled in 'DCN 2.1 family'. I don't hardware for it. With it and DCN 2.0 i get console. I get to see Xorg. though not sure if it's vesa or not, because

[Bug 205089] New: amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125

2019-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=205089 Bug ID: 205089 Summary: amdgpu : drm:amdgpu_cs_ioctl : Failed to initialize parser -125 Product: Drivers Version: 2.5 Kernel Version: 5.3.2 Hardware: All

Re: [PATCH v19 0/2] PS8640 MIPI-to-eDP bridge

2019-10-05 Thread Matthias Brugger
Hi Uli, On 04/10/2019 21:09, Ulrich Hecht wrote: > Hi! > > This driver seems to have fallen by the wayside because, while otherwise > fine, it has a firmware update feature that requires a blob that is not in > the linux-firmware repo.[1] > > Whatever the cause for that may be, the update code

[Bug 204241] amdgpu fails to resume from suspend

2019-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204241 --- Comment #15 from Andreas Jackisch (andreas.jacki...@gmail.com) --- (In reply to Ahzo from comment #14) > Created attachment 285349 [details] > Patch to prevent frequent resume failures > > Another way to prevent these frequent resume

[Bug 109955] amdgpu [RX Vega 64] system freeze while gaming

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=109955 --- Comment #112 from Jan Orsag --- screenfetch ██ johanides@johanides-manjaro ██ OS: Manjaro 18.1.0 Juhraya ██ Kernel: x86_64 Linux 4.19.69-1-MANJARO

Re: [PATCH] drm: lima: Add support for multiple reset lines

2019-10-05 Thread Qiang Yu
On Wed, Oct 2, 2019 at 2:29 AM John Stultz wrote: > > From: Peter Griffin > > Some SoCs like HiKey have 2 reset lines, so update > to use the devm_reset_control_array_* variant of the > API so that multiple resets can be specified in DT. > > Cc: Qiang Yu > Cc: David Airlie > Cc: Daniel Vetter

[Bug 204683] amdgpu: ring sdma0 timeout

2019-10-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204683 --- Comment #11 from Matthias Heinz (m...@familie-heinz.name) --- The bug is still present in linux 5.3. Also I'm not done yet bisecting. But the older kernels seem to have nasty fs bugs and I'm not sure if I'm really willing to put my data on

[Bug 111803] Annoying GPU stucks are continued on Vega 20 with Kernel 5.4 + mesa 9.3.0 + llvm 9.0.0 [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111803 --- Comment #32 from mikhail.v.gavri...@gmail.com --- Created attachment 145661 --> https://bugs.freedesktop.org/attachment.cgi?id=145661=edit dmesg -- You are receiving this mail because: You are the assignee for the

[Bug 111803] Annoying GPU stucks are continued on Vega 20 with Kernel 5.4 + mesa 9.3.0 + llvm 9.0.0 [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111803 --- Comment #31 from mikhail.v.gavri...@gmail.com --- Created attachment 145660 --> https://bugs.freedesktop.org/attachment.cgi?id=145660=edit ./umr -O many,bits -r *.*.mmCP_ME_HEADER_DUMP -- You are receiving this mail because: You are the

[Bug 111803] Annoying GPU stucks are continued on Vega 20 with Kernel 5.4 + mesa 9.3.0 + llvm 9.0.0 [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111803 --- Comment #30 from mikhail.v.gavri...@gmail.com --- Created attachment 145659 --> https://bugs.freedesktop.org/attachment.cgi?id=145659=edit ./umr -O many,bits -r *.*.mmCP_PFP_HEADER_DUMP -- You are receiving this mail because: You are the

[Bug 111803] Annoying GPU stucks are continued on Vega 20 with Kernel 5.4 + mesa 9.3.0 + llvm 9.0.0 [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111803 --- Comment #29 from mikhail.v.gavri...@gmail.com --- Created attachment 145658 --> https://bugs.freedesktop.org/attachment.cgi?id=145658=edit ./umr -O many,bits -r *.*.mmCP_EOP_* -- You are receiving this mail because: You are the assignee

[Bug 111803] Annoying GPU stucks are continued on Vega 20 with Kernel 5.4 + mesa 9.3.0 + llvm 9.0.0 [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111803 --- Comment #28 from mikhail.v.gavri...@gmail.com --- Created attachment 145657 --> https://bugs.freedesktop.org/attachment.cgi?id=145657=edit ./umr -O many,bits -r *.*.mmGRBM_STATUS* -- You are receiving this mail because: You are the

[Bug 111803] Annoying GPU stucks are continued on Vega 20 with Kernel 5.4 + mesa 9.3.0 + llvm 9.0.0 [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111803 --- Comment #27 from mikhail.v.gavri...@gmail.com --- Created attachment 145656 --> https://bugs.freedesktop.org/attachment.cgi?id=145656=edit ./umr -R gfx[.] -- You are receiving this mail because: You are the assignee for the

[Bug 111803] Annoying GPU stucks are continued on Vega 20 with Kernel 5.4 + mesa 9.3.0 + llvm 9.0.0 [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!

2019-10-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111803 --- Comment #26 from mikhail.v.gavri...@gmail.com --- Created attachment 145655 --> https://bugs.freedesktop.org/attachment.cgi?id=145655=edit ./umr -O halt_waves -wa -- You are receiving this mail because: You are the assignee for the