[AMD tahiti xt] amd-staging-drm-next broken since linux 5.3.0-rc3 rebase

Submitted by Sylvain BERTRAND

Assigned to Default DRI bug account

Link to original bug (#111792)

Description

got the rebased amd-staging-drm-next branch today, configured and compiled linux, xorg hangs while probing card0. See provided logs.

yes, I can bisect.

added AMDgpu bugzilla labels

Sylvain BERTRAND uploaded an attachment:

Attachment 145480, "dmesg":
dmesg.5.3.0-rc3-1+

Sylvain BERTRAND uploaded an attachment:

Attachment 145481, "xorg":
Xorg.0.log.5.3.0-rc3-1+

Sylvain BERTRAND said:

This bisection is kind of a pain, as usual on the 'rebase breakage'. I had to
start manually to find a "segment" with good enough good/bad data for bisect.
On this bisected segment, amd-staging-drm-next branch, the first bad commit is:

commit 1929059893022a3bbed43934c7313e66aad7346b
Author: Prike Liang Prike.Liang@amd.com
Date: Mon May 27 16:05:50 2019 +0800

drm/amd/amdgpu: add RLC firmware to support raven1 refresh

Use SMU firmware version to indentify the raven1 refresh device and
then load homologous RLC FW.

Signed-off-by: Prike Liang Prike.Liang@amd.com
Suggested-by: Huang RuiRay.Huang@amd.com
Reviewed-by: Huang Rui ray.huang@amd.com
Reviewed-by: Evan Quan evan.quan@amd.com
Signed-off-by: Alex Deucher alexander.deucher@amd.com

Alex Deucher @agd5f said:

The commit was fixed by:

commit 0079f82e710caf3e821267917af9517ac0fca83d
Author: Alex Deucher alexander.deucher@amd.com
Date: Tue Jun 11 09:45:51 2019 -0500

drm/amdgpu: return 0 by default in amdgpu_pm_load_smu_firmware

Fixes SI cards running on amdgpu.

Fixes: 1929059893022 ("drm/amd/amdgpu: add RLC firmware to support raven1 refresh")
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=110883
Reviewed-by: Evan Quan evan.quan@amd.com
Signed-off-by: Alex Deucher alexander.deucher@amd.com

Sylvain BERTRAND said:

got some sleep then I noticed I have the wrong kernel log message. My bad.

The kernel module is crashing in DP code. see the call stack in the about to be updated kernel log.

Sylvain BERTRAND uploaded an attachment:

Attachment 145511, "good kernel log":
dmesg.5.3.0-rc3-1+

Alex Deucher @agd5f said:

You need this patch:
https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-next-fixes&id=e0f32f78e51b9989ee89f608fd0dd10e9c230652

Sylvain BERTRAND said:

Applied the patch on top of amd-staging-drm-next 4a6c7afe7d1acc6d2f4b94d62843c72cbf2c60a5, fixed.

Is still ok to use amd-staging-drm-next or community "testers" should use another one?

Alex Deucher @agd5f said:

I'll add the patch to amd-staging-drm-next as well.

Sylvain BERTRAND said:

And us "community testers"? Should we be using drm-misc-next-fixes instead of amd-staging-drm-next?

Alex Deucher @agd5f said:

you can use whichever branches you want.

Sylvain BERTRAND said:

What are the differences then?

Alex Deucher @agd5f said:

(In reply to Sylvain BERTRAND from comment 12)

What are the differences then?

for my git repo:
- amd-staging-drm-next is our internal integration branch.
- drm-next is all of our new code for the next kernel integrated into airlied's drm-next tree
- drm-fixes is fixes for the current kernel cycle

Sylvain BERTRAND said:

I seems I should stay on amd-staging-drm-next then.

This issue hasn't had any activity since 2019-11-19. The AMD driver stack changes rapidly and contains lots of shared code across products so it's possible that it has already been fixed. Please upgrade to a current stable kernel and userspace stack and try again. If you still experience this issue with the latest driver stack, please capture relevant logging and open a new issue referring back to this one.

closed