|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Domain 0 crashed when booting OMAP5 uEVM
On Aug 13, 2013, at 3:56 PM, Chen Baozi <baozich@xxxxxxxxx> wrote:
>
> On Aug 12, 2013, at 10:30 PM, Andrii Anisov <andrii.anisov@xxxxxxxxxxxxxxx>
> 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.
>
Yes, it is because of lacking #address-cells and #size-cells.
>
>>
>> Sincerely,
>> Andrii Anisov.
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |