From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QD6fF-00028a-V4 for garchives@archives.gentoo.org; Fri, 22 Apr 2011 03:04:14 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9661F1C0BF for ; Fri, 22 Apr 2011 03:04:13 +0000 (UTC) Received: from smtp.newsguy.com (smtp.newsguy.com [74.209.136.69]) by pigeon.gentoo.org (Postfix) with ESMTP id 1C2F21C02A for ; Fri, 22 Apr 2011 02:15:12 +0000 (UTC) Received: from [192.168.1.101] (CPE-76-178-190-196.natnow.res.rr.com [76.178.190.196] (may be forged)) by smtp.newsguy.com (8.14.3/8.14.3) with ESMTP id p3M2FBNZ079870 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 21 Apr 2011 19:15:12 -0700 (PDT) (envelope-from mikedunn@newsguy.com) Message-ID: <4DB0E452.6000505@newsguy.com> Date: Thu, 21 Apr 2011 19:13:38 -0700 From: Mike Dunn User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110408 Lightning/1.0b3pre Thunderbird/3.1.9 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-embedded@lists.gentoo.org Reply-to: gentoo-embedded@lists.gentoo.org MIME-Version: 1.0 To: gentoo-embedded@lists.gentoo.org Subject: Re: [gentoo-embedded] gentoo baselayout "Attempted to kill init" References: <160bcfee9bc8fef34133fd6ded0ac838@basementcode.com> In-Reply-To: <160bcfee9bc8fef34133fd6ded0ac838@basementcode.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: 1f06678f6f870b356e19dcd25abf1589 On 04/21/2011 02:18 PM, chris@basementcode.com wrote: > I've got a filesystem created with the following toolchain: (from crossdev) > > arm-unknown-linux-gnu- > > with > > arm-unknown-linux-gnu-emerge system > arm-unknown-linux-gnu-emerge baselayout > > I created the kernel separately, and was able to boot it with another > filesystem that was created by somebody else. > > During the boot process the kernel says "Attempted to kill init" because the > /init program exited for some reason. > The problem is that I can't get any other error from the init program. I have > no idea why it's exiting. It could be a missing library, segfault or bad > invocation, so I have no idea where to start. > > Beyond emerging system and baselayout, there will be some hand tweaking and sysadmin chores involved with getting a working bootable root filesystem. The error you see is very common with what you are doing and usually caused by missing libraries required by the init process. You can check which libraries are needed by a particular utility by running (on the build host): readelf -d /path/to/target/utility | grep NEEDED I recommend creating a separate minimal rootfs and building it into the kernel as an initramfs. The minimal filesystem need only contain a statically built busybox and a simple /init shell script that does a few things like mounting /proc and /sys and then execs the shell. See http://en.gentoo-wiki.com/wiki/Initramfs for some guidance. Once this has succesfully booted, you can mount and chroot into your real rootfs and troubleshoot it. HTH Mike