From nobody Tue Dec 23 19:06:53 2025 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 4dbPdc0khpz6KBJW for ; Tue, 23 Dec 2025 19:07:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dbPdb3rb6z3pFr for ; Tue, 23 Dec 2025 19:07:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x42e.google.com with SMTP id d2e1a72fcca58-7baf61be569so5684736b3a.3 for ; Tue, 23 Dec 2025 11:07:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1766516828; x=1767121628; 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=mTP19pfxq4nNARMjyGwBKfZ5nZ75gyc5gswX9BMFSmI=; b=2zd/EUWsySDPUtlQlLs0TfPlVeGhLva89VfFFFnDBXZ6aCO8vOTPNf3yYtXr1w/Aln dFOms91wevDTi+P4UpvbO+8np0lPl/6tCnI9BicKjEYwdKYYsvNtuqe36ly/x15e0iVP VtsAMQUReoei1yOJNo4xKfE1TFPHFFPVr1GWelrVXoaVDW2TDyoDJNGW5jFbDW0YjXxg HC1xiIBOYdgEZwiUZ1bZe9WvyubES+hR8mNskwGtGGqt35aqbh7SQmBO2tO+N0pFI5OK Nl6VbnVVuanNSF+aESroqbUTNxKlCbL+izvDF9RAqeMlaAE7YGRZO0r8eqCapYtJDWRp RIOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1766516828; x=1767121628; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=mTP19pfxq4nNARMjyGwBKfZ5nZ75gyc5gswX9BMFSmI=; b=vc0enu4yEbMndGhkqIGpzw70TRnEafEaqeWraSZaN6d6ANUy65jonyD3HCxoFFZf3q cJ0H/LTn4kB/o4OyZYfb5SSN6vmXwIAb7cc1R763bufcl/AdWEwQlVE/+YPjqVsUxUI8 7RdmYpE8/m632BFmiR1gvRlDg0mEcBgclerRNS0Pfzntxlth/XMKjLY3vP1EmJWQIc4d EZSIKPotFCXyE01SGvZTocwAorIyCCfSdPSOwCvFLAo++z1MhbG0uk+UAdkWZ6IGOuHa gCnrUHleuoEqQXqieUZn6A2rgJ0JhY0SWm9sIjzveGOvPr7Q+Y8pFJpx9q2kSXpJApY3 eXaQ== X-Gm-Message-State: AOJu0YzsiunDSWcQUECr6Ajqi4qkFwZGqxeoZb9xstgih/KRDva+cJQ9 8PqTzoM9RAeAhwrYVh0TBadJO712f5EQIiuGEKfpIQOu2jxdJRUc/jHowu1eWQOD+4B1RtGnOOe BGuB8WKARqUg/ud8ePQd4/kiFqyy9hZA/RwgaHopgHg== X-Gm-Gg: AY/fxX6c+ZsDx+2F6CB8L8sv4u/d6rcsvgvkzXvlZvvcfiiFXl4jXkkYfr2AewkVc2P K1O/CJy+L89tLGf0gcbLr+aQ4MeRFUHLUwAwcAMbYmWLl48EJmRv4UciO3r4MywI6wXx/c8Osc/ kUQNZRXmZbUftKin8EmmlYGn6kOZA8GWsPK557wz9Cmu7IzDRrt9RHAXtMmdNKlOygvc2JMR3kQ 5vpFSPXrIMWpJs5iB8H9a2UQpJIFfu0fGYDEIycWIF7R7T4jsjZ7U0Tz6EFl/o/0lfAD0kj X-Google-Smtp-Source: AGHT+IH4hGFkXlmujh4paAZV4TqFilXUYE0kV3Hefy13pIMsB2MWqJpEuXyiM5qC/ZSL8B+zzJrvwog/hyIBy0wM13Y= X-Received: by 2002:a05:6a20:5491:b0:371:7f31:17f with SMTP id adf61e73a8af0-376ab8cb3b1mr14529289637.77.1766516824668; Tue, 23 Dec 2025 11:07:04 -0800 (PST) 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: <198170948d34f4dc169e94934da82161@Leidinger.net> <89a92e0a926239e2c192dc0ff9c80d6e@Leidinger.net> In-Reply-To: From: Warner Losh Date: Tue, 23 Dec 2025 12:06:53 -0700 X-Gm-Features: AQt7F2rDf5mkWVxf7d6_X4kKsKyoKht5MIKeljg9-JLdE8g6KPEc_dWUqtiT0zE Message-ID: Subject: Re: Changes in cam/nvme causes issues? To: Alexander Leidinger Cc: Current Content-Type: multipart/alternative; boundary="000000000000d30abd0646a33f97" X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dbPdb3rb6z3pFr --000000000000d30abd0646a33f97 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Dec 23, 2025 at 7:19=E2=80=AFAM Alexander Leidinger wrote: > Am 2025-12-23 10:31, schrieb Alexander Leidinger: > > Am 2025-12-22 17:58, schrieb Warner Losh: > > > > On Sun, Dec 21, 2025 at 8:37=E2=80=AFAM Alexander Leidinger < > Alexander@leidinger.net> wrote: > > Am 2025-12-14 14:05, schrieb Warner Losh: > > Let's do one issue at a time. There's too much missing info. Top posting > since there's not a lot of context to this request > > > The disk died now completely, so the CRC errors are out of reach now. > > > First, let's start with pciconf -l of the nvme drive. I have a strong > idea, but need some data. > > > While already provided privately with some other data, here for the publi= c > so that people are aware that currently there is an issue with such drive= s: > nvme0@pci0:5:0:0: class=3D0x010802 rev=3D0x00 hdr=3D0x00 vendor=3D0x144d > device=3D0xa809 subvendor=3D0x144d subdevice=3D0xa801 > Samsung SSD 980 1TB 2B4QFXO7 S649NL0T819360V > > > Yea, so far this is the only report I've received, and there's not enough > data in it to reproduce it with any of the dozen NVMe drives that I have, > or to spot a difference with what I know I check in the code. So if it's > compiled into the kernel with cam also compiled into the kernel, I know i= t > works. > > > CAM is in the kerne, nvme is loaded as a module (from 15-current): > ---snip--- > # kldstat | egrep '(nvm|cam)' > 2 1 0xffffffff811e3000 20db8 nvme.ko > ---snip--- > > I will do a clean rebuild with the most recent 16-current and provide a > full dmesg if this still doesn't work. > > > As a module it fails: > [1] link_elf_obj: symbol nvme_handle_aen_desc undefined > [1] KLD file nvme.ko - could not finalize loading > The kld problem has been fixed. Warner > Bye, > Alexander. > > F > > > -- > http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF > http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF > --000000000000d30abd0646a33f97 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Dec 23,= 2025 at 7:19=E2=80=AFAM Alexander Leidinger <Alexander@leidinger.net> wrote:

