From nobody Sun Jan 30 19:43:09 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A3CF4198B718 for ; Sun, 30 Jan 2022 19:43:13 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jn1ns47jLz3Lwr; Sun, 30 Jan 2022 19:43:13 +0000 (UTC) (envelope-from se@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643571793; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1UBaJt18j6jmFuBZuxCPaj9KJZKeBmHvM8VtGJsX/DE=; b=nzWDtUFLjivcmJO9bxLiWgrCG4ojdZpOzVqAaHQT4Q0B0jvJvugKv5HxsHSiGwk6jjgpKt +s8gkz3UikF9ZfKBGLihJB1TixUO6jQI8lu3DNDX+kJc3Nt21Lyvm/0FCNxDyxi6rMCRCa mrJsIuoJyVmnffTHwEgTJk5lvS7352Y/S6gSFArHQZDiYKcDkUgmACi5RostCEetFoAztY oeyb0RMEhPyZaZ7ZoAqY6WjkBTrMOllHZHXScsITSBt+vbLTtnT0fFDoh4thc1+vJ5QBxd FfAirAduq9qP6K36f9GE+nOIvAl+mkFwVDXK5vpOCZJuJeumxk5gGgU3PZQsng== Received: from [IPV6:2003:cd:5f0c:9800:818c:49c5:f27e:e140] (p200300cd5f0c9800818c49c5f27ee140.dip0.t-ipconnect.de [IPv6:2003:cd:5f0c:9800:818c:49c5:f27e:e140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 0853990EB; Sun, 30 Jan 2022 19:43:12 +0000 (UTC) (envelope-from se@FreeBSD.org) Message-ID: Date: Sun, 30 Jan 2022 20:43:09 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 Subject: Re: Kernel changes causing AMDGPU / DRM to fail? i2c related? Content-Language: en-US To: Vladimir Kondratyev References: <4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org> From: Stefan Esser Cc: freebsd-current@freebsd.org In-Reply-To: <4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------LSTiDFrbrdXqddmjn0y2I3nT" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643571793; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1UBaJt18j6jmFuBZuxCPaj9KJZKeBmHvM8VtGJsX/DE=; b=ogXNMZp291Ua0eT6deR/8M+WPH5+xdQWFbY8N0VkpeGzr0itkt2ziuBU2ovP6CXDNXM4Do 1ngk67xTxK2RyKedb+Acl2tDulwh+dcufxPaqjLaTtkLiLE7dguOo5kk4qWbcWolXaQk3U nWhe6kHu+jGCvwEZmnYGLZiYsyQQzZlPolZ35L/8S6herkh28QjSp4LtChmM2bNAchvYOx d6l0AhPNPXwPnRp/k9MsMpVG1aViiMRxdDXBrPfM2152ghYwuvi6waIGsj5Ocz1vH0tbM+ zUEOW+GXFdU3Kqc91yYszQlQC5k4k0K+088h7T/UMGS9IVr6AHKqgCnAOoWYjw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643571793; a=rsa-sha256; cv=none; b=DFKQ6nUnpBVoA3ldhB1AQDKVxCy4DnufsqueZFbkUGB3Jqx9NUbGkRvxkH1MrdctV1j2ld nTh1/WUi386JW0oLD/BNiU5anr2/GiCDmZgBIjkpNurcthmxbnapr//tZ0K89YShQn9/DQ FQgZm3vYUR+CawXrpozoZO8bpvAdh6RJjj2TEXwrYmIsKqqJciqGlUDnC5EY+V+hkAZ0Em CIwjllHAPhygGUOiiVgjJyLCiyAP2ei+e8sydwZRM9BgkRXhhvO1/ncslWKtHi57G89DOR jF5VO44rp755BNhmvEGZzHYbJTWDC0l8HKAy857+/O8xce1AdQ6HwWPMAPP17A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------LSTiDFrbrdXqddmjn0y2I3nT Content-Type: multipart/mixed; boundary="------------6yDW8Sj3j0b6bNZBv5ak18Jq"; protected-headers="v1" From: Stefan Esser To: Vladimir Kondratyev Cc: freebsd-current@freebsd.org Message-ID: Subject: Re: Kernel changes causing AMDGPU / DRM to fail? i2c related? References: <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--