This is on mercat2 during shutdown -p now: EFI RT fault breakpoint instruction fault Fatal trap 3: breakpoint instruction fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0x7bd26be8 stack pointer = 0x28:0xfffffe00fee06ba8 frame pointer = 0x28:0xfed1c000 code segment = base rx0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 1 (init) rdi: fffffe00fee06ce8 rsi: 0000000000000001 rdx: 0000000000000000 rcx: 00000000800f8040 r8: 0000000000000000 r9: 0000000000000000 rax: 0000000000000000 rbx: 0000000000000002 rbp: 00000000fed1c000 r10: 00000000800f8000 r11: 0000000000000004 r12: fffff800012fbd80 r13: fffffe00dba02010 r14: fffff8000124b680 r15: fffff8000124b6a8 trap number = 3 EFI rt_reset call faulted, error 14 acpi0: Powering system off I just put it here for the archives. If someone wants to work on this let me know; otherwise simply close it after a few months. I have no historic data as I only temporary used the machine.
This is a BIOS problem, FreeBSD only reports the issue.
(In reply to Konstantin Belousov from comment #1) Then I 'll just go ahead and close it right away.
We just print the diagnostic info but then carry on, right? I wonder if we should make it more clear that there's no action to take here.
(In reply to Ed Maste from comment #3) Kernel continues to run, but of course the faulted EFI RT call is aborted. Feel free to add something to 'EFI <call name> call faulted' line. I do not want to blow kernel with lectures about computer organization.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=ddabf7f3ea4f0497dc5a5ffcbbb1d852ea77a4cd commit ddabf7f3ea4f0497dc5a5ffcbbb1d852ea77a4cd Author: Ed Maste <emaste@FreeBSD.org> AuthorDate: 2025-11-26 19:28:13 +0000 Commit: Ed Maste <emaste@FreeBSD.org> CommitDate: 2026-04-28 15:11:46 +0000 amd64: Make EFI runtime faults look less like panics EFI runtime faults may be mistaken for kernel panics, and do not necessarily represent actual problems. Try to differentiate them some more by printing "EFI runtime trap" rather than "Fatal trap". PR: 291193 Reviewed by: kib Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D56309 sys/amd64/amd64/trap.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
A commit in branch stable/15 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=314c85574ae08eea6499380556decfcda3e0f49c commit 314c85574ae08eea6499380556decfcda3e0f49c Author: Ed Maste <emaste@FreeBSD.org> AuthorDate: 2025-11-26 19:28:13 +0000 Commit: Ed Maste <emaste@FreeBSD.org> CommitDate: 2026-06-11 17:08:35 +0000 amd64: Make EFI runtime faults look less like panics EFI runtime faults may be mistaken for kernel panics, and do not necessarily represent actual problems. Try to differentiate them some more by printing "EFI runtime trap" rather than "Fatal trap". PR: 291193 Reviewed by: kib Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D56309 (cherry picked from commit ddabf7f3ea4f0497dc5a5ffcbbb1d852ea77a4cd) sys/amd64/amd64/trap.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)