| Bug ID | 111792 |
|---|---|
| Summary | [AMD tahiti xt] amd-staging-drm-next broken since linux 5.3.0= -rc3 rebase |
| Product | DRI |
| Version | XOrg git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | blocker |
| Priority | highest |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | sylvain.bertrand@gmail.com |
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.
Created attachment 145480 [details]<=
/span>
dmesg
This bisection is kind of a pain, as usual on the 'rebase brea= kage'. 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.Li= ang@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 Rui<Ray= .Huang@amd.com> Reviewed-by: Huang Rui <ray= .huang@amd.com> Reviewed-by: Evan Quan <eva= n.quan@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
The commit was fixed by: commit 0079f82e710caf3e821267917af9517ac0fca83d Author: Alex Deucher <a= lexander.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=3D110883 Reviewed-by: Evan Quan <eva= n.quan@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
got some sleep then I noticed I have the wrong kernel log mess= age. My bad. The kernel module is crashing in DP code. see the call stack in the about t= o be updated kernel log.
| What | Removed | Added |
|---|---|---|
| Attachment #145481 is obsolete | 1 |
Created attachment 145511 [details]
good kernel log
You need this patch: https://cgit.f= reedesktop.org/drm/drm-misc/commit/?h=3Ddrm-misc-next-fixes&id=3De0f32f= 78e51b9989ee89f608fd0dd10e9c230652
Applied the patch on top of amd-staging-drm-next 4a6c7afe7d1acc6d2f4b94d62843c72cbf2c60a5, fixed. Is still ok to use amd-staging-drm-next or community "testers" sh= ould use another one?
And us "community testers"? Should we be using drm-m= isc-next-fixes instead of amd-staging-drm-next?
(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 airli= ed's drm-next tree - drm-fixes is fixes for the current kernel cycle
I seems I should stay on amd-staging-drm-next then.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/915.