From nobody Mon Jan 31 11:19:53 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 B2FD7199FC4E for ; Mon, 31 Jan 2022 11:19:58 +0000 (UTC) (envelope-from wulf@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 4JnQZk4gqjz3FMj for ; Mon, 31 Jan 2022 11:19:58 +0000 (UTC) (envelope-from wulf@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643627998; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9EXivVMFKzDNJ6pGbO0gprEFxfndIstYEb+kV8LgF1A=; b=ZINleT9wIGClxmp79UfPdT4TnBKlrFPY0v0w7gjoius55wMaOywDGHoX6fIYCUXIQEbfkR ba//OUixM+f2neOJNtxBTUN9xIlCP38duhJIaASF3kZlP0UmB7EtcqWDdY/4OaIOpIL0GD VE9IKKkOLEsXbGDZyq9l1xqqf5N5Fpr0eFC+3V968UjpWQRmOZDIxicQHxyCDzSHEZaOXS yIFCkeKErqRiZTjB1/+wWk59MymgPllks704iZrNjNH/S6n/uMMYURZi47lMxPm/JW0zw3 GU6gNqB7bUPQVx36h9z7/9wceCCm1o/+5QhVUQl6Jtur6UHP1xI54EEAQk2YtQ== Received: from [192.168.0.30] (unknown [176.120.228.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: wulf) by smtp.freebsd.org (Postfix) with ESMTPSA id 4053020A62 for ; Mon, 31 Jan 2022 11:19:58 +0000 (UTC) (envelope-from wulf@FreeBSD.org) Message-ID: <41f0a849-f2c9-75fe-e0ed-e60356ac4728@FreeBSD.org> Date: Mon, 31 Jan 2022 14:19:53 +0300 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 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Kernel changes causing AMDGPU / DRM to fail? i2c related? Content-Language: en-US To: freebsd-current@freebsd.org References: <4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org> From: Vladimir Kondratyev In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643627998; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9EXivVMFKzDNJ6pGbO0gprEFxfndIstYEb+kV8LgF1A=; b=lv3SRXFp5QoNeqbzR/VUjB/AhCDgXrKmfZHqg1pupAAr0a/xbTFA/IhLcAUFFqlC+bvB5V EFawfKfMcHR2qwcGNWId3rwMbGypY8CjPSdVNvtuKw/19YWltg4eZKoZ9nKKnXMFqEd3hB BxLQnLDTKE5f9+fM++txRjEU3ne6WMnBOHAeJKEUZrleUoJmKPxxOSFwlhyg8+y+8YH1Mr QEhpgBdx87/gSkuIeEs5xhYD6WUJqBY82iYsKLhQ/j4Xm3k724gLlNkDbDtEVAD0Y7+yHg 4IdTWVY8hBfyuoDlUl5scOwFfTit46zMEc/D0KGeIiI4hQJAi1Sj8aTggO9nzQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643627998; a=rsa-sha256; cv=none; b=OXgd5T/T9Y0Aai0IPSFMo//Laguw/i1HdbAff6LwEbT9W+7YGbzfehzOvgEmAdWgMdfgyM Zy5CluCdXyByRn71Ee9uQLmngLXc/Wp6iFHl40LQRp6IJPDdQmjMLsuuZsC2rJjCGi+S+4 wU0B+xKiP/89v3/dvhFzg+/i6K/QhN03vYivkxIrQr4wv7A/v4OiumbZ62Zjd88O7z/LtT +q5kBZjyaWbQKvZWbVipAc/qwxSNwdvConswr0tvuCDhZF/mU7tBei3ltT8ygn+Lq2BuP4 x4ks2c4vkqbv9uiGjIwBYPZLZGQOZub7mtg7OTrCA0gVM3weUxX3gV7h7hwhYQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 30.01.2022 22:43, Stefan Esser wrote: > 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]   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 >>> >>> A successful driver attach from a reboot a few days ago had ended in: >>> >>> [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 >>> >>> Regards, STefan >> >> 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 found > that 5.5.19.g20211230 works, while 5.7.19.g20220126 (committed as 0c38674b389ad > 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 on 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 i2c > kernel code ... There are no successful lkpi_iic attachments in your output. They look like: lkpi_iic0: on drmn0 Please share your `devinfo -v` output. Kldload output with verbose boot enabled can be helpful too. -- WBR Vladimir Kondratyev