Subject: Re: port-amd64/32400: init loops getting signal 4 on Atlon X2 64
To: None <port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Quentin Garnier <cube@cubidou.net>
List: netbsd-bugs
Date: 12/28/2005 12:45:02
The following reply was made to PR port-amd64/32400; it has been noted by GNATS.

From: Quentin Garnier <cube@cubidou.net>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-amd64/32400: init loops getting signal 4 on Atlon X2 64
Date: Wed, 28 Dec 2005 13:43:27 +0100

 --bNLLTo5eXWXFd6av
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Wed, Dec 28, 2005 at 11:55:00AM +0000, Bernhard Moellemann wrote:
 > >Number:         32400
 > >Category:       port-amd64
 > >Synopsis:       init loops getting signal 4 on Atlon X2 64 with amd64
 [...]=20
 > 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.
 
 This is subtle:  it claims it can run i386 binaries (and it's true), but
 it doesn't claim to boot off an i386 userland (far from it actually).
 
 It'd be interesting to know exactly what is happening though.  I don't
 know if it is the project's goal, but my work on COMPAT_NETBSD32 aims at
 doing this eventually.  Still a long way, though.
 
 --=20
 Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
 "When I find the controls, I'll go where I like, I'll know where I want
 to be, but maybe for now I'll stay right here on a silent sea."
 KT Tunstall, Silent Sea, Eye to the Telescope, 2004.
 
 --bNLLTo5eXWXFd6av
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.6 (NetBSD)
 
 iQEVAwUBQ7KIb9goQloHrPnoAQI1+wgAjDhFEdyiEvVip5f1Lajjc+wV0Ga2V59b
 ITwjBL9202uPPht8TFmK7Oy1GnyWdS8ZXvQrrZ62TM++0gbfGIjBemnhJD5b4Y84
 lsd0V3bo44r7ovcQEbuvqZAFvDW51eNhp+kSIynwgI47sRJnKyyrE58bXL0tndKd
 nPn7YqLnfrrIHLZ5NLtnpJvpJVEjgV2++uhIcK+wMcEepMQ5xWrl//rToBmev3gE
 6BeYYJcS6zXUVUAF9SmeJ+3FP0xrIrcKA6IVnlgfPJZURv/D5MxBraUaPZkFt7fD
 LFhGYxBhtRfV4uyuusRxGI9KOLtEaKUHGYb05wnry2BYDOZWlbBCMg==
 =1Sge
 -----END PGP SIGNATURE-----
 
 --bNLLTo5eXWXFd6av--