From nobody Sat Dec 2 02:00:19 2023 X-Original-To: freebsd-hackers@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 4ShtRv4JzRz531mq for ; Sat, 2 Dec 2023 02:00:27 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ShtRv0MP2z3R5Q for ; Sat, 2 Dec 2023 02:00:27 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm1 header.b="LCEqc/xl"; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="E Qttmsr"; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 64.147.123.21 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 3A5683200BE6 for ; Fri, 1 Dec 2023 21:00:25 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Fri, 01 Dec 2023 21:00:25 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1701482424; x=1701568824; bh=Cp7w3BFRefmwNTAI2kVX3i3zHfJ3Yofz2e8 1sF47xzo=; b=LCEqc/xliOdYVmz3XL8qbM4Enp/mDKED1bioxelFCQQ8mkpdF7U 1AILkyUvOtY9YqgBP837mLCzmEvJVENrNJsCmbt/Uzgi3DedTMDdFjWA3pFOyp2C o/GzpcuCVL9GuzL0UT3lF3bc/wHbVchlepFmPqq0HnioUGIiVWiTvcaYWYCSId6O i71wLzwKLbchsFY+VzJIUUb92Ufy7Jnlx5XWOI7Gz+HCfTYbBNJ7nHufHcjgfikl UM1lej1h1aDMTGIuzj253xp4NX7shAHgYcc7TmMQ4hjGIrTis1FJezT91osHpBeI JSacT7pC6MVSa+op8AVMN7qmPM0MZ/pqBPw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1701482424; x= 1701568824; bh=Cp7w3BFRefmwNTAI2kVX3i3zHfJ3Yofz2e81sF47xzo=; b=E QttmsrRpUDx00BfA2NI8wQMR0a+wlMMa/4XxlSXw9HF/+bKMRXkXNZy7XwJMrBwg aDj2kOVkHiJt5vHMVJH3f2HcKzusfXL7h577H5reYKaMmotEo/lE0Fx3Z8xM1dCE VwuOVyrf328EqfaP5smH8nj0C4ulEg5cKBcgkQtt8w9uKmZi6O8zDwhaP7YJc/Wy F2NMa71+ST/Rn7z49jTH0+REDtywP3u2ULvSHF4mw8xz+rcttbRJMUS4tP8wh8C6 PtZwzL7q0xZ0g4cO153BjJpnqGnHS9PVOf8U5uCDGs/UtgiA1w+zRhfrvc0v11IT 6E0nw3MbKypzcgVcpZH0A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudejtddggedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtvdejnecuhfhrohhmpegjuhhrihcuoeihuhhrihesrggvthgvrhhnrdhorhhgqeen ucggtffrrghtthgvrhhnpeetkeevgfefteejheeifeduiedvkedukeetudffgfejlefhtd ejkeelhedvkeduudenucffohhmrghinhepfhhrvggvsghsugdrohhrghenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpeihuhhrihesrggvthgvrh hnrdhorhhg X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 1 Dec 2023 21:00:23 -0500 (EST) Message-ID: Date: Sat, 2 Dec 2023 09:00:19 +0700 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Radeon DRM kmod problem after LLVM upgrade!? To: freebsd-hackers@freebsd.org References: Content-Language: en-US From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: / X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-Spamd-Result: default: False [0.61 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm1,messagingengine.com:s=fm1]; XM_UA_NO_VERSION(0.01)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org]; SUBJECT_HAS_EXCLAIM(0.00)[]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] X-Rspamd-Queue-Id: 4ShtRv0MP2z3R5Q George Mitchell wrote: > This afternoon after upgrading llvm15 from 15.0.7_5 to 15.0.7_7, Xorg > no longer runs properly -- if I use drm-510-kmod instead of VESA. > > My display card is Raven Ridge [Radeon Vega Series / Radeon Vega Mobile > Series] (USB id vendor=0x1002 device=0x15dd). > > When I boot in single-user mode, load the amdgpu.ko module from > graphics/drm-510-kmod, and attempt to start Xorg, I get a pretty > pattern of dots all over the screen, and Xorg reports (on the console): > > ac_rtld error: !data || data->d_size != shdr->sh_size > LLVM failed to upload shader > ac_rtld error: !data || data->d_size != shdr->sh_size > LLVM failed to upload shader > EE ../src/gallium/drivers/radeonsi/si_state_shaders.cpp:2505 > si_build_shader_variant - Failed to build shader variant (type=0) > ac_rtld error: !data || data->d_size != shdr->sh_size > LLVM failed to upload shader > EE ../src/gallium/drivers/radeonsi/si_state_shaders.cpp:2505 > si_build_shader_variant - Failed to build shader variant (type=0) > ac_rtld error: !data || data->d_size != shdr->sh_size > LLVM failed to upload shader > EE ../src/gallium/drivers/radeonsi/si_state_shaders.cpp:2505 > si_build_shader_variant - Failed to build shader variant (type=0) > ac_rtld error: !data || data->d_size != shdr->sh_size > LLVM failed to upload shader > EE ../src/gallium/drivers/radeonsi/si_state_shaders.cpp:2505 > si_build_shader_variant - Failed to build shader variant (type=0) > ac_rtld error: !data || data->d_size != shdr->sh_size > LLVM failed to upload shader > EE ../src/gallium/drivers/radeonsi/si_state_shaders.cpp:2505 > si_build_shader_variant - Failed to build shader variant (type=0) > > Everything is fine if I use VESA mode, thankfully. > > My system has never been completely trouble-free with amd-510-kmod, > but it has so far worked wonderfully well when it doesn't crash.  But > how that driver could interact with LLVM is beyond me.  Should I try > simply recompiling the module with the latest LLVM?       -- George > See also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275388 and this may or may not help: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275443