Date: Sun, 30 Jan 2022 20:43:09 +0100 From: Stefan Esser <se@FreeBSD.org> To: Vladimir Kondratyev <wulf@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: Kernel changes causing AMDGPU / DRM to fail? i2c related? Message-ID: <c415393e-1cf0-2f7f-36c8-9d4bde73cfdc@FreeBSD.org> In-Reply-To: <4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org> References: <a9560156-4d67-7ca2-e276-31e5585ce58e@FreeBSD.org> <4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------------LSTiDFrbrdXqddmjn0y2I3nT
Content-Type: multipart/mixed; boundary="------------6yDW8Sj3j0b6bNZBv5ak18Jq";
protected-headers="v1"
From: Stefan Esser <se@FreeBSD.org>
To: Vladimir Kondratyev <wulf@FreeBSD.org>
Cc: freebsd-current@freebsd.org
Message-ID: <c415393e-1cf0-2f7f-36c8-9d4bde73cfdc@FreeBSD.org>
Subject: Re: Kernel changes causing AMDGPU / DRM to fail? i2c related?
References: <a9560156-4d67-7ca2-e276-31e5585ce58e@FreeBSD.org>
<4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org>
In-Reply-To: <4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org>
--------------6yDW8Sj3j0b6bNZBv5ak18Jq
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Am 30.01.22 um 19:23 schrieb Vladimir Kondratyev:
> On 30.01.2022 00:25, Stefan Esser wrote:
>> After rebooting with freshly built world, kernel and the amdgpu driver=
>> my console stopped working. It goes blank and the display goes into a
>> power save mode, as soon as the amdgpu driver is loaded.
>>
>> The GPU (a Radeon R7 250E) is correctly detected as before, but there
>> is an error message "drmn0: [drm] Cannot find any crtc or sizes".
>>
[...]
>> [drm] AMDGPU Display Connectors
>> [drm] Connector 0:
>> [drm]=C2=A0=C2=A0 DP-1
>> [drm]=C2=A0=C2=A0 HPD4
>> [drm]=C2=A0=C2=A0 DDC: 0x1950 0x1950 0x1951 0x1951 0x1952 0x1952 0x195=
3 0x1953
>> [drm]=C2=A0=C2=A0 Encoders:
>> [drm]=C2=A0=C2=A0=C2=A0=C2=A0 DFP1: INTERNAL_UNIPHY2
>> [drm] Connector 1:
>> [drm]=C2=A0=C2=A0 HDMI-A-1
>> [drm]=C2=A0=C2=A0 HPD1
>> [drm]=C2=A0=C2=A0 DDC: 0x195c 0x195c 0x195d 0x195d 0x195e 0x195e 0x195=
f 0x195f
>> [drm]=C2=A0=C2=A0 Encoders:
>> [drm]=C2=A0=C2=A0=C2=A0=C2=A0 DFP2: INTERNAL_UNIPHY2
>> [drm] Connector 2:
>> [drm]=C2=A0=C2=A0 DVI-I-1
>> [drm]=C2=A0=C2=A0 HPD2
>> [drm]=C2=A0=C2=A0 DDC: 0x1958 0x1958 0x1959 0x1959 0x195a 0x195a 0x195=
b 0x195b
>> [drm]=C2=A0=C2=A0 Encoders:
>> [drm]=C2=A0=C2=A0=C2=A0=C2=A0 DFP3: INTERNAL_UNIPHY
>> [drm]=C2=A0=C2=A0=C2=A0=C2=A0 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
>>
>> A successful driver attach from a reboot a few days ago had ended in:
>>
>> [drm]=C2=A0=C2=A0=C2=A0=C2=A0 CRT1: INTERNAL_KLDSCP_DAC1
>> [drm] fb mappable at 0xE0503000
>> [drm] vram apper at 0xE0000000
>> [drm] size 33177600
>> [drm] fb depth is 24
>> [drm]=C2=A0=C2=A0=C2=A0 pitch is 15360
>> [drm] Initialized amdgpu 3.36.0 20150101 for drmn0 on minor 0
>>
>> Regards, STefan
>=20
> drm-kmod commit 534aa199c10d forced it to use i2c from base.
Hi Vladimir,
thank you for the information! I'm using drm-devel-kmod, and in fact foun=
d
that 5.5.19.g20211230 works, while 5.7.19.g20220126 (committed as 0c38674=
b389ad
on 2022-01-26) causes the failure.
> You may try to checkout previous revision (444dc58f0247) to find out if=
in-base
> i2c is guilty or not.
Assuming that the same change to use the system i2c code has been in the =
latest
commit to the drm-devel-kmod port, this should be proven, now. ;-)
These is the list of in-kernel i2c modules on my system (a Ryzen 9 5950 o=
n an
ASUS mainboard with B550 chip-set):
$ kldstat -v | grep iic
68 iicsmb/smbus
67 iicbus/iicsmb
66 iichb/iicbus
65 iicbb/iicbus
64 iicbus/iic
63 iicbus/ic
213 lkpi_iicbb/iicbb
212 lkpi_iic/lkpi_iicbb
211 lkpi_iic/iicbus
210 drmn/lkpi_iic
56 iichid/hidbus
Can I help debug this issue?
I could re-install the latest version and boot with hw.dri.drm_debug or
dev.drm.drm_debug set?
Or are there other settings to get a debug log from the i2c side?
Regards, STefan
PS: I'm keeping the CC to current@, since this might be an issue in the i=
2c
kernel code ...
--------------6yDW8Sj3j0b6bNZBv5ak18Jq--
--------------LSTiDFrbrdXqddmjn0y2I3nT
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"
-----BEGIN PGP SIGNATURE-----
wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmH26k0FAwAAAAAACgkQR+u171r99UTi
zwf9GnGgrn6d99ZiqXsmMJ/O4q50ahJEh4ZnymcSkrDOQpUk4zIsl1MYazAuBOnJAVd/xTTlmGeu
ZVZUnC87ZfnhKEVgo5hpvxwTYOryAZjcdTmCNvPwyhUMuTEzSRYe8nHB0JYDYM1zkp39kJQbcURS
5s0V1J1pTfs4DjHrMkHKHgRVcQxQckPFEmXvhSlIEPTAEvENRkA9Krsy9rG4MghB/+o1CqYkNiAu
3HWjA4v3LwJMASqUMBrGWNMfE00e7WeD5Mliw5oVOaXyQvC12Nx4GQ2JxQleTmfrZyNqirspwS7F
NDPwKUBxyGLGVjsT/WDA13RyCGPhqzF5pZtz85S5/Q==
=9cNY
-----END PGP SIGNATURE-----
--------------LSTiDFrbrdXqddmjn0y2I3nT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c415393e-1cf0-2f7f-36c8-9d4bde73cfdc>