From nobody Mon Jan 31 16:02:30 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 107BD199B97F for ; Mon, 31 Jan 2022 16:02:53 +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 4JnXs870zLz4rx0; Mon, 31 Jan 2022 16:02:52 +0000 (UTC) (envelope-from tijl@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643644973; 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=IW0TO2rwaYC6eRcgmDVEN+7Vw3XfIBowOgkdUz87bJ0=; b=eTLPtliuFQY03hxCo84opHxCiOS78xHLG3VbhnkZwzdoHDpPIRIUkNOIGePK/9cmX3Nkuw n8Is4wObh+ciQfXfnbikeXIyKXEDjdeOXVtvtYG++B2m+Kk6RDDEgS7bPSULpt48B6mJSd DJv7sIIjG6tA1Hbq1Snf+I7vaa9bK47mymmSJO9nt1EyY9v2mF+a09jNCXpS22Vyy15jvq r1f9CF+p2t3xvzuh2qaWy+ypSdcDI+KW6LJynet7qkjQAZ4W8dx7/4zyaOSIc+Kg1uz32A wQKf0Y0K95iASusCzPzcAr0aZ0pomMQrVtqDllBk3I5W3rdSzPk7QMHcQhklbw== Received: from localhost (unknown [IPv6:2a02:a03f:894b:4700:6dc8:7b7b:bfc5:33e6]) (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 6D3CC228D3; Mon, 31 Jan 2022 16:02:52 +0000 (UTC) (envelope-from tijl@FreeBSD.org) Date: Mon, 31 Jan 2022 17:02:30 +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: <20220131170230.3f9155be@FreeBSD.org> In-Reply-To: <4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org> References: <4611d16a-ef17-d8f3-c2c0-1b1091723646@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=US-ASCII Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643644973; 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=IW0TO2rwaYC6eRcgmDVEN+7Vw3XfIBowOgkdUz87bJ0=; b=k0A0CGjWpjcsTVO3V2h03pirPHlocbYigufylD2Wop2mFsR8+9i8+qq2X/z6S7+0WCI79O 9jGIKAjqtBRgA1bGNuClcS+PsxjsBpLv2rC3YYofY6SOmIaElH2+R0EXMXAlYmGWM65wQq inVgFJ4LkZI4Zvoo/WuxWJ7QsdRqdWbnH2ld0PNPILNEvhI7yx4zMpr5v0t0ZWd5dTrrWf QyJxICCiW46zb7B+5QM9n1vX1Pg4g1b8MwK77zRfovv9XW8kO0ksAg/sPmEigvLxE/XxH6 AKgPdZhNY2jW2gJHawOMh96mOILQX/roKeFfqBpS4yd6Ltk7uKUpzItQ5JBKmw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643644973; a=rsa-sha256; cv=none; b=pHKCNV8klnlYVk+/IS+SvYMN7vxFZCYUcTNxjoPAj3xjcMCLSpGTExElSlxcjzE7EKHoSo Q0mLmi5mKKlJipohW7oRDoLYRFUJ7DxQMnol+/xHmfM4pRQZ4lCX2GqoYL0apBeiAwrtX6 K+0nJvgRwUq/1toyxyx0Vzn/BKEeoLRMw0bvFSpKMSDfqkUvHc5Oj2wz6Z+phXuJue/cIn Z8roRzwW5wqTmIjL1IhoVN9RTwMM5f74IK8xR0BdZUsukgRu/H5/XPmymUNIlMCP/DCZ8X hodUUjpJBQFj5VMsiaei6/3qMuZDte0XOSM5raoL7sjSgD8tXJct3AxaPFtPww== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N 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. >> >> 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". >> >> 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 mismatch >> between kernel and user land, I have rebuilt all X11 server and library >> ports. >> >> 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. > > drm-kmod commit 534aa199c10d forced it to use i2c from base. > > You may try to checkout previous revision (444dc58f0247) to find out if in-base > i2c is guilty or not. 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.