Issue #604 has been updated by Walter Sonius. % Done changed from 0 to 100
Thanks to Angel Pons his hint to clear the whole `register "gpe0_en_1" = "0x2146"` line in `devicetree.cb` warm boots function correct! More specific setting the first byte to 0 as in "0x0146" has the same effect of fixing warm boots. Shutdown, reboot and wakes are not affected and still function. ---------------------------------------- Bug #604: mb/hp: ProDesk 600 G1 SFF (Haswell / NPCD379) warm boot freezes https://ticket.coreboot.org/issues/604#change-2118 * Author: Walter Sonius * Status: New * Priority: Normal * Category: board support * Target version: none * Start date: 2025-07-30 * Affected versions: 25.03 ---------------------------------------- This board is still WIP code, see [review.coreboot.org](https://review.coreboot.org/c/coreboot/+/88616) Warm boots as in poweron after a previous successful shutdown will hang/freeze boot after "NMI sources disabled" but before [DEBUG] LynxPoint H PM init? However reboots and cold boots are not affected: ``` [INFO ] NMI sources disabled. ... #endless spew repeating following blocks [NOTE ] coreboot-25.06-77-g812d0e2f626d-dirty Fri Jul 04 13:18:33 UTC 2025 x86_32 smm starting (log level: 7)... [DEBUG] SMI_STS: GPE0 [DEBUG] GPE0_STS: PME_B0 [NOTE ] coreboot-25.06-77-g812d0e2f626d-dirty Fri Jul 04 13:18:33 UTC 2025 x86_32 smm starting (log level: 7)... [DEBUG] SMI_STS: GPE0 [DEBUG] GPE0_STS: PME_B0 [NOTE ] coreboot-25.06-77-g812d0e2f626d-dirty Fri Jul 04 13:18:33 UTC 2025 x86_32 smm starting (log level: 7)... [DEBUG] SMI_STS: GPE0 [DEBUG] GPE0_STS: PME_B0 ... #system might never reach the following line as in freeze or is extreme slow, or hangs during booting OS [DEBUG] LynxPoint H PM init ``` A shutdown before this failing warm boot looks like this coreboot log: ``` [NOTE ] coreboot-25.06-77-g812d0e2f626d-dirty Fri Jul 04 13:18:33 UTC 2025 x86_32 smm starting (log level: 7)... [DEBUG] SMI_STS: PERIODIC SLP_SMI #<----------------------------------------bad shutdown warm boot will freeze [DEBUG] SMI#: Entering S5 (Soft Power off) Or like this also bad warm boot after this shutdown [DEBUG] SMI_STS: SLP_SMI #<-------------------------------------------------also issue on warm boot [DEBUG] SMI#: Entering S5 (Soft Power off) ``` A shutdown before a "correct" warm boot looks like this in coreboot log: ``` [NOTE ] coreboot-25.06-77-g812d0e2f626d-dirty Fri Jul 04 13:18:33 UTC 2025 x86_32 smm starting (log level: 7)... [DEBUG] SMI_STS: GPE0 PM1 [DEBUG] PWRBTN GPE0_STS: PME_B0 #<------------- initiated with help of pressing power button [NOTE ] coreboot-25.06-77-g812d0e2f626d-dirty Fri Jul 04 13:18:33 UTC 2025 x86_32 smm starting (log level: 7)... [DEBUG] SMI_STS: GPE0 SLP_SMI #<------------------------------------------- good shutdown no warm reboot issues [DEBUG] SMI#: Entering S5 (Soft Power off) ``` There might be a lot more to this but these are some differences I noticed related to SMI_STS: xxx SLP_SMI where xxx can be GPEO/empty/PERIODIC: ``` [DEBUG] SMI_STS: GPE0 SLP_SMI == warm boot okay (maybe because powerbutton shutdown?) [DEBUG] SMI_STS: SLP_SMI [DEBUG] SMI_STS: PERIODIC SLP_SMI ``` Any hints welcome, to unblock this port? ---Files-------------------------------- coldboot-fast-dblog.txt (53.1 KB) coldboot-fast-nri-dblog.txt (58.5 KB) prodesk-600-g1-oem-autoport-logs.zip (648 KB) warmboot-slow-dblog.txt (634 KB) warmboot-slow-nri-dblog.txt (164 KB) pd600g1oemv265-npcd379-superiotool.log (4.49 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
