[ELDK] Root File System Builder Issues

Tue Sep 8 19:45:37 CEST 2009

I still have not been able to resolve the warnings when building, but I have come up against another, more problematic issue.

The RAMdisk image produces by the RFSB tool will not boot if I include too many packages.  Here is the output:

RAMDISK: gzip image found at block 0
uncompression error
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing unused kernel memory: 144k init
EXT2-fs error (device ram0): ext2_check_page: bad entry in directory #651: : rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
Remounting filesystem read-only
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
Call Trace:
[cf81ff30] [c0006f0c] show_stack+0x44/0x16c (unreliable)
[cf81ff70] [c00342dc] panic+0x9c/0x170
[cf81ffc0] [c00025ec] init_post+0xe8/0xf8
[cf81ffd0] [c03151fc] kernel_init+0xe0/0x108
[cf81fff0] [c00101a8] kernel_thread+0x4c/0x68
Rebooting in 180 seconds...

RAMDISK: gzip image found at block 0
uncompression error
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing unused kernel memory: 144k init
request_module: runaway loop modprobe binfmt-0000
request_module: runaway loop modprobe binfmt-0000
request_module: runaway loop modprobe binfmt-0000
request_module: runaway loop modprobe binfmt-0000
request_module: runaway loop modprobe binfmt-0000

RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing unused kernel memory: 144k init
attempt to access beyond end of device
ram0: rw=0, want=168212, limit=16384
(... 100 more identical messages ...)
attempt to access beyond end of device
ram0: rw=0, want=168212, limit=16384
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
Call Trace:
[cf81ff30] [c0006f0c] show_stack+0x44/0x16c (unreliable)
[cf81ff70] [c00342dc] panic+0x9c/0x170
[cf81ffc0] [c00025ec] init_post+0xe8/0xf8
[cf81ffd0] [c03151fc] kernel_init+0xe0/0x108
[cf81fff0] [c00101a8] kernel_thread+0x4c/0x68
Rebooting in 180 seconds...

Those three attempts are representative of all the messages I have seen.

Here are my current kernel settings, pertaining to RAMdisks:

CONFIG_BLK_DEV_RAM_COUNT = 1
CONFIG_BLK_DEV_RAM_SIZE = 65536

Any ideas as to what is causing the uncompression errors, the runaway loops, accesses beyond the end of the device?

I have been able to get it to boot with just a bare filesystem (no other utilities, no Xenomai libraries - just the SELF and that is it).  That does work, but as soon as I add other things, it fails.  Why?

(PS - I am running on an AMCC Kilauea board, 405EX processor).

Thanks!

Jonathan

> -----Original Message-----
> From: eldk-bounces at lists.denx.de [mailto:eldk-bounces at lists.denx.de]
> On Behalf Of Jonathan Haws
> Sent: Friday, September 04, 2009 1:00 PM
> To: eldk at lists.denx.de
> Subject: [ELDK] RFSB Issues
> 
> All,
> 
> I am trying to create a rootfs filesystem that includes the Xenomai
> user-space support libraries.  When I configure the rootfs and
> include
> Xenomai, I get the following output:
> 
> Current target list is
> /home/jhaws/sdlppc/rfsb/build/images/image.ext2
> /home/jhaws/sdlppc/rfsb/build/images/uRamdisk
> rm -rf /home/jhaws/sdlppc/rfsb/build/* status
> Cleaning /home/jhaws/sdlppc/rfsb/build
> Populating /home/jhaws/sdlppc/rfsb/build with directories
> Using SELF skeleton from 'config/skeleton/self' to populate file
> system
> 2 blocks
> cpio: usr/local/xenomai/kbuild: Cannot stat: No such file or
> directory
> cpio: usr/local/xenomai/kbuild/include: Cannot stat: No such file or
> directory
> cpio: usr/local/xenomai/kbuild/include/COPYING: Cannot stat: No such
> file or directory
> cpio: usr/local/xenomai/kbuild/include/Makefile: Cannot stat: No
> such
> file or directory
> cpio: usr/local/xenomai/kbuild/include/Makefile.am: Cannot stat: No
> such file or directory
> cpio: usr/local/xenomai/kbuild/include/Makefile.in: Cannot stat: No
> such file or directory
> cpio: usr/local/xenomai/kbuild/include/asm-arm: Cannot stat: No such
> file or directory
> ...
> cpio: usr/local/xenomai/kbuild/scripts/xeno-config: Cannot stat: No
> such file or directory
> cpio: usr/local/xenomai/kbuild/scripts/xeno-config.in: Cannot stat:
> No
> such file or directory
> cpio: usr/local/xenomai/kbuild/scripts/xeno-info: Cannot stat: No
> such
> file or directory
> cpio: usr/local/xenomai/kbuild/scripts/xeno-load: Cannot stat: No
> such
> file or directory
> cpio: usr/local/xenomai/kbuild/scripts/xeno-load.in: Cannot stat: No
> such file or directory
> cpio: usr/local/xenomai/kbuild/scripts/xeno-test: Cannot stat: No
> such
> file or directory
> cpio: usr/local/xenomai/kbuild/scripts/xeno-test.in: Cannot stat: No
> such file or directory
> 1472 blocks
> Creating busybox symlinks
> make pkgs
> Current target list is
> /home/jhaws/sdlppc/rfsb/build/images/image.ext2
> /home/jhaws/sdlppc/rfsb/build/images/uRamdisk
> make[1]: Entering directory `/home/jhaws/sdlppc/rfsb'
> make[1]: Nothing to be done for `pkgs'.
> make[1]: Leaving directory `/home/jhaws/sdlppc/rfsb'
> touch status/stamp.custom-pkgs
> Adding dependency libraries
> warning: could not resolve 'libnative.so.1'
> warning: could not resolve 'libpthread_rt.so.1'
> warning: could not resolve 'librtdm.so.1'
> 639 blocks
> Copying files from custom/rootfs
> 1 block
> Generating ext2 image
> rm -f /home/jhaws/sdlppc/rfsb/build/images/image.ext2
> /home/jhaws/sdlppc/rfsb/build/images/image.ext2.gz
> genext2fs -i 4096 -d /home/jhaws/sdlppc/rfsb/build/rootfs -b 9728 -D
> config/rootfs_devices.tab
> /home/jhaws/sdlppc/rfsb/build/images/image.ext2
> genext2fs: couldn't allocate a block (no free space)
> make: *** [/home/jhaws/sdlppc/rfsb/build/images/image.ext2] Error 1
> 
> The issue appears to be that the Xenomai that I built from source
> does
> not contain the kbuild/ directory.  Is that needed?  Is there a way
> to
> get rid of those warnings?
> 
> Next, the "could not resolve 'libXXXXX.so.1'" warnings - those
> libraries exist in eldk/ppc_4xx/usr/local/xenomai, but not in
> eldk/ppc_4xx/lib.  Shouldn't the Makefile know where the Xenomai
> libraries are?  What is the correct way to specify that?  Should I
> just make a symlink to them in lib?  That seems like a kludge to me.
> 
> Finally, the error with genext2fs fails because I have not given
> enough blocks.  However, I do not want a 16MB ramdisk image either.
> I
> have found that by removing the locales in
> build/rootfs/usr/share/locale helps.  But where are those pulled
> from?
> How can I specify the locale I want?
> 
> Thanks for the help on these issues!
> 
> Jonathan
> 
> 
> _______________________________________________
> eldk mailing list
> eldk at lists.denx.de
> http://lists.denx.de/mailman/listinfo/eldk