From nobody Mon Sep 25 09:12:39 2023 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 4RvHGJ2lJCz4vHCG for ; Mon, 25 Sep 2023 09:12:56 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 4RvHGJ0smGz4btt for ; Mon, 25 Sep 2023 09:12:56 +0000 (UTC) (envelope-from markjdb@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-9aa2c6f0806so726502966b.3 for ; Mon, 25 Sep 2023 02:12:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695633174; x=1696237974; 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=5YeSfe1fmQoRx6VFlb+nN5Bdr2sYuifDdQjY1Yr5E2A=; b=G1OWUJj2cqG6mXuLvlf5ES+HTat87TdGL2FJKC3i10vPxX24PgxAQ66EkKJcUQEF2b WkFT1Sz8fVcLTJwgcgNFMBWFXXjciuth6Gg1wiEBMMVnx45DtXbFv7Lt46VH//pGXopm +glDt7zTovD+rrnjwezMnrURiBMdTnB8jeLSZqdcXfNN2zVeig0a69T8eaUCyWxYfwxn WT2B0XO8ofItnwW5NFlEsr24TKR9GErN+l4/J2aV73Dtk7rgufr/TPHMrDAA8NS4HRx1 lUkQY69KfA/yW+HT/ZgOiX+fVCYxFieeOwQ4g3ISmrSjcZLLAa3hMSpXU8jH+0o+EjRd 3GOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695633174; x=1696237974; 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=5YeSfe1fmQoRx6VFlb+nN5Bdr2sYuifDdQjY1Yr5E2A=; b=itkB9gTMKhbGq+TyW93BsgJ4D7IMzQze/LEHq8AGnL7N7l/UQzruC2ID88WK+dRDCd elhmc6pa401x0MY05H3bGY9KTjr/fVS9Uhg8zHswex6a5wDB5p8rBLRIEB/TIXG5w5Lj Az+MYqXUR3RVj/n4y8Xiox5esAqfhAEuEv5kj0FUt6l06Q/MHCUq3z1NVIExeDNHn/Rw j3D5EGHOxhsYMbEL8xn+HsCIbCsD6zQD7O4GieF99DGstVjky2NilPop1VKF2VzJmqVV GabufSA6xVZQDjmO271tqttPrgr8v31AkDDYYdE9RIoOKFfJuQlLDXRbih8sTQ/a9JLL j2jQ== X-Gm-Message-State: AOJu0YwOFm0Jfk6elGnbapN4SeEK0bgcl0Sd80knXHfhcYq5CG4lFDyi S6UUPbEdv1wAADZqw2g5DzcYIk25KVu9ETy00Hn6xtyi X-Google-Smtp-Source: AGHT+IFlLXpBkJAt9iyTtxVrK2oIGMMN2CGELOkvrkjG15ROdvdoNza6XYDofhZkmG4QJWTrA12StCrJfjvystIlE0U= X-Received: by 2002:a17:906:3089:b0:9a2:1e03:1572 with SMTP id 9-20020a170906308900b009a21e031572mr5764983ejv.19.1695633174128; Mon, 25 Sep 2023 02:12:54 -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: In-Reply-To: From: Mark Johnston Date: Mon, 25 Sep 2023 10:12:39 +0100 Message-ID: Subject: Re: 14-ALPHA2 panic on cold boot To: cglogic Cc: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000036b0006062b5d51" 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: 4RvHGJ0smGz4btt --000000000000036b0006062b5d51 Content-Type: text/plain; charset="UTF-8" Yes. I've been traveling for the past couple of weeks and so haven't been committing patches, but I'll be home tomorrow and plan to commit and merge D41883. On Mon., Sep. 25, 2023, 06:59 cglogic, wrote: > Any chance that https://reviews.freebsd.org/D41883 will be merged into > 14.0 before release? > > ------- Original Message ------- > On Sunday, September 10th, 2023 at 5:14 PM, cglogic < > cglogic@protonmail.com> wrote: > > For those who interested or affected by this issue. > Looks like this regression was introduced by > https://reviews.freebsd.org/D34117 > Currently active PR is > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 > It contains a patch proposed by one of users. > But the PR can't move forward without committers attention. > > ------- Original Message ------- > On Tuesday, August 29th, 2023 at 11:09 AM, cglogic > wrote: > > Hello dear FreeBSD community, > > Recently I tried to boot from FreeBSD 14-ALPHA2 image and got panic on > first boot after power on. > My hardware is AMD Ryzen 9 5900X on ASUS ROG STRIX B550-E GAMING. > It's related to audio chip ALC1220 initialization. > > If I remember correctly, when I tried FreeBSD 13-STABLE, around 2 years > ago, no panic was observed. > But at that time my GPU was unsupported by drm-kmod. So I installed Linux > and used it for 2 years. > On Linux, no such a panic observed. Now drm-kmod supports my GPU and I > want move to FreeBSD. > > Also tried 13.2, got the same panic. > Can't try earlier FreeBSD 13 releases, as they are not available for > download anymore. > > I found two related bug reports: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264305 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 > > My backtrace is the same as in reported issues. So I did not write it from > a screen to a paper. > > As I understand, this bug affects all AMD Zen2, Zen3 and Zen4 computers > and laptops. > We are near FreeBSD 14.0 release now, maybe it will be possible to fix it > before release. > > Thanks. > > > > --000000000000036b0006062b5d51 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes. I've been traveling for the past couple of = weeks and so haven't been committing patches, but I'll be home tomo= rrow and plan to commit and merge D41883.

On Mon., Sep. 25, 2023, 06:59 cglogi= c, <cglogic@protonmail.com= > wrote:
Any chance that=C2=A0https://reviews.freeb= sd.org/D41883=C2=A0will be merged into 14.0 before release?
<= /div>

------- Original Message -------
On Sunday, September 10th, 2023 at 5:14 PM, cglogic <cglogic= @protonmail.com> wrote:

For = those who interested or affected by this issue.
Looks like this regression was introduced by=C2= =A0https://reviews.freebsd.org/= D34117
It contains a patch proposed by one of users.
But the PR can't move = forward without committers attention.

------- Original Message -------
On Tuesday, August 29th, 2023 at 11:09 AM, cglogic <cglogic@= protonmail.com> wrote:

Hell= o dear FreeBSD community,

Recently I tried to boot from FreeBSD 14-ALPHA2 image and got pani= c on first boot after power on.
My hardware is=C2=A0AMD Ryzen 9 5900X on ASUS=C2= =A0ROG STRIX B550-E GAMING.
It's related to audio chip=C2=A0ALC1220 initialization.

If I remember correctly, when I tried = FreeBSD 13-STABLE, around 2 years ago, no panic was observed.
<= div style=3D"font-family:Arial,sans-serif;font-size:14px">But at that= time my GPU was unsupported by drm-kmod. So I installed Linux and used it = for 2 years.
On Linux, no such a panic observed. Now drm-kmod supports my= GPU and I want move to FreeBSD.

Also tried 13.2, got the same pan= ic.
= Can't try earlier FreeBSD 13 releases, as they are not available = for download anymore.

I found two related bug reports:

My backtrac= e is the same as in reported issues. So I did not write it from a screen to= a paper.

As I understand, this bug affects all AMD Ze= n2, Zen3 and Zen4 computers and laptops.
We are near FreeBSD 14.0 release now, maybe it will be = possible to fix it before release.

Thanks.


--000000000000036b0006062b5d51--