On Sun, May 18, 2008 at 01:09:54PM +0200, Christoph Egger wrote:
Manuel Bouyer wrote:
On Sun, May 18, 2008 at 05:59:02PM +1000, James Laird wrote:
Hi,
I'm having trouble with a fresh -current build, running as Dom0 on amd64.
init keeps getting bonked with signal 4 and restarting.
Someone else had the same trouble with a XEN3PAE_DOMU, which was
magically resolved when something changed in CVS (
http://mail-index.netbsd.org/current-users/2008/05/01/msg002169.html ).
I've had a quick poke through the source tree, but I can't see anything
obvious. Does anyone have any suggestions as to where to look for the
trouble?
Not sure. A current kernel built 2 days ago works fine for me as
dom0 for amd64.
What are the normal conditions where the kernels sends SIGILL to userland?
When the CPU sends an illegal intruction trap, I guess.