From nobody Fri Sep 01 12:15:20 2023 X-Original-To: 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 4RccS92h51z4sR7X for ; Fri, 1 Sep 2023 12:15:37 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [94.130.200.20]) (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 ECDSA (P-384) client-digest SHA384) (Client CN "mail.bsd4all.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RccS36Dnrz4KnR for ; Fri, 1 Sep 2023 12:15:31 +0000 (UTC) (envelope-from herbert@gojira.at) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gojira.at header.s=mail202005 header.b=Inz8FGAB; spf=pass (mx1.freebsd.org: domain of herbert@gojira.at designates 94.130.200.20 as permitted sender) smtp.mailfrom=herbert@gojira.at; dmarc=none Date: Fri, 01 Sep 2023 14:15:20 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gojira.at; s=mail202005; t=1693570524; bh=YhCe1fJ60oUKrvz5OYqo0yZ/+b/RCzkvzqKPnqIJ30Q=; h=Date:Message-ID:From:To:Subject:MIME-Version:Content-Type; b=Inz8FGAB6rLYyKob8WkDTQjN4xMBsxkDCVer0QYD0AL3OTT3J470rblUTZb3M0a8q OdkxVMj6L0fPOQsvPwqbQsRDyFdsv04zVVKKDA/i8aI9BffAl093+QgG1URswrMeYV fo9tx49xXV//EqhFypG5MkBTbZVypqTAcWXUkeZZ5h6eQHykR0YWIy4vRepBbSOeFR iqTiiXE9bQcps1kxmD0H01mkyrKieEh+oF6o9vgJyTkC16TjLIC+vwOf9uYWNO0ulN Jg0EPbBe+hNL17C1w4GGVsvMzNM19vLfa1Sj5GMae79+0FcIjiTy3c1XRypXUmiC96 s4egKAWwFs5kg== Message-ID: <87edjixf6v.wl-herbert@gojira.at> From: "Herbert J. Skuhra" To: current@freebsd.org Subject: Re: FreeBSD-15 kernel panic when the amdtemp device is in the kernel In-Reply-To: <20230901130314.460f91bf@ernst.home> References: <20230901130314.460f91bf@ernst.home> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/30.0 Mule/6.0 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 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.40 / 15.00]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_LONG(-0.99)[-0.994]; NEURAL_HAM_MEDIUM(-0.97)[-0.968]; NEURAL_HAM_SHORT(-0.94)[-0.938]; R_SPF_ALLOW(-0.20)[+ip4:94.130.200.20]; R_DKIM_ALLOW(-0.20)[gojira.at:s=mail202005]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[current@freebsd.org]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; BLOCKLISTDE_FAIL(0.00)[94.130.200.20:query timed out]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[gojira.at:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[gojira.at]; TO_DN_NONE(0.00)[]; ASN(0.00)[asn:24940, ipnet:94.130.0.0/16, country:DE] X-Rspamd-Queue-Id: 4RccS36Dnrz4KnR On Fri, 01 Sep 2023 13:03:14 +0200, Gary Jennejohn wrote: > > I have a laptop wioth a AMD Ryzen 5 and a tower with a AMD Ryzen 7 3700X. > > These are respectively Zen 1 and Zen 2 CPUs. > > I built a kernel on both computers using the FreeBSD-15 source tree. > > If I include the amdtemp device in my kernel file BOTH computers end up > with a kernel panic while trying to attach the amdtemp device. > > If I remove amdtemp both computers boot without any issues. > > I suspect that this commit is the cause: > > commit 323a94afb6236bcec3a07721566aec6f2ea2b209 > Author: Akio Morita > Date: Tue Aug 1 22:32:12 2023 +0200 > > amdsmn(4), amdtemp(4): add support for Zen 4 > > Zen 4 support, tested on Ryzen 9 7900 > > Reviewed by: imp (previous version), mhorne > Approved by: mhorne > Obtained from: http://jyurai.ddo.jp/~amorita/diary/?date=20221102#p01 > Differential Revision: https://reviews.freebsd.org/D41049 Thanks for sharing your findings. Now I probably know why my old kernel from stable/13 no longer booted after updating to stable/14. I've create a new kernel config and forgot to add "device amdtemp" & "device amdsmn" and forgot about the issue. After removing only "device amdtemp" from my old kernel config it boots again. Unfortunately reverting this commit (git revert -n 323a94afb623) doesn't resolve this issue. Old kernel does not boot if "device amdtemp" is enabled. Probably wrong commit or I am doing somethig wrong!? -- Herbert