Hi,
I'm trying to boot Linux, but the /init process failed. Here is the
info:
=FF<6>/init exit code: -14
/init exit code: -14
<4>Failed to execute /init
Failed to execute /init
<6>/sbin/init exit code: -14
Just wondering what do those different exit codes mean?
Thanks, -J
"Jack Harvard" <[email protected]> writes:
> Hi,
>
> I'm trying to boot Linux, but the /init process failed. Here is the
> info:
>
> =FF<6>/init exit code: -14
> /init exit code: -14
> <4>Failed to execute /init
> Failed to execute /init
> <6>/sbin/init exit code: -14
>
> Just wondering what do those different exit codes mean?
#define EFAULT 14 /* Bad address */
Andreas.
--
Andreas Schwab, SuSE Labs, [email protected]
SuSE Linux Products GmbH, Maxfeldstra?e 5, 90409 N?rnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
On Jan 25 2008 13:40, Jack Harvard wrote:
>Hi,
>
>I'm trying to boot Linux, but the /init process failed. Here is the
>info:
>
>=FF<6>/init exit code: -14
>/init exit code: -14
><4>Failed to execute /init
>Failed to execute /init
> <6>/sbin/init exit code: -14
>
>Just wondering what do those different exit codes mean?
asm-generic/errno-base.h:#define EFAULT 14 /* Bad address */
On Jan 25, 2008 2:27 PM, Jan Engelhardt <[email protected]> wrote:
>
>
> On Jan 25 2008 13:40, Jack Harvard wrote:
> >Hi,
> >
> >I'm trying to boot Linux, but the /init process failed. Here is the
> >info:
> >
> >=FF<6>/init exit code: -14
> >/init exit code: -14
> ><4>Failed to execute /init
> >Failed to execute /init
> > <6>/sbin/init exit code: -14
> >
> >Just wondering what do those different exit codes mean?
>
> asm-generic/errno-base.h:#define EFAULT 14 /* Bad address */
>
Also, before the init process hung up and printed out /init exit code:
-14, it printed out the following symbol
?
Which doesn't make any sense to me, just wondering what could have
caused this? it's unlikely due to baud rate and printed out something
unreadable.
On Jan 25 2008 14:39, Jack Harvard wrote:
>> On Jan 25 2008 13:40, Jack Harvard wrote:
>> >Hi,
>> >
>> >I'm trying to boot Linux, but the /init process failed. Here is the
>> >info:
>> >
>> >=FF<6>/init exit code: -14
>> >/init exit code: -14
>> ><4>Failed to execute /init
>> >Failed to execute /init
>> > <6>/sbin/init exit code: -14
>> >
>> >Just wondering what do those different exit codes mean?
>>
>> asm-generic/errno-base.h:#define EFAULT 14 /* Bad address */
>>
>
>Also, before the init process hung up and printed out /init exit code:
>-14, it printed out the following symbol
>ÿ
>Which doesn't make any sense to me, just wondering what could have
>caused this? it's unlikely due to baud rate and printed out something
>unreadable.
ÿ is 255. While this could indicate a serial transmission error (my
guess: bad timing), printing -14 repeatedly certainly does not.
Is the ÿ reproducable, does it happen every time?
On Jan 25, 2008 3:02 PM, Jan Engelhardt <[email protected]> wrote:
>
>
> On Jan 25 2008 14:39, Jack Harvard wrote:
> >> On Jan 25 2008 13:40, Jack Harvard wrote:
> >> >Hi,
> >> >
> >> >I'm trying to boot Linux, but the /init process failed. Here is the
> >> >info:
> >> >
> >> >=FF<6>/init exit code: -14
> >> >/init exit code: -14
> >> ><4>Failed to execute /init
> >> >Failed to execute /init
> >> > <6>/sbin/init exit code: -14
> >> >
> >> >Just wondering what do those different exit codes mean?
> >>
> >> asm-generic/errno-base.h:#define EFAULT 14 /* Bad address */
> >>
> >
> >Also, before the init process hung up and printed out /init exit code:
> >-14, it printed out the following symbol
> >?
> >Which doesn't make any sense to me, just wondering what could have
> >caused this? it's unlikely due to baud rate and printed out something
> >unreadable.
>
> ? is 255. While this could indicate a serial transmission error (my
> guess: bad timing), printing -14 repeatedly certainly does not.
> Is the ? reproducable, does it happen every time?
>
This is reproduceable and it happens every time. IMHO, I also suspect
this could be caused by some obscure timing issues, as the kernel is
booting up from an FPGA-prototyped SoC, the same Linux image was
running fine on a previous build of FPGA-prototyped SoC, but it's
coming across this /init failed problem repeatedly on the currently
running newly built bit file.
On Jan 25, 2008 3:34 PM, Jack Harvard <[email protected]> wrote:
>
> On Jan 25, 2008 3:02 PM, Jan Engelhardt <[email protected]> wrote:
> >
> >
> > On Jan 25 2008 14:39, Jack Harvard wrote:
> > >> On Jan 25 2008 13:40, Jack Harvard wrote:
> > >> >Hi,
> > >> >
> > >> >I'm trying to boot Linux, but the /init process failed. Here is the
> > >> >info:
> > >> >
> > >> >=FF<6>/init exit code: -14
> > >> >/init exit code: -14
> > >> ><4>Failed to execute /init
> > >> >Failed to execute /init
> > >> > <6>/sbin/init exit code: -14
> > >> >
> > >> >Just wondering what do those different exit codes mean?
> > >>
> > >> asm-generic/errno-base.h:#define EFAULT 14 /* Bad address */
> > >>
> > >
> > >Also, before the init process hung up and printed out /init exit code:
> > >-14, it printed out the following symbol
> > >?
> > >Which doesn't make any sense to me, just wondering what could have
> > >caused this? it's unlikely due to baud rate and printed out something
> > >unreadable.
> >
> > ? is 255. While this could indicate a serial transmission error (my
> > guess: bad timing), printing -14 repeatedly certainly does not.
> > Is the ? reproducable, does it happen every time?
> >
>
> This is reproduceable and it happens every time. IMHO, I also suspect
> this could be caused by some obscure timing issues, as the kernel is
> booting up from an FPGA-prototyped SoC, the same Linux image was
> running fine on a previous build of FPGA-prototyped SoC, but it's
> coming across this /init failed problem repeatedly on the currently
> running newly built bit file.
>
Here is the terminal printout from the correct bootup on a previous build.
<6>Freeing init memory: 584K
Freeing init memory: 584K
init started: BusyBox v0.60.5 (2006.06.15-11:12+0000) multi-call binary
Bummer, could not run '/etc/init.d/rcS': No such file or directory
?
Please press Enter to activate this console.
It looks that it's printing out several ? first and then replaced them
with "init started: BusyBox..." seems quite obscure, as the only
difference between those two FPGA builds is they were built at
different runs using exactly the same source files.
Jack Harvard wrote:
> This is reproduceable and it happens every time. IMHO, I also suspect
> this could be caused by some obscure timing issues, as the kernel is
> booting up from an FPGA-prototyped SoC, the same Linux image was
> running fine on a previous build of FPGA-prototyped SoC, but it's
> coming across this /init failed problem repeatedly on the currently
> running newly built bit file.
Sounds like a problem in your drivers, and/or your memory controller.
Especially the memory controller.
-hpa
-14 is EFAULT. This means that there was some access
to memory that was not mapped.
In the future, check /usr/include/asm/errno.h for exit
codes. Of course in user-space they are positive with
-1 being return from the function-call and errno being
set to this code. In the kernel, they are combined with
'error' being the negative of the return code.
On Fri, 25 Jan 2008, Jack Harvard wrote:
> Hi,
>
> I'm trying to boot Linux, but the /init process failed. Here is the
> info:
>
> =FF<6>/init exit code: -14
> /init exit code: -14
> <4>Failed to execute /init
> Failed to execute /init
> <6>/sbin/init exit code: -14
>
> Just wondering what do those different exit codes mean?
>
> Thanks, -J
> --
Cheers,
Dick Johnson
Penguin : Linux version 2.6.22.1 on an i686 machine (5588.29 BogoMips).
My book : http://www.AbominableFirebug.com/
_
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.