| Message ID | 56EAC498.1030400@arm.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Hi Julien, On Thu, Mar 17, 2016 at 8:22 PM, Julien Grall <julien.grall@arm.com> wrote: > Hi Dushyant, > > On 14/03/16 14:19, Dushyant Behl wrote: >> > Yes, I have enabled these configuration parameters when compiling linux - > > The list of options looks good to me. I guess Linux is crashing before setting > up the console. Can you apply the below to Linux and post the log here? I applied your patch to Linux but still there is no output from the kernel. But I have found location of the problem, I have a debugger attached to the Jetson board and using that I was able to find out that Linux is failing while initializing the Tegra timer. The call stack at the time of failing is - - prefetchw (inline) arch_spin_lock (inline) do_raw_spin_lock_flags (inline) __raw_spin_lock_irqssave (inline) raw_spin_lock_irq_save (lock = 0xC0B746F0) - of_get_parent (node = 0xA00001D3) - of_get_address (dev = 0xDBBABC30, index = 0, size = 0xC0A83F30) - of_address_to_resource(dev = 0xDBBABC30, index = 0, r = 0xC0A83F50) - of_iomap (np = 0xDBBABC30, index = 0) - tegra20_init_timer (np = 0xDBBABC30) - clocksource_of_init() - start_kernel() After this Linux jumps to floating point exception handler and then to undefined instruction and fails. Thanks, Dushyant
On 18/03/16 15:01, Dushyant Behl wrote: > Hi Julien, Hi Dushyant, > On Thu, Mar 17, 2016 at 8:22 PM, Julien Grall <julien.grall@arm.com> wrote: >> On 14/03/16 14:19, Dushyant Behl wrote: >>>> Yes, I have enabled these configuration parameters when compiling linux - >> >> The list of options looks good to me. I guess Linux is crashing before setting >> up the console. Can you apply the below to Linux and post the log here? > > I applied your patch to Linux but still there is no output from the kernel. > > But I have found location of the problem, I have a debugger attached > to the Jetson board > and using that I was able to find out that Linux is failing while > initializing the Tegra timer. > > The call stack at the time of failing is - > > - prefetchw (inline) > arch_spin_lock (inline) > do_raw_spin_lock_flags (inline) > __raw_spin_lock_irqssave (inline) > raw_spin_lock_irq_save (lock = 0xC0B746F0) > - of_get_parent (node = 0xA00001D3) > - of_get_address (dev = 0xDBBABC30, index = 0, size = 0xC0A83F30) > - of_address_to_resource(dev = 0xDBBABC30, index = 0, r = 0xC0A83F50) > - of_iomap (np = 0xDBBABC30, index = 0) > - tegra20_init_timer (np = 0xDBBABC30) > - clocksource_of_init() > - start_kernel() > > After this Linux jumps to floating point exception handler and then to > undefined instruction and fails. I don't know why Linux is receiving a floating point exception. However, DOM0 must not use the tegra timer as it doesn't support virtualization. You need to ensure that DOM0 will use the arch timer instead. Xen provides some facilities to blacklist a device tree node (see blacklist dev in arm/platforms/tegra.c). Regards,
Hi Julien, On Fri, Mar 18, 2016 at 10:53 PM, Julien Grall <julien.grall@arm.com> wrote: > > > On 18/03/16 15:01, Dushyant Behl wrote: >> >> Hi Julien, > > > Hi Dushyant, > >> On Thu, Mar 17, 2016 at 8:22 PM, Julien Grall <julien.grall@arm.com> >> wrote: >>> >>> On 14/03/16 14:19, Dushyant Behl wrote: >>>>> >>>>> Yes, I have enabled these configuration parameters when compiling linux >>>>> - >>> >>> >>> The list of options looks good to me. I guess Linux is crashing before >>> setting >>> up the console. Can you apply the below to Linux and post the log here? >> >> >> I applied your patch to Linux but still there is no output from the >> kernel. >> >> But I have found location of the problem, I have a debugger attached >> to the Jetson board >> and using that I was able to find out that Linux is failing while >> initializing the Tegra timer. >> >> The call stack at the time of failing is - >> >> - prefetchw (inline) >> arch_spin_lock (inline) >> do_raw_spin_lock_flags (inline) >> __raw_spin_lock_irqssave (inline) >> raw_spin_lock_irq_save (lock = 0xC0B746F0) >> - of_get_parent (node = 0xA00001D3) >> - of_get_address (dev = 0xDBBABC30, index = 0, size = 0xC0A83F30) >> - of_address_to_resource(dev = 0xDBBABC30, index = 0, r = 0xC0A83F50) >> - of_iomap (np = 0xDBBABC30, index = 0) >> - tegra20_init_timer (np = 0xDBBABC30) >> - clocksource_of_init() >> - start_kernel() >> >> After this Linux jumps to floating point exception handler and then to >> undefined instruction and fails. > > > I don't know why Linux is receiving a floating point exception. However, > DOM0 must not use the tegra timer as it doesn't support virtualization. > > You need to ensure that DOM0 will use the arch timer instead. Xen provides > some facilities to blacklist a device tree node (see blacklist dev in > arm/platforms/tegra.c). I have blacklisted the tegra20_timer and now dom0 is able to pass that step but now the dom0 kernel gets stuck in an infinite loop in the function calibrate_delay_converge. This is the call stack - - calibrate_delay_converge - calibrate_delay - start_kernel Right now I'm not sure about the exact point where it is going into the infinite loop. Thanks, Dushyant Behl
Hi Everyone, On Mon, Mar 21, 2016 at 3:42 PM, Dushyant Behl <myselfdushyantbehl@gmail.com> wrote: > Hi Julien, > > On Fri, Mar 18, 2016 at 10:53 PM, Julien Grall <julien.grall@arm.com> wrote: >> >> >> On 18/03/16 15:01, Dushyant Behl wrote: >>> >>> Hi Julien, >> >> >> Hi Dushyant, >> >>> On Thu, Mar 17, 2016 at 8:22 PM, Julien Grall <julien.grall@arm.com> >>> wrote: >>>> >>>> On 14/03/16 14:19, Dushyant Behl wrote: >>>>>> >>>>>> Yes, I have enabled these configuration parameters when compiling linux >>>>>> - >>>> >>>> >>>> The list of options looks good to me. I guess Linux is crashing before >>>> setting >>>> up the console. Can you apply the below to Linux and post the log here? >>> >>> >>> I applied your patch to Linux but still there is no output from the >>> kernel. >>> >>> But I have found location of the problem, I have a debugger attached >>> to the Jetson board >>> and using that I was able to find out that Linux is failing while >>> initializing the Tegra timer. >>> >>> The call stack at the time of failing is - >>> >>> - prefetchw (inline) >>> arch_spin_lock (inline) >>> do_raw_spin_lock_flags (inline) >>> __raw_spin_lock_irqssave (inline) >>> raw_spin_lock_irq_save (lock = 0xC0B746F0) >>> - of_get_parent (node = 0xA00001D3) >>> - of_get_address (dev = 0xDBBABC30, index = 0, size = 0xC0A83F30) >>> - of_address_to_resource(dev = 0xDBBABC30, index = 0, r = 0xC0A83F50) >>> - of_iomap (np = 0xDBBABC30, index = 0) >>> - tegra20_init_timer (np = 0xDBBABC30) >>> - clocksource_of_init() >>> - start_kernel() >>> >>> After this Linux jumps to floating point exception handler and then to >>> undefined instruction and fails. >> >> >> I don't know why Linux is receiving a floating point exception. However, >> DOM0 must not use the tegra timer as it doesn't support virtualization. >> >> You need to ensure that DOM0 will use the arch timer instead. Xen provides >> some facilities to blacklist a device tree node (see blacklist dev in >> arm/platforms/tegra.c). > > I have blacklisted the tegra20_timer and now dom0 is able to pass that > step but now the dom0 kernel gets stuck in an infinite loop in the > function calibrate_delay_converge. > > This is the call stack - > - calibrate_delay_converge > - calibrate_delay > - start_kernel > > Right now I'm not sure about the exact point where it is going into > the infinite loop. 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 - (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? Thanks, Dushyant
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,
Hi Julian, Thanks for the reply. On Wed, Mar 30, 2016 at 12:31 AM, Julien Grall <julien.grall@arm.com> wrote: > 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. This is the complete log of Xen + Dom0 - ## Booting kernel from Legacy Image at fd000000 ... Image Name: Xen unstable build Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 721776 Bytes = 704.9 KiB Load Address: fd000000 Entry Point: fd000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 82000000 Booting using the fdt blob at 0x82000000 Loading Kernel Image ... OK reserving fdt memory region: addr=82000000 size=10000 Using Device Tree in place at 82000000, end 82012fff Starting kernel ... - UART enabled - - CPU 00000000 booting - - Xen starting in Hyp mode - - Zero BSS - - Setting up control registers - - Turning on paging - - Ready - (XEN) Checking for initrd in /chosen (XEN) RAM: 0000000080000000 - 00000000ffefffff (XEN) (XEN) MODULE[0]: 0000000082000000 - 0000000082010000 Device Tree (XEN) MODULE[1]: 0000000081000000 - 0000000081544828 Kernel console=hvc0 console=tty1 earlyprintk=xen root=/dev/mmcblk0p1 rw rootwait tegraid=40.1.1.0.0 (XEN) RESVD[0]: 0000000082000000 - 0000000082010000 (XEN) (XEN) Command line: console=dtuart dtuart=serial0 dom0_mem=512M (XEN) Placing Xen at 0x00000000ffc00000-0x00000000ffe00000 (XEN) Update BOOTMOD_XEN from 00000000fd000000-00000000fd0f9701 => 00000000ffc00000-00000000ffcf9701 (XEN) Xen heap: 00000000fa000000-00000000fe000000 (16384 pages) (XEN) Dom heap: 507648 pages (XEN) Domain heap initialised (XEN) Platform: TEGRA124 (XEN) Looking for dtuart at "s Xen 4.6-unstable (XEN) Xen version 4.6-unstable (root@) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.7.3-11ubuntu1) 4.7.3) debug=y Thu Mar 24 08:02:39 UTC 2016 (XEN) Latest ChangeSet: (XEN) Processor: 413fc0f3: "ARM Limited", variant: 0x3, part 0xc0f, rev 0x3 (XEN) 32-bit Execution: (XEN) Processor Features: 00001131:00011011 (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle (XEN) Extensions: GenericTimer Security (XEN) Debug Features: 02010555 (XEN) Auxiliary Features: 00000000 (XEN) Memory Model Features: 10201105 40000000 01240000 02102211 (XEN) ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000 (XEN) Using PSCI-0.1 for SMP bringup (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 12000 KHz (XEN) GICv2 initialization: (XEN) gic_dist_addr=0000000050041000 (XEN) gic_cpu_addr=0000000050042000 (XEN) gic_hyp_addr=0000000050044000 (XEN) gic_vcpu_addr=0000000050046000 (XEN) gic_maintenance_irq=25 (XEN) GICv2: 192 lines, 4 cpus, secure (IID 0000043b). (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) I/O virtualisation disabled (XEN) Allocated console ring of 32 KiB. (XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0 (XEN) Bringing up CPU1 - CPU 00000001 booting - - Xen starting in Hyp mode - - Setting up control registers - - Turning on paging - - Ready - (XEN) CPU 1 booted. (XEN) Bringing up CPU2 - CPU 00000002 booting - - Xen starting in Hyp mode - - Setting up control registers - - Turning on paging - - Ready - (XEN) CPU 2 booted. (XEN) Bringing up CPU3 - CPU 00000003 booting - - Xen starting in Hyp mode - - Setting up control registers - - Turning on paging - - Ready - (XEN) CPU 3 booted. (XEN) Brought up 4 CPUs (XEN) P2M: 40-bit IPA (XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558 (XEN) *** LOADING DOMAIN 0 *** (XEN) Loading kernel from boot module @ 0000000081000000 (XEN) Allocating 1:1 mappings totalling 512MB for dom0: (XEN) BANK[0] 0x000000a0000000-0x000000c0000000 (512MB) (XEN) Additional MMIO 40000-40040 (IRAM) (XEN) Additional MMIO 54200-54240 (Display A) (XEN) Additional MMIO 54240-54280 (Display B) (XEN) Additional MMIO 6000f-60010 (EXCEPTION VECTORS) (XEN) Additional MMIO 6000c-6000d (SYSREG) (XEN) Additional MMIO 1000-1001 (PCI CFG0) (XEN) Additional MMIO 1001-1002 (PCI CFG1) (XEN) Additional MMIO 12000-12010 (PCI IO) (XEN) Additional MMIO 13000-20000 (PCI MEM) (XEN) Additional MMIO 20000-40000 (PCI MEM (PREFETCH)) (XEN) Additional IRQ 105 (DISPLAY) (XEN) TEGRA: Routing IRQ105 to dom0, ICTLR2, mask 0x000200 (XEN) Additional IRQ 106 (DISPLAY B) (XEN) TEGRA: Routing IRQ106 to dom0, ICTLR2, mask 0x000400 (XEN) Loading zImage from 0000000081000000 to 00000000a7a00000-00000000a7f44828 (XEN) Allocating PPI 16 for event channel interrupt (XEN) Loading dom0 DTB to 0x00000000a8000000-0x00000000a800f1f0 (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs (XEN) ....done. (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 272kB init memory. (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 (XEN) DOM0: .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 re (XEN) DOM0: served, 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 (XEN) DOM0: [ 0.000000] bootconsole [earlycon0] disabled >> >> 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? I am using the device tree which is built with the Linux kernel version 4.1.0 (tegra124-jetson-tk1.dtb), I have also attached the device tree source with this mail, If you want to have a look. Thanks, Dushyant
Hello Dushyant, On 29/03/16 21:56, Dushyant Behl wrote: > On Wed, Mar 30, 2016 at 12:31 AM, Julien Grall <julien.grall@arm.com> wrote: >> On 24/03/16 11:05, Dushyant Behl wrote: > (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 It looks like to me that Xen is not recreating the device-tree correctly. I would look into the kernel to find what is expected. Regards,
Hello, On Fri, Apr 1, 2016 at 3:34 PM, Julien Grall <julien.grall@arm.com> wrote: > Hello Dushyant, > > On 29/03/16 21:56, Dushyant Behl wrote: >> >> On Wed, Mar 30, 2016 at 12:31 AM, Julien Grall <julien.grall@arm.com> >> wrote: >>> >>> On 24/03/16 11:05, Dushyant Behl wrote: > > >> (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 > > > It looks like to me that Xen is not recreating the device-tree correctly. I > would look into the kernel to find what is expected. This looks like a possible bug (or some missing feature) in Xen's device tree creation which could take some time to handle, so if I could be of any more help to you with this issue please let me know. [I've cc'ed Ian Campbell in this mail (Sorry for cc'ing you explicitly)] Ian, Actually, I want to run Xen on the Tegra Jetson board for some project of mine but currently Linux-4.1 is failing as dom0 because its not able to receive interrupts from the arch_timer. This link contains the dom0 failure boot log - http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg03715.html In your patch for *Hacky* support for Jetsok-TK1 you said that you were able to run guests on Jetson-tk1 board with Xen. Can I know which kernel version you used as dom0 (and possibly domU guests)? Thanks and Regards, Dushyant Behl
On 07/04/16 08:48, Dushyant Behl wrote: > Hello, Hi Dushyant, > On Fri, Apr 1, 2016 at 3:34 PM, Julien Grall <julien.grall@arm.com> wrote: >> Hello Dushyant, >> >> On 29/03/16 21:56, Dushyant Behl wrote: >>> >>> On Wed, Mar 30, 2016 at 12:31 AM, Julien Grall <julien.grall@arm.com> >>> wrote: >>>> >>>> On 24/03/16 11:05, Dushyant Behl wrote: >> >> >>> (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 >> >> >> It looks like to me that Xen is not recreating the device-tree correctly. I >> would look into the kernel to find what is expected. > > This looks like a possible bug (or some missing feature) in Xen's > device tree creation which could > take some time to handle, so if I could be of any more help to you > with this issue please let me know. There was a conversation on #xen-arm few days ago about this problem. Xen doesn't correctly recreate the GIC node which result in a loop between the interrupt controller. Can you try the below patch? http://dev.ktemkin.com/misc/xenarm-gic-parents.patch > > [I've cc'ed Ian Campbell in this mail (Sorry for cc'ing you explicitly)] Ian's citrix e-mail is not valid anymore. I have CC'ed the new one. > Ian, > > Actually, I want to run Xen on the Tegra Jetson board for some project > of mine but currently Linux-4.1 is > failing as dom0 because its not able to receive interrupts from the arch_timer. > This link contains the dom0 failure boot log - > http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg03715.html > > In your patch for *Hacky* support for Jetsok-TK1 you said that you > were able to run guests on > Jetson-tk1 board with Xen. Can I know which kernel version you used as > dom0 (and possibly domU guests)? Regards,
On Fri, 2016-04-08 at 11:10 +0100, Julien Grall wrote: > > In your patch for *Hacky* support for Jetsok-TK1 you said that you > > were able to run guests on > > Jetson-tk1 board with Xen. Can I know which kernel version you used as > > dom0 (and possibly domU guests)? I'm afraid I don't remember. It would probably either have been some current-ish upstream kernel from the time, or possibly a Debian kernel from around the time. So maybe something 3.16-ish? Ian.
Hi Everyone, On Fri, Apr 8, 2016 at 5:57 PM, Ian Campbell <ijc@hellion.org.uk> wrote: >> > In your patch for *Hacky* support for Jetsok-TK1 you said that you >> > were able to run guests on >> > Jetson-tk1 board with Xen. Can I know which kernel version you used as >> > dom0 (and possibly domU guests)? > > I'm afraid I don't remember. It would probably either have been some > current-ish upstream kernel from the time, or possibly a Debian kernel > from around the time. So maybe something 3.16-ish? @Ian Thanks for the Reply. @Julien, Thanks a lot, your patch for GIC dtb node worked and the linux kernel is now able to enable the arch timer. (Although I needed to modify the code manually as the tree I'm using is older Xen-4.6, and maybe the patch was against the latest version of xen). The kernel is able to initialize itself but it fails while initializing some nvidia devices in the boot process. I've posted the log here, Could this also be an issue with the device tree or this is something related to the kernel? - UART enabled - - CPU 00000000 booting - - Xen starting in Hyp mode - - Zero BSS - - Setting up control registers - - Turning on paging - - Ready - (XEN) Checking for initrd in /chosen (XEN) RAM: 0000000080000000 - 00000000ffefffff (XEN) (XEN) MODULE[0]: 0000000082000000 - 0000000082010000 Device Tree (XEN) MODULE[1]: 0000000081000000 - 00000000815443f0 Kernel console=hvc0 root=/dev/mmcblk0p1 rw rootwait (XEN) RESVD[0]: 0000000082000000 - 0000000082010000 (XEN) (XEN) Command line: console=dtuart dtuart=serial0 dom0_mem=512M sync_console log_lvl=all guest_loglvl=all (XEN) Placing Xen at 0x00000000ffc00000-0x00000000ffe00000 (XEN) Update BOOTMOD_XEN from 00000000fd000000-00000000fd0f9701 => 00000000ffc00000-00000000ffcf9701 (XEN) Xen heap: 00000000fa000000-00000000fe000000 (16384 pages) (XEN) Dom heap: 507648 pages (XEN) Domain heap initialised (XEN) Platform: TEGRA124 (XEN) Looking for dtuart at "s Xen 4.6-unstable (XEN) Xen version 4.6-unstable (root@) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.7.3-11ubuntu1) 4.7.3) debug=y Mon Apr 11 09:20:25 UTC 2016 (XEN) Latest ChangeSet: (XEN) Console output is synchronous. (XEN) Processor: 413fc0f3: "ARM Limited", variant: 0x3, part 0xc0f, rev 0x3 (XEN) 32-bit Execution: (XEN) Processor Features: 00001131:00011011 (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle (XEN) Extensions: GenericTimer Security (XEN) Debug Features: 02010555 (XEN) Auxiliary Features: 00000000 (XEN) Memory Model Features: 10201105 40000000 01240000 02102211 (XEN) ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000 (XEN) Using PSCI-0.1 for SMP bringup (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 12000 KHz (XEN) GICv2 initialization: (XEN) gic_dist_addr=0000000050041000 (XEN) gic_cpu_addr=0000000050042000 (XEN) gic_hyp_addr=0000000050044000 (XEN) gic_vcpu_addr=0000000050046000 (XEN) gic_maintenance_irq=25 (XEN) GICv2: 192 lines, 4 cpus, secure (IID 0000043b). (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) I/O virtualisation disabled (XEN) Allocated console ring of 32 KiB. (XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0 (XEN) Bringing up CPU1 - CPU 00000001 booting - - Xen starting in Hyp mode - - Setting up control registers - - Turning on paging - - Ready - (XEN) CPU 1 booted. (XEN) Bringing up CPU2 - CPU 00000002 booting - - Xen starting in Hyp mode - - Setting up control registers - - Turning on paging - - Ready - (XEN) CPU 2 booted. (XEN) Bringing up CPU3 - CPU 00000003 booting - - Xen starting in Hyp mode - - Setting up control registers - - Turning on paging - - Ready - (XEN) CPU 3 booted. (XEN) Brought up 4 CPUs (XEN) P2M: 40-bit IPA (XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558 (XEN) *** LOADING DOMAIN 0 *** (XEN) Loading kernel from boot module @ 0000000081000000 (XEN) zImage: no appended dtb (XEN) zImage32 Probe successful (XEN) Allocating 1:1 mappings totalling 512MB for dom0: (XEN) BANK[0] 0x000000a0000000-0x000000c0000000 (512MB) (XEN) Additional MMIO 40000-40040 (IRAM) (XEN) Additional MMIO 54200-54240 (Display A) (XEN) Additional MMIO 54240-54280 (Display B) (XEN) Additional MMIO 6000f-60010 (EXCEPTION VECTORS) (XEN) Additional MMIO 6000c-6000d (SYSREG) (XEN) Additional MMIO 1000-1001 (PCI CFG0) (XEN) Additional MMIO 1001-1002 (PCI CFG1) (XEN) Additional MMIO 12000-12010 (PCI IO) (XEN) Additional MMIO 13000-20000 (PCI MEM) (XEN) Additional MMIO 20000-40000 (PCI MEM (PREFETCH)) (XEN) Additional IRQ 105 (DISPLAY) (XEN) TEGRA: Routing IRQ105 to dom0, ICTLR2, mask 0x000200 (XEN) Additional IRQ 106 (DISPLAY B) (XEN) TEGRA: Routing IRQ106 to dom0, ICTLR2, mask 0x000400 (XEN) Loading zImage from 0000000081000000 to 00000000a7a00000-00000000a7f443f0 (XEN) Allocating PPI 16 for event channel interrupt (XEN) Loading dom0 DTB to 0x00000000a8000000-0x00000000a800f1d0 (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs (XEN) ....done. (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: All (XEN) Guest Loglevel: All (XEN) ********************************************** (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS (XEN) ******* This option is intended to aid debugging of Xen by ensuring (XEN) ******* that all output is synchronously delivered on the serial line. (XEN) ******* However it can introduce SIGNIFICANT latencies and affect (XEN) ******* timekeeping. It is NOT recommended for production use! (XEN) ********************************************** (XEN) 3... 2... 1... (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 272kB init memory. (XEN) DOM0: Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.1.0-196898-g2e68ed9-dirty (root@ubuntu-server) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-11ubuntu1) ) #3 SMP PREEMPT Wed Apr 13 08:28:23 UTC 2016 [ 0.000000] CPU: ARMv7 Processor [413fc0f3] revision 3 (ARMv7), cr=30c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] Machine model: NVIDIA Tegra124 Jetson TK1 [ 0.000000] cma: Reserved 64 MiB at 0x00000000bc000000 [ 0.000000] Forcing write-allocate cache policy for SMP [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv0.2 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] PERCPU: Embedded 12 pages/cpu @dbb77000 s19712 r8192 d21248 u49152 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [ 0.000000] Kernel command line: console=hvc0 root=/dev/mmcblk0p1 rw rootwait [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 441884K/524288K available (7657K kernel code, 634K rwdata, 2584K rodata, 484K init, 383K bss, 16868K reserved, 65536K cma-reserved, 0K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc0a08c10 (10244 kB) [ 0.000000] .init : 0xc0a09000 - 0xc0a82000 ( 484 kB) [ 0.000000] .data : 0xc0a82000 - 0xc0b20bec ( 635 kB) [ 0.000000] .bss : 0xc0b23000 - 0xc0b82ea0 ( 384 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 32. [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] /interrupt-controller@60004000: 160 interrupts forwarded to /interrupt-controller [ 0.000000] L2C: failed to init: -19 [ 0.000000] Architected cp15 timer(s) running at 12.00MHz (virt). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2c47f4ee7, max_idle_ns: 440795202497 ns [ 0.000005] sched_clock: 56 bits at 12MHz, resolution 83ns, wraps every 4398046511096ns [ 0.000018] Switching to timer-based delay loop, resolution 83ns [ 0.000500] Console: colour dummy device 80x30 [ 0.000521] Calibrating delay loop (skipped), value calculated using timer frequency.. 24.00 BogoMIPS (lpj=120000) [ 0.000536] pid_max: default: 32768 minimum: 301 [ 0.000948] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.000959] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.002350] Initializing cgroup subsys freezer [ 0.002376] Initializing cgroup subsys debug [ 0.002431] CPU: Testing write buffer coherency: ok [ 0.002752] /cpus/cpu@0 missing clock-frequency property [ 0.002794] /cpus/cpu@1 missing clock-frequency property [ 0.002835] /cpus/cpu@2 missing clock-frequency property [ 0.002877] /cpus/cpu@3 missing clock-frequency property [ 0.002890] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.003106] Xen 4.6 support found, events_irq=19 gnttab_frame=0x0000000068000000 [ 0.003265] xen:grant_table: Grant tables using version 1 layout [ 0.003313] Grant table initialized [ 0.003378] xen:events: Using FIFO-based ABI [ 0.003398] Xen: initializing cpu0 [ 0.003496] Setting up static identity map for 0xa0008480 - 0xa0008518 [ 0.020405] Tegra Revision: A01 SKU: 129 CPU Process: 1 Core Process: 1 [ 0.030786] Xen: initializing cpu1 [ 0.030840] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.040798] Xen: initializing cpu2 [ 0.040851] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.050839] Xen: initializing cpu3 [ 0.050890] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.051037] Brought up 4 CPUs [ 0.051063] SMP: Total of 4 processors activated (96.00 BogoMIPS). [ 0.051071] CPU: All CPU(s) started in SVC mode. [ 0.052162] devtmpfs: initialized [ 0.100284] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 [ 0.101016] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.103189] pinctrl core: initialized pinctrl subsystem [ 0.105124] NET: Registered protocol family 16 [ 0.106377] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.108915] xen:swiotlb_xen: Warning: only able to allocate 4 MB for software IO TLB [ 0.110050] software IO TLB [mem 0xbac00000-0xbb000000] (4MB) mapped at [dac00000-daffffff] [ 0.133440] hw-breakpoint: Failed to enable monitor mode on CPU 1. [ 0.183494] xen:balloon: Initialising balloon driver [ 0.184060] xen_balloon: Initialising balloon driver [ 0.187333] +USB0_VBUS_SW: Failed to request enable GPIO108: -517 [ 0.187556] reg-fixed-voltage regulators:regulator@7: Failed to register regulator: -517 [ 0.188011] +5V_USB_HS: Failed to request enable GPIO109: -517 [ 0.188224] reg-fixed-voltage regulators:regulator@8: Failed to register regulator: -517 [ 0.188785] +1.05V_RUN_AVDD_HDMI_PLL: Failed to request enable GPIO63: -517 [ 0.188995] reg-fixed-voltage regulators:regulator@11: Failed to register regulator: -517 [ 0.189447] +5V_HDMI_CON: Failed to request enable GPIO86: -517 [ 0.189655] reg-fixed-voltage regulators:regulator@12: Failed to register regulator: -517 [ 0.190105] +5V_SATA: Failed to request enable GPIO242: -517 [ 0.190352] reg-fixed-voltage regulators:regulator@13: Failed to register regulator: -517 [ 0.190806] +12V_SATA: Failed to request enable GPIO242: -517 [ 0.191013] reg-fixed-voltage regulators:regulator@14: Failed to register regulator: -517 [ 0.192568] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 32 [ 0.192786] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 36 [ 0.192994] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 40 [ 0.193217] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 42 [ 0.193467] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 44 [ 0.193673] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 48 [ 0.193892] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 32 [ 0.194553] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 36 [ 0.195292] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 40 [ 0.195949] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 42 [ 0.196604] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 44 [ 0.197262] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 48 [ 0.197974] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 32 [ 0.200524] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 36 [ 0.203036] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 40 [ 0.205604] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 42 [ 0.208285] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 44 [ 0.210797] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 48 [ 0.213295] arm-lpae io-pgtable: selftest: completed with 18 PASS 0 FAIL [ 0.214020] vgaarb: loaded [ 0.215731] SCSI subsystem initialized [ 0.216928] usbcore: registered new interface driver usbfs [ 0.217108] usbcore: registered new interface driver hub [ 0.217316] usbcore: registered new device driver usb [ 0.221769] Linux video capture interface: v2.00 [ 0.221900] pps_core: LinuxPPS API ver. 1 registered [ 0.221908] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.221980] PTP clock support registered [ 0.223885] Advanced Linux Sound Architecture Driver Initialized. [ 0.225412] Bluetooth: Core ver 2.20 [ 0.225493] NET: Registered protocol family 31 [ 0.225502] Bluetooth: HCI device and connection manager initialized [ 0.225533] Bluetooth: HCI socket layer initialized [ 0.225555] Bluetooth: L2CAP socket layer initialized [ 0.225611] Bluetooth: SCO socket layer initialized [ 0.226236] cfg80211: Calling CRDA to update world regulatory domain [ 0.227195] clocksource: Switched to clocksource arch_sys_counter [ 0.362983] NET: Registered protocol family 2 [ 0.364477] TCP established hash table entries: 4096 (order: 2, 16384 bytes) [ 0.364539] TCP bind hash table entries: 4096 (order: 3, 32768 bytes) [ 0.364637] TCP: Hash tables configured (established 4096 bind 4096) [ 0.364907] UDP hash table entries: 256 (order: 1, 8192 bytes) [ 0.364935] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [ 0.365428] NET: Registered protocol family 1 [ 0.366382] RPC: Registered named UNIX socket transport module. [ 0.366392] RPC: Registered udp transport module. [ 0.366399] RPC: Registered tcp transport module. [ 0.366406] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.370824] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.374618] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.383547] io scheduler noop registered (default) [ 0.394250] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration [ 0.394303] tegra-pcie 1003000.pcie-controller: Failed to get supply 'avddio-pex': -517 [ 0.406173] tegra-apbdma 60020000.dma: Tegra20 APB DMA driver register 32 channels [ 0.406682] tegra-pmc 7000e400.pmc: emergency thermal reset enabled [ 0.408157] xen:xen_evtchn: Event-channel device installed [ 1.317385] console [hvc0] enabled [ 1.320937] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 1.333011] [drm] Initialized drm 1.1.0 20060810 [ 1.368145] tegra-hdmi 54280000.hdmi: failed to get HDMI regulator [ 1.388139] loop: module loaded [ 1.390403] at24 0-0056: 256 byte 24c02 EEPROM, writable, 8 bytes/write [ 2.387235] tegra-i2c 7000d000.i2c: i2c transfer timed out [ 2.390845] as3722 4-0040: ASIC_ID1 read failed: -110 [ 2.396044] as3722: probe of 4-0040 failed with error -110 [ 2.402569] tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517 [ 2.408180] tegra-ahci 70027000.sata: Failed to get regulators [ 3.387251] cfg80211: Calling CRDA to update world regulatory domain [ 3.417234] ------------[ cut here ]------------ [ 3.419967] WARNING: CPU: 1 PID: 1 at drivers/spi/spi-tegra114.c:838 tegra_spi_transfer_one_message+0x410/0x438() [ 3.430302] Modules linked in: [ 3.433392] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.1.0-196898-g2e68ed9-dirty #3 [ 3.441203] Hardware name: NVIDIA Tegra SoC (Flattened Device Tree) [ 3.447560] [<c00177d8>] (unwind_backtrace) from [<c0013040>] (show_stack+0x10/0x14) [ 3.455327] [<c0013040>] (show_stack) from [<c073b7e8>] (dump_stack+0x84/0xd0) [ 3.462622] [<c073b7e8>] (dump_stack) from [<c0028b84>] (warn_slowpath_common+0x78/0xb4) [ 3.470766] [<c0028b84>] (warn_slowpath_common) from [<c0028bdc>] (warn_slowpath_null+0x1c/0x24) [ 3.479606] [<c0028bdc>] (warn_slowpath_null) from [<c03ed068>] (tegra_spi_transfer_one_message+0x410/0x438) [ 3.489485] [<c03ed068>] (tegra_spi_transfer_one_message) from [<c03e9d68>] (__spi_pump_messages+0x36c/0x674) [ 3.499462] [<c03e9d68>] (__spi_pump_messages) from [<c03ea194>] (__spi_sync+0x124/0x1a8) [ 3.507701] [<c03ea194>] (__spi_sync) from [<c03ea2ec>] (spi_write_then_read+0xc4/0x174) [ 3.515814] [<c03ea2ec>] (spi_write_then_read) from [<c03e6904>] (m25p80_read_reg+0x34/0x64) [ 3.524321] [<c03e6904>] (m25p80_read_reg) from [<c03e6fec>] (spi_nor_read_id+0x20/0xa8) [ 3.532483] [<c03e6fec>] (spi_nor_read_id) from [<c03e7ac8>] (spi_nor_scan+0x2a8/0x80c) [ 3.540524] [<c03e7ac8>] (spi_nor_scan) from [<c03e6840>] (m25p_probe+0xb0/0x140) [ 3.548065] [<c03e6840>] (m25p_probe) from [<c03e96c8>] (spi_drv_probe+0x5c/0x74) [ 3.555600] [<c03e96c8>] (spi_drv_probe) from [<c037db44>] (driver_probe_device+0x1c8/0x26c) [ 3.564106] [<c037db44>] (driver_probe_device) from [<c037c244>] (bus_for_each_drv+0x44/0x8c) [ 3.572684] [<c037c244>] (bus_for_each_drv) from [<c037d904>] (__device_attach+0x88/0xd8) [ 3.580917] [<c037d904>] (__device_attach) from [<c037d0bc>] (bus_probe_device+0x84/0x8c) [ 3.589149] [<c037d0bc>] (bus_probe_device) from [<c037b5fc>] (device_add+0x33c/0x524) [ 3.597110] [<c037b5fc>] (device_add) from [<c03e9540>] (spi_add_device+0x88/0x130) [ 3.604835] [<c03e9540>] (spi_add_device) from [<c03eab64>] (of_register_spi_device+0x208/0x2f8) [ 3.613676] [<c03eab64>] (of_register_spi_device) from [<c03eb034>] (spi_register_master+0x214/0x444) [ 3.622950] [<c03eb034>] (spi_register_master) from [<c03eb290>] (devm_spi_register_master+0x2c/0x68) [ 3.632222] [<c03eb290>] (devm_spi_register_master) from [<c03ebdc8>] (tegra_spi_probe+0x29c/0x350) [ 3.641322] [<c03ebdc8>] (tegra_spi_probe) from [<c037f230>] (platform_drv_probe+0x48/0xa4) [ 3.649728] [<c037f230>] (platform_drv_probe) from [<c037db44>] (driver_probe_device+0x1c8/0x26c) [ 3.658671] [<c037db44>] (driver_probe_device) from [<c037dc74>] (__driver_attach+0x8c/0x90) [ 3.667135] [<c037dc74>] (__driver_attach) from [<c037c2e0>] (bus_for_each_dev+0x54/0x88) [ 3.675382] [<c037c2e0>] (bus_for_each_dev) from [<c037d2a0>] (bus_add_driver+0xe8/0x1f4) [ 3.683622] [<c037d2a0>] (bus_add_driver) from [<c037e6a0>] (driver_register+0x78/0xf4) [ 3.691693] [<c037e6a0>] (driver_register) from [<c00096c4>] (do_one_initcall+0x80/0x1d0) [ 3.699908] [<c00096c4>] (do_one_initcall) from [<c0a09dc8>] (kernel_init_freeable+0x110/0x1dc) [ 3.708663] [<c0a09dc8>] (kernel_init_freeable) from [<c0736770>] (kernel_init+0x8/0xec) [ 3.716795] [<c0736770>] (kernel_init) from [<c000fde8>] (ret_from_fork+0x14/0x2c) [ 3.724439] ---[ end trace e92698c5376bfefb ]--- [ 3.729108] spi-tegra114 7000da00.spi: spi trasfer timeout, err 0 [ 3.735272] spi_master spi32765: failed to transfer one message from queue [ 3.742195] m25p80 spi32765.0: error -5 reading 9f [ 3.747049] m25p80: probe of spi32765.0 failed with error -5 [ 3.754768] CAN device driver interface [ 3.756829] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k [ 3.763827] igb: Copyright (c) 2007-2014 Intel Corporation. [ 3.769830] xen_netfront: Initialising Xen virtual ethernet driver [ 3.776009] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver [ 3.783289] usbcore: registered new interface driver pegasus [ 3.789058] usbcore: registered new interface driver asix [ 3.794455] usbcore: registered new interface driver ax88179_178a [ 3.800637] usbcore: registered new interface driver cdc_ether [ 3.806555] usbcore: registered new interface driver smsc75xx [ 3.812372] usbcore: registered new interface driver smsc95xx [ 3.818129] usbcore: registered new interface driver net1080 [ 3.823837] usbcore: registered new interface driver cdc_subset [ 3.829849] usbcore: registered new interface driver zaurus [ 3.835520] usbcore: registered new interface driver cdc_ncm [ 3.841358] tegra-phy 7d004000.usb-phy: no vbus regulator [ 3.847023] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.853106] ehci-pci: EHCI PCI platform driver [ 3.857735] tegra-ehci: Tegra EHCI driver [ 3.862029] tegra-ehci 7d004000.usb: EHCI Host Controller [ 3.867164] tegra-ehci 7d004000.usb: new USB bus registered, assigned bus number 1 [ 3.875088] tegra-ehci 7d004000.usb: irq 342, io mem 0x7d004000 [ 3.897244] tegra-ehci 7d004000.usb: USB 2.0 started, EHCI 1.10 [ 3.903016] hub 1-0:1.0: USB hub found [ 3.905146] hub 1-0:1.0: 1 port detected [ 3.910543] usbcore: registered new interface driver cdc_acm [ 3.914781] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 3.923002] usbcore: registered new interface driver cdc_wdm [ 3.928802] usbcore: registered new interface driver usb-storage [ 3.935427] mousedev: PS/2 mouse device common for all mice [ 3.943355] tegra_rtc 7000e000.rtc: rtc core: registered 7000e000.rtc as rtc1 [ 3.948720] tegra_rtc 7000e000.rtc: Tegra internal Real Time Clock [ 3.955257] i2c /dev entries driver [ 3.960738] usbcore: registered new interface driver uvcvideo [ 3.964583] USB Video Class driver (1.1.1) [ 3.968790] gspca_main: v2.14.0 registered [ 3.973727] 0-004c supply vcc not found, using dummy regulator [ 4.977235] tegra-i2c 7000c000.i2c: i2c transfer timed out [ 4.980846] lm90 0-004c: Register 0x4 read failed (-110) [ 4.986196] lm90 0-004c: Failed to read convrate register! [ 5.987234] tegra-i2c 7000c000.i2c: i2c transfer timed out [ 6.547246] cfg80211: Calling CRDA to update world regulatory domain [ 6.987237] tegra-i2c 7000c000.i2c: i2c transfer timed out [ 6.990842] lm90 0-004c: Register 0x3 read failed (-110) [ 6.996198] lm90 0-004c: Initialization failed! [ 7.002041] sdhci: Secure Digital Host Controller Interface driver [ 7.007027] sdhci: Copyright(c) Pierre Ossman [ 7.011481] sdhci-pltfm: SDHCI platform and OF driver helper [ 7.017580] sdhci-tegra 700b0400.sdhci: Got CD GPIO [ 7.022128] sdhci-tegra 700b0400.sdhci: Got WP GPIO [ 7.027105] mmc0: Unknown controller version (3). You may experience problems. [ 7.034491] sdhci-tegra 700b0400.sdhci: No vmmc regulator found [ 7.040550] mmc0: Unknown controller version (3). You may experience problems. [ 7.047721] sdhci-tegra 700b0600.sdhci: No vmmc regulator found [ 7.053570] sdhci-tegra 700b0600.sdhci: No vqmmc regulator found [ 7.059654] mmc0: Invalid maximum block size, assuming 512 bytes [ 7.117253] mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit [ 7.124468] usbcore: registered new interface driver usbhid [ 7.128999] usbhid: USB HID core driver [ 8.537237] tegra-i2c 7000c000.i2c: i2c transfer timed out [ 8.540847] rt5640 0-001c: Device with ID register c0af9d34 is not rt5640/39 [ 8.551341] tegra30-i2s 70301100.i2s: DMA channels sourced from device 70300000.ahub [ 8.557838] tegra-snd-rt5640 sound: ASoC: CODEC DAI rt5640-aif1 not registered [ 8.564464] tegra-snd-rt5640 sound: snd_soc_register_card failed (-517) [ 8.573237] NET: Registered protocol family 10 [ 8.577517] mip6: Mobile IPv6 [ 8.578820] sit: IPv6 over IPv4 tunneling driver [ 8.586541] NET: Registered protocol family 17 [ 8.589192] NET: Registered protocol family 15 [ 8.593603] can: controller area network core (rev 20120528 abi 9) [ 8.600037] NET: Registered protocol family 29 [ 8.604351] can: raw protocol (rev 20120528) [ 8.608697] can: broadcast manager protocol (rev 20120528 t) [ 8.614418] can: netlink gateway (rev 20130117) max_hops=1 [ 8.620197] Bluetooth: RFCOMM socket layer initialized [ 8.625156] Bluetooth: RFCOMM ver 1.11 [ 8.628991] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 8.634341] Bluetooth: BNEP socket layer initialized [ 8.639374] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 8.645349] Bluetooth: HIDP socket layer initialized [ 8.650678] Registering SWP/SWPB emulation handler [ 8.661218] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration [ 8.665886] tegra-pcie 1003000.pcie-controller: Failed to get supply 'avddio-pex': -517 [ 8.674354] +5V_SYS: supplied by +VDD_MUX [ 8.678090] +5V_HDMI_CON: supplied by +5V_SYS [ 8.682576] reg-fixed-voltage regulators:regulator@11: Failed to resolve vin-supply for +1.05V_RUN_AVDD_HDMI_PLL [ 8.692649] tegra-hdmi 54280000.hdmi: failed to get PLL regulator [ 8.699325] tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517 [ 8.705454] tegra-ahci 70027000.sata: Failed to get regulators [ 8.711824] +5V_USB_HS: supplied by +5V_SYS [ 8.716182] tegra-ehci 7d008000.usb: EHCI Host Controller [ 8.721165] tegra-ehci 7d008000.usb: new USB bus registered, assigned bus number 2 [ 8.729155] tegra-ehci 7d008000.usb: irq 343, io mem 0x7d008000 [ 8.747246] tegra-ehci 7d008000.usb: USB 2.0 started, EHCI 1.10 [ 8.753009] hub 2-0:1.0: USB hub found [ 8.755139] hub 2-0:1.0: 1 port detected [ 8.760236] sdhci-tegra 700b0400.sdhci: Got CD GPIO [ 8.764021] sdhci-tegra 700b0400.sdhci: Got WP GPIO [ 8.769021] mmc1: Unknown controller version (3). You may experience problems. [ 8.776370] sdhci-tegra 700b0400.sdhci: No vmmc regulator found [ 8.782726] tegra-snd-rt5640 sound: ASoC: CODEC DAI rt5640-aif1 not registered [ 8.789521] tegra-snd-rt5640 sound: snd_soc_register_card failed (-517) [ 8.796977] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration [ 8.802818] tegra-pcie 1003000.pcie-controller: Failed to get supply 'avddio-pex': -517 [ 8.811291] reg-fixed-voltage regulators:regulator@11: Failed to resolve vin-supply for +1.05V_RUN_AVDD_HDMI_PLL [ 8.821048] tegra-hdmi 54280000.hdmi: failed to get PLL regulator [ 8.827691] tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517 [ 8.833857] tegra-ahci 70027000.sata: Failed to get regulators [ 8.840805] input: gpio-keys as /devices/soc0/gpio-keys/input/input0 [ 8.846820] hctosys: unable to open rtc device (rtc0) [ 8.847331] sdhci-tegra 700b0400.sdhci: Got CD GPIO [ 8.847369] sdhci-tegra 700b0400.sdhci: Got WP GPIO [ 8.847471] mmc1: Unknown controller version (3). You may experience problems. [ 8.851403] sdhci-tegra 700b0400.sdhci: No vmmc regulator found [ 8.852328] tegra-snd-rt5640 sound: ASoC: CODEC DAI rt5640-aif1 not registered [ 8.852340] tegra-snd-rt5640 sound: snd_soc_register_card failed (-517) [ 8.854009] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration [ 8.854062] tegra-pcie 1003000.pcie-controller: Failed to get supply 'avddio-pex': -517 [ 8.855019] reg-fixed-voltage regulators:regulator@11: Failed to resolve vin-supply for +1.05V_RUN_AVDD_HDMI_PLL [ 8.855030] tegra-hdmi 54280000.hdmi: failed to get PLL regulator [ 8.856050] tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517 [ 8.856059] tegra-ahci 70027000.sata: Failed to get regulators [ 8.951051] +12V_SATA: disabling [ 8.952391] +5V_SATA: disabling [ 8.955596] +5V_HDMI_CON: disabling [ 8.959166] +1.05V_RUN_AVDD_HDMI_PLL: disabling [ 8.963742] +USB0_VBUS_SW: disabling [ 8.967400] +3.3V_AVDD_HDMI_ Thanks and Regards, Dushyant
Hi Julien and Dushyant, >>> >>>> (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 >>> >>> >>> >>> It looks like to me that Xen is not recreating the device-tree correctly. >>> I >>> would look into the kernel to find what is expected. >> >> >> This looks like a possible bug (or some missing feature) in Xen's >> device tree creation which could >> take some time to handle, so if I could be of any more help to you >> with this issue please let me know. > > > There was a conversation on #xen-arm few days ago about this problem. Is there a way that we can see the conversation on #xen-arm? I hope to better understand the problem. > Xen doesn't correctly recreate the GIC node which result in a loop between > the interrupt controller. Can you try the below patch? > > http://dev.ktemkin.com/misc/xenarm-gic-parents.patch It seems this link is invalid now... Has this patch been upstreamed? Hi Dushyant, Could you help repost this patch in this email if it's not that large? (Since we used the same repo, which is IanC's, it may be even better if you could kindly share the patch based on the tegra-tk1-jetson-v1 branch of Ian's repo.?) Hi Julien, Do you have some suggestions on how we can debug and fix the issue related to the device tree? I saw that there may still be some issues with the NVIDIA devices as Dushyant described after he applied the patch. Right now, I have the exact same board as Dushyant has. I think I may encounter the exact same issue as he did. So I'm wondering if there is some documentation/tutorial/notes that we can learn about how to debug the issues. Thank you both very much for your help and time! Best Regards, Meng ----------- Meng Xu PhD Student in Computer and Information Science University of Pennsylvania http://www.cis.upenn.edu/~mengxu/
Hey Meng, On Sat, May 14, 2016 at 7:39 AM, Meng Xu <xumengpanda@gmail.com> wrote: >> >> http://dev.ktemkin.com/misc/xenarm-gic-parents.patch > > It seems this link is invalid now... > Has this patch been upstreamed? > > Hi Dushyant, > Could you help repost this patch in this email if it's not that large? > (Since we used the same repo, which is IanC's, it may be even better > if you could kindly share the patch based on the tegra-tk1-jetson-v1 > branch of Ian's repo.?) The patch is attached with the mail. Thanks, Dushyant
Hi Dushyant, On Sat, May 14, 2016 at 1:36 PM, Dushyant Behl <myselfdushyantbehl@gmail.com> wrote: > Hey Meng, > > On Sat, May 14, 2016 at 7:39 AM, Meng Xu <xumengpanda@gmail.com> wrote: >>> >>> http://dev.ktemkin.com/misc/xenarm-gic-parents.patch >> >> It seems this link is invalid now... >> Has this patch been upstreamed? >> >> Hi Dushyant, >> Could you help repost this patch in this email if it's not that large? >> (Since we used the same repo, which is IanC's, it may be even better >> if you could kindly share the patch based on the tegra-tk1-jetson-v1 >> branch of Ian's repo.?) > > The patch is attached with the mail. > Thank you so much for your help! I applied the patch and the kernel can have further progress in booting. I'm replying to your last email about the issue I'm facing to, which seems not same with what you saw. Best Regards, Meng ----------- Meng Xu PhD Student in Computer and Information Science University of Pennsylvania http://www.cis.upenn.edu/~mengxu/
Hi Dushyant, >>> On Thu, Mar 17, 2016 at 8:22 PM, Julien Grall <julien.grall@arm.com> >>> wrote: >>>> >>>> On 14/03/16 14:19, Dushyant Behl wrote: >>>>>> >>>>>> Yes, I have enabled these configuration parameters when compiling linux >>>>>> - >>>> >>>> >>>> The list of options looks good to me. I guess Linux is crashing before >>>> setting >>>> up the console. Can you apply the below to Linux and post the log here? >>> >>> >>> I applied your patch to Linux but still there is no output from the >>> kernel. >>> >>> But I have found location of the problem, I have a debugger attached >>> to the Jetson board >>> and using that I was able to find out that Linux is failing while >>> initializing the Tegra timer. >>> >>> The call stack at the time of failing is - >>> >>> - prefetchw (inline) >>> arch_spin_lock (inline) >>> do_raw_spin_lock_flags (inline) >>> __raw_spin_lock_irqssave (inline) >>> raw_spin_lock_irq_save (lock = 0xC0B746F0) >>> - of_get_parent (node = 0xA00001D3) >>> - of_get_address (dev = 0xDBBABC30, index = 0, size = 0xC0A83F30) >>> - of_address_to_resource(dev = 0xDBBABC30, index = 0, r = 0xC0A83F50) >>> - of_iomap (np = 0xDBBABC30, index = 0) >>> - tegra20_init_timer (np = 0xDBBABC30) >>> - clocksource_of_init() >>> - start_kernel() >>> >>> After this Linux jumps to floating point exception handler and then to >>> undefined instruction and fails. >> >> >> I don't know why Linux is receiving a floating point exception. However, >> DOM0 must not use the tegra timer as it doesn't support virtualization. >> >> You need to ensure that DOM0 will use the arch timer instead. Xen provides >> some facilities to blacklist a device tree node (see blacklist dev in >> arm/platforms/tegra.c). > > I have blacklisted the tegra20_timer I guess you blocked the "tegra20-timer" (which uses "-" instead of "_") right as shown in the following patch? Am I right? diff --git a/xen/arch/arm/platforms/tegra.c b/xen/arch/arm/platforms/tegra.c index 5ec9dda..8477ad1 100644 --- a/xen/arch/arm/platforms/tegra.c +++ b/xen/arch/arm/platforms/tegra.c @@ -431,6 +431,7 @@ static const struct dt_device_match tegra_blacklist_dev[] __initconst = * UART to dom0, so don't map any of them. */ DT_MATCH_COMPATIBLE("nvidia,tegra20-uart"), + DT_MATCH_COMPATIBLE("nvidia,tegra20-timer"), { /* sentinel */ }, }; Thanks and Best Regards, Meng ----------- Meng Xu PhD Student in Computer and Information Science University of Pennsylvania http://www.cis.upenn.edu/~mengxu/
On Thu, Apr 14, 2016 at 11:54 AM, Dushyant Behl <myselfdushyantbehl@gmail.com> wrote: > Hi Everyone, > > On Fri, Apr 8, 2016 at 5:57 PM, Ian Campbell <ijc@hellion.org.uk> wrote: >>> > In your patch for *Hacky* support for Jetsok-TK1 you said that you >>> > were able to run guests on >>> > Jetson-tk1 board with Xen. Can I know which kernel version you used as >>> > dom0 (and possibly domU guests)? >> >> I'm afraid I don't remember. It would probably either have been some >> current-ish upstream kernel from the time, or possibly a Debian kernel >> from around the time. So maybe something 3.16-ish? > > @Ian Thanks for the Reply. > > @Julien, Thanks a lot, your patch for GIC dtb node worked and the > linux kernel is now able to enable the arch timer. > (Although I needed to modify the code manually as the tree I'm using > is older Xen-4.6, and maybe the patch was against the latest version > of xen). > > The kernel is able to initialize itself but it fails while initializing some > nvidia devices in the boot process. I've posted the log here, Thanks to Dyshyant's help, I see the similar log as Dushyant attached in his email. > Could this also be an issue with the device tree or this is something > related to the kernel? I plan to try the L4T kernel and see if the problem still exist. But I have a quick question: With the following kernel booting log, did your dom0 boot up successfully? I mean, can you log into your dom0 now? > > - UART enabled - > - CPU 00000000 booting - > - Xen starting in Hyp mode - > - Zero BSS - > - Setting up control registers - > - Turning on paging - > - Ready - > (XEN) Checking for initrd in /chosen > (XEN) RAM: 0000000080000000 - 00000000ffefffff > (XEN) > (XEN) MODULE[0]: 0000000082000000 - 0000000082010000 Device Tree > (XEN) MODULE[1]: 0000000081000000 - 00000000815443f0 Kernel > console=hvc0 root=/dev/mmcblk0p1 rw rootwait > (XEN) RESVD[0]: 0000000082000000 - 0000000082010000 > (XEN) > (XEN) Command line: console=dtuart dtuart=serial0 dom0_mem=512M > sync_console log_lvl=all guest_loglvl=all > (XEN) Placing Xen at 0x00000000ffc00000-0x00000000ffe00000 > (XEN) Update BOOTMOD_XEN from 00000000fd000000-00000000fd0f9701 => > 00000000ffc00000-00000000ffcf9701 > (XEN) Xen heap: 00000000fa000000-00000000fe000000 (16384 pages) > (XEN) Dom heap: 507648 pages > (XEN) Domain heap initialised > (XEN) Platform: TEGRA124 > (XEN) Looking for dtuart at "s Xen 4.6-unstable > (XEN) Xen version 4.6-unstable (root@) (arm-linux-gnueabihf-gcc > (Ubuntu/Linaro 4.7.3-11ubuntu1) 4.7.3) debug=y Mon Apr 11 09:20:25 UTC > 2016 > (XEN) Latest ChangeSet: > (XEN) Console output is synchronous. > (XEN) Processor: 413fc0f3: "ARM Limited", variant: 0x3, part 0xc0f, rev 0x3 > (XEN) 32-bit Execution: > (XEN) Processor Features: 00001131:00011011 > (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle > (XEN) Extensions: GenericTimer Security > (XEN) Debug Features: 02010555 > (XEN) Auxiliary Features: 00000000 > (XEN) Memory Model Features: 10201105 40000000 01240000 02102211 > (XEN) ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000 > (XEN) Using PSCI-0.1 for SMP bringup > (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 12000 KHz > (XEN) GICv2 initialization: > (XEN) gic_dist_addr=0000000050041000 > (XEN) gic_cpu_addr=0000000050042000 > (XEN) gic_hyp_addr=0000000050044000 > (XEN) gic_vcpu_addr=0000000050046000 > (XEN) gic_maintenance_irq=25 > (XEN) GICv2: 192 lines, 4 cpus, secure (IID 0000043b). > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) I/O virtualisation disabled > (XEN) Allocated console ring of 32 KiB. > (XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0 > (XEN) Bringing up CPU1 > - CPU 00000001 booting - > - Xen starting in Hyp mode - > - Setting up control registers - > - Turning on paging - > - Ready - > (XEN) CPU 1 booted. > (XEN) Bringing up CPU2 > - CPU 00000002 booting - > - Xen starting in Hyp mode - > - Setting up control registers - > - Turning on paging - > - Ready - > (XEN) CPU 2 booted. > (XEN) Bringing up CPU3 > - CPU 00000003 booting - > - Xen starting in Hyp mode - > - Setting up control registers - > - Turning on paging - > - Ready - > (XEN) CPU 3 booted. > (XEN) Brought up 4 CPUs > (XEN) P2M: 40-bit IPA > (XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558 > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Loading kernel from boot module @ 0000000081000000 > (XEN) zImage: no appended dtb > (XEN) zImage32 Probe successful > (XEN) Allocating 1:1 mappings totalling 512MB for dom0: > (XEN) BANK[0] 0x000000a0000000-0x000000c0000000 (512MB) > (XEN) Additional MMIO 40000-40040 (IRAM) > (XEN) Additional MMIO 54200-54240 (Display A) > (XEN) Additional MMIO 54240-54280 (Display B) > (XEN) Additional MMIO 6000f-60010 (EXCEPTION VECTORS) > (XEN) Additional MMIO 6000c-6000d (SYSREG) > (XEN) Additional MMIO 1000-1001 (PCI CFG0) > (XEN) Additional MMIO 1001-1002 (PCI CFG1) > (XEN) Additional MMIO 12000-12010 (PCI IO) > (XEN) Additional MMIO 13000-20000 (PCI MEM) > (XEN) Additional MMIO 20000-40000 (PCI MEM (PREFETCH)) > (XEN) Additional IRQ 105 (DISPLAY) > (XEN) TEGRA: Routing IRQ105 to dom0, ICTLR2, mask 0x000200 > (XEN) Additional IRQ 106 (DISPLAY B) > (XEN) TEGRA: Routing IRQ106 to dom0, ICTLR2, mask 0x000400 > (XEN) Loading zImage from 0000000081000000 to 00000000a7a00000-00000000a7f443f0 > (XEN) Allocating PPI 16 for event channel interrupt > (XEN) Loading dom0 DTB to 0x00000000a8000000-0x00000000a800f1d0 > (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs > (XEN) ....done. > (XEN) Initial low memory virq threshold set at 0x4000 pages. > (XEN) Std. Loglevel: All > (XEN) Guest Loglevel: All > (XEN) ********************************************** > (XEN) ******* WARNING: CONSOLE OUTPUT IS SYNCHRONOUS > (XEN) ******* This option is intended to aid debugging of Xen by ensuring > (XEN) ******* that all output is synchronously delivered on the serial line. > (XEN) ******* However it can introduce SIGNIFICANT latencies and affect > (XEN) ******* timekeeping. It is NOT recommended for production use! > (XEN) ********************************************** > (XEN) 3... 2... 1... > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch > input to Xen) > (XEN) Freed 272kB init memory. > (XEN) DOM0: Uncompressing Linux... done, booting the kernel. > [ 0.000000] Booting Linux on physical CPU 0x0 > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Initializing cgroup subsys cpuacct > [ 0.000000] Linux version 4.1.0-196898-g2e68ed9-dirty > (root@ubuntu-server) (gcc version 4.7.3 (Ubuntu/Linaro > 4.7.3-11ubuntu1) ) #3 SMP PREEMPT Wed Apr 13 08:28:23 UTC 2016 > [ 0.000000] CPU: ARMv7 Processor [413fc0f3] revision 3 (ARMv7), cr=30c5387d > [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache > [ 0.000000] Machine model: NVIDIA Tegra124 Jetson TK1 > [ 0.000000] cma: Reserved 64 MiB at 0x00000000bc000000 > [ 0.000000] Forcing write-allocate cache policy for SMP > [ 0.000000] Memory policy: Data cache writealloc > [ 0.000000] psci: probing for conduit method from DT. > [ 0.000000] psci: PSCIv0.2 detected in firmware. > [ 0.000000] psci: Using standard PSCI v0.2 function IDs > [ 0.000000] PERCPU: Embedded 12 pages/cpu @dbb77000 s19712 r8192 > d21248 u49152 > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. > Total pages: 130048 > [ 0.000000] Kernel command line: console=hvc0 root=/dev/mmcblk0p1 rw rootwait > [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) > [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > [ 0.000000] Memory: 441884K/524288K available (7657K kernel code, > 634K rwdata, 2584K rodata, 484K init, 383K bss, 16868K reserved, > 65536K cma-reserved, 0K highmem) > [ 0.000000] Virtual kernel memory layout: > [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) > [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) > [ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) > [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) > [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) > [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) > [ 0.000000] .text : 0xc0008000 - 0xc0a08c10 (10244 kB) > [ 0.000000] .init : 0xc0a09000 - 0xc0a82000 ( 484 kB) > [ 0.000000] .data : 0xc0a82000 - 0xc0b20bec ( 635 kB) > [ 0.000000] .bss : 0xc0b23000 - 0xc0b82ea0 ( 384 kB) > [ 0.000000] Preemptible hierarchical RCU implementation. > [ 0.000000] Build-time adjustment of leaf fanout to 32. > [ 0.000000] NR_IRQS:16 nr_irqs:16 16 > [ 0.000000] /interrupt-controller@60004000: 160 interrupts > forwarded to /interrupt-controller > [ 0.000000] L2C: failed to init: -19 > [ 0.000000] Architected cp15 timer(s) running at 12.00MHz (virt). > [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff > max_cycles: 0x2c47f4ee7, max_idle_ns: 440795202497 ns > [ 0.000005] sched_clock: 56 bits at 12MHz, resolution 83ns, wraps > every 4398046511096ns > [ 0.000018] Switching to timer-based delay loop, resolution 83ns > [ 0.000500] Console: colour dummy device 80x30 > [ 0.000521] Calibrating delay loop (skipped), value calculated > using timer frequency.. 24.00 BogoMIPS (lpj=120000) > [ 0.000536] pid_max: default: 32768 minimum: 301 > [ 0.000948] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) > [ 0.000959] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) > [ 0.002350] Initializing cgroup subsys freezer > [ 0.002376] Initializing cgroup subsys debug > [ 0.002431] CPU: Testing write buffer coherency: ok > [ 0.002752] /cpus/cpu@0 missing clock-frequency property > [ 0.002794] /cpus/cpu@1 missing clock-frequency property > [ 0.002835] /cpus/cpu@2 missing clock-frequency property > [ 0.002877] /cpus/cpu@3 missing clock-frequency property > [ 0.002890] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 > [ 0.003106] Xen 4.6 support found, events_irq=19 > gnttab_frame=0x0000000068000000 > [ 0.003265] xen:grant_table: Grant tables using version 1 layout > [ 0.003313] Grant table initialized > [ 0.003378] xen:events: Using FIFO-based ABI > [ 0.003398] Xen: initializing cpu0 > [ 0.003496] Setting up static identity map for 0xa0008480 - 0xa0008518 > [ 0.020405] Tegra Revision: A01 SKU: 129 CPU Process: 1 Core Process: 1 > [ 0.030786] Xen: initializing cpu1 > [ 0.030840] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 > [ 0.040798] Xen: initializing cpu2 > [ 0.040851] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 > [ 0.050839] Xen: initializing cpu3 > [ 0.050890] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 > [ 0.051037] Brought up 4 CPUs > [ 0.051063] SMP: Total of 4 processors activated (96.00 BogoMIPS). > [ 0.051071] CPU: All CPU(s) started in SVC mode. > [ 0.052162] devtmpfs: initialized > [ 0.100284] VFP support v0.3: implementor 41 architecture 4 part 30 > variant f rev 0 > [ 0.101016] clocksource: jiffies: mask: 0xffffffff max_cycles: > 0xffffffff, max_idle_ns: 19112604462750000 ns > [ 0.103189] pinctrl core: initialized pinctrl subsystem > [ 0.105124] NET: Registered protocol family 16 > [ 0.106377] DMA: preallocated 256 KiB pool for atomic coherent allocations > [ 0.108915] xen:swiotlb_xen: Warning: only able to allocate 4 MB > for software IO TLB > [ 0.110050] software IO TLB [mem 0xbac00000-0xbb000000] (4MB) > mapped at [dac00000-daffffff] > [ 0.133440] hw-breakpoint: Failed to enable monitor mode on CPU 1. > [ 0.183494] xen:balloon: Initialising balloon driver > [ 0.184060] xen_balloon: Initialising balloon driver > [ 0.187333] +USB0_VBUS_SW: Failed to request enable GPIO108: -517 > [ 0.187556] reg-fixed-voltage regulators:regulator@7: Failed to > register regulator: -517 > [ 0.188011] +5V_USB_HS: Failed to request enable GPIO109: -517 > [ 0.188224] reg-fixed-voltage regulators:regulator@8: Failed to > register regulator: -517 > [ 0.188785] +1.05V_RUN_AVDD_HDMI_PLL: Failed to request enable GPIO63: -517 > [ 0.188995] reg-fixed-voltage regulators:regulator@11: Failed to > register regulator: -517 > [ 0.189447] +5V_HDMI_CON: Failed to request enable GPIO86: -517 > [ 0.189655] reg-fixed-voltage regulators:regulator@12: Failed to > register regulator: -517 > [ 0.190105] +5V_SATA: Failed to request enable GPIO242: -517 > [ 0.190352] reg-fixed-voltage regulators:regulator@13: Failed to > register regulator: -517 > [ 0.190806] +12V_SATA: Failed to request enable GPIO242: -517 > [ 0.191013] reg-fixed-voltage regulators:regulator@14: Failed to > register regulator: -517 > [ 0.192568] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 32 > [ 0.192786] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 36 > [ 0.192994] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 40 > [ 0.193217] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 42 > [ 0.193467] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 44 > [ 0.193673] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x40201000, IAS 48 > [ 0.193892] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 32 > [ 0.194553] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 36 > [ 0.195292] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 40 > [ 0.195949] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 42 > [ 0.196604] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 44 > [ 0.197262] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x02004000, IAS 48 > [ 0.197974] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 32 > [ 0.200524] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 36 > [ 0.203036] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 40 > [ 0.205604] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 42 > [ 0.208285] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 44 > [ 0.210797] arm-lpae io-pgtable: selftest: pgsize_bitmap 0x20010000, IAS 48 > [ 0.213295] arm-lpae io-pgtable: selftest: completed with 18 PASS 0 FAIL > [ 0.214020] vgaarb: loaded > [ 0.215731] SCSI subsystem initialized > [ 0.216928] usbcore: registered new interface driver usbfs > [ 0.217108] usbcore: registered new interface driver hub > [ 0.217316] usbcore: registered new device driver usb > [ 0.221769] Linux video capture interface: v2.00 > [ 0.221900] pps_core: LinuxPPS API ver. 1 registered > [ 0.221908] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 > Rodolfo Giometti <giometti@linux.it> > [ 0.221980] PTP clock support registered > [ 0.223885] Advanced Linux Sound Architecture Driver Initialized. > [ 0.225412] Bluetooth: Core ver 2.20 > [ 0.225493] NET: Registered protocol family 31 > [ 0.225502] Bluetooth: HCI device and connection manager initialized > [ 0.225533] Bluetooth: HCI socket layer initialized > [ 0.225555] Bluetooth: L2CAP socket layer initialized > [ 0.225611] Bluetooth: SCO socket layer initialized > [ 0.226236] cfg80211: Calling CRDA to update world regulatory domain > [ 0.227195] clocksource: Switched to clocksource arch_sys_counter > [ 0.362983] NET: Registered protocol family 2 > [ 0.364477] TCP established hash table entries: 4096 (order: 2, 16384 bytes) > [ 0.364539] TCP bind hash table entries: 4096 (order: 3, 32768 bytes) > [ 0.364637] TCP: Hash tables configured (established 4096 bind 4096) > [ 0.364907] UDP hash table entries: 256 (order: 1, 8192 bytes) > [ 0.364935] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) > [ 0.365428] NET: Registered protocol family 1 > [ 0.366382] RPC: Registered named UNIX socket transport module. > [ 0.366392] RPC: Registered udp transport module. > [ 0.366399] RPC: Registered tcp transport module. > [ 0.366406] RPC: Registered tcp NFSv4.1 backchannel transport module. > [ 0.370824] futex hash table entries: 1024 (order: 4, 65536 bytes) > [ 0.374618] squashfs: version 4.0 (2009/01/31) Phillip Lougher > [ 0.383547] io scheduler noop registered (default) > [ 0.394250] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration > [ 0.394303] tegra-pcie 1003000.pcie-controller: Failed to get > supply 'avddio-pex': -517 > [ 0.406173] tegra-apbdma 60020000.dma: Tegra20 APB DMA driver > register 32 channels > [ 0.406682] tegra-pmc 7000e400.pmc: emergency thermal reset enabled > [ 0.408157] xen:xen_evtchn: Event-channel device installed > [ 1.317385] console [hvc0] enabled > [ 1.320937] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled > [ 1.333011] [drm] Initialized drm 1.1.0 20060810 > [ 1.368145] tegra-hdmi 54280000.hdmi: failed to get HDMI regulator > [ 1.388139] loop: module loaded > [ 1.390403] at24 0-0056: 256 byte 24c02 EEPROM, writable, 8 bytes/write > [ 2.387235] tegra-i2c 7000d000.i2c: i2c transfer timed out On my Jetson TK1 board, it starts to fail at this as well, although the log is not exactly the same. I guess that's because we may use different .config file for the same linux repo.. > [ 2.390845] as3722 4-0040: ASIC_ID1 read failed: -110 > [ 2.396044] as3722: probe of 4-0040 failed with error -110 > [ 2.402569] tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517 > [ 2.408180] tegra-ahci 70027000.sata: Failed to get regulators > [ 3.387251] cfg80211: Calling CRDA to update world regulatory domain > [ 3.417234] ------------[ cut here ]------------ > [ 3.419967] WARNING: CPU: 1 PID: 1 at > drivers/spi/spi-tegra114.c:838 > tegra_spi_transfer_one_message+0x410/0x438() > [ 3.430302] Modules linked in: > [ 3.433392] CPU: 1 PID: 1 Comm: swapper/0 Not tainted > 4.1.0-196898-g2e68ed9-dirty #3 > [ 3.441203] Hardware name: NVIDIA Tegra SoC (Flattened Device Tree) > [ 3.447560] [<c00177d8>] (unwind_backtrace) from [<c0013040>] > (show_stack+0x10/0x14) > [ 3.455327] [<c0013040>] (show_stack) from [<c073b7e8>] > (dump_stack+0x84/0xd0) > [ 3.462622] [<c073b7e8>] (dump_stack) from [<c0028b84>] > (warn_slowpath_common+0x78/0xb4) > [ 3.470766] [<c0028b84>] (warn_slowpath_common) from [<c0028bdc>] > (warn_slowpath_null+0x1c/0x24) > [ 3.479606] [<c0028bdc>] (warn_slowpath_null) from [<c03ed068>] > (tegra_spi_transfer_one_message+0x410/0x438) > [ 3.489485] [<c03ed068>] (tegra_spi_transfer_one_message) from > [<c03e9d68>] (__spi_pump_messages+0x36c/0x674) > [ 3.499462] [<c03e9d68>] (__spi_pump_messages) from [<c03ea194>] > (__spi_sync+0x124/0x1a8) > [ 3.507701] [<c03ea194>] (__spi_sync) from [<c03ea2ec>] > (spi_write_then_read+0xc4/0x174) > [ 3.515814] [<c03ea2ec>] (spi_write_then_read) from [<c03e6904>] > (m25p80_read_reg+0x34/0x64) > [ 3.524321] [<c03e6904>] (m25p80_read_reg) from [<c03e6fec>] > (spi_nor_read_id+0x20/0xa8) > [ 3.532483] [<c03e6fec>] (spi_nor_read_id) from [<c03e7ac8>] > (spi_nor_scan+0x2a8/0x80c) > [ 3.540524] [<c03e7ac8>] (spi_nor_scan) from [<c03e6840>] > (m25p_probe+0xb0/0x140) > [ 3.548065] [<c03e6840>] (m25p_probe) from [<c03e96c8>] > (spi_drv_probe+0x5c/0x74) > [ 3.555600] [<c03e96c8>] (spi_drv_probe) from [<c037db44>] > (driver_probe_device+0x1c8/0x26c) > [ 3.564106] [<c037db44>] (driver_probe_device) from [<c037c244>] > (bus_for_each_drv+0x44/0x8c) > [ 3.572684] [<c037c244>] (bus_for_each_drv) from [<c037d904>] > (__device_attach+0x88/0xd8) > [ 3.580917] [<c037d904>] (__device_attach) from [<c037d0bc>] > (bus_probe_device+0x84/0x8c) > [ 3.589149] [<c037d0bc>] (bus_probe_device) from [<c037b5fc>] > (device_add+0x33c/0x524) > [ 3.597110] [<c037b5fc>] (device_add) from [<c03e9540>] > (spi_add_device+0x88/0x130) > [ 3.604835] [<c03e9540>] (spi_add_device) from [<c03eab64>] > (of_register_spi_device+0x208/0x2f8) > [ 3.613676] [<c03eab64>] (of_register_spi_device) from [<c03eb034>] > (spi_register_master+0x214/0x444) > [ 3.622950] [<c03eb034>] (spi_register_master) from [<c03eb290>] > (devm_spi_register_master+0x2c/0x68) > [ 3.632222] [<c03eb290>] (devm_spi_register_master) from > [<c03ebdc8>] (tegra_spi_probe+0x29c/0x350) > [ 3.641322] [<c03ebdc8>] (tegra_spi_probe) from [<c037f230>] > (platform_drv_probe+0x48/0xa4) > [ 3.649728] [<c037f230>] (platform_drv_probe) from [<c037db44>] > (driver_probe_device+0x1c8/0x26c) > [ 3.658671] [<c037db44>] (driver_probe_device) from [<c037dc74>] > (__driver_attach+0x8c/0x90) > [ 3.667135] [<c037dc74>] (__driver_attach) from [<c037c2e0>] > (bus_for_each_dev+0x54/0x88) > [ 3.675382] [<c037c2e0>] (bus_for_each_dev) from [<c037d2a0>] > (bus_add_driver+0xe8/0x1f4) > [ 3.683622] [<c037d2a0>] (bus_add_driver) from [<c037e6a0>] > (driver_register+0x78/0xf4) > [ 3.691693] [<c037e6a0>] (driver_register) from [<c00096c4>] > (do_one_initcall+0x80/0x1d0) > [ 3.699908] [<c00096c4>] (do_one_initcall) from [<c0a09dc8>] > (kernel_init_freeable+0x110/0x1dc) > [ 3.708663] [<c0a09dc8>] (kernel_init_freeable) from [<c0736770>] > (kernel_init+0x8/0xec) > [ 3.716795] [<c0736770>] (kernel_init) from [<c000fde8>] > (ret_from_fork+0x14/0x2c) > [ 3.724439] ---[ end trace e92698c5376bfefb ]--- > [ 3.729108] spi-tegra114 7000da00.spi: spi trasfer timeout, err 0 > [ 3.735272] spi_master spi32765: failed to transfer one message from queue > [ 3.742195] m25p80 spi32765.0: error -5 reading 9f > [ 3.747049] m25p80: probe of spi32765.0 failed with error -5 > [ 3.754768] CAN device driver interface > [ 3.756829] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k > [ 3.763827] igb: Copyright (c) 2007-2014 Intel Corporation. > [ 3.769830] xen_netfront: Initialising Xen virtual ethernet driver > [ 3.776009] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB > Ethernet driver > [ 3.783289] usbcore: registered new interface driver pegasus > [ 3.789058] usbcore: registered new interface driver asix > [ 3.794455] usbcore: registered new interface driver ax88179_178a > [ 3.800637] usbcore: registered new interface driver cdc_ether > [ 3.806555] usbcore: registered new interface driver smsc75xx > [ 3.812372] usbcore: registered new interface driver smsc95xx > [ 3.818129] usbcore: registered new interface driver net1080 > [ 3.823837] usbcore: registered new interface driver cdc_subset > [ 3.829849] usbcore: registered new interface driver zaurus > [ 3.835520] usbcore: registered new interface driver cdc_ncm > [ 3.841358] tegra-phy 7d004000.usb-phy: no vbus regulator > [ 3.847023] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver > [ 3.853106] ehci-pci: EHCI PCI platform driver > [ 3.857735] tegra-ehci: Tegra EHCI driver > [ 3.862029] tegra-ehci 7d004000.usb: EHCI Host Controller > [ 3.867164] tegra-ehci 7d004000.usb: new USB bus registered, > assigned bus number 1 > [ 3.875088] tegra-ehci 7d004000.usb: irq 342, io mem 0x7d004000 > [ 3.897244] tegra-ehci 7d004000.usb: USB 2.0 started, EHCI 1.10 > [ 3.903016] hub 1-0:1.0: USB hub found > [ 3.905146] hub 1-0:1.0: 1 port detected > [ 3.910543] usbcore: registered new interface driver cdc_acm > [ 3.914781] cdc_acm: USB Abstract Control Model driver for USB > modems and ISDN adapters > [ 3.923002] usbcore: registered new interface driver cdc_wdm > [ 3.928802] usbcore: registered new interface driver usb-storage > [ 3.935427] mousedev: PS/2 mouse device common for all mice > [ 3.943355] tegra_rtc 7000e000.rtc: rtc core: registered 7000e000.rtc as rtc1 > [ 3.948720] tegra_rtc 7000e000.rtc: Tegra internal Real Time Clock > [ 3.955257] i2c /dev entries driver > [ 3.960738] usbcore: registered new interface driver uvcvideo > [ 3.964583] USB Video Class driver (1.1.1) > [ 3.968790] gspca_main: v2.14.0 registered > [ 3.973727] 0-004c supply vcc not found, using dummy regulator > [ 4.977235] tegra-i2c 7000c000.i2c: i2c transfer timed out > [ 4.980846] lm90 0-004c: Register 0x4 read failed (-110) > [ 4.986196] lm90 0-004c: Failed to read convrate register! > [ 5.987234] tegra-i2c 7000c000.i2c: i2c transfer timed out > [ 6.547246] cfg80211: Calling CRDA to update world regulatory domain > [ 6.987237] tegra-i2c 7000c000.i2c: i2c transfer timed out > [ 6.990842] lm90 0-004c: Register 0x3 read failed (-110) > [ 6.996198] lm90 0-004c: Initialization failed! > [ 7.002041] sdhci: Secure Digital Host Controller Interface driver > [ 7.007027] sdhci: Copyright(c) Pierre Ossman > [ 7.011481] sdhci-pltfm: SDHCI platform and OF driver helper > [ 7.017580] sdhci-tegra 700b0400.sdhci: Got CD GPIO > [ 7.022128] sdhci-tegra 700b0400.sdhci: Got WP GPIO > [ 7.027105] mmc0: Unknown controller version (3). You may > experience problems. > [ 7.034491] sdhci-tegra 700b0400.sdhci: No vmmc regulator found > [ 7.040550] mmc0: Unknown controller version (3). You may > experience problems. > [ 7.047721] sdhci-tegra 700b0600.sdhci: No vmmc regulator found > [ 7.053570] sdhci-tegra 700b0600.sdhci: No vqmmc regulator found > [ 7.059654] mmc0: Invalid maximum block size, assuming 512 bytes > [ 7.117253] mmc0: SDHCI controller on 700b0600.sdhci > [700b0600.sdhci] using ADMA 64-bit > [ 7.124468] usbcore: registered new interface driver usbhid > [ 7.128999] usbhid: USB HID core driver > [ 8.537237] tegra-i2c 7000c000.i2c: i2c transfer timed out > [ 8.540847] rt5640 0-001c: Device with ID register c0af9d34 is not rt5640/39 > [ 8.551341] tegra30-i2s 70301100.i2s: DMA channels sourced from > device 70300000.ahub > [ 8.557838] tegra-snd-rt5640 sound: ASoC: CODEC DAI rt5640-aif1 not > registered > [ 8.564464] tegra-snd-rt5640 sound: snd_soc_register_card failed (-517) > [ 8.573237] NET: Registered protocol family 10 > [ 8.577517] mip6: Mobile IPv6 > [ 8.578820] sit: IPv6 over IPv4 tunneling driver > [ 8.586541] NET: Registered protocol family 17 > [ 8.589192] NET: Registered protocol family 15 > [ 8.593603] can: controller area network core (rev 20120528 abi 9) > [ 8.600037] NET: Registered protocol family 29 > [ 8.604351] can: raw protocol (rev 20120528) > [ 8.608697] can: broadcast manager protocol (rev 20120528 t) > [ 8.614418] can: netlink gateway (rev 20130117) max_hops=1 > [ 8.620197] Bluetooth: RFCOMM socket layer initialized > [ 8.625156] Bluetooth: RFCOMM ver 1.11 > [ 8.628991] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > [ 8.634341] Bluetooth: BNEP socket layer initialized > [ 8.639374] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 > [ 8.645349] Bluetooth: HIDP socket layer initialized > [ 8.650678] Registering SWP/SWPB emulation handler > [ 8.661218] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration > [ 8.665886] tegra-pcie 1003000.pcie-controller: Failed to get > supply 'avddio-pex': -517 > [ 8.674354] +5V_SYS: supplied by +VDD_MUX > [ 8.678090] +5V_HDMI_CON: supplied by +5V_SYS > [ 8.682576] reg-fixed-voltage regulators:regulator@11: Failed to > resolve vin-supply for +1.05V_RUN_AVDD_HDMI_PLL > [ 8.692649] tegra-hdmi 54280000.hdmi: failed to get PLL regulator > [ 8.699325] tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517 > [ 8.705454] tegra-ahci 70027000.sata: Failed to get regulators > [ 8.711824] +5V_USB_HS: supplied by +5V_SYS > [ 8.716182] tegra-ehci 7d008000.usb: EHCI Host Controller > [ 8.721165] tegra-ehci 7d008000.usb: new USB bus registered, > assigned bus number 2 > [ 8.729155] tegra-ehci 7d008000.usb: irq 343, io mem 0x7d008000 > [ 8.747246] tegra-ehci 7d008000.usb: USB 2.0 started, EHCI 1.10 > [ 8.753009] hub 2-0:1.0: USB hub found > [ 8.755139] hub 2-0:1.0: 1 port detected > [ 8.760236] sdhci-tegra 700b0400.sdhci: Got CD GPIO > [ 8.764021] sdhci-tegra 700b0400.sdhci: Got WP GPIO > [ 8.769021] mmc1: Unknown controller version (3). You may > experience problems. > [ 8.776370] sdhci-tegra 700b0400.sdhci: No vmmc regulator found > [ 8.782726] tegra-snd-rt5640 sound: ASoC: CODEC DAI rt5640-aif1 not > registered > [ 8.789521] tegra-snd-rt5640 sound: snd_soc_register_card failed (-517) > [ 8.796977] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration > [ 8.802818] tegra-pcie 1003000.pcie-controller: Failed to get > supply 'avddio-pex': -517 > [ 8.811291] reg-fixed-voltage regulators:regulator@11: Failed to > resolve vin-supply for +1.05V_RUN_AVDD_HDMI_PLL > [ 8.821048] tegra-hdmi 54280000.hdmi: failed to get PLL regulator > [ 8.827691] tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517 > [ 8.833857] tegra-ahci 70027000.sata: Failed to get regulators > [ 8.840805] input: gpio-keys as /devices/soc0/gpio-keys/input/input0 > [ 8.846820] hctosys: unable to open rtc device (rtc0) > [ 8.847331] sdhci-tegra 700b0400.sdhci: Got CD GPIO > [ 8.847369] sdhci-tegra 700b0400.sdhci: Got WP GPIO > [ 8.847471] mmc1: Unknown controller version (3). You may > experience problems. > [ 8.851403] sdhci-tegra 700b0400.sdhci: No vmmc regulator found > [ 8.852328] tegra-snd-rt5640 sound: ASoC: CODEC DAI rt5640-aif1 not > registered > [ 8.852340] tegra-snd-rt5640 sound: snd_soc_register_card failed (-517) > [ 8.854009] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration > [ 8.854062] tegra-pcie 1003000.pcie-controller: Failed to get > supply 'avddio-pex': -517 > [ 8.855019] reg-fixed-voltage regulators:regulator@11: Failed to > resolve vin-supply for +1.05V_RUN_AVDD_HDMI_PLL > [ 8.855030] tegra-hdmi 54280000.hdmi: failed to get PLL regulator > [ 8.856050] tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517 > [ 8.856059] tegra-ahci 70027000.sata: Failed to get regulators > [ 8.951051] +12V_SATA: disabling > [ 8.952391] +5V_SATA: disabling > [ 8.955596] +5V_HDMI_CON: disabling > [ 8.959166] +1.05V_RUN_AVDD_HDMI_PLL: disabling > [ 8.963742] +USB0_VBUS_SW: disabling > [ 8.967400] +3.3V_AVDD_HDMI_ > The last several dom0 log messages are: [ 5.398512] sdhci: Copyright(c) Pierre Ossman 6sdhci-pltfm: SDHCI platform and OF driver helper [ 5.398574] sdhci-pltfm: SDHCI platform and OF driver helper sdhci-tegra 700b0400.sdhci: Got CD GPIO [ 5.399032] sdhci-tegra 700b0400.sdhci: Got CD GPIO sdhci-tegra 700b0400.sdhci: Got WP GPIO [ 5.399109] sdhci-tegra 700b0400.sdhci: Got WP GPIO 3mmc0: Unknown controller version (3). You may experience problems. [ 5.399231] mmc0: Unknown controller version (3). You may experience problems. sdhci-tegra 700b0400.sdhci: No vmmc regulator found [ 5.399443] sdhci-tegra 700b0400.sdhci: No vmmc regulator found 3mmc0: Unknown controller version (3). You may experience problems. [ 5.399731] mmc0: Unknown controller version (3). You may experience problems. sdhci-tegra 700b0600.sdhci: No vmmc regulator found [ 5.399868] sdhci-tegra 700b0600.sdhci: No vmmc regulator found sdhci-tegra 700b0600.sdhci: No vqmmc regulator found [ 5.399931] sdhci-tegra 700b0600.sdhci: No vqmmc regulator found 4mmc0: Invalid maximum block size, assuming 512 bytes [ 5.399993] mmc0: Invalid maximum block size, assuming 512 bytes 6mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit [ 5.446794] mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit 6usbcore: registered new interface driver usbhid [ 5.448020] usbcore: registered new interface driver usbhid 6usbhid: USB HID core driver [ 5.448075] usbhid: USB HID core driver 6cfg80211: Calling CRDA to update world regulatory domain [ 6.536872] cfg80211: Calling CRDA to update world regulatory domain tegra-hda 70030000.hda: azx_get_response timeout, switching to polling mode: last cmd=0x300f0001 [ 8.526885] tegra-hda 70030000.hda: azx_get_response timeout, switching to polling mode: last cmd=0x300f0001 6input: tegra-hda HDMI/DP,pcm=3 as /devices/soc0/70030000.hda/sound/card0/input0 [ 8.968688] input: tegra-hda HDMI/DP,pcm=3 as /devices/soc0/70030000.hda/sound/card0/input0 6cfg80211: Calling CRDA to update world regulatory domain [ 9.696855] cfg80211: Calling CRDA to update world regulatory domain tegra-i2c 7000c000.i2c: ---- From Dushyant's log, I saw the "tegra-i2c 7000c000.i2c:" will finally time out. However, in my case, I didn't see the time out happens. Thanks and Best Regards, Meng ----------- Meng Xu PhD Student in Computer and Information Science University of Pennsylvania http://www.cis.upenn.edu/~mengxu/
On Sun, May 15, 2016 at 12:07 AM, Meng Xu <mengxu@cis.upenn.edu> wrote: >>> some facilities to blacklist a device tree node (see blacklist dev in >>> arm/platforms/tegra.c). >> >> I have blacklisted the tegra20_timer > > I guess you blocked the "tegra20-timer" (which uses "-" instead of > "_") right as shown in the following patch? Am I right? That was a typo in the email but I had blocked the correct timer, without blacklisting the tegra timer the linux only boots to a few steps and fails, in my next bootlog linux booted a lot further and then failed due to some other reason.
On Sun, May 15, 2016 at 12:13 AM, Meng Xu <mengxu@cis.upenn.edu> wrote: > But I have a quick question: > With the following kernel booting log, did your dom0 boot up successfully? > I mean, can you log into your dom0 now? No, I was not able to boot the dom0 kernel successfully hence I was not able to login into the dom0 linux. Thanks, Dushyant
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c index c963ba5..6f3b85b 100644 --- a/kernel/printk/printk.c +++ b/kernel/printk/printk.c @@ -1657,6 +1657,8 @@ static size_t cont_print_text(char *text, size_t size) return textlen; } +#include <xen/hvc-console.h> + asmlinkage int vprintk_emit(int facility, int level, const char *dict, size_t dictlen, const char *fmt, va_list args) @@ -1724,6 +1726,7 @@ asmlinkage int vprintk_emit(int facility, int level, * prefix which might be passed-in as a parameter. */ text_len = vscnprintf(text, sizeof(textbuf), fmt, args); + xen_raw_console_write(text); /* mark and strip a trailing newline */ if (text_len && text[text_len-1] == '\n') {
Hi Dushyant, On 14/03/16 14:19, Dushyant Behl wrote: > > Yes, I have enabled these configuration parameters when compiling linux - The list of options looks good to me. I guess Linux is crashing before setting up the console. Can you apply the below to Linux and post the log here? Regards,