Re: panic: init died (signal 0, exit 12) during booting

[newbie <mailto635%yahoo.com@localhost>]

Hi Christos,

Thanks.

>That is very strange. Perhaps some shared library loading issue? Do you
>see a lot of other syscalls passing by? 
yes. few printed syscall codes in the LIFO order are:
1 430 430 56 33 54 147 4 449 5 1 308 2 340 340 202 4 308 430 
etc.


>Can you boot -a and try /rescue/init?
I do not know about this. could you describe more about this?

christos


--- On Tue, 3/17/09, newbie <mailto635%yahoo.com@localhost> wrote:


From: newbie <mailto635%yahoo.com@localhost>
Subject: Re: panic: init died (signal 0, exit 12) during booting
To: christos%astron.com@localhost, tech-kern%netbsd.org@localhost
Date: Tuesday, March 17, 2009, 11:01 AM


Hi Christos,

Thanks for your reply.

I put a printf in syscall.c to print the syscall number and the last syscall 
number before the panic is 1 (i.e. sys_exit). I guess this is a supported 
syscall. 

What else could be the problem?

Regards

>I am trying to bring up NetBSD-5_RC2 on an ARM based platform (upto
>serial console). Currently I am using ramdisk as the root file system
>and Cygwin as the development host. 
>
>I am getting the following panic during initial boot. 
>panic: init died (signal 0, exit 12).
>
>What are the reasons to get this panic? Any hints and suggestions would
>be appreciated.

init seems to want to execute a system call that the kernel does not support.
perhaps you are running a newer userland? Put a printf in syscall.c to print
the number of the syscall you are running, and the last one printed will be
the one not supported.

christos