kern/57520: netbsd-10 amd64 system hangs on reboot

[htodd%twofifty.com@localhost]

>Number:         57520
>Category:       kern
>Synopsis:       netbsd-10 amd64 system hangs on reboot
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 11 22:05:00 +0000 2023
>Originator:     Hisashi T Fujinaka
>Release:        NetBSD 10.0_BETA
>Organization:
none
>Environment:
System: NetBSD mail.i8u.org 10.0_BETA NetBSD 10.0_BETA (CHRIS) #518: Thu Jul 6 10:12:28 PDT 2023 htodd%mail.i8u.org@localhost:/usr/obj/amd64/sys/arch/amd64/compile/CHRIS amd64
Architecture: x86_64
Machine: amd64
>Description:
This is one of several problems I'm having with my Intel system.

My system no longer boots with "shutdown -r" or "reboot" as it either hangs in BIOS (less common)
or hangs after trying to start up the CPUs (very common). I bisected the kernel and probably need
more investigation around the particular commit, but here's what bisect said was the bad commit:

[htodd@mara]/home/netbsd-git/src 1169 % git bisect good
5dc4f69652439cc1381a2f97747e783b95804f85 is the first bad commit
commit 5dc4f69652439cc1381a2f97747e783b95804f85
Author: martin <martin%NetBSD.org@localhost>
Date:   Thu Mar 30 11:41:07 2023 +0000

    Pull up following revision(s) (requested by bouyer in ticket #129):

            sys/kern/vfs_xattr.c: revision 1.39

    extattr_set_vp(): properly handle XATTR_REPLACE flags, FFSv2ea will return
    ENOATTR, not ENODATA if the attribute is missing.

    Makes glusterfs 10 run on a FFSv2ea file system.

 sys/kern/vfs_xattr.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

This is my local server so I'd rather not have it out of commission very long.

I marked this as high because rebooting requires a physical presence with this
problem.

I will provide the kernel config (commenting out several things) later, because
the GENERIC kernel panics.
>How-To-Repeat:
Just reboot the system with the latest kernel.
>Fix: