From: Chen Baozi <baozich@gmail.com>
To: Andrii Anisov <andrii.anisov@globallogic.com>
Cc: Julien Grall <julien.grall@linaro.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Domain 0 crashed when booting OMAP5 uEVM
Date: Tue, 13 Aug 2013 15:56:44 +0800 [thread overview]
Message-ID: <5F9894A3-C273-4C9E-96EE-D9C3F80D85F5@gmail.com> (raw)
In-Reply-To: <CAGQvs6h_SxDzdyyL7QDx7VAW6_2mhW-Sqn50RsmPwUbpp6GOqQ@mail.gmail.com>
On Aug 12, 2013, at 10:30 PM, Andrii Anisov <andrii.anisov@globallogic.com> wrote:
>
>
>
> > - Turning on paging -
> > - Ready -
> > fdt: node `cpu@0': invalid #address-cells or #size-cellsfdt: node `cpu@1':
> > - invalid #addref
>
> Hum ... this is why Xen can't find the other cpus. Could you paste the
> content of the node cpus here?
>
>
> I bet, something like this:
>
> };
>
> cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> cpu@0 {
> + device_type = "cpu";
> compatible = "arm,cortex-a15";
> + reg = <0>;
> operating-points = <
> /* kHz uV */
> /* Only for Nominal Samples */
> @@ -48,7 +53,9 @@
> clock-latency = <300000>; /* From omap-cpufreq driver */
> };
> cpu@1 {
> + device_type = "cpu";
> compatible = "arm,cortex-a15";
> + reg = <1>;
> };
> };
>
> will help to Chen.
I used the original 3.8 kernel's dts from TI. And the cpu node (I've modified
to move the timer node outside it) is like:
cpus {
cpu@0 {
device_type = "cpu";
compatible = "arm,cortex-a15";
reg = <0x0>;
};
cpu@1 {
device_type = "cpu";
compatible = "arm,cortex-a15";
reg = <0x1>;
};
};
And I checked the latest git tree I've used, it is:
cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
cpu@0 {
device_type = "cpu";
compatible = "arm,cortex-a15";
reg = <0x0>;
};
cpu@1 {
device_type = "cpu";
compatible = "arm,cortex-a15";
reg = <0x1>;
};
};
I'll check if the missing address-cells and size-cells caused my
issues.
Thanks.
Baozi
>
> Sincerely,
> Andrii Anisov.
next prev parent reply other threads:[~2013-08-13 7:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 12:24 Domain 0 crashed when booting OMAP5 uEVM Chen Baozi
2013-08-12 12:47 ` Julien Grall
2013-08-12 14:15 ` Andrii Anisov
2013-08-12 14:30 ` Andrii Anisov
2013-08-12 15:08 ` Julien Grall
2013-08-12 15:32 ` Andrii Anisov
2013-08-12 15:40 ` Andrii Anisov
2013-08-13 2:40 ` Chen Baozi
2013-08-13 7:56 ` Chen Baozi [this message]
2013-08-13 8:45 ` Chen Baozi
2013-08-13 9:55 ` Julien Grall
2013-08-12 14:54 ` Andrii Anisov
2013-08-13 9:10 ` Chen Baozi
2013-08-13 9:36 ` Andrii Anisov
2013-08-13 9:40 ` Chen Baozi
2013-08-13 9:58 ` Julien Grall
2013-08-14 9:46 ` Chen Baozi
2013-08-14 9:55 ` Julien Grall
2013-08-14 12:38 ` Chen Baozi
2013-08-15 9:13 ` Julien Grall
2013-08-15 9:47 ` Chen Baozi
2013-08-15 10:07 ` Julien Grall
2013-08-15 10:54 ` Andrii Anisov
2013-08-15 11:00 ` Chen Baozi
2013-08-15 11:07 ` Andrii Anisov
2013-08-15 10:59 ` Chen Baozi
2013-08-15 12:24 ` Ian Campbell
2013-08-15 12:43 ` Julien Grall
2013-08-14 16:07 ` Andrii Anisov
2013-08-14 19:47 ` Julien Grall
2013-08-14 9:53 ` Chen Baozi
2013-08-14 16:03 ` Andrii Anisov
2013-08-15 2:31 ` Chen Baozi
2013-08-15 7:37 ` Chen Baozi
2013-08-15 8:34 ` Andrii Anisov
2013-08-15 8:51 ` Chen Baozi
2013-08-15 9:12 ` Andrii Anisov
2013-08-15 9:17 ` Chen Baozi
2013-08-15 8:45 ` Andrii Anisov
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=5F9894A3-C273-4C9E-96EE-D9C3F80D85F5@gmail.com \
--to=baozich@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrii.anisov@globallogic.com \
--cc=julien.grall@linaro.org \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.