Re: [Xen-devel] Debootstrapping a rootfs for Xen on FastModels A15

[Sander Bogaert <sander.bogaert@xxxxxxxxx>]

On 3 April 2013 16:24, Stefano Stabellini
<stefano.stabellini@xxxxxxxxxxxxx> wrote:
> On Wed, 3 Apr 2013, Sander Bogaert wrote:
>> On 3 April 2013 15:41, Stefano Stabellini
>> <stefano.stabellini@xxxxxxxxxxxxx> wrote:
>> > On Wed, 3 Apr 2013, Sander Bogaert wrote:
>> >> On 2 April 2013 15:47, Stefano Stabellini
>> >> <stefano.stabellini@xxxxxxxxxxxxx> wrote:
>> >> > On Tue, 2 Apr 2013, Sander Bogaert wrote:
>> >> >> I did however try the branches you linked but without much progress.
>> >> >> Using the xen and kernel branches you linked together with this config
>> >> >> ( http://xenbits.xen.org/people/sstabellini/config where I selected
>> >> >> the defaults for newer kernel options ) Xen crashes. I attached a log;
>> >> >> log.txt. Isn't this the exact same setup as you are using?
>> >> >
>> >> > I am attaching the kernel config I am using with that branch.
>> >> > However I tried the one linked above, using the default for all the
>> >> > newer kernel options, and I can still boot Dom0 to a bash prompt :-S
>> >> > For the sake of completeness I am also going to attach my DTS (that is
>> >> > SMP ready).
>> >> >
>> >>
>> >> Thanks a lot for all your help!
>> >>
>> >> I used the files you supplied, build myself a A15x2 model and still
>> >> get a crash booting dom0, it is one I never seen before. I attached
>> >> the Xen and dom0 logs. The isue seems to be
>> >> "Unhandled fault: external abort on non-linefetch (0x1008) at 0xc8820084
>> >> Internal error: : 1008 [#1] SMP ARM"
>> >>
>> >> Any idea what could still be different between our setups? Maybe the
>> >> compilers? I'm using arm-linux-gnueabi-gcc (Debian 4.7.2-4) 4.7.2 for
>> >> crosscompilation. The model was built with gcc (Debian 4.4.7-2) 4.4.7.
>> >>
>> >> Kernel is the branch you indicated with the .config you supplied.
>> >> Xen is the branch you indicated.
>> >> I'm using the dts you supplied and compile it to a dtb with DTC 1.3.0.
>> >
>> > Ah yes, I know about that one :)
>> > The problem is the DTS, you need this simple fix for the network card
>> > entry:
>> >
>> > diff --git a/arch/arm/boot/dts/vexpress-v2m-rs1.dtsi 
>> > b/arch/arm/boot/dts/vexpress-v2m-rs1.dtsi
>> > index ac870fb..d6d3c47 100644
>> > --- a/arch/arm/boot/dts/vexpress-v2m-rs1.dtsi
>> > +++ b/arch/arm/boot/dts/vexpress-v2m-rs1.dtsi
>> > @@ -47,7 +47,7 @@
>> >                 };
>> >
>> >                 ethernet@2,02000000 {
>> > -                       compatible = "smsc,lan9118", "smsc,lan9115";
>> > +                       compatible = "smsc,lan91c111";
>> >                         reg = <2 0x02000000 0x10000>;
>> >                         interrupts = <15>;
>> >                         phy-mode = "mii";
>>
>> Thanks, this fixed the error. Now I'm back at square one... :) Crashing with:
>>
>> VFS: Cannot open root device "mmcblk0" or unknown-block(0,0): error -6
>> Please append a correct "root=" boot option; here are the available 
>> partitions:
>> Kernel panic - not syncing: VFS: Unable to mount root fs on 
>> unknown-block(0,0)
>>
>> I attached the whole log. I've been having this with a lot of
>> different kernels & xen branches. I'm using your device tree,.. is it
>> possible this has something to do with the rootfs? I don't know how I
>> could mess up the debootstrapping, it wasn't difficult but that the
>> only thing that could differ?
>
> I made my rootfs available here:
>
> http://xenbits.xen.org/people/sstabellini/rootfs.small.img.big
>
> if you would like the sources for any of the components of the rootfs,
> just ask.

I'm getting the exact same error. I really don't get how that's
possible since all the components are yours, I guess I'll start adding
some printk's to xen/arch/arm/gic.c as you suggested? I should have
tested this before but providing no fs results in the same error so it
has nothing to do with it.

Thanks

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel