[Bug 262043] update of drm-*kmod breaks AMD GPU support

From: <bugzilla-noreply_at_freebsd.org>
Date: Fri, 18 Feb 2022 21:28:02 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262043

            Bug ID: 262043
           Summary: update of drm-*kmod breaks AMD GPU support
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: se@FreeBSD.org

The update of drm-devel-kmod to 5.7.19.g20220126 (commit 0c38674b389ad) broke
support for my AMD GPU of type Radeon R7 250E (but probably many other AMD
cards, too).

The probe and attach proceeds to the point where the final parameter set is
chosen and the frame buffer made available.

[drm] AMDGPU Display Connectors
[drm] Connector 0:
[drm]   DP-1
[drm]   HPD4
[drm]   DDC: 0x1950 0x1950 0x1951 0x1951 0x1952 0x1952 0x1953 0x1953
[drm]   Encoders:
[drm]     DFP1: INTERNAL_UNIPHY2
[drm] Connector 1:
[drm]   HDMI-A-1
[drm]   HPD1
[drm]   DDC: 0x195c 0x195c 0x195d 0x195d 0x195e 0x195e 0x195f 0x195f
[drm]   Encoders:
[drm]     DFP2: INTERNAL_UNIPHY2
[drm] Connector 2:
[drm]   DVI-I-1
[drm]   HPD2
[drm]   DDC: 0x1958 0x1958 0x1959 0x1959 0x195a 0x195a 0x195b 0x195b
[drm]   Encoders:
[drm]     DFP3: INTERNAL_UNIPHY
[drm]     CRT1: INTERNAL_KLDSCP_DAC1
drmn0: [drm] Cannot find any crtc or sizes
drmn0: [drm] Cannot find any crtc or sizes
drmn0: [drm] Cannot find any crtc or sizes
[drm] Initialized amdgpu 3.37.0 20150101 for drmn0 on minor 0

The previous, working driver version showed the following final attach message
lines:

[drm]   Encoders:
[drm]     DFP3: INTERNAL_UNIPHY
[drm]     CRT1: INTERNAL_KLDSCP_DAC1
[drm] fb mappable at 0xE0503000
[drm] vram apper at 0xE0000000
[drm] size 33177600
[drm] fb depth is 24
[drm]    pitch is 15360
[drm] Initialized amdgpu 3.36.0 20150101 for drmn0 on minor 0

It seems that the I2C code changed significantly between the working and broken
version, but I do not know where to start debugging/diagnosing the issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.