From nobody Sun Dec 8 03:23:11 2024 X-Original-To: bugs@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 4Y5Vgh2ktWz5fx8n for ; Sun, 08 Dec 2024 03:23:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Y5Vgh0lBVz4rNS for ; Sun, 8 Dec 2024 03:23:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1733628192; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=vGa9TdWyFd5y8zhkboaCDz/LbrnXslMVIg4aFA/JnhE=; b=qcD7VobJI05tOjY6voRTmGcyEOtEreOsIg9hUBQqazosJk/auD1uCq52RZsHXH8DB+NxX3 qG7YMIQQvX3Op8N/rNZrTREvsFF6+aYAFZIGDWJuWw2+vBF2k0hqcWzLqEDs4+DmMVevqR Jt/0Spgo9S+fqqGPjTFAiL6sG2aJV5A5r5TG21lHq9SUGBw9n0uyK4h5sBBeAedrJ8piIW RZ2XD/ET59v0xeFsbIU5KvPWV3dXDNdqhWeExhafc0Nt+8s3Y/uoL1LYsteBFb3ZCCCqgp ncbFAsERyfqW0uc6XrDVb3xZ3qa2sNrcMC1XD8BimLC/9mQE7QjscGYvwRqDBA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1733628192; a=rsa-sha256; cv=none; b=qST3CRtww+D8tQvp3kKsTaNi6Uq5j4pw7zeUC3vFlcrObS5rG22gnindGJFBoarnYVGrYE q4nLXbJo5IRCYNjvtIzUKfhtnbPRZvS8HROdp3LXqHUkv94ONcaBt+16kHVOLQ/WbhFzcs +/G2mxPRO9EsLjjaoqqI2ySWPCTto9nMZGBPxgybCq6pmJphaIK2fmg/pmxZAU8lJx0ds8 4eXnvZ93copTgckrf6cos3kuWoaN/fiKYjlMH84cMbV8pas8OfcNLDpDuFrXGsqWCbAeI0 yaSHqwJKDurExXSSNP2PV29j/NHjmgEWZmtpDbZ9mvq/5EeoRjVpqwPDAwuaow== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Y5Vgh0KkJzbRP for ; Sun, 8 Dec 2024 03:23:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 4B83NBAi007156 for ; Sun, 8 Dec 2024 03:23:11 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4B83NBrW007155 for bugs@FreeBSD.org; Sun, 8 Dec 2024 03:23:11 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283189] Sporadic NVMe DMAR faults since updating to 14.2-STABLE Date: Sun, 08 Dec 2024 03:23:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jah@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283189 Bug ID: 283189 Summary: Sporadic NVMe DMAR faults since updating to 14.2-STABLE Product: Base System Version: 14.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: jah@FreeBSD.org As described in https://lists.freebsd.org/archives/freebsd-stable/2024-November/002549.html Within a few hours of updating from 13.4-STABLE to 14.2-STABLE, I started seeing sporadic nvme DMAR faults (followed by nvme transfer errors that see= med to be triggered by the IOMMU failing the DMA request). These errors always look like the following: Nov 24 16:17:52 corona kernel: DMAR4: Fault Overflow Nov 24 16:17:52 corona kernel: nvme0: WRITE sqid:15 cid:121 nsid:1 lba:1615751416 len:256 Nov 24 16:17:52 corona kernel: DMAR4: nvme0: pci7:0:0 sid 700 fault acc 1 a= dt 0x0 reason 0x6 addr 42d000 Nov 24 16:17:52 corona kernel: nvme0: DATA TRANSFER ERROR (00/04) crd:0 m:1 dnr:1 p:1 sqid:15 cid:121 cdw0:0 Nov 24 16:17:52 corona kernel: (nda0:nvme0:0:0:1): WRITE. NCB: opc=3D1 fuse= =3D0 nsid=3D1 prp1=3D0 prp2=3D0 cdw=3D604e68f8 0 ff 0 0 0 Nov 24 16:17:52 corona kernel: (nda0:nvme0:0:0:1): CAM status: Unknown (0x4= 20) Nov 24 16:17:52 corona kernel: (nda0:nvme0:0:0:1): Error 5, Retries exhaust= ed Nov 24 16:17:52 corona ZFS[11614]: vdev I/O failure, zpool=3Dzroot path=3D/dev/nda0p4 offset=3D824843563008 size=3D131072 error=3D5 I've seen 5 of these error sequences since the system was updated from 13 t= o 14 two weeks ago. Previously the same machine had been running various builds= of 13-stable for nearly two years (with Intel DMAR enabled the entire time) without issue. Other things to note: --The failures are very sporadic, often with several days between them. --They don't seem to be directly correlated with heavy disk I/O. I can run -j16 buildworld/buildkernel without issue, yet in some cases these errors h= ave been logged while the system was nearly idle. --In all cases, the transfer in question is an NVMe WRITE (host->device). = The transfer length reported by the nvme0 error log so far has always been 16-2= 56 bytes (so well less than the 4K nvme page size) --In all cases the fault reason reported by the IOMMU is 6, which if I'm reading the VT-d spec correctly means "no read access in the IOMMU paging entry". --In all cases the prp1/prp2 fields reported by the CAM error log are both = 0, which seems surprising given my (very limited) knowledge of the NVMe protoc= ol. --So far there have been no obvious ill effects (no kernel panics, no *apparent* data corruption, no controller failures, etc.). The SSD generating these errors: nda0: There's no other NVMe device on the system in question. I don't suspect a hardware failure here, as I never saw issues while running 13 but immediate= ly started seeing them after updating to 14. >From a quick look at the deltas between stable/13 and stable/14, I don't see any DMAR or NVMe changes that would seem a likely culprit for this issue. = It seems the biggest change was the switch from nvd(4) to nda(4) for the disk device, so I will probably try setting hw.nvme.use_nvd to see if going back= to nvd eliminates the errors (which to me would indicate the more-sophisticated CAM I/O scheduling brought by nda(4) is likely exposing some existing issue= ). --=20 You are receiving this mail because: You are the assignee for the bug.=