From nobody Fri Sep 01 12:57:47 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 4RcdP559smz4sSn4 for ; Fri, 1 Sep 2023 12:58:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RcdP53VqRz4NHF for ; Fri, 1 Sep 2023 12:58:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-5256d74dab9so2477146a12.1 for ; Fri, 01 Sep 2023 05:58:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1693573080; x=1694177880; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=SuYkhSVEbUCHSDw6liwHrkNdHVta97vebQ3m4Ba8g+0=; b=3HUf6RHsKcD/7mGAucEBLK/getDhTtPAdICk8ctUQt8r4PDh0P00GAbn3cdc9LvPDl sMfl0jpZ32wCTzjvuO/tsjnDAGBKyiOb+WRbLfuZaLu/gN+T/W+wDjEpM8t0shsJevJJ sQT10ou4wiivs2SGhJhVUbzeSRYaRDXvzzBk5bRAnQEfnC/Qqlb8HdHJCu/6uBbiMQTW yzHLPUZG7S0USN6OVlrHBsX3J9p9Ewaq5zFzwya/KhRIgs8x11kF2bhjN2PLZI0lVpZJ G8TFJwufwcCZH08lZC1czKnn1//ZYeaiFEaol6y1fd2wFaY3ecYf/3QCSG/g7NDrnVXM KRsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693573080; x=1694177880; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=SuYkhSVEbUCHSDw6liwHrkNdHVta97vebQ3m4Ba8g+0=; b=KKlJ+9f5jqYMiUAYu1auCxl6Lg2KVmSDoQoQ19WKiAVr5tzNG1D0j7A+tjWIVEfuGw WkhCyckqjvIbQphPWYHTL4Kwah24OiGINnACMlFNZLbVdVgj4hEbG1CWhf9PREIu3dFa 7wm6kmKL5juPYC9MdBNQT6XeSjnlGU1Bqgfnw5XrP7mWPrewdvRpDqx2i41Y/p5SqAJJ OxrWv6neokMx7PkM62oVqp91lbKLQFQUCNYgMofTkRVfa44M+JliZ+FAL+BoHtZKgpFg rJWrwEJCy9PZ/0ya88qVU2V9UQKgZUs0KJaaXRjG4ZTJ2bsJb+V5VmR0LWjMWNAm7Iz2 Ck2g== X-Gm-Message-State: AOJu0YzZZNusFdr82eYRQPik0i5HbgsA8Z1zk25D2BJpUJOIWqs62GPD 67eV1qeGBL63Ob8n0ho/BOoH5X69h2EsbZvzDLBuIbyFnWOVx6Zs X-Google-Smtp-Source: AGHT+IE7f+yw3BYahXfmZ/7bRBXheT2Erzo7rEhCKOJBlh5o1cyr+smSvdpT6EaDCAWTShFxxO/Hq1TAyvo1wQ3SQSs= X-Received: by 2002:aa7:da45:0:b0:523:c19d:a521 with SMTP id w5-20020aa7da45000000b00523c19da521mr1782495eds.40.1693573079815; Fri, 01 Sep 2023 05:57:59 -0700 (PDT) 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 References: <20230901130314.460f91bf@ernst.home> In-Reply-To: <20230901130314.460f91bf@ernst.home> From: Warner Losh Date: Fri, 1 Sep 2023 06:57:47 -0600 Message-ID: Subject: Re: FreeBSD-15 kernel panic when the amdtemp device is in the kernel To: garyj@gmx.de Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000d2ea6106044bb554" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4RcdP53VqRz4NHF --000000000000d2ea6106044bb554 Content-Type: text/plain; charset="UTF-8" On Fri, Sep 1, 2023, 5:03 AM 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. > Traceback? Warner 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 > > -- > Gary Jennejohn > > --000000000000d2ea6106044bb554 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Sep 1, 2023, 5:03 AM Gary Jennejohn <garyj@gmx.de> wrote:
I have a laptop wioth a AMD Ryzen 5 and a tower with a A= MD 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.

Traceback?

Warner=C2=A0

If I remove amdtemp both computers boot without any issues.

I suspect that this commit is the cause:

commit 323a94afb6236bcec3a07721566aec6f2ea2b209
Author: Akio Morita <akio.morita@kek.jp>
Date:=C2=A0 =C2=A0Tue Aug 1 22:32:12 2023 +0200

=C2=A0 =C2=A0 amdsmn(4), amdtemp(4): add support for Zen 4

=C2=A0 =C2=A0 Zen 4 support, tested on Ryzen 9 7900

=C2=A0 =C2=A0 Reviewed by:=C2=A0 =C2=A0 imp (previous version), mhorne
=C2=A0 =C2=A0 Approved by:=C2=A0 =C2=A0 mhorne
=C2=A0 =C2=A0 Obtained from:=C2=A0 http://jyurai.ddo.jp/~amorita/diary/?date=3D20221102#p01
=C2=A0 =C2=A0 Differential Revision:=C2=A0 https://revi= ews.freebsd.org/D41049

--
Gary Jennejohn

--000000000000d2ea6106044bb554--