Bug#1111027: linux-image-6.12.38+deb13-amd64: HP Gen8: Crashing with 6.12 from trixie, NMI error in IML logs

From	Thorsten Sperber <lists+debian@aero2k.de>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#1111027: linux-image-6.12.38+deb13-amd64: HP Gen8: Crashing with 6.12 from trixie, NMI error in IML logs
Date	2025-09-06 07:50 +0200
Message-ID	<LrTYd-dbd7-23@gated-at.bofh.it> (permalink)
References	<Ljo5b-7khn-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

Hate to be like this, but I was wrong again. The box is not entirely dead, but blinks read (for the first time it behaves like this, I haven't physically looked at the box until now, today). Timestamp in IML entry roughly matches dmesg time (off by 20 minutes after a week looks normal to me). So it _is_ the cause (?).


"ID","Severity","Class","Last Update","Initial Update","Count","Description",
"100","Critical","OS","09/05/2025 20:57","09/05/2025 20:57","1","User Initiated NMI Switch",
"99","Critical","System Error","09/05/2025 20:57","09/05/2025 20:57","1","Unrecoverable System Error (NMI) has occurred.  System Firmware will log additional details in a separate IML entry if possible",
"98","Critical","OS","09/05/2025 19:12","09/05/2025 19:12","1","User Initiated NMI Switch",
"97","Critical","System Error","09/05/2025 19:12","09/05/2025 19:12","1","Unrecoverable System Error (NMI) has occurred.  System Firmware will log additional details in a separate IML entry if possible",
"96","Critical","OS","08/31/2025 04:01","08/31/2025 04:01","1","User Initiated NMI Switch",
"95","Critical","System Error","08/31/2025 04:01","08/31/2025 04:01","1","Unrecoverable System Error (NMI) has occurred.  System Firmware will log additional details in a separate IML entry if possible",
"94","Critical","OS","08/29/2025 17:04","08/29/2025 17:04","1","User Initiated NMI Switch",
"93","Critical","System Error","08/29/2025 17:04","08/29/2025 17:04","1","Unrecoverable System Error (NMI) has occurred.  System Firmware will log additional details in a separate IML entry if possible",
"92","Critical","OS","08/29/2025 14:48","08/29/2025 14:48","1","User Initiated NMI Switch",
"91","Critical","System Error","08/29/2025 14:48","08/29/2025 14:48","1","Unrecoverable System Error (NMI) has occurred.  System Firmware will log additional details in a separate IML entry if possible",
"90","Critical","OS","08/26/2025 09:47","08/26/2025 09:47","1","User Initiated NMI Switch",
"89","Critical","System Error","08/26/2025 09:47","08/26/2025 09:47","1","Unrecoverable System Error (NMI) has occurred.  System Firmware will log additional details in a separate IML entry if possible",
"88","Caution","POST Message","08/25/2025 20:46","08/25/2025 20:46","1","POST Error: 1785-Slot X Drive Array Not Configured",
"87","Informational","POST Message","09/05/2025 19:21","08/25/2025 20:45","13","POST Information: Processor 1, DIMM 2 could not be authenticated as genuine HP SmartMemory. Enhanced and extended HP SmartMemory features will not be active.",
"86","Informational","Maintenance","[NOT SET] ","[NOT SET] ","1","IML Cleared (iLO 4 user:me)",

Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread

Thread

Bug#1111027: linux-image-6.12.38+deb13-amd64: HP Gen8: Crashing with 6.12 from trixie, NMI error in IML logs Thorsten Sperber <lists+debian@aero2k.de> - 2025-09-06 07:50 +0200

csiph-web