Xen devel - Mar 2013 - Debootstrapping a rootfs for Xen on FastModels A15

Hi,

I''ve tried several different approaches to debootstrap a working
rootfs for with a Cortex A15 model ( FastModels ) and Xen but still
face some issues.

Some information on my setup.
For a Dom0 kernel I''m using the latest version from
git://github.com/torvalds/linux.git, I attached my config as it might
be of some use for others. I''m using the latest Xen unstable branch
git://xenbits.xen.org/xen.git and my device tree comes from:
git://xenbits.xen.org/people/sstabellini/device-trees.git .

These are my xen and kernel arguments:
bootargs = "dom0_mem=128M dom0_max_vcpus=1 console=com1,vga";
 xen,dom0-bootargs = "earlyprintk=xenboot console=ttyAMA0
root=/dev/mmcblk0 init=/bin/bash rw ip=dhcp";

This is how I launch the model ( where the variables of course contain
the right paths ):
./model_shell ../resources/Cortex-A15x1/cadi_system_Linux-Release-GCC-4.4.so
$1 -C motherboard.flashloader0.fname=$2 -C
motherboard.smsc_91c111.enabled=1 -C
motherboard.hostbridge.userNetworking=1 -C
motherboard.pl011_uart0.out_file=./log.txt -C
motherboard.mmc.p_mmc_file="$3"

To get a basic filesystem I:
- created a empty file ( with fallocate or dd )
- formated it ext4
- mounted the file and used HOSTNAME=armhf sudo debootstrap --foreign
--arch armhf wheezy $path
- did the some configuration and the second stage debootstrapping

The problem now is Xen hangs on/after booting dom0, I included a log (
log.txt ). This filesystem boots fine with the same kernel, without
Xen on the same FastModel model.

My question: did I miss something in the debootstrapping? Are there
some steps I don''t know of? Does anyway have an idea on what goes
wrong ( see log.txt )?

Thanks a lot!
Sander



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

On Sun, 31 Mar 2013, Sander Bogaert wrote:
> Hi,
> 
> I''ve tried several different approaches to debootstrap a working
> rootfs for with a Cortex A15 model ( FastModels ) and Xen but still
> face some issues.
> 
> Some information on my setup.
> For a Dom0 kernel I''m using the latest version from
> git://github.com/torvalds/linux.git, I attached my config as it might
> be of some use for others. I''m using the latest Xen unstable
branch
> git://xenbits.xen.org/xen.git and my device tree comes from:
> git://xenbits.xen.org/people/sstabellini/device-trees.git .
> 
> These are my xen and kernel arguments:
> bootargs = "dom0_mem=128M dom0_max_vcpus=1 console=com1,vga";
>  xen,dom0-bootargs = "earlyprintk=xenboot console=ttyAMA0
> root=/dev/mmcblk0 init=/bin/bash rw ip=dhcp";
> 
> This is how I launch the model ( where the variables of course contain
> the right paths ):
> ./model_shell
../resources/Cortex-A15x1/cadi_system_Linux-Release-GCC-4.4.so
> $1 -C motherboard.flashloader0.fname=$2 -C
> motherboard.smsc_91c111.enabled=1 -C
> motherboard.hostbridge.userNetworking=1 -C
> motherboard.pl011_uart0.out_file=./log.txt -C
> motherboard.mmc.p_mmc_file="$3"
> 
> To get a basic filesystem I:
> - created a empty file ( with fallocate or dd )
> - formated it ext4
> - mounted the file and used HOSTNAME=armhf sudo debootstrap --foreign
> --arch armhf wheezy $path
> - did the some configuration and the second stage debootstrapping
> 
> The problem now is Xen hangs on/after booting dom0, I included a log (
> log.txt ). This filesystem boots fine with the same kernel, without
> Xen on the same FastModel model.
> 
> My question: did I miss something in the debootstrapping? Are there
> some steps I don''t know of? Does anyway have an idea on what goes
> wrong ( see log.txt )?
I don''t see any mistakes in your setup. Unless you are running an
outdated version of the FastModel (they were known to have a broken
virt_timer implementation), my guess is that you are seeing an
issue that we actually have already solved.

At the moment Ian is on vacation (the Xen on ARM committer), as a
consequence we have several outstanding patches, many of which are
actually bug fixes. Maybe the very latest trees would solve your issue.
Could you please try:

