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

Path	csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod
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	Sat, 06 Sep 2025 07:50:01 +0200
Message-ID	<LrTYd-dbd7-23@gated-at.bofh.it> (permalink)
References	<Ljo5b-7khn-1@gated-at.bofh.it>
X-Original-To	1111027@bugs.debian.org
X-Mailbox-Line	From debian-bugs-dist-request@lists.debian.org Sat Sep 6 05:49:08 2025
Old-Return-Path	<debbugs@buxtehude.debian.org>
X-Spam-Flag	NO
X-Spam-Score	-1.899
Reply-To	Thorsten Sperber <lists+debian@aero2k.de>, 1111027@bugs.debian.org
Resent-To	debian-bugs-dist@lists.debian.org
Resent-Cc	debian-kernel@lists.debian.org
X-Debian-Pr-Message	followup 1111027
X-Debian-Pr-Package	src:linux
X-Debian-Pr-Source	linux
MIME-Version	1.0
User-Agent	Mozilla Thunderbird
Content-Language	en-US
Content-Type	text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding	8bit
X-Debian-Message	from BTS
X-Mailing-List	<debian-bugs-dist@lists.debian.org> archive/latest/1923347
List-ID	<debian-bugs-dist.lists.debian.org>
List-URL	<https://lists.debian.org/debian-bugs-dist/>
Approved	robomod@news.nic.it
Lines	19
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Sat, 6 Sep 2025 07:47:40 +0200
X-Original-Message-ID	<5fc96c8c-4618-4ff3-8dba-36ec674febe6@aero2k.de>
X-Original-References	<175510789123.203101.6246500216299289705.reportbug@heimdall.asgard>
Xref	csiph.com linux.debian.bugs.dist:1260173 linux.debian.kernel:89076

Cross-posted to 2 groups.

Show key headers only | 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