>Number:         32400
>Category:       port-amd64
>Synopsis:       init loops getting signal 4 on Atlon X2 64 with amd64
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-amd64-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 28 11:55:00 +0000 2005
>Originator:     Bernhard Moellemann
>Release:        NetBSD 3.99.15 (2005-12-26)
>Organization:
>Environment:
System: NetBSD arcanic 3.99.11 NetBSD 3.99.11 (ARCANIC-3.99) #0: Sat Nov 12 19:39:32 CET 2005 root@arcanic:/usr/src-3.99.11/sys/arch/i386/compile/ARCANIC-3.99 i386
Architecture: amd64
Machine: amd64
>Description:
This is a machine with an Athlon X2 64 on a NForce4 mainboard (kind of Asus
A8N). The machine runs with an i386 3.99.11 kernel. dmesg is at
http://circinus.de/multic-dmesg.txt

I have installed the 3.99.15 amd64 bootloader (stage 1 and 2) and want use
an 3.99.15 amd64 kernel (conf is at http://circinus.de/MULTIC_ACPI.txt)
The kernel is ACPI and was crossbuild with the i386 environment. Without
ACPI it hangs during device detection, but this is not to be handled in
this PR.

When booting this amd64 kernel the box runs through (most of?) the device
detection and then displays "Process (pid 1) got signal 4"
in an endless loop. The last message I _see_ is configuration of
wd0. But this takes some time and afterwardes the console and all buffers
are flushed with the above messeage. There may be a dozend of messages
in between wd0 and the loop. So the kernel may have approached (my i386)
userland. But the kernel has compat_netbsd32 and the amd64 port claims
it can run i386 binaries.

Entering the kernel debugger is possible and ps shows that process 1 is
COMMAND "init" with FLAGS "0x44000" and the field "WAIT" is empty.

>How-To-Repeat:
Build amd64 of 2005-12-26, and boot it with Athlon X2 64 on NForce4
with i386 userland.
>Fix:
wanted