git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git 3.9-rc3-smp-dom0-hack-2
git://xenbits.xen.org/people/sstabellini/xen-unstable.git guest-smp-3

On 1 April 2013 13:51, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> wrote:
> On Sun, 31 Mar 2013, Sander Bogaert wrote:
>> Hi,
>>
>> I''ve tried several different approaches to debootstrap a
working
>> rootfs for with a Cortex A15 model ( FastModels ) and Xen but still
>> face some issues.
>>
>> Some information on my setup.
>> For a Dom0 kernel I''m using the latest version from
>> git://github.com/torvalds/linux.git, I attached my config as it might
>> be of some use for others. I''m using the latest Xen unstable
branch
>> git://xenbits.xen.org/xen.git and my device tree comes from:
>> git://xenbits.xen.org/people/sstabellini/device-trees.git .
>>
>> These are my xen and kernel arguments:
>> bootargs = "dom0_mem=128M dom0_max_vcpus=1 console=com1,vga";
>>  xen,dom0-bootargs = "earlyprintk=xenboot console=ttyAMA0
>> root=/dev/mmcblk0 init=/bin/bash rw ip=dhcp";
>>
>> This is how I launch the model ( where the variables of course contain
>> the right paths ):
>> ./model_shell
../resources/Cortex-A15x1/cadi_system_Linux-Release-GCC-4.4.so
>> $1 -C motherboard.flashloader0.fname=$2 -C
>> motherboard.smsc_91c111.enabled=1 -C
>> motherboard.hostbridge.userNetworking=1 -C
>> motherboard.pl011_uart0.out_file=./log.txt -C
>> motherboard.mmc.p_mmc_file="$3"
>>
>> To get a basic filesystem I:
>> - created a empty file ( with fallocate or dd )
>> - formated it ext4
>> - mounted the file and used HOSTNAME=armhf sudo debootstrap --foreign
>> --arch armhf wheezy $path
>> - did the some configuration and the second stage debootstrapping
>>
>> The problem now is Xen hangs on/after booting dom0, I included a log (
>> log.txt ). This filesystem boots fine with the same kernel, without
>> Xen on the same FastModel model.
>>
>> My question: did I miss something in the debootstrapping? Are there
>> some steps I don''t know of? Does anyway have an idea on what
goes
>> wrong ( see log.txt )?
>
> I don''t see any mistakes in your setup. Unless you are running an
> outdated version of the FastModel (they were known to have a broken
> virt_timer implementation), my guess is that you are seeing an
> issue that we actually have already solved.
I''m using version 8, downloaded last week. Model_shell is version
8.0.16.
>
> At the moment Ian is on vacation (the Xen on ARM committer), as a
> consequence we have several outstanding patches, many of which are
> actually bug fixes. Maybe the very latest trees would solve your issue.
> Could you please try:
>
> git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git
3.9-rc3-smp-dom0-hack-2
> git://xenbits.xen.org/people/sstabellini/xen-unstable.git guest-smp-3
I discovered that the kernel I was trying this with before is one I
compiled with a ramdisk, the problems in my initial e-mail could be
related to that ( I had many kernel images and mixed them up ).

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?

About the ''regular'' branches: The problem I''m having
with a
non-ramdisk kernel and my debootstrapped rootfs I''m also facing
without Xen on the FastModel simulator. I know this isn''t really the
place to ask but if you have any idea on how to fix it I would really,
really appreciate it! I''ve been stuck for quite some time on it and I
know others have it working. All the information from my initial mail
is still relevant.

<NUL>[   12.340651] VFS: Cannot open root device "mmcblk0" or
unknown-block(0,0): error -6
[   12.340714] Please append a correct "root=" boot option; here are
the available partitions:
[   12.340805] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(0,0)
[   12.340947] [<c000d3a8>] (unwind_backtrace+0x0/0xe0) from
[<c02ac5a0>] (panic+0x70/0x1c0)
....

I included logs from this kernel and my rootfs booting on the model (
log_linux.txt ) and with Xen ( log_xen.txt ). I also tried with having
root mmcblk0p0 and some other things. I just debootstrapped a rootfs (
wheezy ) the way I described so I''d think it should be mmcblk0 or
mmcblk0p0.

I really hope someone could help with getting this setup working,
either the ''regular'' one or the uncommited branches.
I''ve been at this
for days and really need a working setup.




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

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).

