From nobody Tue Dec 23 14:18:24 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 4dbHG62BTBz6LVDh for ; Tue, 23 Dec 2025 14:19:58 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (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 (prime256v1) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "E7" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dbHG438Dpz4Kdq for ; Tue, 23 Dec 2025 14:19:56 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=leidinger.net header.s=outgoing-alex header.b=nd4Nx4U1; dmarc=pass (policy=quarantine) header.from=leidinger.net; spf=pass (mx1.freebsd.org: domain of Alexander@Leidinger.net designates 89.238.82.207 as permitted sender) smtp.mailfrom=Alexander@Leidinger.net 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 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1766499554; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=MCsLRHhaM7zYUhKy60shdgQGJI+t/NE/sobuQp+u3B8=; b=nd4Nx4U1gHQWE6+ncUlLaoUM9FlJKzOpv1KNC0IO1JHDpuDgi9vvzu8Hg+cAkxzzXU0FHr cCFwV4ADD6YLbk2siszRHQu0Qx6v5SFTcdngXp4db6tjpgLLN7uXnyCM6pBS0buztY1ZhH nCUe7vt+ZbUoyTQfAs6MD3kIzhO2IOK0i0RNUMW+3XQ8cTAOYl/r3hCGtL+OQYTwoCfchL 2i4cpqNsIc45RUm6cQt/xM+8afWKAS3kyd6eDH2dJeOrbzT/jCjCITYUAxTUgfEdB5WtyT f8f4z9nREb4QZ5YHe4KcHxRjG9GQeYkKlwBxyyBYyxQ9AguwXfudN7qjzs0edQ== Date: Tue, 23 Dec 2025 15:18:24 +0100 From: Alexander Leidinger To: Warner Losh Cc: Current Subject: Re: Changes in cam/nvme causes issues? In-Reply-To: References: <198170948d34f4dc169e94934da82161@Leidinger.net> <89a92e0a926239e2c192dc0ff9c80d6e@Leidinger.net> Message-ID: Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_5b8398f92dd80349ad073fab75fdfec1"; micalg=pgp-sha256 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.98 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[leidinger.net,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.20)[multipart/signed,multipart/alternative,text/plain]; R_DKIM_ALLOW(-0.20)[leidinger.net:s=outgoing-alex]; ONCE_RECEIVED(0.10)[]; NEURAL_SPAM_SHORT(0.02)[0.021]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; HAS_ATTACHMENT(0.00)[]; DKIM_TRACE(0.00)[leidinger.net:+]; RCPT_COUNT_TWO(0.00)[2]; MISSING_XM_UA(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; MID_RHS_MATCH_FROM(0.00)[]; BLOCKLISTDE_FAIL(0.00)[89.238.82.207:server fail]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~,4:~] X-Rspamd-Queue-Id: 4dbHG438Dpz4Kdq This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_5b8398f92dd80349ad073fab75fdfec1 Content-Type: multipart/alternative; boundary="=_a1d23432334b461710ca90b104d8b2e2" --=_a1d23432334b461710ca90b104d8b2e2 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed 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 AM Alexander Leidinger > 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 > public so that people are aware that currently there is an issue with > such drives: > nvme0@pci0:5:0:0: class=0x010802 rev=0x00 hdr=0x00 vendor=0x144d > device=0xa809 subvendor=0x144d subdevice=0xa801 > 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 it 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 Bye, Alexander. > F -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_a1d23432334b461710ca90b104d8b2e2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

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, schrie= b Warner Losh:

Let's do one issue at a time. There's too much missi= ng info. Top posting since there's  not a lot of context to this reque= st 
 
The disk died now completely, so the CRC errors are out o= f reach now.
 
First, let's start with pciconf -l of the nvme drive. I h= ave a strong idea, but need some data.
 
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
 
Yea, so far this is the only report I've received, and there's not eno= ugh data in it to reproduce it with any of the dozen NVMe drives that I hav= e, 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 it= works.
 
CAM is in the kerne, nvme is loaded as a module (from 15-current):
---snip---
# kldstat | egrep '(nvm|cam)'
 2    1 0xffffffff81= 1e3000    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 f= ile nvme.ko - could not finalize loading
 
Bye,
Alexander.
F


--
--=_a1d23432334b461710ca90b104d8b2e2-- --=_5b8398f92dd80349ad073fab75fdfec1 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmlKpMAACgkQEg2wmwP4 2IYaGw/9Ecuti7E8hQwbANj4zuLKfTcxH5L79nocGFG2Ui7o8MaZWLM40TMK2zCv yPRo3dmChGEu23gO+nezHH6cy3QBsfbI5J1BoQ9UnVqR9JPzCBXeHRQXfdxc2hf2 q3zQ3JTHccVwhdFxkfagJ5EH2M/7JrectWwff0jfanKxMLOPlP7je6QY4degz0z4 wuBVmj/g2Yl+pn74ZZxtzY+gygiXWdOPPgPe+NWdXHSSUaaUsnbkLPkqI1DIrktf 5xgjm4krIXa2BBXl9wUPWlXkU3To0q/X6PSJR/4KRohwaUU7Ru6bLUVVLA7hW2Ou YW0hDa+5tYYwzIvt4TVd3+Tq5xRvkYEK4QqMbrV6qA7B6XShfNQMucQ4/egN5t8O OK0k0NRv0+iRr3c2BYwyDhLQAExfnNEtDIydX/mAsQP32aNpzZ2esP8U9dhfDHnd LrO+2ZRT9u0wpZwnnp7BNiANabW2D0Wz1kTlniC+w0iH69w3GidNqsGuST57AZiL cYkekj81HUQEZI40ROy85IcZCjjcl2e6D8Az+LRFOD75Wld91Y/zto8m5b4I8bvO sl1XeTAYORAcmREgm6oEb85nkjwxsMEAIJz947JLp5f5EV5Q8QgdFXZp7NGt7n47 N6MpgJS0XSBDdk1zdw1PpkW9EKU4RV+jN+PBg84RJznJKXhQLnc= =WsmL -----END PGP SIGNATURE----- --=_5b8398f92dd80349ad073fab75fdfec1--