Re: [axfs-developer] Mounting profiled axfs

[Andre P. <and...@im...>]

Hi Will,

Will Marone wrote:
> I forgot to ask last time, what version of the kernel are you using?
> Mount methods other than iomem, physaddr and block devices are not
> (currently) supported pre-2.6.22, and our effective backport testing
> goes to 2.6.18.
I am running these tests on a gumstix verdex board which has a ARM 
pxa270 core. Currently, I am using the stock gumstix kernel, which is 
version 2.6.21.

> So when you attempt to mount AXFS as the root filing system, with a 
> profiled
> image, and you mount via rootflags=physaddr, you get a segfault? 
No segfault, using the physaddr flag raises this:
<log>
[    1.170000] VFS: Mounted root (axfs filesystem) readonly.
[    1.170000] Freeing init memory: 72K
Illegal instruction
sh: rcBoot: unknown operand
Illegal instruction
Illegal instruction
</log>

As you can see, mounting is ok. Executing any application raises the 
illegal instruction. If I append "init=/bin/sh" to my command line, I 
get the shell, so busybox seems to _work partly_. If I then run "ls" or 
"dmesg" or whatever, I get the illegal instruction again.

> We've had 
> rumblings of a bug in mkfs.axfs that we've been needing to track down.
So let's do this! You need my images or profiles?

>>  Seems like there is something wrong :-) Maybe mapping the XIP 
>> sections fails?
>> If I mount the same image after booting the rootfs via nfs it works 
>> with the -o physaddr-flag, but I can't umount the image afterwards.
> We have some noisy unmounts, depending on the kernel. When you mount 
> after
> booting with nfs, does XIP work?
Yes, works.


Regards,
Andre