Renoir: visual artifacts associated with scrolling

I am dealing with visual artifacts on my laptop. I'm not sure if screendumps are OK on this list so I will try to describe the two vulnerable applications I identified so far. Both of them can be healed by forcing a full redraws (changing workspace back and forth, minimizing and maximizing window

Re: [PATCH 1/1] drm/amdgpu: fix NULL pointer dereference for Renoir

Dirk Gouders writes: > Commit c1cf79ca5ced46 (drm/amdgpu: use IP discovery table for renoir) > introduced a NULL pointer dereference when booting with > amdgpu.discovery=0, because it removed the call of vega10_reg_base_init() > for that case. > > Fix this by calli

[PATCH 0/1] drm/amdgpu: fix NULL pointer dereference for Renoir

Alex Deucher writes: > On Wed, Sep 30, 2020 at 4:46 PM Dirk Gouders wrote: >> >> Commit c1cf79ca5ced46 (drm/amdgpu: use IP discovery table for renoir) >> introduced a NULL pointer dereference when booting with >> amdgpu.discovery=0. >> >> For amdgpu.disc

[PATCH 1/1] drm/amdgpu: fix NULL pointer dereference for Renoir

that amdgpu_discovery_reg_base_init() failed. Fixes: c1cf79ca5ced46 (drm/amdgpu: use IP discovery table for renoir) Signed-off-by: Dirk Gouders Cc: Hawking Zhang Cc: Evan Quan --- drivers/gpu/drm/amd/amdgpu/soc15.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a

BUG: amdgpu: NULL pointer dereference introduced in 5.9-rc1

Commit c1cf79ca5ced46 (drm/amdgpu: use IP discovery table for renoir) introduced a NULL pointer dereference when booting with amdgpu.discovery=0. For amdgpu.discovery=0 that commit effectively removed the call of vega10_reg_base_init(adev), so I tested the correctness of the bisect session by rest

Re: [PATCH] drm/amd/pm: setup APU dpm clock table in SMU HW initialization

so wonder if we probably want a fixes-line for completeness: Fixes: 02cf91c113ea (drm/amd/powerplay: postpone operations not required for hw setup to late_init) Dirk > Change-Id: I2bb1f9ba26f9c8820c08241da62f7be64ab75840 > Signed-off-by: Evan Quan > Reported-by: Dirk Gouders >

Re: amdgpu: call trace introduced in 5.9-rc1 for Lenovo L14 Renoir

Alex Deucher writes: > On Wed, Sep 23, 2020 at 3:45 PM Dirk Gouders wrote: >> >> Dirk Gouders writes: >> >> > Alex Deucher writes: >> > >> >> On Wed, Sep 23, 2020 at 8:54 AM Dirk Gouders wrote: >> >>> >> >>> D

[PATCH] drm/amd/display: remove duplicate call to rn_vbios_smu_get_smu_version()

oor for Certain SMU Versions) Signed-off-by: Dirk Gouders Cc: Alex Deucher Cc: Sung Lee Cc: Yongqiang Sun Cc: Rodrigo Siqueira --- drivers/gpu/drm/amd/display/dc/clk_mgr/dcn21/rn_clk_mgr.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/amd/display/dc/clk_mgr/dcn21/rn_clk_mg

Re: amdgpu: call trace introduced in 5.9-rc1 for Lenovo L14 Renoir

Dirk Gouders writes: > Alex Deucher writes: > >> On Wed, Sep 23, 2020 at 8:54 AM Dirk Gouders wrote: >>> >>> Dirk Gouders writes: >>> >>> > Hi, >>> > >>> > I noticed a call trace (attached) when starting my machin

Re: amdgpu: call trace introduced in 5.9-rc1 for Lenovo L14 Renoir

Alex Deucher writes: > On Wed, Sep 23, 2020 at 8:54 AM Dirk Gouders wrote: >> >> Dirk Gouders writes: >> >> > Hi, >> > >> > I noticed a call trace (attached) when starting my machine (ThinkPad >> > L14). This machine is new and I

Re: amdgpu: call trace introduced in 5.9-rc1 for Lenovo L14 Renoir

Dirk Gouders writes: > Hi, > > I noticed a call trace (attached) when starting my machine (ThinkPad > L14). This machine is new and I am still working on it's > configuration but visually noticeable is that scrolling in xterms with > SHIFT-PgUp/PgDn is broken. Usin

amdgpu: call trace introduced in 5.9-rc1 for Lenovo L14 Renoir

Hi, I noticed a call trace (attached) when starting my machine (ThinkPad L14). This machine is new and I am still working on it's configuration but visually noticeable is that scrolling in xterms with SHIFT-PgUp/PgDn is broken. Using the mouse wheel works. It seems the call trace has been intro