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

From	lists+debian@aero2k.de
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#1111027: Acknowledgement (linux-image-6.12.38+deb13-amd64: HP Gen8: Crashing with 6.12 from trixie, NMI error in IML logs)
Date	2025-08-31 09:40 +0200
Message-ID	<LpKPn-bGxS-3@gated-at.bofh.it> (permalink)
References	<Ljo5b-7khn-1@gated-at.bofh.it> <LpKPn-bGxS-5@gated-at.bofh.it> <Ljo5b-7khn-1@gated-at.bofh.it> <LpKPn-bGxS-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

I ran some more tests with a fresh trixie install, and can tell that those measurements previously taken don't help here:

- disabling intel_iommu(=off in cmdline)

- blacklisting hpwdt (which was not loaded in bookworm, but is in trixie kernel, was the same with a bookworm base installation)

It takes a variable amount of hours, up to 2-3 days, and then my (now idle) cube blinks red again.


IML:

"ID","Severity","Class","Last Update","Initial Update","Count","Description",
"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","08/31/2025 07:10","08/25/2025 20:45","12","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)",

No dmesg entries (lured using tmux, dmesg -Tw from another machine) on freeze.

Now at 6.12.41+deb13-amd64

Any other ideas?

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

Thread

Bug#1111027: Acknowledgement (linux-image-6.12.38+deb13-amd64: HP Gen8: Crashing with 6.12 from trixie, NMI error in IML logs) lists+debian@aero2k.de - 2025-08-31 09:40 +0200

csiph-web