> About the ''regular'' branches: The problem I''m
having with a
> non-ramdisk kernel and my debootstrapped rootfs I''m also facing
> without Xen on the FastModel simulator. I know this isn''t really
the
> place to ask but if you have any idea on how to fix it I would really,
> really appreciate it! I''ve been stuck for quite some time on it
and I
> know others have it working. All the information from my initial mail
> is still relevant.
> 
> <NUL>[   12.340651] VFS: Cannot open root device "mmcblk0"
or
> unknown-block(0,0): error -6
> [   12.340714] Please append a correct "root=" boot option; here
are
> the available partitions:
> [   12.340805] Kernel panic - not syncing: VFS: Unable to mount root
> fs on unknown-block(0,0)
> [   12.340947] [<c000d3a8>] (unwind_backtrace+0x0/0xe0) from
> [<c02ac5a0>] (panic+0x70/0x1c0)
> ....
> 
> I included logs from this kernel and my rootfs booting on the model (
> log_linux.txt ) and with Xen ( log_xen.txt ). I also tried with having
> root mmcblk0p0 and some other things. I just debootstrapped a rootfs (
> wheezy ) the way I described so I''d think it should be mmcblk0 or
> mmcblk0p0.
> 
> I really hope someone could help with getting this setup working,
> either the ''regular'' one or the uncommited branches.
I''ve been at this
> for days and really need a working setup.
It looks like an interrupt issue: Linux doesn''t receive any interrupts
from the MMC controller. But I don''t know what the exact cause of the
issue could be. I would start investigating by adding some printk''s to
xen/arch/arm/gic.c.


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

On 2 April 2013 15:47, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> 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.

Since everything starts I''m assuming I invoke the model_shell correct.
./model_shell ../resources/Cortex-A15x$3/cadi_system_Linux-Release-GCC-4.4.so
$1 -C motherboard.flashloader0.fname=$2 -C
motherboard.smsc_91c111.enabled=1 -C
motherboard.hostbridge.userNetworking=1 -C
motherboard.pl011_uart0.out_file=./log.txt -C
motherboard.mmc.p_mmc_file="$4"
>> About the ''regular'' branches: The problem
I''m having with a
>> non-ramdisk kernel and my debootstrapped rootfs I''m also
facing
>> without Xen on the FastModel simulator. I know this isn''t
really the
>> place to ask but if you have any idea on how to fix it I would really,
>> really appreciate it! I''ve been stuck for quite some time on
it and I
>> know others have it working. All the information from my initial mail
>> is still relevant.
>>
>> <NUL>[   12.340651] VFS: Cannot open root device
"mmcblk0" or
>> unknown-block(0,0): error -6
>> [   12.340714] Please append a correct "root=" boot option;
here are
>> the available partitions:
>> [   12.340805] Kernel panic - not syncing: VFS: Unable to mount root
>> fs on unknown-block(0,0)
>> [   12.340947] [<c000d3a8>] (unwind_backtrace+0x0/0xe0) from
>> [<c02ac5a0>] (panic+0x70/0x1c0)
>> ....
>>
>> I included logs from this kernel and my rootfs booting on the model (
>> log_linux.txt ) and with Xen ( log_xen.txt ). I also tried with having
>> root mmcblk0p0 and some other things. I just debootstrapped a rootfs (
>> wheezy ) the way I described so I''d think it should be mmcblk0
or
>> mmcblk0p0.
>>
>> I really hope someone could help with getting this setup working,
>> either the ''regular'' one or the uncommited branches.
I''ve been at this
>> for days and really need a working setup.
>
> It looks like an interrupt issue: Linux doesn''t receive any
interrupts
> from the MMC controller. But I don''t know what the exact cause of
the
> issue could be. I would start investigating by adding some
printk''s to
> xen/arch/arm/gic.c.
I''m focusing on the first scenario since that one most resembles a
working setup ( yours ). I''ll add some debug prints and test this one
later.



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

On Wed, 3 Apr 2013, Sander Bogaert wrote:
> On 2 April 2013 15:47, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> 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";

On 3 April 2013 15:41, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> wrote:
> On Wed, 3 Apr 2013, Sander Bogaert wrote:
>> On 2 April 2013 15:47, Stefano Stabellini
>> <stefano.stabellini@eu.citrix.com> 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?

Thanks again


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

