linux-kernel - Re: Q: linux failed to execute /init?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a72f6a3c0801250747n4861d55vbab3bd35b26c8219@mail.gmail.com>
Date:	Fri, 25 Jan 2008 15:47:24 +0000
From:	"Jack Harvard" <jack.harvard@...glemail.com>
To:	"Jan Engelhardt" <jengelh@...putergmbh.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Q: linux failed to execute /init?

On Jan 25, 2008 3:34 PM, Jack Harvard <jack.harvard@...glemail.com> wrote:
>
> On Jan 25, 2008 3:02 PM, Jan Engelhardt <jengelh@...putergmbh.de> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/