Am 2025-12-23 10:31, schrieb Al= exander Leidinger:

Am 2025-12-22 17:58, schrieb = Warner Losh:

=C2=A0

On Sun, Dec 21, 2025 at 8:37=E2=80=AFAM Alexander Leidinge= r <Alexander@leidinger.net> wrote:

Am 20= 25-12-14 14:05, schrieb Warner Losh:

Let's do one issue at=C2=A0a time. There's too mu= ch missing info. Top posting since there's=C2=A0 not a lot of context t= o this request=C2=A0
=C2=A0
The disk died now completely, so the CRC errors are out o= f reach now.
=C2=A0
First, let's start with pciconf -l of the nvme drive.= I have a strong idea, but need some data.
=C2=A0
While already provided privately with some other data, he= re for the public so that people are aware that currently there is an issue= with such drives:
nvme0@pci0:5:0:0: class=3D0x010802 rev=3D0x00 hdr=3D0x00 = vendor=3D0x144d device=3D0xa809 subvendor=3D0x144d subdevice=3D0xa801
Samsung SSD 980 1TB 2B4QFXO7 S649NL0T819360V
=C2=A0
Yea, so far this is the only report I've received, and there's= not enough data in it to reproduce it with any of the dozen NVMe drives th= at I have, or to spot a difference with what I know I check in the code. So= if it's compiled into the kernel with cam also compiled into the kerne= l, I know it works.
=C2=A0
CAM is in the kerne, nvme is loaded as a module (from 15-current):
---snip---
# kldstat | egrep '(nvm|cam)'
=C2=A02 =C2=A0 =C2=A01 0xffff= ffff811e3000 =C2=A0 =C2=A020db8 nvme.ko
---snip---
=C2=A0
I will do a clean rebuild with the most recent 16-current and provide = a full dmesg if this still doesn't work.
=C2=A0
As a module it fails:
[1] link_elf_obj: symbol nvme_handle_aen_desc undefined
[1] KLD fil= e nvme.ko - could not finalize loading
<= /blockquote>

The kld problem has been fixed.
<= br>
Warner
=C2=A0
Bye,
Alexander.
F


--
http://= www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http:= //www.FreeBSD.org =C2=A0 =C2=A0netchild@FreeBSD.org =C2=A0: PGP 0x8F31830F9F2772BF
--000000000000d30abd0646a33f97--