From: Doug Kehn <rdkehn@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 Root Filesystem and Linux 2.6.19
Date: Sun, 4 Feb 2007 05:43:11 -0800 (PST) [thread overview]
Message-ID: <53943.37121.qm@web51903.mail.yahoo.com> (raw)
In-Reply-To: <142644.61282.qm@web51907.mail.yahoo.com>
Hi All,
Some additional information/clarification.
> --- Doug Kehn wrote:
>
> > Hi All,
> >
> > Target: ADI Coyote, Intel XScale IXP-425,
> bigendian
> > Source: uClinux-dist-test-20070108
> > Linux 2.6.19
> > uClibc 0.9.27
> > Busybox 1.0.0
> > Toolchain: arm-linux-tools-20061213
> > binutils-2.16
> > gcc-3.4.4
> > glibc-2.3.3
> > glibc-linuxthreads-2.3.3
> >
> > When the kernel is configured for a jffs2 rootfs,
> > some
> > apps fail to load with either a Segment Fault or
> > "'/lib' is not an ELF file" the first time they
> are
> > executed. The second and subsequent executions of
> > the
> > same app work properly. Attached is a sample boot
> > log. MTD and JFFS2 debugging information has been
> > enabled.
> >
> > If, on the other hand, the kernel is configured
> for
> > an
> > initrd and the jffs2 partition is mounted with
> > 'mount'
> > after boot, this error does not occur.
> >
I should have said if the rootfs is a ramdisk, sorry.
The stock kernel command line for ADI Coyote in
uClinux is:
CONFIG_CMDLINE="console=ttyS0,115200 root=/dev/ram0
initrd=0x00800000,8M mem=64M@0x00000000"
Then from the shell:
# mount -n -t jffs2 -o rw,noatime /dev/mtdblock2
/mnt/jffs2
Then running /mnt/jffs2/bin/<app> does not produce
the error.
I then tried an initrd with a kernel command line of
CONFIG_CMDLINE="console=ttyS0,115200 root=/dev/ram0
init=/linuxrc rw initrd=0x03E00000,1M
mem=64M@0x00000000"
and a linuxrc of
#!/bin/sh
echo"initrd: mounting jffs2 rootfs
mkdir /jffs2
mount -n -t jffs2 -o rw,noatime /dev/mtdblock2
/jffs2
echo "initrd: starting rootfs"
cd /jffs2
[ -d initrd ] || mkdir initrd
pivot_root . initrd
exec chroot . /sbin/init <dev/console >dev/console
2>&1
The error still occurs with this scheme.
> > I've posted to the uClibc group and the uClinux
> > group.
> > My posts to these groups contain additional
> detail
> > as
> > well as additional traces (included as
> attachments).
> >
> > I thought it easier to provide links (see below)
> > than
> > to include all the information here. If this is
> not
> > the case, I'll compile all the information in to
> one
> > big post here.
> >
> > The uClibc thread is -- Bummer: could not find!
> >
>
http://www.uclibc.org/lists/uclibc/2007-January/017086.html
> >
> > The uClinux thread is --
> uClinux-dist-test-20070108:
> > Problems with jffs2 rootfs
> >
>
http://mailman.uclinux.org/pipermail/uclinux-dev/2007-January/041699.html
> >
> > Any assistance will be appreciated.
> >
> > Thanks,
> > ...doug
> >
>
>
>
>
>
____________________________________________________________________________________
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367
next parent reply other threads:[~2007-02-04 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <142644.61282.qm@web51907.mail.yahoo.com>
2007-02-04 13:43 ` Doug Kehn [this message]
2007-02-13 12:07 ` JFFS2 Root Filesystem and Linux 2.6.19 Doug Kehn
2007-01-24 2:48 Doug Kehn
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=53943.37121.qm@web51903.mail.yahoo.com \
--to=rdkehn@yahoo.com \
--cc=linux-mtd@lists.infradead.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