From nobody Tue Feb 1 09:39:49 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 712D3198D6A6 for ; Tue, 1 Feb 2022 09:39:55 +0000 (UTC) (envelope-from tijl@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4Jp0Jq2qT8z4m1L; Tue, 1 Feb 2022 09:39:55 +0000 (UTC) (envelope-from tijl@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643708395; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jaSn8H8U9wZisp1p7mBDyPuPeFCobGzuSn/zG6/a0YA=; b=QIP1j+3u4m0vJkkCvtA43+v6vNjpfg2tO0Y2iph7GrNXhnnjR18u6q6GR2Ica06ztKysa3 Sh7g6mxmAvK2GKOmaqkVEtkss8ewbqI6CEgYXUB/ZiBD+HtTThEFgCGYJG/C+uKNo0YecL JmqBAz+xeXBt0FI7MKfrQHXB8riGj1OcK+kYuL6AFdk8hbX2T02/N3Y8nuKh84JCf5Utiu qBs180TC2V0nxG/lzTwwAuirVREOthsrNeN6zxUXpi3BeGNWx6PW9JmbCxVVhRhLmAWvL1 ZOPHP7pzfa0X9sfWPJsUcq62ITzrJxd835s/gvmb2F/E5sA7LUwQlYtAj+h+YQ== Received: from localhost (unknown [IPv6:2a02:a03f:894b:4700:1063:43e6:117a:7021]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: tijl) by smtp.freebsd.org (Postfix) with ESMTPSA id CDF1E2BB1B; Tue, 1 Feb 2022 09:39:54 +0000 (UTC) (envelope-from tijl@FreeBSD.org) Date: Tue, 1 Feb 2022 10:39:49 +0100 From: =?UTF-8?B?VMSzbA==?= Coosemans To: Vladimir Kondratyev Cc: freebsd-current@freebsd.org Subject: Re: Kernel changes causing AMDGPU / DRM to fail? i2c related? Message-ID: <20220201103949.11e09ce8@FreeBSD.org> In-Reply-To: <20220131170230.3f9155be@FreeBSD.org> References: <4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org> <20220131170230.3f9155be@FreeBSD.org> 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643708395; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=jaSn8H8U9wZisp1p7mBDyPuPeFCobGzuSn/zG6/a0YA=; b=P96aETby8sELkzPaf5PuurC1EFDYl6Un42D6B4JNTkxpBPyc8nnNTRrUJr6R7t09RrHFHc z1U2d/zP1PHy9WEN1mfIHvpzlYpyuC6vOwIJ0QJq5InhK29khUNIPeMA0I8jIiuafH2gpY i7vEbwnCL9JDXj0zuUDDBCo9DrekM38vAo4eKoIu1QKUgcNLDErQdEUxvJoFySmG4wHlZL z+35mus/EAJ6FC+QMMbGjSQuOSWUfFM/HXPkL3NDOUBAG7/Aca68wCiAsW1THaTz9mVNTr 2vgov29JdbaLTs9ryD7fUX9VWRQL659bsFOPpXb4uNoGh2EJsc/zlRTK0Cny/Q== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643708395; a=rsa-sha256; cv=none; b=Loks6PRlg0EDMB81G5rD8ZhUhILL3isUPyEn+tK8xSgxChYvkcgUNqlUxYmWTPq+SKuyiV 7b292IsXh9qvirGJh02tLbm3AswVfuB8oi5djjojlv0BCl7p3/8/YrzkVf07kSLJEZ1AyH uHeZ+T7hCGOmjVyvjU6Vknd9G+v12LG2pUwwMrWcN+gdWLbsH9paUbcF/n3uLDPz2cfBKR KtrTQhw1vKaMbmIR5PeW71OUgXKcvaEFbid9TbqfddQNGri5elLw0wfnPVVYiyRwBdALvT IJEPE4tX1YD7DaHFOHg7cx4O1ubEZxm7NbnTmr+f/LxRrrVzqMJNcNhl5R2QeA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Mon, 31 Jan 2022 17:02:30 +0100 T=C4=B3l Coosemans wrote: > On Sun, 30 Jan 2022 21:23:49 +0300 Vladimir Kondratyev > wrote: >> 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. >>>=20 >>> 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". >>>=20 >>> I'm asking here and not on the ports list, since the AMDGPU driver has >>> not been updated for half a year. But to be sure that there is no misma= tch >>> between kernel and user land, I have rebuilt all X11 server and library >>> ports. >>>=20 >>> There have been changes affecting the i2c driver, IIRC, and the error >>> message seems to point at an issue obtaining information from the LCD >>> display. >>=20 >> drm-kmod commit 534aa199c10d forced it to use i2c from base. >>=20 >> You may try to checkout previous revision (444dc58f0247) to find out >> if in-base i2c is guilty or not. >=20 > I found that since base dbc920bd9a9b (linuxkpi interval_tree) > linuxkpi.ko now exports some rb_* functions (from rbtree.h). These are > declared static inline but the compiler may decide not to inline them. > These functions conflict with the ones in linuxkpi_gplv2.ko from > drm-kmod, because both implementations use a different order for the > fields in struct rb_node. Here's a list of functions that linuxkpi.ko and linuxkpi_gplv2.ko have in common in my case. Some are probably ok. device_register i2c_transfer linux_compat_init lkpi_arch_phys_wc_add lkpi_arch_phys_wc_del rb_erase_cached rb_insert_color_cached sysctl_handle_attr