From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] Setup for VMDK to use Direct Disk
Date: Fri, 30 Mar 2012 15:17:17 +0100 [thread overview]
Message-ID: <1640360.hZYVmbFPaV@helios> (raw)
In-Reply-To: <cover.1332826876.git.sgw@linux.intel.com>
On Monday 26 March 2012 22:42:54 Saul Wold wrote:
> Updated comments per Darren's request, added cleanup to
> image-types to only use one -i (inode-count) parameter.
>
> Sau!
> The following changes since commit 644b7503c37fd73730dd3d7841463b158b8934ed:
>
> guile: Deal with hardcoded path issues (2012-03-27 00:28:41 +0100)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib sgw/self
>
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/
> self
So these patches have been merged now; I updated to latest master and re-ran
bitbake self-hosted-image; unfortunately the output doesn't appear to be
usable. I don't know what has gone wrong but during boot there are complaints
that the filesystem is corrupt:
SYSLINUX 4.03 2010-10-22 EDD Copyright (C) 1994-2010 H. Peter Anvin et al
EXT3-fs error (device hda2): ext3_lookup: deleted inode referenced: 581713
EXT3-fs error (device hda2): ext3_lookup: deleted inode referenced: 610383
Kernel panic - not syncing: no init found. Try passing init= option to
kernel.
Running e2fsck -fn on the rootfs.ext3 file shows quite a number of errors.
There were no unusual errors in the log.do_rootfs.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-30 14:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 5:42 [PATCH 0/6] Setup for VMDK to use Direct Disk Saul Wold
2012-03-27 5:42 ` [PATCH 1/6] self-hosted-image: pre-populate the builder user with poky source Saul Wold
2012-03-28 15:35 ` Cui, Dexuan
2012-03-28 21:07 ` Saul Wold
2012-03-29 7:15 ` Cui, Dexuan
2012-03-28 20:45 ` Paul Eggleton
2012-03-28 21:08 ` Saul Wold
2012-03-27 5:42 ` [PATCH 2/6] image-vmdk: Add symbolic link for a short named vmdk image Saul Wold
2012-03-27 5:42 ` [PATCH 3/6] boot-directdisk: Fix Block Calcuation Saul Wold
2012-03-27 5:42 ` [PATCH 4/6] vmdk: Update for direstdisk Saul Wold
2012-03-27 5:42 ` [PATCH 5/6] builder: Enable auto starting of Hob Saul Wold
2012-03-27 5:43 ` [PATCH 6/6] image_types: remove duplicate setting of -i for inode count Saul Wold
2012-03-27 14:37 ` [PATCH 0/6] Setup for VMDK to use Direct Disk Paul Eggleton
2012-03-27 18:16 ` Saul Wold
2012-03-27 20:21 ` Paul Eggleton
2012-03-27 20:45 ` João Henrique Freitas
2012-03-28 15:21 ` Cui, Dexuan
2012-03-30 14:17 ` Paul Eggleton [this message]
2012-03-30 21:16 ` Cui, Dexuan
2012-03-31 5:11 ` Cui, Dexuan
2012-04-01 10:28 ` Cui, Dexuan
2012-04-01 19:43 ` Paul Eggleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1640360.hZYVmbFPaV@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox