From: Julien Grall <julien.grall@arm.com>
To: Dushyant Behl <myselfdushyantbehl@gmail.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Dushyant K Behl <dushyantbehl@in.ibm.com>,
Xen Devel <xen-devel@lists.xen.org>,
Meng Xu <xumengpanda@gmail.com>
Subject: Re: Running Xen on Nvidia Jetson-TK1
Date: Tue, 29 Mar 2016 20:01:23 +0100 [thread overview]
Message-ID: <56FAD103.5070203@arm.com> (raw)
In-Reply-To: <CAHF350+gTtev4gM6U+bCCtO52oxTFKEb2vmmvEfd88un9_YqpQ@mail.gmail.com>
Hello Dushyant,
On 24/03/16 11:05, Dushyant Behl wrote:
> I was not receiving the dom0 logs because of a mistake in my dom0
> bootargs. In the bootargs the option
> for earlyprintk was not marked as Xen. Now that I've enabled it I'm
> able to see some bootlog from dom0 linux.
>
> At least now I'm able to figure out the reason of Linux running into
> infinite loop.
>
> It seems like Linux is not receiving any interrupts from the arch
> timer and when it tries
> to calibrate the timer delay then there's a loop where linux waits to
> receive ticks to calculate
> loops_per_jiffies and that's the point where dom0 is running into the
> infinite loop.
> (exact point is http://osxr.org:8080/linux/source/init/calibrate.c#0196)
>
> This is the dom0 bootlog which I received after correcting the
> earlyprintk argument -
Can you provide the full log? So we can see if there is anything which
could give us a hint about your problem.
>
> (XEN) DOM0: Uncompressing Linux... done, booting the kernel.
> (XEN) DOM0: [ 0.000000] Booting Linux on physical CPU 0x0
> (XEN) DOM0: [ 0.000000] Initializing cgroup subsys cpu
> (XEN) DOM0: [ 0.000000] Initializing cgroup subsys cpuacct
> (XEN) DOM0: [ 0.000000] Linux version
> 4.1.0-196898-g2e68ed9-dirty(root@ubuntu-server) (gcc version 4.7.3
> (Ubuntu/Linaro 4.7.3-11ubuntu
> (XEN) DOM0: 1) ) #12 SMP PREEMPT Thu Mar 24 09:56:36 UTC 2016
> (XEN) DOM0: [ 0.000000] CPU: ARMv7 Processor [413fc0f3] revision 3
> (ARMv7), cr=30c5387d
> (XEN) DOM0: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache,
> PIPT instruction cache
> (XEN) DOM0: [ 0.000000] Machine model: NVIDIA Tegra124 Jetson TK1
> (XEN) DOM0: [ 0.000000] bootconsole [earlycon0] enabled
> (XEN) DOM0: [ 0.000000] cma: Reserved 64 MiB at 0x00000000bc000000
> (XEN) DOM0: [ 0.000000] Forcing write-allocate cache policy for SMP
> (XEN) DOM0: [ 0.000000] Memory policy: Data cache writealloc
> (XEN) DOM0: [ 0.000000] psci: probing for conduit method from DT.
> (XEN) DOM0: [ 0.000000] psci: PSCIv0.2 detected in firmware.
> (XEN) DOM0: [ 0.000000] psci: Using standard PSCI v0.2 function IDs
> (XEN) DOM0: [ 0.000000] PERCPU: Embedded 12 pages/cpu @dbb77000
> s19712 r8192 d21248 u49152
> (XEN) DOM0: [ 0.000000] Built 1 zonelists in Zone order, mobility
> grouping on. Total pages: 130048
> (XEN) DOM0: [ 0.000000] Kernel command line: console=hvc0
> console=tty1 earlyprintk=xen root=/dev/mmcblk0p1 rw rootwait
> tegraid=40.1.1.0.0
> (XEN) DOM0: [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
> (XEN) DOM0: [ 0.000000] Dentry cache hash table entries: 65536
> (order: 6, 262144 bytes)
> (XEN) DOM0: [ 0.000000] Inode-cache hash table entries: 32768
> (order: 5, 131072 bytes)
> (XEN) DOM0: [ 0.000000] Memory: 441884K/524288K available (7657K
> kernel code, 634K rwdata, 2584K rodata, 484K init, 383K bss, 16868K
> reserved, 65536K cma-reserved, 0K highmem)
> (XEN) DOM0: [ 0.000000] Virtual kernel memory layout:
> (XEN) DOM0: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
> (XEN) DOM0: [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
> (XEN) DOM0: [ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)
> (XEN) DOM0: [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
> (XEN) DOM0: [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
> (XEN) DOM0: [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
> (XEN) DOM0: [ 0.000000] .text : 0xc0008000 - 0xc0a08c10 (10244 kB)
> (XEN) DOM0: [ 0.000000] .init : 0xc0a09000 - 0xc0a82000 ( 484 kB)
> (XEN) DOM0: [ 0.000000] .data : 0xc0a82000 - 0xc0b20bec ( 635 kB)
> (XEN) DOM0: [ 0.000000] .bss : 0xc0b23000 - 0xc0b82ea0 ( 384 kB)
> (XEN) DOM0: [ 0.000000] Preemptible hierarchical RCU implementation.
> (XEN) DOM0: [ 0.000000] Build-time adjustment of leaf fanout to 32.
> (XEN) DOM0: [ 0.000000] NR_IRQS:16 nr_irqs:16 16
> (XEN) DOM0: [ 0.000000] of_irq_init: children remain, but no parents
> (XEN) DOM0: [ 0.000000] L2C: failed to init: -19
> (XEN) DOM0: [ 0.000000] irq: no irq domain found for /interrupt-controller !
> (XEN) DOM0: [ 0.000000] irq: no irq domain found for /interrupt-controller !
> (XEN) DOM0: [ 0.000000] irq: no irq domain found for /interrupt-controller !
> (XEN) DOM0: [ 0.000000] arch_timer: No interrupt available, giving up
> (XEN) DOM0: [ 0.000000] sched_clock: 32 bits at 100 Hz, resolution
> 10000000ns, wraps every 21474836475000000ns
> (XEN) DOM0: [ 0.000000] Console: colour dummy device 80x30
> (XEN) DOM0: [ 0.000000] console [tty1] enabled
>
> Can anyone explain why Linux is not able to get any interrupts from
> the arch timer?
> Is this some problem with Xen's interrupt mappings or some issue with
> the dom0 kernel?
From the log: "arch_timer: No interrupt available, giving up". So the
kernel is not able to get the interrupt from device tree.
Which device-tree are you using for the board?
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-29 19:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 8:23 Running Xen on Nvidia Jetson-TK1 Dushyant K Behl
2016-03-09 13:37 ` Wei Liu
2016-03-10 5:08 ` Julien Grall
2016-03-12 14:20 ` Dushyant Behl
2016-03-12 15:27 ` Meng Xu
2016-03-12 20:23 ` Dushyant Behl
2016-03-13 2:10 ` Meng Xu
2016-03-14 9:31 ` Dushyant Behl
2016-03-14 14:12 ` Konrad Rzeszutek Wilk
2016-03-14 14:19 ` Dushyant Behl
2016-03-17 14:52 ` Julien Grall
2016-03-18 15:01 ` Dushyant Behl
2016-03-18 17:23 ` Julien Grall
2016-03-21 10:12 ` Dushyant Behl
2016-03-24 11:05 ` Dushyant Behl
2016-03-29 19:01 ` Julien Grall [this message]
2016-03-29 20:56 ` Dushyant Behl
2016-04-01 10:04 ` Julien Grall
2016-04-07 7:48 ` Dushyant Behl
2016-04-08 10:10 ` Julien Grall
2016-04-08 12:27 ` Ian Campbell
2016-04-14 15:54 ` Dushyant Behl
2016-05-14 18:43 ` Meng Xu
2016-05-14 19:03 ` Dushyant Behl
2016-05-14 2:09 ` Meng Xu
2016-05-14 17:36 ` Dushyant Behl
2016-05-14 18:34 ` Meng Xu
2016-05-14 18:37 ` Meng Xu
2016-05-14 18:58 ` Dushyant Behl
2016-05-12 1:00 ` Meng Xu
2016-05-12 9:19 ` Dushyant Behl
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=56FAD103.5070203@arm.com \
--to=julien.grall@arm.com \
--cc=dushyantbehl@in.ibm.com \
--cc=myselfdushyantbehl@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@gmail.com \
/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.