On Wed, 3 Apr 2013, Sander Bogaert wrote:
> On 3 April 2013 15:41, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
> > On Wed, 3 Apr 2013, Sander Bogaert wrote:
> >> On 2 April 2013 15:47, Stefano Stabellini
> >> <stefano.stabellini@eu.citrix.com> 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.

On 3 April 2013 16:24, Stefano Stabellini
<stefano.stabellini@eu.citrix.com> wrote:
> On Wed, 3 Apr 2013, Sander Bogaert wrote:
>> On 3 April 2013 15:41, Stefano Stabellini
>> <stefano.stabellini@eu.citrix.com> wrote:
>> > On Wed, 3 Apr 2013, Sander Bogaert wrote:
>> >> On 2 April 2013 15:47, Stefano Stabellini
>> >> <stefano.stabellini@eu.citrix.com> 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

On 3 April 2013 16:52, Sander Bogaert <sander.bogaert@gmail.com>
wrote:
> On 3 April 2013 16:24, Stefano Stabellini
> <stefano.stabellini@eu.citrix.com> wrote:
>> On Wed, 3 Apr 2013, Sander Bogaert wrote:
>>> On 3 April 2013 15:41, Stefano Stabellini
>>> <stefano.stabellini@eu.citrix.com> wrote:
>>> > On Wed, 3 Apr 2013, Sander Bogaert wrote:
>>> >> On 2 April 2013 15:47, Stefano Stabellini
>>> >> <stefano.stabellini@eu.citrix.com> 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.
Hi,

I have things working now, it was a combination of small mistakes. My
own rootfs boots fine, if I use yours the model_shell outputs some
error and crashes. I was just curious if there are some special
parameters or something to pass with ( apparently ) ''big'' mmc
images?
I couldn''t really find any.

Thanks

terminal_0: Listening for serial connection on port 5000
terminal_1: Listening for serial connection on port 5001
terminal_2: Listening for serial connection on port 5002
terminal_3: Listening for serial connection on port 5003
ERROR: mmc: Backing store size (512000000) adjusted to 512098304!
ERROR: mmc: Backing store size (512000000) adjusted to 512098304!

FlashLoader: Loaded 2MB
ERROR: mmc: Backing store size (512000000) adjusted to 512098304!
Simulation is started
WARNING: mmc: Won''t map beyond the end of
''/home/dz/downloads/rootfs.small.img.big''
0x8512032768-0x8512036864
exceeds 0x8512000000
Segmentation fault (core dumped)

On Fri, 5 Apr 2013, Sander Bogaert wrote:
> On 3 April 2013 16:52, Sander Bogaert <sander.bogaert@gmail.com>
wrote:
> > On 3 April 2013 16:24, Stefano Stabellini
> > <stefano.stabellini@eu.citrix.com> wrote:
> >> On Wed, 3 Apr 2013, Sander Bogaert wrote:
> >>> On 3 April 2013 15:41, Stefano Stabellini
> >>> <stefano.stabellini@eu.citrix.com> wrote:
> >>> > On Wed, 3 Apr 2013, Sander Bogaert wrote:
> >>> >> On 2 April 2013 15:47, Stefano Stabellini
> >>> >> <stefano.stabellini@eu.citrix.com> 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.
> 
> Hi,
> 
> I have things working now, it was a combination of small mistakes.
Good to hear!!
> My
> own rootfs boots fine, if I use yours the model_shell outputs some
> error and crashes. I was just curious if there are some special
> parameters or something to pass with ( apparently ) ''big''
mmc images?
> I couldn''t really find any.
I don''t think so.

> Thanks
> 
> terminal_0: Listening for serial connection on port 5000
> terminal_1: Listening for serial connection on port 5001
> terminal_2: Listening for serial connection on port 5002
> terminal_3: Listening for serial connection on port 5003
> ERROR: mmc: Backing store size (512000000) adjusted to 512098304!
> ERROR: mmc: Backing store size (512000000) adjusted to 512098304!
> 
> FlashLoader: Loaded 2MB
> ERROR: mmc: Backing store size (512000000) adjusted to 512098304!
I get these, but they don''t cause me any issues.

> Simulation is started
> WARNING: mmc: Won''t map beyond the end of
> ''/home/dz/downloads/rootfs.small.img.big''
0x8512032768-0x8512036864
> exceeds 0x8512000000
> Segmentation fault (core dumped)
That''s weird, I have never seen this before.