From nobody Mon Jan 12 16:13:58 2026 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 4dqcrQ5JVFz6NmtL for ; Mon, 12 Jan 2026 16:13:58 +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 "R13" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dqcrQ4qgBz3qYB for ; Mon, 12 Jan 2026 16:13:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1768234438; 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=lURkYr7gbHPTGud3v/iFQKuu2r9D0c2QSCCkgMVHVW8=; b=idMlNCJ05o2h4ShShNr24FrOcqsBuvmxhNyyk7av95Uqhm9ytN0YQ/fQHcjCSktPBJt7mr fK3f11EWxHKvJWzKNfp+oNFt5shmU4SrLATO46FQUe/gWPoyt3R4OpM2dACaK35KIpceki +GGQYhnGiBc6aTnoCXlWFG6gNxqNpYMP2EssDiGMEjbibVEhis82sL7nwQr7wKQazZvOJM 3UV+rF9iinGe0NYjOiPn0x2HAZezvaLqYrmXcFYwC13qE8LcCjpy1PiEb3cBKVZo1JO1W0 2ysfRx17wRlLboxUlXXM+8pzqRw9ugHZkcmc3XGBDTfX6RPcnt+AZFiC2JHm4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1768234438; 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=lURkYr7gbHPTGud3v/iFQKuu2r9D0c2QSCCkgMVHVW8=; b=gPbZErihFmyyDMnLI64ES3x1XQApRqLovc8h/Ptt8UBbkob9ki4HZqsIULjNb0Pswx+HBe KlPNo/YYZ/W2OkyTNcExSW/7LwPBM/sDT+GxlV8QeAy2vnRHYeO1GLdInSULXa1AOeYNOA HKlQVgkbSUX8iK1CxLqzX1iAid9xQ3lzHipLgQsuXp3m3BRY5S9z4wJ+rokAG4bZfZ+F3g n7w0QvAWhIa3Tb375V2/7PrE2tUSMrYYS8a3Zr1TFrZtHxXj1dONTOUC1+ERjeXcV3GBdt vnLnfhWYnke8OVdNwGDgbSP14gi2Jpw7He/6gy9zQcb1CSUWhN3QziwvHY+/Ug== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1768234438; a=rsa-sha256; cv=none; b=nDqUojPn4Caj06xBndGbngiV7FCFvMvzAQ+NQsUusO+P4oCdHPkSrddNoUmx3sNUt69hi/ 83YIAb8vpVI3oPqD59kYr24ZRknUA8ePjZnDbEkz+ZdDHw7KDeCa2ocRxWcMEEKcjYpCjM EDqKPL5GqcXLrUjd9k2yvf+Z6dmkXgpFkDmL/llE1xW+txxzEz5XiD1wfGYXQAaE3S+kuc 173XK2e4y35dZVQW/fhPwteFAH9jYSVPyM4o6OIaklPneM3aRZT9rA8HEju7DTuCeJhYCk 7O1DLWdHdA5V4eG80q0A9LWJ7x9HZDzLLpkUMUwZuS7b3s0cWovO69XYphNknQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4dqcrQ4QCVzZLJ for ; Mon, 12 Jan 2026 16:13:58 +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 60CGDw3C031288 for ; Mon, 12 Jan 2026 16:13:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 60CGDwTn031287 for bugs@FreeBSD.org; Mon, 12 Jan 2026 16:13:58 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 292410] nvme: repeated "async event occurred" console spam Date: Mon, 12 Jan 2026 16:13:58 +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.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: justinwiden1@gmail.com 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-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" 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=3D292410 Bug ID: 292410 Summary: nvme: repeated "async event occurred" console spam Product: Base System Version: 14.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: justinwiden1@gmail.com Hello all, This is my first bug report, so please forgive any informality. I will do my best to include as much pertinent info as possible. This bug stems from an issue I was experiencing on an x86 Mini PC with OPNs= ense 25.7 when attempting to install on a lower-quality Silicon Power NVMe drive (SP500GBP44UD900). When live booting to perform an install the console woul= d be flooded with the following messages: nvme0: async event occurred (type 0x1, info 0x01, page 0x02) These appear to be SMART/Health related (reference NVMe spec pages below), = and I have not observed this with any other NVMe drives. These messages are generated at such a rate it's impossible to use the console and thus makes = it rather difficult to install. I decided to look further into this and found /sys/dev/nvme_ctrlr.c generat= es these messages on line 795. To address this for the time being, I added a tunable (hw.nvme.log_async_events) that essentially just wraps this print i= n an if statement controlled by a sysctl tunable, which allows you to disable the logging of these messages. I branched OPNsense src 25.7 for this, but the 3x files I've modified are identical to both releng/14.3 & stable/14. I went a= head and built with this change, booted, applied my tunable, and it was smooth sailing from there. Below is additional info, along with my branch and my t= wo commits to address this. Please let me know if this is the correct place to post this, and if I should submit a PR somewhere. Original Forum Post: https://forum.opnsense.org/index.php?topic=3D50307 My Fixed Branch: https://github.com/jwidess/src/tree/25.7-async-tunable - Primary Commit: 6e0b458a1da959986c2746d393f1238b76d4621a - Secondary Commit that adds logging: 6e0b458a1da959986c2746d393f1238b76d46= 21a Confirmed on: freebsd releng/14.3 & stable/14 (Originally observed when run= ning OPNsense 25.7, which tracks 14.3). NVMe Base Specification, Revision 1.4c - Ref, - Page 98, Figure 146: Asynchronous Event Request =E2=80=93 Completion Queu= e Entry Dword 0 - Page 118, Figure 195: Get Log Page =E2=80=93 Log Page Identifiers SP500GBP44UD900 nvmecontrol Output: ``` ~ # nvmecontrol logpage -p 2 nvme0 SMART/Health Information Log =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D Critical Warning State: 0x00 Available spare: 0 Temperature: 0 Device reliability: 0 Read only: 0 Volatile memory backup: 0 Temperature: 311 K, 37.85 C, 100.13 F Available spare: 100 Available spare threshold: 10 Percentage used: 0 Data units (512,000 byte) read: 7531 Data units written: 10305 Host read commands: 216800 Host write commands: 150867 Controller busy time (minutes): 2596 Power cycles: 32 Power on hours: 43 Unsafe shutdowns: 9 Media errors: 0 No. error info log entries: 0 Warning Temp Composite Time: 0 Error Temp Composite Time: 0 Temperature 1 Transition Count: 0 Temperature 2 Transition Count: 0 Total Time For Temperature 1: 0 Total Time For Temperature 2: 0 ``` --=20 You are receiving this mail because: You are the assignee for the bug.=