Date: Mon, 12 Jan 2026 16:13:58 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 292410] nvme: repeated "async event occurred" console spam Message-ID: <bug-292410-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292410 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 OPNsense 25.7 when attempting to install on a lower-quality Silicon Power NVMe drive (SP500GBP44UD900). When live booting to perform an install the console would 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 generates 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 in 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 ahead 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 two 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=50307 My Fixed Branch: https://github.com/jwidess/src/tree/25.7-async-tunable - Primary Commit: 6e0b458a1da959986c2746d393f1238b76d4621a - Secondary Commit that adds logging: 6e0b458a1da959986c2746d393f1238b76d4621a Confirmed on: freebsd releng/14.3 & stable/14 (Originally observed when running OPNsense 25.7, which tracks 14.3). NVMe Base Specification, Revision 1.4c - Ref, - Page 98, Figure 146: Asynchronous Event Request – Completion Queue Entry Dword 0 - Page 118, Figure 195: Get Log Page – Log Page Identifiers SP500GBP44UD900 nvmecontrol Output: ``` ~ # nvmecontrol logpage -p 2 nvme0 SMART/Health Information Log ============================ 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 ``` -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-292410-227>