* Question about running Xen on NVIDIA Jetson-TK1
@ 2016-05-15 19:35 Meng Xu
2016-05-16 11:33 ` Julien Grall
0 siblings, 1 reply; 12+ messages in thread
From: Meng Xu @ 2016-05-15 19:35 UTC (permalink / raw)
To: xen-devel, Julien Grall, Ian Campbell; +Cc: Dushyant K Behl
[-- Attachment #1: Type: text/plain, Size: 4286 bytes --]
Hi Julien and Ian,
I'm trying to run Xen on NVIDIA Jetson TK1 board. (Right now, Xen does
not support the Jetson board officially. But I'm thinking it may be
very interesting and useful to see it happens, since it has GPU inside
which is quite popular in automotive.)
Now I encountered some problem to boot dom0 in Xen environment. I want
to debug the issues and maybe fix the issues, but I'm not so sure how
I should debug the issue more efficiently. I really appreciate it if
you advise me a little bit about the method of how to fix the issue.
:-)
---Below is the details----
I noticed the Dushyant from IBM also tried to run Xen on the Jetson
board. (http://www.gossamer-threads.com/lists/xen/devel/422519). I
used the same Linux kernel (Jan Kiszka's development tree -
http://git.kiszka.org/linux.git/, branch queues/assorted) and Ian's
Xen repo. with the hack for Jetson board. I can see the dom0 kernel
can boot to some extend and then "stall/spin" before the dom0 kernel
fully boot up.
In order to figure out the possible issue, I boot the exact same Linux
kernel in native environment on one CPU and collected the boot log
information in [1]. I also boot the same Linux kernel as dom0 in Xen
environment and collected the boot log information in [2].
In Xen environment, dom0 hangs after the following message
[ 10.541010] NET: Registered protocol family 10
6mip6: Mobile IPv6
[ 10.542510] mi
In native environment, the kernel has the following log after initializing NET.
[ 2.934693] NET: Registered protocol family 10
[ 2.940611] mip6: Mobile IPv6
[ 2.943645] sit: IPv6 over IPv4 tunneling driver
[ 2.951303] NET: Registered protocol family 17
[ 2.955800] NET: Registered protocol family 15
[ 2.960257] can: controller area network core (rev 20120528 abi 9)
[ 2.966617] NET: Registered protocol family 29
[ 2.971098] can: raw protocol (rev 20120528)
[ 2.975384] can: broadcast manager protocol (rev 20120528 t)
[ 2.981088] can: netlink gateway (rev 20130117) max_hops=1
[ 2.986734] Bluetooth: RFCOMM socket layer initialized
[ 2.991979] Bluetooth: RFCOMM ver 1.11
[ 2.995757] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.001109] Bluetooth: BNEP socket layer initialized
[ 3.006089] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 3.012052] Bluetooth: HIDP socket layer initialized
[ 3.017894] Registering SWP/SWPB emulation handler
[ 3.029675] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration
[ 3.036586] +3.3V_SYS: supplied by +VDD_MUX
[ 3.040857] +3.3V_LP0: supplied by +3.3V_SYS
[ 3.045509] +1.35V_LP0(sd2): supplied by +5V_SYS
[ 3.050201] +1.05V_RUN_AVDD: supplied by +1.35V_LP0(sd2)
[ 3.057131] tegra-pcie 1003000.pcie-controller: probing port 0, using 2 lanes
[ 3.066479] tegra-pcie 1003000.pcie-controller: Slot present pin
change, signature: 00000008
I'm suspecting that my dom0 kernel hangs when it tries to initialize
"can: controller area network core ". However, from Dushyant's post at
http://www.gossamer-threads.com/lists/xen/devel/422519, it seems
Dushyant's dom0 kernel hangs when it tries to initialize pci_bus. (The
linux config I used may be different form Dushyant's. That could be
the reason.)
Right now, the system just hangs and has no output indicating what the
problem could be. Although there are a lot of error message before the
system hangs, I'm not that sure if I should start with solving all of
those error messages. Maybe some errors can be ignored?
My questions are:
1) Do you have suggestion on how to see more information about the
reason why the dom0 hangs?
2) Is it because the device tree is not correctly recreated by Xen?
(This is just a guess. Since dom0's linux can boot up in HYP mode in
native environment, I think dom0's kernel should be good and the
problem should be Xen?)
Thank you very much for your time and help in this question!
I really appreciate it!
[1] tk1-linux-boot-1cpu.log, the boot log information when Linux
successfully boot on 1 CPU with HYP mode.
[2] tk1-xen-linux-boot-1vcpu.log, the boot log information when Linux
tries to boot in dom0 on Xen
Best Regards,
Meng
-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
[-- Attachment #2: tk1-linux-boot-1cpu.log --]
[-- Type: application/octet-stream, Size: 71460 bytes --]
[ 0.000000] .bss : 0xc0a74000 - 0xc0ad1a94 ( 375 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Additional per-CPU info printed with stalls.
[ 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,50041000
[ 0.000000] L2C: failed to init: -19
[ 0.000009] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
[ 0.006536] clocksource: timer_us: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
[ 0.016151] Switching to timer-based delay loop, resolution 1000ns
[ 0.023591] Architected cp15 timer(s) running at 12.00MHz (phys).
[ 0.028548] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2c47f4ee7, max_idle_ns: 440795202497 ns
[ 0.039383] sched_clock: 56 bits at 12MHz, resolution 83ns, wraps every 4398046511096ns
[ 0.047437] Switching to timer-based delay loop, resolution 83ns
[ 0.053927] Console: colour dummy device 80x30
[ 0.058011] console [tty1] enabled
[ 0.061474] bootconsole [earlycon0] disabled
[ 0.065838] Calibrating delay loop (skipped), value calculated using timer frequency.. 24.00 BogoMIPS (lpj=120000)
[ 0.065870] pid_max: default: 32768 minimum: 301
[ 0.066283] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.066306] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.067714] Initializing cgroup subsys freezer
[ 0.067748] Initializing cgroup subsys debug
[ 0.067809] CPU: Testing write buffer coherency: ok
[ 0.068134] /cpus/cpu@0 missing clock-frequency property
[ 0.068180] /cpus/cpu@1 missing clock-frequency property
[ 0.068226] /cpus/cpu@2 missing clock-frequency property
[ 0.068272] /cpus/cpu@3 missing clock-frequency property
[ 0.068292] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.068520] Setting up static identity map for 0x80008440 - 0x800084d8
[ 0.089129] Tegra Revision: A01 SKU: 129 CPU Process: 1 Core Process: 1
[ 0.096703] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.106693] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.116703] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.116785] Brought up 4 CPUs
[ 0.116834] SMP: Total of 4 processors activated (96.00 BogoMIPS).
[ 0.116850] CPU: All CPU(s) started in HYP mode.
[ 0.116864] CPU: Virtualization extensions available.
[ 0.117783] devtmpfs: initialized
[ 0.167249] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[ 0.167964] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.169787] pinctrl core: initialized pinctrl subsystem
[ 0.171662] NET: Registered protocol family 16
[ 0.173425] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.196061] cpuidle: using governor ladder
[ 0.226087] cpuidle: using governor menu
[ 0.249868] No ATAGs?
[ 0.249913] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.249956] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.311698] +USB0_VBUS_SW: Failed to request enable GPIO108: -517
[ 0.311939] reg-fixed-voltage regulators:regulator@7: Failed to register regulator: -517
[ 0.312423] +5V_USB_HS: Failed to request enable GPIO109: -517
[ 0.312650] reg-fixed-voltage regulators:regulator@8: Failed to register regulator: -517
[ 0.313237] +1.05V_RUN_AVDD_HDMI_PLL: Failed to request enable GPIO63: -517
[ 0.313465] reg-fixed-voltage regulators:regulator@11: Failed to register regulator: -517
[ 0.313943] +5V_HDMI_CON: Failed to request enable GPIO86: -517
[ 0.314169] reg-fixed-voltage regulators:regulator@12: Failed to register regulator: -517
[ 0.314647] +5V_SATA: Failed to request enable GPIO242: -517
[ 0.314870] reg-fixed-voltage regulators:regulator@13: Failed to register regulator: -517
[ 0.315347] +12V_SATA: Failed to request enable GPIO242: -517
[ 0.315571] reg-fixed-voltage regulators:regulator@14: Failed to register regulator: -517
[ 0.317677] vgaarb: loaded
[ 0.319150] SCSI subsystem initialized
[ 0.319478] libata version 3.00 loaded.
[ 0.320226] usbcore: registered new interface driver usbfs
[ 0.320410] usbcore: registered new interface driver hub
[ 0.320593] usbcore: registered new device driver usb
[ 0.324886] Linux video capture interface: v2.00
[ 0.325031] pps_core: LinuxPPS API ver. 1 registered
[ 0.325054] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.325152] PTP clock support registered
[ 0.327165] Advanced Linux Sound Architecture Driver Initialized.
[ 0.328789] Bluetooth: Core ver 2.20
[ 0.328885] NET: Registered protocol family 31
[ 0.328907] Bluetooth: HCI device and connection manager initialized
[ 0.328945] Bluetooth: HCI socket layer initialized
[ 0.328981] Bluetooth: L2CAP socket layer initialized
[ 0.329052] Bluetooth: SCO socket layer initialized
[ 0.329687] cfg80211: Calling CRDA to update world regulatory domain
[ 0.331015] clocksource: Switched to clocksource arch_sys_counter
[ 0.356104] NET: Registered protocol family 2
[ 0.357273] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.357402] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.357604] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.358067] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.358127] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.358518] NET: Registered protocol family 1
[ 0.359221] RPC: Registered named UNIX socket transport module.
[ 0.359248] RPC: Registered udp transport module.
[ 0.359269] RPC: Registered tcp transport module.
[ 0.359290] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.359332] PCI: CLS 0 bytes, default 64
[ 0.364201] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.366677] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.371965] bounce: pool size: 64 pages
[ 0.372003] io scheduler noop registered (default)
[ 0.382614] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration
[ 0.382685] tegra-pcie 1003000.pcie-controller: Failed to get supply 'avddio-pex': -517
[ 0.394260] tegra-apbdma 60020000.dma: Tegra20 APB DMA driver register 32 channels
[ 0.394805] tegra-pmc 7000e400.pmc: emergency thermal reset enabled
[ 0.395033] xenfs: not registering filesystem on non-xen platform
[ 0.395676] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.399536] console [ttyS0] disabled
[ 0.399609] 70006300.serial: ttyS0 at MMIO 0x70006300 (irq = 333, base_baud = 25500000) is a Tegra
[ 1.286397] console [ttyS0] enabled
[ 1.293042] [drm] Initialized drm 1.1.0 20060810
[ 1.299227] tegra-hdmi 54280000.hdmi: failed to get HDMI regulator
[ 1.321108] loop: module loaded
[ 1.324893] at24 0-0056: 256 byte 24c02 EEPROM, writable, 8 bytes/write
[ 1.332369] as3722 4-0040: AS3722 with revision 0x1 found
[ 1.359062] +5V_SYS: supplied by +VDD_MUX
[ 1.363179] +1.05V_RUN: supplied by +5V_SYS
[ 1.367538] tegra-ahci 70027000.sata: Failed to get supply 'hvdd': -517
[ 1.374237] tegra-ahci 70027000.sata: Failed to get regulators
[ 1.383020] m25p80 spi32765.0: w25q32dw (4096 Kbytes)
[ 1.391483] CAN device driver interface
[ 1.395451] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k
[ 1.402524] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 1.408478] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[ 1.416053] usbcore: registered new interface driver pegasus
[ 1.421942] usbcore: registered new interface driver asix
[ 1.427481] usbcore: registered new interface driver ax88179_178a
[ 1.433738] usbcore: registered new interface driver cdc_ether
[ 1.439758] usbcore: registered new interface driver smsc75xx
[ 1.445721] usbcore: registered new interface driver smsc95xx
[ 1.451630] usbcore: registered new interface driver net1080
[ 1.457437] usbcore: registered new interface driver cdc_subset
[ 1.463516] usbcore: registered new interface driver zaurus
[ 1.469288] usbcore: registered new interface driver cdc_ncm
[ 1.475303] tegra-phy 7d004000.usb-phy: no vbus regulator
[ 1.481272] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.487840] ehci-pci: EHCI PCI platform driver
[ 1.492445] tegra-ehci: Tegra EHCI driver
[ 1.496827] tegra-ehci 7d004000.usb: EHCI Host Controller
[ 1.502296] tegra-ehci 7d004000.usb: new USB bus registered, assigned bus number 1
[ 1.510202] tegra-ehci 7d004000.usb: irq 349, io mem 0x7d004000
[ 1.531047] tegra-ehci 7d004000.usb: USB 2.0 started, EHCI 1.10
[ 1.538764] hub 1-0:1.0: USB hub found
[ 1.542602] hub 1-0:1.0: 1 port detected
[ 1.547942] usbcore: registered new interface driver cdc_acm
[ 1.553635] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 1.561828] usbcore: registered new interface driver cdc_wdm
[ 1.567696] usbcore: registered new interface driver usb-storage
[ 1.574567] mousedev: PS/2 mouse device common for all mice
[ 1.583865] as3722-rtc as3722-rtc: rtc core: registered as3722-rtc as rtc0
[ 1.590753] as3722-rtc as3722-rtc: RTC interrupt 368
[ 1.598955] tegra_rtc 7000e000.rtc: rtc core: registered 7000e000.rtc as rtc1
[ 1.606241] tegra_rtc 7000e000.rtc: Tegra internal Real Time Clock
[ 1.612910] i2c /dev entries driver
[ 1.618814] usbcore: registered new interface driver uvcvideo
[ 1.624592] USB Video Class driver (1.1.1)
[ 1.628707] gspca_main: v2.14.0 registered
[ 1.633708] 0-004c supply vcc not found, using dummy regulator
[ 1.643232] sdhci: Secure Digital Host Controller Interface driver
[ 1.649418] sdhci: Copyright(c) Pierre Ossman
[ 1.653807] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.659789] sdhci-tegra 700b0400.sdhci: Got CD GPIO
[ 1.664716] sdhci-tegra 700b0400.sdhci: Got WP GPIO
[ 1.669654] mmc0: Unknown controller version (3). You may experience problems.
[ 1.677017] as3722-regulator as3722-regulator: Failed to resolve vin-ldo1-6-supply for as3722-ldo6
[ 1.686011] sdhci-tegra 700b0400.sdhci: No vmmc regulator found
[ 1.692176] mmc0: Unknown controller version (3). You may experience problems.
[ 1.699475] sdhci-tegra 700b0600.sdhci: No vmmc regulator found
[ 1.705451] sdhci-tegra 700b0600.sdhci: No vqmmc regulator found
[ 1.711519] mmc0: Invalid maximum block size, assuming 512 bytes
[ 1.761075] mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit
[ 1.775639] usbcore: registered new interface driver usbhid
[ 1.781319] usbhid: USB HID core driver
[ 1.825082] mmc0: MAN_BKOPS_EN bit is not set
[ 1.832548] mmc0: new high speed MMC card at address 0001
[ 1.838759] mmcblk0: mmc0:0001 SEM16G 14.6 GiB
[ 1.843581] mmcblk0boot0: mmc0:0001 SEM16G partition 1 4.00 MiB
[ 1.849764] mmcblk0boot1: mmc0:0001 SEM16G partition 2 4.00 MiB
[ 1.855940] mmcblk0rpmb: mmc0:0001 SEM16G partition 3 4.00 MiB
[ 1.865140] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9
[ 2.292928] input: tegra-hda HDMI/DP,pcm=3 as /devices/soc0/70030000.hda/sound/card0/input0
[ 2.930941] tegra30-i2s 70301100.i2s: DMA channels sourced from device 70300000.ahub
[ 2.952003] tegra-snd-rt5640 sound: rt5640-aif1 <-> 70301100.i2s mapping ok
[ 2.963844] input: NVIDIA Tegra Jetson TK1 Headphones as /devices/soc0/sound/sound/card1/input1
[ 2.974950] NET: Registered protocol family 10
[ 2.980858] mip6: Mobile IPv6
[ 2.983874] sit: IPv6 over IPv4 tunneling driver
[ 2.991548] NET: Registered protocol family 17
[ 2.996043] NET: Registered protocol family 15
[ 3.000500] can: controller area network core (rev 20120528 abi 9)
[ 3.006861] NET: Registered protocol family 29
[ 3.011336] can: raw protocol (rev 20120528)
[ 3.015621] can: broadcast manager protocol (rev 20120528 t)
[ 3.021326] can: netlink gateway (rev 20130117) max_hops=1
[ 3.026980] Bluetooth: RFCOMM socket layer initialized
[ 3.032161] Bluetooth: RFCOMM ver 1.11
[ 3.035938] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.041293] Bluetooth: BNEP socket layer initialized
[ 3.046271] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 3.052236] Bluetooth: HIDP socket layer initialized
[ 3.058067] Registering SWP/SWPB emulation handler
[ 3.069988] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration
[ 3.076896] +3.3V_SYS: supplied by +VDD_MUX
[ 3.081190] +3.3V_LP0: supplied by +3.3V_SYS
[ 3.085826] +1.35V_LP0(sd2): supplied by +5V_SYS
[ 3.090516] +1.05V_RUN_AVDD: supplied by +1.35V_LP0(sd2)
[ 3.097395] tegra-pcie 1003000.pcie-controller: probing port 0, using 2 lanes
[ 3.106746] tegra-pcie 1003000.pcie-controller: Slot present pin change, signature: 00000008
[ 3.491045] cfg80211: Calling CRDA to update world regulatory domain
[ 3.523050] tegra-pcie 1003000.pcie-controller: link 0 down, retrying
[ 3.934528] tegra-pcie 1003000.pcie-controller: link 0 down, retrying
[ 4.346472] tegra-pcie 1003000.pcie-controller: link 0 down, retrying
[ 4.354973] tegra-pcie 1003000.pcie-controller: link 0 down, ignoring
[ 4.361461] tegra-pcie 1003000.pcie-controller: probing port 1, using 1 lanes
[ 4.370635] tegra-pcie 1003000.pcie-controller: Slot present pin change, signature: 00000000
[ 4.387641] tegra-pcie 1003000.pcie-controller: PCI host bridge to bus 0000:00
[ 4.394910] pci_bus 0000:00: root bus resource [mem 0x13000000-0x1fffffff]
[ 4.401816] pci_bus 0000:00: root bus resource [mem 0x20000000-0x3fffffff pref]
[ 4.409140] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 4.414653] pci_bus 0000:00: root bus resource [io 0x1000-0xffff]
[ 4.420891] pci 0000:00:02.0: [10de:0e13] type 01 class 0x060400
[ 4.426983] pci 0000:00:02.0: IOMMU is currently not supported for PCI
[ 4.433575] pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 4.440845] PCI: bus0: Fast back to back transfers disabled
[ 4.446451] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.454880] pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000
[ 4.460952] pci 0000:01:00.0: reg 0x10: [io 0x0000-0x00ff]
[ 4.466584] pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x00000fff 64bit]
[ 4.473419] pci 0000:01:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit pref]
[ 4.480676] pci 0000:01:00.0: IOMMU is currently not supported for PCI
[ 4.487297] pci 0000:01:00.0: supports D1 D2
[ 4.491596] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 4.511070] PCI: bus1: Fast back to back transfers disabled
[ 4.516656] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 4.523383] pci 0000:00:02.0: BAR 8: assigned [mem 0x13000000-0x130fffff]
[ 4.530186] pci 0000:00:02.0: BAR 9: assigned [mem 0x20000000-0x200fffff 64bit pref]
[ 4.537965] pci 0000:00:02.0: BAR 7: assigned [io 0x1000-0x1fff]
[ 4.544096] pci 0000:01:00.0: BAR 4: assigned [mem 0x20000000-0x20003fff 64bit pref]
[ 4.551895] pci 0000:01:00.0: BAR 2: assigned [mem 0x13000000-0x13000fff 64bit]
[ 4.559236] pci 0000:01:00.0: BAR 0: assigned [io 0x1000-0x10ff]
[ 4.565363] pci 0000:00:02.0: PCI bridge to [bus 01]
[ 4.570338] pci 0000:00:02.0: bridge window [io 0x1000-0x1fff]
[ 4.576462] pci 0000:00:02.0: bridge window [mem 0x13000000-0x130fffff]
[ 4.583281] pci 0000:00:02.0: bridge window [mem 0x20000000-0x200fffff 64bit pref]
[ 4.591078] pci 0000:00:02.0: nv_msi_ht_cap_quirk didn't locate host bridge
[ 4.598194] pcieport 0000:00:02.0: enabling device (0140 -> 0143)
[ 4.604766] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
[ 4.611760] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[ 4.618298] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
[ 4.625319] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 4.630945] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[ 4.653429] r8169 0000:01:00.0 eth0: RTL8168g/8111g at 0xf0142000, 00:04:4b:49:0f:67, XID 0c000800 IRQ 385
[ 4.663128] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 4.672039] +5V_HDMI_CON: supplied by +5V_SYS
[ 4.676577] +1.05V_RUN_AVDD_HDMI_PLL: supplied by +1.05V_RUN
[ 4.682455] +3.3V_RUN: supplied by +3.3V_SYS
[ 4.686807] +3.3V_AVDD_HDMI_AP_GATED: supplied by +3.3V_RUN
[ 4.695329] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.702017] [drm] No driver support for vblank timestamp query.
[ 4.708029] drm drm: No connectors reported connected with modes
[ 4.714100] [drm] Cannot find any crtc or sizes - going 1024x768
[ 4.727617] drm drm: fb0: frame buffer device
[ 4.732100] drm drm: registered panic notifier
[ 4.761055] [drm] Initialized tegra 0.0.0 20120330 on minor 0
[ 4.767512] +5V_SATA: supplied by +5V_SYS
[ 4.771732] +12V_SATA: supplied by +VDD_MUX
[ 4.776566] tegra-ahci 70027000.sata: AHCI 0001.0301 32 slots 2 ports 3 Gbps 0x1 impl platform mode
[ 4.785661] tegra-ahci 70027000.sata: flags: 64bit ncq sntf pm led pio slum part sadm sds apst
[ 4.797620] scsi host0: tegra-ahci
[ 4.802171] scsi host1: tegra-ahci
[ 4.806364] ata1: SATA max UDMA/133 mmio [mem 0x70027000-0x70028fff] port 0x100 irq 343
[ 4.814423] ata2: DUMMY
[ 4.817316] +5V_USB_HS: supplied by +5V_SYS
[ 4.822127] tegra-ehci 7d008000.usb: EHCI Host Controller
[ 4.827576] tegra-ehci 7d008000.usb: new USB bus registered, assigned bus number 2
[ 4.835492] tegra-ehci 7d008000.usb: irq 350, io mem 0x7d008000
[ 4.861046] tegra-ehci 7d008000.usb: USB 2.0 started, EHCI 1.10
[ 4.868731] hub 2-0:1.0: USB hub found
[ 4.872597] hub 2-0:1.0: 1 port detected
[ 4.877718] sdhci-tegra 700b0400.sdhci: Got CD GPIO
[ 4.882681] sdhci-tegra 700b0400.sdhci: Got WP GPIO
[ 4.887621] mmc1: Unknown controller version (3). You may experience problems.
[ 4.895011] +VDDIO_SDMMC3: supplied by +3.3V_RUN
[ 4.899779] sdhci-tegra 700b0400.sdhci: No vmmc regulator found
[ 4.905807] mmc1: Invalid maximum block size, assuming 512 bytes
[ 4.951232] mmc1: SDHCI controller on 700b0400.sdhci [700b0400.sdhci] using ADMA 64-bit
[ 4.960207] input: gpio-keys as /devices/soc0/gpio-keys/input/input2
[ 4.967572] as3722-rtc as3722-rtc: setting system clock to 2016-05-14 21:20:51 UTC (1463260851)
[ 4.995044] +USB0_VBUS_SW: disabling
[ 4.999144] ALSA device list:
[ 5.002149] #0: tegra-hda at 0x70038000 irq 344
[ 5.006859] #1: NVIDIA Tegra Jetson TK1
[ 5.161062] ata1: SATA link down (SStatus 0 SControl 300)
[ 5.182025] EXT3-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (240)
[ 5.191864] EXT2-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (240)
[ 5.211543] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[ 5.219698] VFS: Mounted root (ext4 filesystem) on device 179:1.
[ 5.230765] devtmpfs: mounted
[ 5.234120] Freeing unused kernel memory: 320K (c09b6000 - c0a06000)
[ 5.454941] random: init urandom read with 11 bits of entropy available
[ 5.573182] init: plymouth-upstart-bridge main process (99) terminated with status 1
[ 5.581070] init: plymouth-upstart-bridge main process ended, respawning
[ 5.626057] init: plymouth-upstart-bridge main process (109) terminated with status 1
[ 5.634171] init: plymouth-upstart-bridge main process ended, respawning
[ 5.666478] init: plymouth-upstart-bridge main process (114) terminated with status 1
[ 5.675302] init: plymouth-upstart-bridge main process ended, respawning
[ 5.675824] init: ureadahead main process (102) terminated with status 5
[ 6.573801] systemd-udevd[255]: starting version 204
[ 6.651081] cfg80211: Calling CRDA to update world regulatory domain
[ 6.729451] init: idmapd main process (264) terminated with status 1
[ 6.739024] init: idmapd main process ended, respawning
[ 6.880018] cfg80211: World regulatory domain updated:
[ 6.893836] cfg80211: DFS Master region: unset
[ 6.898205] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 6.916276] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 6.924894] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 6.937252] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 6.945852] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 6.954875] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 7.078407] init: nv main process (262) terminated with status 1
[ 7.542948] init: idmapd main process (380) terminated with status 1
[ 7.551944] init: idmapd main process ended, respawning
[ 7.920736] init: udev-fallback-graphics main process (422) terminated with status 1
[ 8.128502] init: idmapd main process (440) terminated with status 1
[ 8.134985] init: idmapd main process ended, respawning
* Starting Mount filesystems on boot [ OK ]
* Starting Signal sysvinit that the rootfs is mounted [ OK ]
* Starting Populate /dev filesystem [ OK ]
* Stopping Populate /dev filesystem [ OK ]
* Starting Clean /tmp directory [ OK ]
* Starting Populate and link to /run filesystem [ OK ]
* Stopping Clean /tmp directory [ OK ]
* Stopping Populate and link to /run filesystem [ OK ]
* Stopping Track if upstart is running in a container [ OK ]
* Starting Initialize or finalize resolvconf [ OK ]
* Starting set console keymap [ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted [ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted [ OK ]
* Starting Bridge udev events into upstart [ OK ]
* Stopping set console keymap [ OK ]
* Starting Signal sysvinit that local filesystems are mounted [ OK ]
* Starting restore software rfkill state [ OK ]
* Stopping restore software rfkill state [ OK ]
* Starting device node and kernel event manager [ OK ]
* Starting Signal sysvinit that remote filesystems are mounted [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
* Starting D-Bus system message bus [ OK ]
* Starting NVIDIA specific init script [ OK ]
* Starting load modules from /etc/modules [ OK ]
* Starting cold plug devices [ OK ]
* Starting log initial device creation [ OK ]
* Starting NVIDIA specific init script [fail]
* Stopping Mount filesystems on boot [ OK ]
* Stopping load modules from /etc/modules [ OK ]
* Starting flush early job output to logs [ OK ]
* Starting SystemD login management service [ OK ]
* Stopping flush early job output to logs [ OK ]
* Starting bluetooth daemon [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
* Stopping cold plug devices [ OK ]
* Stopping rpcsec_gss daemon [ OK ]
* Stopping log initial device creation [ OK ]
* Starting system logging daemon [ OK ]
* Starting configure network device security [ OK ]
* Starting enable remaining boot-time encrypted block devices [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
* Starting mDNS/DNS-SD daemon [ OK ]
* Starting userspace bootsplash [ OK ]
* Stopping NVIDIA specific first-boot script [ OK ]
* Stopping userspace bootsplash [ OK ]
* Starting Reload cups, upon starting avahi-daemon to make sure remote q[ OK ]are populated
* Starting Send an event to indicate plymouth is up [ OK ]
* Starting configure network device security [ OK ]
* Starting CUPS printing spooler/server [ OK ]
* Starting configure network device [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
* Stopping Send an event to indicate plymouth is up [ OK ]
[ 8.906346] init: idmapd main process (541) terminated with status 1
[ 8.912861] init: idmapd main process ended, respawning
* Starting System V initialisation compatibility [ OK ]
* Starting modem connection manager [ OK ]
* Starting configure network device security [ OK ]
* Stopping Reload cups, upon starting avahi-daemon to make sure remote q[ OK ]are populated
* Starting configure virtual network devices [ OK ]
* Starting early crypto disks... [ OK ]
* Starting cups-browsed - Bonjour remote printer browsing daemon [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
* Starting network connection manager [ OK ]
[ 9.324257] init: idmapd main process (663) terminated with status 1
[ 9.333131] init: idmapd main process ended, respawning
* Setting up X socket directories... [ OK ]
* Stopping System V initialisation compatibility [ OK ]
[ 9.738714] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2
[ 9.747860] r8169 0000:01:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168g-2.fw (-2)
[ 9.763783] r8169 0000:01:00.0 eth0: link down
[ 9.763836] r8169 0000:01:00.0 eth0: link down
[ 9.772997] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
* Starting configure network device security [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device [ OK ]
* Starting configure network device [ OK ]
* Starting configure network device [ OK ]
* Starting System V runlevel compatibility [ OK ]
* Starting Restore Sound Card State [ OK ]
* Starting anac(h)ronistic cron [ OK ]
* Starting save kernel messages [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
* Starting OpenSSH server [ OK ]
* Starting regular background program processing daemon [ OK ]
* Starting crash report submission daemon [ OK ]
[ 10.267015] init: idmapd main process (832) terminated with status 1
[ 10.273590] init: idmapd main process ended, respawning
* Stopping save kernel messages [ OK ]
* speech-dispatcher disabled; edit /etc/default/speech-dispatcher
* Stopping Restore Sound Card State [ OK ]
* Stopping anac(h)ronistic cron [ OK ]
* Starting NTP server ntpd [ OK ]
saned disabled; edit /etc/default/saned
* Starting configure network device [ OK ]
* Stopping System V runlevel compatibility [ OK ]
Ubuntu 14.04.1 LTS tegra-ubuntu ttyS0
tegra-ubuntu login: ubuntu (automatic login)
[ 10.866245] init: plymouth-upstart-bridge main process ended, respawning
Last login: Sat May 14 21:18:00 UTC 2016 from 158.130.110.134 on pts/0
Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 4.1.0-196900-g02942d8 armv7l)
* Documentation: https://help.ubuntu.com/
540 packages can be updated.
260 updates are security updates.
[ 11.045298] init: lightdm main process (830) terminated with status 1
[ 11.151267] init: plymouth-ready (startup) main process (98) terminated with status 1
[ 11.172552] init: idmapd main process (983) terminated with status 1
[ 11.179018] init: idmapd main process ended, respawning
[ 11.375028] init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE
[ 11.509226] init: idmapd main process (1026) terminated with status 1
[ 11.516480] init: idmapd main process ended, respawning
ubuntu@tegra-ubuntu:~$ [ 11.703432] init: idmapd main process (1065) terminated with status 1
[ 11.709949] init: idmapd main process ended, respawning
[ 11.885486] init: idmapd main process (1084) terminated with status 1
[ 11.892133] init: idmapd main process ended, respawning
[ 12.072448] init: idmapd main process (1097) terminated with status 1
[ 12.079002] init: idmapd main process ended, respawning
[ 12.212796] init: idmapd main process (1110) terminated with status 1
[ 12.219353] init: idmapd main process ended, respawning
[ 12.342734] init: idmapd main process (1123) terminated with status 1
[ 12.349304] init: idmapd main process ended, respawning
[ 12.489893] r8169 0000:01:00.0 eth0: link up
[ 12.494346] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 12.503416] init: idmapd main process (1136) terminated with status 1
[ 12.509929] init: idmapd main process ended, respawning
[ 12.671786] init: idmapd main process (1151) terminated with status 1
[ 12.678368] init: idmapd main process ended, respawning
[ 12.842767] init: idmapd main process (1165) terminated with status 1
[ 12.849327] init: idmapd main process ended, respawning
[ 13.002202] init: idmapd main process (1178) terminated with status 1
[ 13.008764] init: idmapd respawning too fast, stopped
[ 31.440798] init: failsafe-x main process (1349) terminated with status 1
[ 41.510549] random: nonblocking pool is initialized
ubuntu@tegra-ubuntu:~$
Broadcast message from ubuntu@tegra-ubuntu
(/dev/pts/1) at 21:21 ...
The system is going down for reboot NOW!
[ 68.362225] init: tty4 main process (761) killed by TERM signal
[ 68.369683] init: tty5 main process (765) killed by TERM signal
[ 68.377128] init: tty2 main process (771) killed by TERM signal
[ 68.384586] init: tty3 main process (772) killed by TERM signal
[ 68.392221] init: tty6 main process (775) killed by TERM signal
[ 68.401142] init: cron main process (828) killed by TERM signal
[ 68.409892] init: tty1 main process (950) killed by TERM signal
[ 68.417515] init: ttyS0 main process (953) killed by TERM signal
[ 68.436723] init: plymouth-upstart-bridge main process (1488) terminated with status 1
[ 68.445002] init: plymouth-upstart-bridge main process ended, respawning
[ 68.695407] init: plymouth-upstart-bridge main process (1518) terminated with status 1
[ 68.703441] init: plymouth-upstart-bridge main process ended, respawning
[ 68.784549] init: plymouth-upstart-bridge main process (1522) terminated with status 1
[ 68.792623] init: plymouth-upstart-bridge main process ended, respawning
[ 68.825728] init: plymouth-upstart-bridge main process (1525) terminated with status 1
[ 68.833817] init: plymouth-upstart-bridge main process ended, respawning
[ 68.860738] init: plymouth-upstart-bridge main process (1527) terminated with status 1
[ 68.868778] init: plymouth-upstart-bridge main process ended, respawning
[ 68.901206] init: plymouth-upstart-bridge main process (1529) terminated with status 1
[ 68.909245] init: plymouth-upstart-bridge main process ended, respawning
[ 68.938807] init: plymouth-upstart-bridge main process (1531) terminated with status 1
[ 68.947030] init: plymouth-upstart-bridge main process ended, respawning
[ 68.992586] init: plymouth-upstart-bridge main process (1534) terminated with status 1
[ 69.000657] init: plymouth-upstart-bridge main process ended, respawning
[ 69.050324] init: plymouth-upstart-bridge main process (1538) terminated with status 1
[ 69.058333] init: plymouth-upstart-bridge main process ended, respawning
[ 69.093174] init: plymouth-upstart-bridge main process (1541) terminated with status 1
[ 69.101232] init: plymouth-upstart-bridge main process ended, respawning
[ 69.129752] init: plymouth-upstart-bridge main process (1543) terminated with status 1
[ 69.137871] init: plymouth-upstart-bridge respawning too fast, stopped
[ 69.316804] init: wait-for-state (rcplymouth-shutdown) main process (1545) killed by TERM signal
[ 70.109808] init: failsafe main process (929) terminated with status 143
[ 70.570966] init: rpcbind main process (1009) terminated with status 2
[ 70.606224] init: systemd-logind main process (368) killed by TERM signal
[ 70.985344] init: Disconnected from D-Bus system bus
[ 71.304367] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
[ 72.370573] reboot: Restarting system
U-Boot SPL 2016.05-rc3-00070-g4baca92-dirty (May 12 2016 - 19:10:02)
Trying to boot from RAM
U-Boot 2016.05-rc3-00070-g4baca92-dirty (May 12 2016 - 19:10:02 -0400)
TEGRA124
Model: NVIDIA Jetson TK1
Board: NVIDIA Jetson TK1
DRAM: 2 GiB
MC: Tegra SD/MMC: 0, Tegra SD/MMC: 1
In: serial
Out: serial
Err: serial
Net: No ethernet found.
Hit any key to stop autoboot: 0
MMC: no card present
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
6786 bytes read in 292 ms (22.5 KiB/s)
Jetson-TK1 eMMC boot options
1: primary kernel
2: NVIDIA-L4T-SRC
3: NVIDIA-L4T-SRC-Xen
4: NVIDIA-L4T-SRC-Xen-Drivers
5: Linux 4.1.0 PSCI (work under HYP mode)
6: Linux 4.1.0 PSCI with Xen (not work under HYP mode)
7: Linux 4.1.0 PSCI with Xen and Xen drivers (work under HYP mode)
8: Linux 4.1.0 PSCI with Xen and Xen drivers Debug (work under HYP mode)
Enter choice: 8
8: Linux 4.1.0 PSCI with Xen and Xen drivers Debug (work under HYP mode)
Retrieving file: /boot/zImage-psci-xen-xendrivers-debug
5369456 bytes read in 517 ms (9.9 MiB/s)
append: console=ttyS0,115200n8 console=tty1 no_console_suspend=1 lp0_vec=2064@0xf46ff000 mem=2015M@2048M memtype=255 ddr_die=204
8M@2048M section=256M pmuboard=0x0177:0x0000:0x02:0x43:0x00 tsec=32M@3913M otf_key=c75e5bb91eb3bd947560357b64422f85 usbcore.old_
scheme_first=1 core_edp_mv=1150 core_edp_ma=4000 tegraid=40.1.1.0.0 debug_uartport=lsport,3 power_supply=Adapter audio_codec=rt5
640 modem_id=0 android.kerneltype=normal fbcon=map:1 commchip_id=0 usb_port_owner_info=0 lane_owner_info=6 emc_max_dvfs=0 touch_
id=0@0 board_info=0x0177:0x0000:0x02:0x43:0x00 root=/dev/mmcblk0p1 rw rootwait tegraboot=sdmmc gpt ignore_loglevel earlyprintk=t
tyS0,115200n8 maxcpus=1
Retrieving file: /boot/tegra124-jetson-tk1-psci-xen-xendrivers.dtb
62999 bytes read in 354 ms (172.9 KiB/s)
Kernel image @ 0x81000000 [ 0x000000 - 0x51ee70 ]
## Flattened Device Tree blob at 82000000
Booting using the fdt blob at 0x82000000
Using Device Tree in place at 82000000, end 82012616
Starting kernel ...
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-196900-g02942d8 (root@menglab6c) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #11 SMP
PREEMPT Sat May 14 17:13:27 EDT 2016
[ 0.000000] CPU: ARMv7 Processor [413fc0f3] revision 3 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] Machine model: NVIDIA Tegra124 Jetson TK1
[ 0.000000] debug: ignoring loglevel setting.
[ 0.000000] bootconsole [earlycon0] enabled
[ 0.000000] cma: Reserved 64 MiB at 0xf9c00000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 515840
[ 0.000000] free_area_init_node: node 0, pgdat c0a5bfc0, node_mem_map ee837000
[ 0.000000] Normal zone: 1520 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 194560 pages, LIFO batch:31
[ 0.000000] HighMem zone: 321280 pages, LIFO batch:31
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: Using PSCI v0.1 Function IDs from DT
[ 0.000000] PERCPU: Embedded 11 pages/cpu @ee7d3000 s15808 r8192 d21056 u45056
[ 0.000000] pcpu-alloc: s15808 r8192 d21056 u45056 alloc=11*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 514320
[ 0.000000] Kernel command line: console=ttyS0,115200n8 console=tty1 no_console_suspend=1 lp0_vec=2064@0xf46ff000 mem=2015M@2
048M memtype=255 ddr_die=2048M@2048M section=256M pmuboard=0x0177:0x0000:0x02:0x43:0x00 tsec=32M@3913M otf_key=c75e5bb91eb3bd947
560357b64422f85 usbcore.old_scheme_first=1 core_edp_mv=1150 core_edp_ma=4000 tegraid=40.1.1.0.0 debug_uartport=lsport,3 power_su
pply=Adapter audio_codec=rt5640 modem_id=0 android.kerneltype=normal fbcon=map:1 commchip_id=0 usb_port_owner_info=0 lane_owner_
info=6 emc_max_dvfs=0 touch_id=0@0 board_info=0x0177:0x0000:0x02:0x43:0x00 root=/dev/mmcblk0p1 rw rootwait tegraboot=sdmmc gpt i
gnore_loglevel earlyprintk=ttyS0,115200n8 maxcpus=1
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 1969356K/2063360K available (7317K kernel code, 428K rwdata, 2592K rodata, 320K init, 374K bss, 28468K re
served, 65536K cma-reserved, 1219584K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc09b5a58 (9911 kB)
[ 0.000000] .init : 0xc09b6000 - 0xc0a06000 ( 320 kB)
[ 0.000000] .data : 0xc0a06000 - 0xc0a711a0 ( 429 kB)
[ 0.000000] .bss : 0xc0a74000 - 0xc0ad1a94 ( 375 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Additional per-CPU info printed with stalls.
[ 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,50041000
[ 0.000000] L2C: failed to init: -19
[ 0.000009] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
[ 0.006536] clocksource: timer_us: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
[ 0.016151] Switching to timer-based delay loop, resolution 1000ns
[ 0.023590] Architected cp15 timer(s) running at 12.00MHz (phys).
[ 0.028547] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2c47f4ee7, max_idle_ns: 440795202497 ns
[ 0.039383] sched_clock: 56 bits at 12MHz, resolution 83ns, wraps every 4398046511096ns
[ 0.047437] Switching to timer-based delay loop, resolution 83ns
[ 0.053927] Console: colour dummy device 80x30
[ 0.058010] console [tty1] enabled
[ 0.061473] bootconsole [earlycon0] disabled
[ 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-196900-g02942d8 (root@menglab6c) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #11 SMP
PREEMPT Sat May 14 17:13:27 EDT 2016
[ 0.000000] CPU: ARMv7 Processor [413fc0f3] revision 3 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] Machine model: NVIDIA Tegra124 Jetson TK1
[ 0.000000] debug: ignoring loglevel setting.
[ 0.000000] bootconsole [earlycon0] enabled
[ 0.000000] cma: Reserved 64 MiB at 0xf9c00000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 515840
[ 0.000000] free_area_init_node: node 0, pgdat c0a5bfc0, node_mem_map ee837000
[ 0.000000] Normal zone: 1520 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 194560 pages, LIFO batch:31
[ 0.000000] HighMem zone: 321280 pages, LIFO batch:31
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: Using PSCI v0.1 Function IDs from DT
[ 0.000000] PERCPU: Embedded 11 pages/cpu @ee7d3000 s15808 r8192 d21056 u45056
[ 0.000000] pcpu-alloc: s15808 r8192 d21056 u45056 alloc=11*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 514320
[ 0.000000] Kernel command line: console=ttyS0,115200n8 console=tty1 no_console_suspend=1 lp0_vec=2064@0xf46ff000 mem=2015M@2
048M memtype=255 ddr_die=2048M@2048M section=256M pmuboard=0x0177:0x0000:0x02:0x43:0x00 tsec=32M@3913M otf_key=c75e5bb91eb3bd947
560357b64422f85 usbcore.old_scheme_first=1 core_edp_mv=1150 core_edp_ma=4000 tegraid=40.1.1.0.0 debug_uartport=lsport,3 power_su
pply=Adapter audio_codec=rt5640 modem_id=0 android.kerneltype=normal fbcon=map:1 commchip_id=0 usb_port_owner_info=0 lane_owner_
info=6 emc_max_dvfs=0 touch_id=0@0 board_info=0x0177:0x0000:0x02:0x43:0x00 root=/dev/mmcblk0p1 rw rootwait tegraboot=sdmmc gpt i
gnore_loglevel earlyprintk=ttyS0,115200n8 maxcpus=1
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 1969356K/2063360K available (7317K kernel code, 428K rwdata, 2592K rodata, 320K init, 374K bss, 28468K re
served, 65536K cma-reserved, 1219584K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc09b5a58 (9911 kB)
[ 0.000000] .init : 0xc09b6000 - 0xc0a06000 ( 320 kB)
[ 0.000000] .data : 0xc0a06000 - 0xc0a711a0 ( 429 kB)
[ 0.000000] .bss : 0xc0a74000 - 0xc0ad1a94 ( 375 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Additional per-CPU info printed with stalls.
[ 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,50041000
[ 0.000000] L2C: failed to init: -19
[ 0.000009] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
[ 0.006536] clocksource: timer_us: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
[ 0.016151] Switching to timer-based delay loop, resolution 1000ns
[ 0.023590] Architected cp15 timer(s) running at 12.00MHz (phys).
[ 0.028547] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2c47f4ee7, max_idle_ns: 440795202497 ns
[ 0.039383] sched_clock: 56 bits at 12MHz, resolution 83ns, wraps every 4398046511096ns
[ 0.047437] Switching to timer-based delay loop, resolution 83ns
[ 0.053927] Console: colour dummy device 80x30
[ 0.058010] console [tty1] enabled
[ 0.061473] bootconsole [earlycon0] disabled
[ 0.065837] Calibrating delay loop (skipped), value calculated using timer frequency.. 24.00 BogoMIPS (lpj=120000)
[ 0.065869] pid_max: default: 32768 minimum: 301
[ 0.066284] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.066307] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.067707] Initializing cgroup subsys freezer
[ 0.067741] Initializing cgroup subsys debug
[ 0.067802] CPU: Testing write buffer coherency: ok
[ 0.068124] /cpus/cpu@0 missing clock-frequency property
[ 0.068171] /cpus/cpu@1 missing clock-frequency property
[ 0.068216] /cpus/cpu@2 missing clock-frequency property
[ 0.068262] /cpus/cpu@3 missing clock-frequency property
[ 0.068282] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.068512] Setting up static identity map for 0x80008440 - 0x800084d8
[ 0.089130] Tegra Revision: A01 SKU: 129 CPU Process: 1 Core Process: 1
[ 0.089829] Brought up 1 CPUs
[ 0.089845] SMP: Total of 1 processors activated (24.00 BogoMIPS).
[ 0.089862] CPU: All CPU(s) started in HYP mode.
[ 0.089875] CPU: Virtualization extensions available.
[ 0.090603] devtmpfs: initialized
[ 0.140149] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[ 0.140833] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.142624] pinctrl core: initialized pinctrl subsystem
[ 0.144455] NET: Registered protocol family 16
[ 0.146283] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.176019] cpuidle: using governor ladder
[ 0.206044] cpuidle: using governor menu
[ 0.229823] No ATAGs?
[ 0.229860] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.229903] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.291416] +USB0_VBUS_SW: Failed to request enable GPIO108: -517
[ 0.291658] reg-fixed-voltage regulators:regulator@7: Failed to register regulator: -517
[ 0.292139] +5V_USB_HS: Failed to request enable GPIO109: -517
[ 0.292367] reg-fixed-voltage regulators:regulator@8: Failed to register regulator: -517
[ 0.292953] +1.05V_RUN_AVDD_HDMI_PLL: Failed to request enable GPIO63: -517
[ 0.293181] reg-fixed-voltage regulators:regulator@11: Failed to register regulator: -517
[ 0.293659] +5V_HDMI_CON: Failed to request enable GPIO86: -517
[ 0.293884] reg-fixed-voltage regulators:regulator@12: Failed to register regulator: -517
[ 0.294360] +5V_SATA: Failed to request enable GPIO242: -517
[ 0.294584] reg-fixed-voltage regulators:regulator@13: Failed to register regulator: -517
[ 0.295058] +12V_SATA: Failed to request enable GPIO242: -517
[ 0.295282] reg-fixed-voltage regulators:regulator@14: Failed to register regulator: -517
[ 0.297609] vgaarb: loaded
[ 0.299051] SCSI subsystem initialized
[ 0.299382] libata version 3.00 loaded.
[ 0.300134] usbcore: registered new interface driver usbfs
[ 0.300319] usbcore: registered new interface driver hub
[ 0.300487] usbcore: registered new device driver usb
[ 0.304792] Linux video capture interface: v2.00
[ 0.304937] pps_core: LinuxPPS API ver. 1 registered
[ 0.304961] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.305058] PTP clock support registered
[ 0.307076] Advanced Linux Sound Architecture Driver Initialized.
[ 0.308712] Bluetooth: Core ver 2.20
[ 0.308806] NET: Registered protocol family 31
[ 0.308828] Bluetooth: HCI device and connection manager initialized
[ 0.308866] Bluetooth: HCI socket layer initialized
[ 0.308902] Bluetooth: L2CAP socket layer initialized
[ 0.308971] Bluetooth: SCO socket layer initialized
[ 0.309595] cfg80211: Calling CRDA to update world regulatory domain
[ 0.310901] clocksource: Switched to clocksource arch_sys_counter
[ 0.334798] NET: Registered protocol family 2
[ 0.335842] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.335971] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.336173] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.336635] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.336695] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.337070] NET: Registered protocol family 1
[ 0.337717] RPC: Registered named UNIX socket transport module.
[ 0.337743] RPC: Registered udp transport module.
[ 0.337764] RPC: Registered tcp transport module.
[ 0.337784] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.337824] PCI: CLS 0 bytes, default 64
[ 0.342667] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.345016] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.350965] bounce: pool size: 64 pages
[ 0.351003] io scheduler noop registered (default)
[ 0.361903] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration
[ 0.361973] tegra-pcie 1003000.pcie-controller: Failed to get supply 'avddio-pex': -517
[ 0.373455] tegra-apbdma 60020000.dma: Tegra20 APB DMA driver register 32 channels
[ 0.373995] tegra-pmc 7000e400.pmc: emergency thermal reset enabled
[ 0.374220] xenfs: not registering filesystem on non-xen platform
[ 0.374848] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.378613] console [ttyS0] disabled
[ 0.378682] 70006300.serial: ttyS0 at MMIO 0x70006300 (irq = 333, base_baud = 25500000) is a Tegra
[ 1.249604] console [ttyS0] enabled
[ 1.255975] [drm] Initialized drm 1.1.0 20060810
[ 1.262203] tegra-hdmi 54280000.hdmi: failed to get HDMI regulator
[ 1.282011] loop: module loaded
[ 1.285792] at24 0-0056: 256 byte 24c02 EEPROM, writable, 8 bytes/write
[ 1.293272] as3722 4-0040: AS3722 with revision 0x1 found
[ 1.319759] +5V_SYS: supplied by +VDD_MUX
[ 1.323875] +1.05V_RUN: supplied by +5V_SYS
[ 1.328235] tegra-ahci 70027000.sata: Failed to get supply 'hvdd': -517
[ 1.334933] tegra-ahci 70027000.sata: Failed to get regulators
[ 1.343739] m25p80 spi32765.0: w25q32dw (4096 Kbytes)
[ 1.352218] CAN device driver interface
[ 1.356186] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k
[ 1.363304] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 1.369280] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[ 1.376891] usbcore: registered new interface driver pegasus
[ 1.382791] usbcore: registered new interface driver asix
[ 1.388332] usbcore: registered new interface driver ax88179_178a
[ 1.394615] usbcore: registered new interface driver cdc_ether
[ 1.400638] usbcore: registered new interface driver smsc75xx
[ 1.406609] usbcore: registered new interface driver smsc95xx
[ 1.412517] usbcore: registered new interface driver net1080
[ 1.418318] usbcore: registered new interface driver cdc_subset
[ 1.424397] usbcore: registered new interface driver zaurus
[ 1.430173] usbcore: registered new interface driver cdc_ncm
[ 1.436187] tegra-phy 7d004000.usb-phy: no vbus regulator
[ 1.442160] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.448718] ehci-pci: EHCI PCI platform driver
[ 1.453327] tegra-ehci: Tegra EHCI driver
[ 1.457705] tegra-ehci 7d004000.usb: EHCI Host Controller
[ 1.463174] tegra-ehci 7d004000.usb: new USB bus registered, assigned bus number 1
[ 1.471090] tegra-ehci 7d004000.usb: irq 349, io mem 0x7d004000
[ 1.490928] tegra-ehci 7d004000.usb: USB 2.0 started, EHCI 1.10
[ 1.498673] hub 1-0:1.0: USB hub found
[ 1.502531] hub 1-0:1.0: 1 port detected
[ 1.507906] usbcore: registered new interface driver cdc_acm
[ 1.513625] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 1.521827] usbcore: registered new interface driver cdc_wdm
[ 1.527706] usbcore: registered new interface driver usb-storage
[ 1.534560] mousedev: PS/2 mouse device common for all mice
[ 1.543828] as3722-rtc as3722-rtc: rtc core: registered as3722-rtc as rtc0
[ 1.550714] as3722-rtc as3722-rtc: RTC interrupt 368
[ 1.558870] tegra_rtc 7000e000.rtc: rtc core: registered 7000e000.rtc as rtc1
[ 1.566163] tegra_rtc 7000e000.rtc: Tegra internal Real Time Clock
[ 1.572811] i2c /dev entries driver
[ 1.578624] usbcore: registered new interface driver uvcvideo
[ 1.584398] USB Video Class driver (1.1.1)
[ 1.588512] gspca_main: v2.14.0 registered
[ 1.593520] 0-004c supply vcc not found, using dummy regulator
[ 1.603074] sdhci: Secure Digital Host Controller Interface driver
[ 1.609260] sdhci: Copyright(c) Pierre Ossman
[ 1.613651] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.619634] sdhci-tegra 700b0400.sdhci: Got CD GPIO
[ 1.624560] sdhci-tegra 700b0400.sdhci: Got WP GPIO
[ 1.629498] mmc0: Unknown controller version (3). You may experience problems.
[ 1.636863] as3722-regulator as3722-regulator: Failed to resolve vin-ldo1-6-supply for as3722-ldo6
[ 1.645857] sdhci-tegra 700b0400.sdhci: No vmmc regulator found
[ 1.652019] mmc0: Unknown controller version (3). You may experience problems.
[ 1.659319] sdhci-tegra 700b0600.sdhci: No vmmc regulator found
[ 1.665297] sdhci-tegra 700b0600.sdhci: No vqmmc regulator found
[ 1.671355] mmc0: Invalid maximum block size, assuming 512 bytes
[ 1.720956] mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit
[ 1.735404] usbcore: registered new interface driver usbhid
[ 1.741028] usbhid: USB HID core driver
[ 1.785013] mmc0: MAN_BKOPS_EN bit is not set
[ 1.792731] mmc0: new high speed MMC card at address 0001
[ 1.798910] mmcblk0: mmc0:0001 SEM16G 14.6 GiB
[ 1.803746] mmcblk0boot0: mmc0:0001 SEM16G partition 1 4.00 MiB
[ 1.809927] mmcblk0boot1: mmc0:0001 SEM16G partition 2 4.00 MiB
[ 1.816121] mmcblk0rpmb: mmc0:0001 SEM16G partition 3 4.00 MiB
[ 1.825311] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9
[ 2.252761] input: tegra-hda HDMI/DP,pcm=3 as /devices/soc0/70030000.hda/sound/card0/input0
[ 2.890791] tegra30-i2s 70301100.i2s: DMA channels sourced from device 70300000.ahub
[ 2.911808] tegra-snd-rt5640 sound: rt5640-aif1 <-> 70301100.i2s mapping ok
[ 2.923637] input: NVIDIA Tegra Jetson TK1 Headphones as /devices/soc0/sound/sound/card1/input1
[ 2.934693] NET: Registered protocol family 10
[ 2.940611] mip6: Mobile IPv6
[ 2.943645] sit: IPv6 over IPv4 tunneling driver
[ 2.951303] NET: Registered protocol family 17
[ 2.955800] NET: Registered protocol family 15
[ 2.960257] can: controller area network core (rev 20120528 abi 9)
[ 2.966617] NET: Registered protocol family 29
[ 2.971098] can: raw protocol (rev 20120528)
[ 2.975384] can: broadcast manager protocol (rev 20120528 t)
[ 2.981088] can: netlink gateway (rev 20130117) max_hops=1
[ 2.986734] Bluetooth: RFCOMM socket layer initialized
[ 2.991979] Bluetooth: RFCOMM ver 1.11
[ 2.995757] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.001109] Bluetooth: BNEP socket layer initialized
[ 3.006089] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 3.012052] Bluetooth: HIDP socket layer initialized
[ 3.017894] Registering SWP/SWPB emulation handler
[ 3.029675] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration
[ 3.036586] +3.3V_SYS: supplied by +VDD_MUX
[ 3.040857] +3.3V_LP0: supplied by +3.3V_SYS
[ 3.045509] +1.35V_LP0(sd2): supplied by +5V_SYS
[ 3.050201] +1.05V_RUN_AVDD: supplied by +1.35V_LP0(sd2)
[ 3.057131] tegra-pcie 1003000.pcie-controller: probing port 0, using 2 lanes
[ 3.066479] tegra-pcie 1003000.pcie-controller: Slot present pin change, signature: 00000008
[ 3.470925] cfg80211: Calling CRDA to update world regulatory domain
[ 3.482952] tegra-pcie 1003000.pcie-controller: link 0 down, retrying
[ 3.894302] tegra-pcie 1003000.pcie-controller: link 0 down, retrying
[ 4.306218] tegra-pcie 1003000.pcie-controller: link 0 down, retrying
[ 4.314708] tegra-pcie 1003000.pcie-controller: link 0 down, ignoring
[ 4.321190] tegra-pcie 1003000.pcie-controller: probing port 1, using 1 lanes
[ 4.330363] tegra-pcie 1003000.pcie-controller: Slot present pin change, signature: 00000000
[ 4.347351] tegra-pcie 1003000.pcie-controller: PCI host bridge to bus 0000:00
[ 4.354613] pci_bus 0000:00: root bus resource [mem 0x13000000-0x1fffffff]
[ 4.361516] pci_bus 0000:00: root bus resource [mem 0x20000000-0x3fffffff pref]
[ 4.368841] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 4.374350] pci_bus 0000:00: root bus resource [io 0x1000-0xffff]
[ 4.380590] pci 0000:00:02.0: [10de:0e13] type 01 class 0x060400
[ 4.386680] pci 0000:00:02.0: IOMMU is currently not supported for PCI
[ 4.393270] pci 0000:00:02.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 4.400535] PCI: bus0: Fast back to back transfers disabled
[ 4.406141] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 4.414571] pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000
[ 4.420642] pci 0000:01:00.0: reg 0x10: [io 0x0000-0x00ff]
[ 4.426272] pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x00000fff 64bit]
[ 4.433104] pci 0000:01:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit pref]
[ 4.440359] pci 0000:01:00.0: IOMMU is currently not supported for PCI
[ 4.446977] pci 0000:01:00.0: supports D1 D2
[ 4.451273] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 4.470948] PCI: bus1: Fast back to back transfers disabled
[ 4.476533] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 4.483253] pci 0000:00:02.0: BAR 8: assigned [mem 0x13000000-0x130fffff]
[ 4.490054] pci 0000:00:02.0: BAR 9: assigned [mem 0x20000000-0x200fffff 64bit pref]
[ 4.497833] pci 0000:00:02.0: BAR 7: assigned [io 0x1000-0x1fff]
[ 4.503961] pci 0000:01:00.0: BAR 4: assigned [mem 0x20000000-0x20003fff 64bit pref]
[ 4.511755] pci 0000:01:00.0: BAR 2: assigned [mem 0x13000000-0x13000fff 64bit]
[ 4.519095] pci 0000:01:00.0: BAR 0: assigned [io 0x1000-0x10ff]
[ 4.525219] pci 0000:00:02.0: PCI bridge to [bus 01]
[ 4.530194] pci 0000:00:02.0: bridge window [io 0x1000-0x1fff]
[ 4.536314] pci 0000:00:02.0: bridge window [mem 0x13000000-0x130fffff]
[ 4.543127] pci 0000:00:02.0: bridge window [mem 0x20000000-0x200fffff 64bit pref]
[ 4.550920] pci 0000:00:02.0: nv_msi_ht_cap_quirk didn't locate host bridge
[ 4.558038] pcieport 0000:00:02.0: enabling device (0140 -> 0143)
[ 4.564600] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
[ 4.571592] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[ 4.578130] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
[ 4.585151] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 4.590778] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[ 4.613297] r8169 0000:01:00.0 eth0: RTL8168g/8111g at 0xf0142000, 00:04:4b:49:0f:67, XID 0c000800 IRQ 385
[ 4.622989] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 4.631897] +5V_HDMI_CON: supplied by +5V_SYS
[ 4.636434] +1.05V_RUN_AVDD_HDMI_PLL: supplied by +1.05V_RUN
[ 4.642315] +3.3V_RUN: supplied by +3.3V_SYS
[ 4.646672] +3.3V_AVDD_HDMI_AP_GATED: supplied by +3.3V_RUN
[ 4.655148] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.661824] [drm] No driver support for vblank timestamp query.
[ 4.667830] drm drm: No connectors reported connected with modes
[ 4.673897] [drm] Cannot find any crtc or sizes - going 1024x768
[ 4.687455] drm drm: fb0: frame buffer device
[ 4.691936] drm drm: registered panic notifier
[ 4.720935] [drm] Initialized tegra 0.0.0 20120330 on minor 0
[ 4.727395] +5V_SATA: supplied by +5V_SYS
[ 4.731604] +12V_SATA: supplied by +VDD_MUX
[ 4.736466] tegra-ahci 70027000.sata: AHCI 0001.0301 32 slots 2 ports 3 Gbps 0x1 impl platform mode
[ 4.745554] tegra-ahci 70027000.sata: flags: 64bit ncq sntf pm led pio slum part sadm sds apst
[ 4.757424] scsi host0: tegra-ahci
[ 4.761969] scsi host1: tegra-ahci
[ 4.766150] ata1: SATA max UDMA/133 mmio [mem 0x70027000-0x70028fff] port 0x100 irq 343
[ 4.774207] ata2: DUMMY
[ 4.777187] +5V_USB_HS: supplied by +5V_SYS
[ 4.782068] tegra-ehci 7d008000.usb: EHCI Host Controller
[ 4.787516] tegra-ehci 7d008000.usb: new USB bus registered, assigned bus number 2
[ 4.795458] tegra-ehci 7d008000.usb: irq 350, io mem 0x7d008000
[ 4.820926] tegra-ehci 7d008000.usb: USB 2.0 started, EHCI 1.10
[ 4.828616] hub 2-0:1.0: USB hub found
[ 4.832466] hub 2-0:1.0: 1 port detected
[ 4.837536] sdhci-tegra 700b0400.sdhci: Got CD GPIO
[ 4.842495] sdhci-tegra 700b0400.sdhci: Got WP GPIO
[ 4.847436] mmc1: Unknown controller version (3). You may experience problems.
[ 4.854816] +VDDIO_SDMMC3: supplied by +3.3V_RUN
[ 4.859585] sdhci-tegra 700b0400.sdhci: No vmmc regulator found
[ 4.865613] mmc1: Invalid maximum block size, assuming 512 bytes
[ 4.911206] mmc1: SDHCI controller on 700b0400.sdhci [700b0400.sdhci] using ADMA 64-bit
[ 4.920169] input: gpio-keys as /devices/soc0/gpio-keys/input/input2
[ 4.928600] as3722-rtc as3722-rtc: setting system clock to 2016-05-14 21:22:13 UTC (1463260933)
[ 4.956369] +USB0_VBUS_SW: disabling
[ 4.960471] ALSA device list:
[ 4.963472] #0: tegra-hda at 0x70038000 irq 344
[ 4.968181] #1: NVIDIA Tegra Jetson TK1
[ 5.120944] ata1: SATA link down (SStatus 0 SControl 300)
[ 5.141854] EXT3-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (240)
[ 5.151690] EXT2-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (240)
[ 5.171203] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[ 5.179357] VFS: Mounted root (ext4 filesystem) on device 179:1.
[ 5.190430] devtmpfs: mounted
[ 5.193779] Freeing unused kernel memory: 320K (c09b6000 - c0a06000)
[ 5.417050] random: init urandom read with 12 bits of entropy available
[ 5.569732] init: plymouth-upstart-bridge main process (85) terminated with status 1
[ 5.586487] init: plymouth-upstart-bridge main process ended, respawning
[ 5.667222] init: ureadahead main process (88) terminated with status 5
[ 5.686938] init: plymouth-upstart-bridge main process (95) terminated with status 1
[ 5.687014] init: plymouth-upstart-bridge main process ended, respawning
[ 6.631132] cfg80211: Calling CRDA to update world regulatory domain
[ 7.630343] systemd-udevd[235]: starting version 204
[ 8.192066] init: nv main process (246) terminated with status 1
[ 8.227104] init: idmapd main process (245) terminated with status 1
[ 8.251130] init: idmapd main process ended, respawning
[ 9.790972] cfg80211: Calling CRDA to update world regulatory domain
[ 10.051728] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 10.100882] systemd-udevd[279]: could not open moddep file '/lib/modules/4.1.0-196900-g02942d8/modules.dep.bin'
[ 10.140922] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 10.227793] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 10.441707] cfg80211: World regulatory domain updated:
[ 10.447218] cfg80211: DFS Master region: unset
[ 10.452014] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 10.462072] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 10.470738] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 10.479545] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 10.488926] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 10.498416] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (N/A)
[ 10.530473] init: idmapd main process (400) terminated with status 1
[ 10.536999] init: idmapd main process ended, respawning
* Starting Mount filesystems on boot [ OK ]
* Starting Signal sysvinit that the rootfs is mounted [ OK ]
* Starting Clean /tmp directory [ OK ]
* Stopping Clean /tmp directory [ OK ]
* Starting Populate and link to /run filesystem [ OK ]
* Stopping Populate and link to /run filesystem [ OK ]
* Stopping Track if upstart is running in a container [ OK ]
* Starting Initialize or finalize resolvconf [ OK ]
* Starting set console keymap [ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted [ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted [ OK ]
* Starting Bridge udev events into upstart [ OK ]
* Stopping set console keymap [ OK ]
* Starting Signal sysvinit that local filesystems are mounted [ OK ]
* Starting device node and kernel event manager [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
* Starting D-Bus system message bus [ OK ]
* Starting Signal sysvinit that remote filesystems are mounted [ OK ]
* Starting load modules from /etc/modules [ OK ]
* Starting cold plug devices [ OK ]
* Starting log initial device creation [ OK ]
* Stopping load modules from /etc/modules [ OK ]
* Starting SystemD login management service [ OK ]
* Starting flush early job output to logs [ OK ]
* Stopping Mount filesystems on boot [ OK ]
* Starting bluetooth daemon [ OK ]
* Stopping flush early job output to logs [ OK ]
* Stopping cold plug devices [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
* Stopping log initial device creation [ OK ]
* Starting userspace bootsplash [ OK ]
* Starting configure network device security [ OK ]
* Starting enable remaining boot-time encrypted block devices [ OK ]
* Stopping rpcsec_gss daemon [ OK ]
* Starting mDNS/DNS-SD daemon [ OK ]
* Stopping userspace bootsplash [ OK ]
* Starting save udev log and update rules [ OK ]
* Starting configure network device security [ OK ]
* Starting Send an event to indicate plymouth is up [ OK ]
* Starting system logging daemon [ OK ]
* Stopping save udev log and update rules [ OK ]
* Starting Reload cups, upon starting avahi-daemon to make sure remote q[ OK ]are populated
* Starting configure network device [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
[ 11.309930] init: idmapd main process (507) terminated with status 1
[ 11.317570] init: idmapd main process ended, respawning
* Stopping Send an event to indicate plymouth is up [ OK ]
* Stopping NVIDIA specific first-boot script [ OK ]
[ 11.482503] init: cups main process (509) killed by HUP signal
[ 11.489867] init: cups main process ended, respawning
* Stopping Reload cups, upon starting avahi-daemon to make sure remote q[ OK ]are populated
* Starting System V initialisation compatibility [ OK ]
* Starting modem connection manager [ OK ]
* Starting configure network device security [ OK ]
* Starting configure virtual network devices [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
[ 11.822493] init: idmapd main process (589) terminated with status 1
[ 11.832221] init: idmapd main process ended, respawning
* Starting early crypto disks... [ OK ]
* Starting network connection manager [ OK ]
* Starting NFSv4 id <-> name mapper [ OK ]
[ 12.121013] init: idmapd main process (669) terminated with status 1
[ 12.127553] init: idmapd main process ended, respawning
* Setting up X socket directories... [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device [ OK ]
* Starting configure network device [ OK ]
* Starting configure network device [ OK ]
[ 12.382992] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2
[ 12.393789] r8169 0000:01:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168g-2.fw (-2)
* Stopping System V initialisation compatibility [ OK ]
[ 12.424253] r8169 0000:01:00.0 eth0: link down
[ 12.424316] r8169 0000:01:00.0 eth0: link down
[ 12.433417] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[-- Attachment #3: tk1-xen-linux-boot-1vcpu.log --]
[-- Type: application/octet-stream, Size: 63882 bytes --]
[ 0.004026] Initializing cgroup subsys debug
[ 0.004089] CPU: Testing write buffer coherency: ok
[ 0.004431] /cpus/cpu@0 missing clock-frequency property
[ 0.004482] /cpus/cpu@1 missing clock-frequency property
[ 0.004531] /cpus/cpu@2 missing clock-frequency property
[ 0.004580] /cpus/cpu@3 missing clock-frequency property
[ 0.004601] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.004834] Xen 4.6 support found, events_irq=19 gnttab_frame=0x68000000
[ 0.005040] xen:grant_table: Grant tables using version 1 layout
[ 0.005104] Grant table initialized
[ 0.005179] xen:events: Using FIFO-based ABI
[ 0.005220] Xen: initializing cpu0
[ 0.005329] Setting up static identity map for 0xa0008440 - 0xa00084d8
[ 0.019271] Tegra Revision: A01 SKU: 129 CPU Process: 1 Core Process: 1
[ 0.029736] Xen: initializing cpu1
[ 0.029797] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.039752] Xen: initializing cpu2
[ 0.039812] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.049765] Xen:tegra-i2c 7000d000.i2c: i2c transfer timed out
[ 1.346677] tegra-i2c 7000d000.i2c: i2c transfer timed out
as3722 4-0040: ASIC_ID1 read failed: -110
[ 1.346761] as3722 4-0040: ASIC_ID1 read failed: -110
4as3722: probe of 4-0040 failed with error -110
[ 1.346923] as3722: probe of 4-0040 failed with error -110
tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517
[ 1.348047] tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517
tegra-ahci 70027000.sata: Failed to get regulators
[ 1.348113] tegra-ahci 70027000.sata: Failed to get regulators
4------------[ cut here ]------------
[ 2.346742] ------------[ cut here ]------------
4WARNING: CPU: 0 PID: 1 at drivers/spi/spi-tegra114.c:838 tegra_spi_transfer_one_message+0x44c/0x47c()
[ 2.346833] WARNING: CPU: 0 PID: 1 at drivers/spi/spi-tegra114.c:838 tegra_spi_transfer_one_message+0x44c/0x47c()
dModules linked in:[ 2.346918] Modules linked in:
dCPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.0-196899-gf6c89b7 #10
[ 2.346985] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.0-196899-gf6c89b7 #10
dHardware name: NVIDIA Tegra SoC (Flattened Device Tree)
[ 2.347058] Hardware name: NVIDIA Tegra SoC (Flattened Device Tree)
[<c0016edc>] (unwind_backtrace) from [<c0012804>] (show_stack+0x10/0x14)
[ 2.347139] [<c0016edc>] (unwind_backtrace) from [<c0012804>] (show_stack+0x10/0x14)
[<c0012804>] (show_stack) from [<c06b5e3c>] (dump_stack+0x7c/0xcc)
[ 2.347227] [<c0012804>] (show_stack) from [<c06b5e3c>] (dump_stack+0x7c/0xcc)
[<c06b5e3c>] (dump_stack) from [<c0027678>] (warn_slowpath_common+0x74/0xac)
[ 2.347319] [<c06b5e3c>] (dump_stack) from [<c0027678>] (warn_slowpath_common+0x74/0xac)
[<c0027678>] (warn_slowpath_common) from [<c00276cc>] (warn_slowpath_null+0x1c/0x24)
[ 2.347405] [<c0027678>] (warn_slowpath_common) from [<c00276cc>] (warn_slowpath_null+0x1c/0x24)
[<c00276cc>] (warn_slowpath_null) from [<c038c8ec>] (tegra_spi_transfer_one_message+0x44c/0x47c)
[ 2.347498] [<c00276cc>] (warn_slowpath_null) from [<c038c8ec>] (tegra_spi_transfer_one_message+0x44c/0x47c)
[<c038c8ec>] (tegra_spi_transfer_one_message) from [<c0389ab8>] (__spi_pump_messages+0x374/0x4f0)
[ 2.347596] [<c038c8ec>] (tegra_spi_transfer_one_message) from [<c0389ab8>] (__spi_pump_messages+0x374/0x4f0)
[<c0389ab8>] (__spi_pump_messages) from [<c0389d48>] (__spi_sync+0x114/0x120)
[ 2.347702] [<c0389ab8>] (__spi_pump_messages) from [<c0389d48>] (__spi_sync+0x114/0x120)
[<c0389d48>] (__spi_sync) from [<c0389e20>] (spi_write_then_read+0xbc/0x168)
[ 2.347784] [<c0389d48>] (__spi_sync) from [<c0389e20>] (spi_write_then_read+0xbc/0x168)
[<c0389e20>] (spi_write_then_read) from [<c0386e5c>] (m25p80_read_reg+0x34/0x64)
[ 2.347865] [<c0389e20>] (spi_write_then_read) from [<c0386e5c>] (m25p80_read_reg+0x34/0x64)
[<c0386e5c>] (m25p80_read_reg) from [<c0387544>] (spi_nor_read_id+0x20/0xb0)
[ 2.347951] [<c0386e5c>] (m25p80_read_reg) from [<c0387544>] (spi_nor_read_id+0x20/0xb0)
[<c0387544>] (spi_nor_read_id) from [<c0387b54>] (spi_nor_scan+0x4b4/0x838)
[ 2.348031] [<c0387544>] (spi_nor_read_id) from [<c0387b54>] (spi_nor_scan+0x4b4/0x838)
[<c0387b54>] (spi_nor_scan) from [<c0386da8>] (m25p_probe+0xb4/0x134)
[ 2.348110] [<c0387b54>] (spi_nor_scan) from [<c0386da8>] (m25p_probe+0xb4/0x134)
[<c0386da8>] (m25p_probe) from [<c0389498>] (spi_drv_probe+0x58/0x70)
[ 2.348206] [<c0386da8>] (m25p_probe) from [<c0389498>] (spi_drv_probe+0x58/0x70)
[<c0389498>] (spi_drv_probe) from [<c03255e0>] (driver_probe_device+0x1b4/0x26c)
[ 2.348292] [<c0389498>] (spi_drv_probe) from [<c03255e0>] (driver_probe_device+0x1b4/0x26c)
[<c03255e0>] (driver_probe_device) from [<c0323ea0>] (bus_for_each_drv+0x5c/0x88)
[ 2.348383] [<c03255e0>] (driver_probe_device) from [<c0323ea0>] (bus_for_each_drv+0x5c/0x88)
[<c0323ea0>] (bus_for_each_drv) from [<c03253bc>] (__device_attach+0x88/0xd4)
[ 2.348473] [<c0323ea0>] (bus_for_each_drv) from [<c03253bc>] (__device_attach+0x88/0xd4)
[<c03253bc>] (__device_attach) from [<c0324b7c>] (bus_probe_device+0x84/0x8c)
[ 2.348559] [<c03253bc>] (__device_attach) from [<c0324b7c>] (bus_probe_device+0x84/0x8c)
[<c0324b7c>] (bus_probe_device) from [<c03230e0>] (device_add+0x324/0x51c)
[ 2.348642] [<c0324b7c>] (bus_probe_device) from [<c03230e0>] (device_add+0x324/0x51c)
[<c03230e0>] (device_add) from [<c0389314>] (spi_add_device+0x88/0x130)
[ 2.348724] [<c03230e0>] (device_add) from [<c0389314>] (spi_add_device+0x88/0x130)
[<c0389314>] (spi_add_device) from [<c038a8a0>] (spi_register_master+0x53c/0x6f0)
[ 2.348806] [<c0389314>] (spi_add_device) from [<c038a8a0>] (spi_register_master+0x53c/0x6f0)
[<c038a8a0>] (spi_register_master) from [<c038aa84>] (devm_spi_register_master+0x30/0x64)
[ 2.348893] [<c038a8a0>] (spi_register_master) from [<c038aa84>] (devm_spi_register_master+0x30/0x64)
[<c038aa84>] (devm_spi_register_master) from [<c038b52c>] (tegra_spi_probe+0x29c/0x350)
[ 2.348998] [<c038aa84>] (devm_spi_register_master) from [<c038b52c>] (tegra_spi_probe+0x29c/0x350)
[<c038b52c>] (tegra_spi_probe) from [<c0326a98>] (platform_drv_probe+0x48/0x98)
[ 2.349086] [<c038b52c>] (tegra_spi_probe) from [<c0326a98>] (platform_drv_probe+0x48/0x98)
[<c0326a98>] (platform_drv_probe) from [<c03255e0>] (driver_probe_device+0x1b4/0x26c)
[ 2.349171] [<c0326a98>] (platform_drv_probe) from [<c03255e0>] (driver_probe_device+0x1b4/0x26c)
[<c03255e0>] (driver_probe_device) from [<c0325724>] (__driver_attach+0x8c/0x90)
[ 2.349261] [<c03255e0>] (driver_probe_device) from [<c0325724>] (__driver_attach+0x8c/0x90)
[<c0325724>] (__driver_attach) from [<c0323f20>] (bus_for_each_dev+0x54/0x88)
[ 2.349349] [<c0325724>] (__driver_attach) from [<c0323f20>] (bus_for_each_dev+0x54/0x88)
[<c0323f20>] (bus_for_each_dev) from [<c0324dd4>] (bus_add_driver+0x15c/0x1f0)
[ 2.349433] [<c0323f20>] (bus_for_each_dev) from [<c0324dd4>] (bus_add_driver+0x15c/0x1f0)
[<c0324dd4>] (bus_add_driver) from [<c0325eec>] (driver_register+0x78/0xf4)
[ 2.349518] [<c0324dd4>] (bus_add_driver) from [<c0325eec>] (driver_register+0x78/0xf4)
[<c0325eec>] (driver_register) from [<c00096e4>] (do_one_initcall+0x80/0x1d0)
[ 2.349620] [<c0325eec>] (driver_register) from [<c00096e4>] (do_one_initcall+0x80/0x1d0)
[<c00096e4>] (do_one_initcall) from [<c0956d7c>] (kernel_init_freeable+0x110/0x1dc)
[ 2.349703] [<c00096e4>] (do_one_initcall) from [<c0956d7c>] (kernel_init_freeable+0x110/0x1dc)
[<c0956d7c>] (kernel_init_freeable) from [<c06b1830>] (kernel_init+0x8/0xe4)
[ 2.349792] [<c0956d7c>] (kernel_init_freeable) from [<c06b1830>] (kernel_init+0x8/0xe4)
[<c06b1830>] (kernel_init) from [<c000fc68>] (ret_from_fork+0x14/0x2c)
[ 2.349879] [<c06b1830>] (kernel_init) from [<c000fc68>] (ret_from_fork+0x14/0x2c)
4---[ end trace 97f86a9f6079351e ]---
[ 2.349965] ---[ end trace 97f86a9f6079351e ]---
spi-tegra114 7000da00.spi: spi trasfer timeout, err 0
[ 2.350023] spi-tegra114 7000da00.spi: spi trasfer timeout, err 0
spi_master spi32765: failed to transfer one message from queue
[ 2.350099] spi_master spi32765: failed to transfer one message from queue
m25p80 spi32765.0: error -5 reading 9f
[ 2.350165] m25p80 spi32765.0: error -5 reading 9f
4m25p80: probe of spi32765.0 failed with error -5
[ 2.350235] m25p80: probe of spi32765.0 failed with error -5
6CAN device driver interface
[ 2.352326] CAN device driver interface
6igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k
[ 2.352508] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k
6igb: Copyright (c) 2007-2014 Intel Corporation.
[ 2.352574] igb: Copyright (c) 2007-2014 Intel Corporation.
6xen_netfront: Initialising Xen virtual ethernet driver
[ 2.352986] xen_netfront: Initialising Xen virtual ethernet driver
6pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[ 2.353375] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
6usbcore: registered new interface driver pegasus
[ 2.353588] usbcore: registered new interface driver pegasus
6usbcore: registered new interface driver asix
[ 2.353855] usbcore: registered new interface driver asix
6usbcore: registered new interface driver ax88179_178a
[ 2.354042] usbcore: registered new interface driver ax88179_178a
6usbcore: registered new interface driver cdc_ether
[ 2.354236] usbcore: registered new interface driver cdc_ether
6usbcore: registered new interface driver smsc75xx
[ 2.354477] usbcore: registered new interface driver smsc75xx
6usbcore: registered new interface driver smsc95xx
[ 2.354730] usbcore: registered new interface driver smsc95xx
6usbcore: registered new interface driver net1080
[ 2.354921] usbcore: registered new interface driver net1080
6usbcore: registered new interface driver cdc_subset
[ 2.355135] usbcore: registered new interface driver cdc_subset
6usbcore: registered new interface driver zaurus
[ 2.355327] usbcore: registered new interface driver zaurus
6usbcore: registered new interface driver cdc_ncm
[ 2.355576] usbcore: registered new interface driver cdc_ncm
tegra-phy 7d004000.usb-phy: no vbus regulator[ 2.355951] tegra-phy 7d004000.usb-phy: no vbus regulator
6ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.356560] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
6ehci-pci: EHCI PCI platform driver
[ 2.356713] ehci-pci: EHCI PCI platform driver
6tegra-ehci: Tegra EHCI driver
[ 2.356914] tegra-ehci: Tegra EHCI driver
tegra-ehci 7d004000.usb: EHCI Host Controller
[ 2.357346] tegra-ehci 7d004000.usb: EHCI Host Controller
tegra-ehci 7d004000.usb: new USB bus registered, assigned bus number 1
[ 2.357443] tegra-ehci 7d004000.usb: new USB bus registered, assigned bus number 1
tegra-ehci 7d004000.usb: irq 342, io mem 0x7d004000
[ 2.357844] tegra-ehci 7d004000.usb: irq 342, io mem 0x7d004000
tegra-ehci 7d004000.usb: USB 2.0 started, EHCI 1.10
[ 2.376682] tegra-ehci 7d004000.usb: USB 2.0 started, EHCI 1.10
hub 1-0:1.0: USB hub found
[ 2.378597] hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
[ 2.378700] hub 1-0:1.0: 1 port detected
6usbcore: registered new interface driver cdc_acm
[ 2.380169] usbcore: registered new interface driver cdc_acm
6cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 2.380232] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
6usbcore: registered new interface driver cdc_wdm
[ 2.380447] usbcore: registered new interface driver cdc_wdm
6usbcore: registered new interface driver usb-storage
[ 2.380725] usbcore: registered new interface driver usb-storage
6mousedev: PS/2 mouse device common for all mice
[ 2.381603] mousedev: PS/2 mouse device common for all mice
tegra_rtc 7000e000.rtc: rtc core: registered 7000e000.rtc as rtc1
[ 2.384722] tegra_rtc 7000e000.rtc: rtc core: registered 7000e000.rtc as rtc1
tegra_rtc 7000e000.rtc: Tegra internal Real Time Clock
[ 2.384900] tegra_rtc 7000e000.rtc: Tegra internal Real Time Clock
6i2c /dev entries driver
[ 2.385381] i2c /dev entries driver
6usbcore: registered new interface driver uvcvideo
[ 2.387822] usbcore: registered new interface driver uvcvideo
6USB Video Class driver (1.1.1)
[ 2.387883] USB Video Class driver (1.1.1)
6gspca_main: v2.14.0 registered
[ 2.387938] gspca_main: v2.14.0 registered
40-004c supply vcc not found, using dummy regulator
[ 2.388812] 0-004c supply vcc not found, using dummy regulator
6cfg80211: Calling CRDA to update world regulatory domain
[ 3.376758] cfg80211: Calling CRDA to update world regulatory domain
tegra-i2c 7000c000.i2c: i2c transfer timed out
[ 3.386691] tegra-i2c 7000c000.i2c: i2c transfer timed out
lm90 0-004c: Register 0x4 read failed (-110)
[ 3.386776] lm90 0-004c: Register 0x4 read failed (-110)
lm90 0-004c: Failed to read convrate register!
[ 3.386831] lm90 0-004c: Failed to read convrate register!
tegra-i2c 7000c000.i2c: i2c transfer timed out
[ 4.386672] tegra-i2c 7000c000.i2c: i2c transfer timed out
tegra-i2c 7000c000.i2c: i2c transfer timed out
[ 5.386672] tegra-i2c 7000c000.i2c: i2c transfer timed out
lm90 0-004c: Register 0x3 read failed (-110)
[ 5.386752] lm90 0-004c: Register 0x3 read failed (-110)
lm90 0-004c: Initialization failed!
[ 5.386807] lm90 0-004c: Initialization failed!
6sdhci: Secure Digital Host Controller Interface driver
[ 5.388315] sdhci: Secure Digital Host Controller Interface driver
6sdhci: Copyright(c) Pierre Ossman
[ 5.388376] sdhci: Copyright(c) Pierre Ossman
6sdhci-pltfm: SDHCI platform and OF driver helper
[ 5.388438] sdhci-pltfm: SDHCI platform and OF driver helper
sdhci-tegra 700b0400.sdhci: Got CD GPIO
[ 5.388891] sdhci-tegra 700b0400.sdhci: Got CD GPIO
sdhci-tegra 700b0400.sdhci: Got WP GPIO
[ 5.388966] sdhci-tegra 700b0400.sdhci: Got WP GPIO
3mmc0: Unknown controller version (3). You may experience problems.
[ 5.389078] mmc0: Unknown controller version (3). You may experience problems.
sdhci-tegra 700b0400.sdhci: No vmmc regulator found
[ 5.389292] sdhci-tegra 700b0400.sdhci: No vmmc regulator found
3mmc0: Unknown controller version (3). You may experience problems.
[ 5.389580] mmc0: Unknown controller version (3). You may experience problems.
sdhci-tegra 700b0600.sdhci: No vmmc regulator found
[ 5.389718] sdhci-tegra 700b0600.sdhci: No vmmc regulator found
sdhci-tegra 700b0600.sdhci: No vqmmc regulator found
[ 5.389781] sdhci-tegra 700b0600.sdhci: No vqmmc regulator found
4mmc0: Invalid maximum block size, assuming 512 bytes
[ 5.389842] mmc0: Invalid maximum block size, assuming 512 bytes
6mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit
[ 5.436694] mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit
6usbcore: registered new interface driver usbhid
[ 5.437914] usbcore: registered new interface driver usbhid
6usbhid: USB HID core driver
[ 5.437970] usbhid: USB HID core driver
6cfg80211: Calling CRDA to update world regulatory domain
[ 6.536756] cfg80211: Calling CRDA to update world regulatory domain
tegra-hda 70030000.hda: azx_get_response timeout, switching to polling mode: last cmd=0x300f0001
[ 8.526785] 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.968581] input: tegra-hda HDMI/DP,pcm=3 as /devices/soc0/70030000.hda/sound/card0/input0
6cfg80211: Calling CRDA to update world regulatory domain
[ 9.696757] cfg80211: Calling CRDA to update world regulatory domain
tegra-i2c 7000c000.i2c:
U-Boot SPL 2016.05-rc3-00070-g4baca92-dirty (May 12 2016 - 19:10:02)
Trying to boot from RAM
U-Boot 2016.05-rc3-00070-g4baca92-dirty (May 12 2016 - 19:10:02 -0400)
TEGRA124
Model: NVIDIA Jetson TK1
Board: NVIDIA Jetson TK1
DRAM: 2 GiB
MC: Tegra SD/MMC: 0, Tegra SD/MMC: 1
In: serial
Out: serial
Err: serial
Net: No ethernet found.
Hit any key to stop autoboot: 0
Tegra124 (Jetson TK1) # fdt addr $fdt_addr_r
Tegra124 (Jetson TK1) # ext2load mmc 0:1 ${xen_addr_r} /boot/xen-4.6-unstable
721776 bytes read in 406 ms (1.7 MiB/s)
Tegra124 (Jetson TK1) #
Tegra124 (Jetson TK1) # ext2load mmc 0:1 ${kernel_addr_r} /boot/zImage-psci-xen-xendrivers
5161216 bytes read in 463 ms (10.6 MiB/s)
Tegra124 (Jetson TK1) #
Tegra124 (Jetson TK1) # setenv bootargs "console=dtuart dtuart=serial0 dom0_mem=512M"
Tegra124 (Jetson TK1) #
Tegra124 (Jetson TK1) # setenv bootargs "console=dtuart dtuart=serial0 dom0_mem=512M loglvl=all guest_loglvl=all dom0_max_vcpus=
1 dom0_vcpus_pin"
Tegra124 (Jetson TK1) #
Tegra124 (Jetson TK1) # fdt set /chosen xen,xen-bootargs "console=dtuart dtuart=serial0 dom0_mem=512M loglvl=all guest_loglvl=al
l dom0_max_vcpus=1 dom0_vcpus_pin"
Tegra124 (Jetson TK1) # fdt print /chosen
chosen {
xen,xen-bootargs = "console=dtuart dtuart=serial0 dom0_mem=512M loglvl=all guest_loglvl=all dom0_max_vcpus=1 dom0_vcpus_
pin";
bootargs = "console=dtuart dtuart=serial0 dom0_mem=512M";
module {
bootargs = "console=hvc0 console=tty1 earlyprintk=xen root=/dev/mmcblk0p1 rw rootwait";
reg = <0x00000000 0x81000000 0x00000000 0x004ec100>;
compatible = "xen,linux-zimage", "xen,multiboot-module";
};
};
Tegra124 (Jetson TK1) # bootz $xen_addr_r - $fdt_addr_r
Kernel image @ 0xfd000000 [ 0x000000 - 0x0f9700 ]
## Flattened Device Tree blob at 82000000
Booting using the fdt blob at 0x82000000
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 - 00000000814ec100 Kernel console=hvc0 console=tty1 earlyprintk=xen root=/dev/mmcblk0p1
rw rootwait
(XEN) RESVD[0]: 0000000082000000 - 0000000082010000
(XEN)
(XEN) Command line: console=dtuart dtuart=serial0 dom0_mem=512M loglvl=all guest_loglvl=all dom0_max_vcpus=1 dom0_vcpus_pin
(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@localdomain) (arm-linux-gnueabi-gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3) debug=y Sat May 1
4 16:33:06 EDT 2016
(XEN) Latest ChangeSet: Sat May 14 14:47:57 2016 -0400 git:7051e90-dirty
(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) handle /
(XEN) / nirq = 0 naddr = 0
(XEN) handle /psci
(XEN) Skip it (matched)
(XEN) handle /chosen
(XEN) /chosen nirq = 0 naddr = 0
(XEN) handle /chosen/module
(XEN) Skip it (matched)
(XEN) handle /aliases
(XEN) /aliases nirq = 0 naddr = 0
(XEN) handle /memory
(XEN) Skip it (matched)
(XEN) handle /pcie-controller@0,01003000
(XEN) /pcie-controller@0,01003000 nirq = 2 naddr = 3
(XEN) irq 0 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 1 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) addr 0 = 0x1003000 - 0x10037ff
(XEN) addr 1 = 0x1003800 - 0x1003fff
(XEN) addr 2 = 0x2000000 - 0x11ffffff
(XEN) handle /pcie-controller@0,01003000/pci@1,0
(XEN) handle /pcie-controller@0,01003000/pci@2,0
(XEN) handle /host1x@0,50000000
(XEN) /host1x@0,50000000 nirq = 2 naddr = 1
(XEN) irq 0 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 1 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) addr 0 = 0x50000000 - 0x50033fff
(XEN) handle /host1x@0,50000000/dc@0,54200000
(XEN) handle /host1x@0,50000000/dc@0,54240000
(XEN) handle /host1x@0,50000000/hdmi@0,54280000
(XEN) handle /host1x@0,50000000/sor@0,54540000
(XEN) handle /host1x@0,50000000/dpaux@0,545c0000
(XEN) handle /interrupt-controller@0,50041000
(XEN) Create gic node
(XEN) Set phandle = 0x2
(XEN) handle /gpu@0,57000000
(XEN) /gpu@0,57000000 nirq = 2 naddr = 2
(XEN) irq 0 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 1 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) addr 0 = 0x57000000 - 0x57ffffff
(XEN) addr 1 = 0x58000000 - 0x58ffffff
(XEN) handle /interrupt-controller@60004000
(XEN) /interrupt-controller@60004000 nirq = 0 naddr = 5
(XEN) addr 0 = 0x60004000 - 0x600040ff
(XEN) addr 1 = 0x60004100 - 0x600041ff
(XEN) addr 2 = 0x60004200 - 0x600042ff
(XEN) addr 3 = 0x60004300 - 0x600043ff
(XEN) addr 4 = 0x60004400 - 0x600044ff
(XEN) handle /timer@0,60005000
(XEN) Skip it (blacklisted)
(XEN) handle /clock@0,60006000
(XEN) /clock@0,60006000 nirq = 0 naddr = 1
(XEN) addr 0 = 0x60006000 - 0x60006fff
(XEN) handle /clock@0,60006000/emc-timings-3
(XEN) /clock@0,60006000/emc-timings-3 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-12750000
(XEN) /clock@0,60006000/emc-timings-3/timing-12750000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-20400000
(XEN) /clock@0,60006000/emc-timings-3/timing-20400000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-40800000
(XEN) /clock@0,60006000/emc-timings-3/timing-40800000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-68000000
(XEN) /clock@0,60006000/emc-timings-3/timing-68000000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-102000000
(XEN) /clock@0,60006000/emc-timings-3/timing-102000000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-204000000
(XEN) /clock@0,60006000/emc-timings-3/timing-204000000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-300000000
(XEN) /clock@0,60006000/emc-timings-3/timing-300000000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-396000000
(XEN) /clock@0,60006000/emc-timings-3/timing-396000000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-528000000
(XEN) /clock@0,60006000/emc-timings-3/timing-528000000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-600000000
(XEN) /clock@0,60006000/emc-timings-3/timing-600000000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-792000000
(XEN) /clock@0,60006000/emc-timings-3/timing-792000000 nirq = 0 naddr = 0
(XEN) handle /clock@0,60006000/emc-timings-3/timing-924000000
(XEN) /clock@0,60006000/emc-timings-3/timing-924000000 nirq = 0 naddr = 0
(XEN) handle /flow-controller@0,60007000
(XEN) /flow-controller@0,60007000 nirq = 0 naddr = 1
(XEN) addr 0 = 0x60007000 - 0x60007fff
(XEN) handle /actmon@0,6000c800
(XEN) /actmon@0,6000c800 nirq = 1 naddr = 1
(XEN) irq 0 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) addr 0 = 0x6000c800 - 0x6000cbff
(XEN) handle /gpio@0,6000d000
(XEN) /gpio@0,6000d000 nirq = 8 naddr = 1
(XEN) irq 0 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 1 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 2 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 3 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 4 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 5 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 6 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 7 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) addr 0 = 0x6000d000 - 0x6000dfff
(XEN) handle /dma@0,60020000
(XEN) /dma@0,60020000 nirq = 32 naddr = 1
(XEN) irq 0 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 1 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 2 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 3 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 4 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 5 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 6 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 7 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 8 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 9 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 10 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 11 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 12 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 13 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 14 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 15 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 16 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 17 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 18 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 19 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 20 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 21 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 22 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 23 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 24 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 25 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 26 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 27 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 28 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 29 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 30 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) irq 31 not connected to primary controller.Connected to /interrupt-controller@60004000
(XEN) addr 0 = 0x60020000 - 0x600213ff
(XEN) handle /apbmisc@0,70000800
(XEN) /apbmisc@0,70000800 nirq = 0 naddr = 2
(XEN) addr 0 = 0x70000800 - 0x70000863
(XEN) addr 1 = 0x7000e864 - 0x7000e867
(XEN) handle /pinmux@0,70000868
(XEN) /pinmux@0,70000868 nirq = 0 naddr = 3
(XEN) addr 0 = 0x70000868 - 0x700009cb
(XEN) addr 1 = 0x70003000 - 0x70003433
(XEN) addr 2 = 0x70000820 - 0x70000827
(XEN) handle /pinmux@0,70000868/pinmux
(XEN) /pinmux@0,70000868/pinmux nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/clk_32k_out_pa0
(XEN) /pinmux@0,70000868/pinmux/clk_32k_out_pa0 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/uart3_cts_n_pa1
(XEN) /pinmux@0,70000868/pinmux/uart3_cts_n_pa1 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/dap2_fs_pa2
(XEN) /pinmux@0,70000868/pinmux/dap2_fs_pa2 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/dap2_sclk_pa3
(XEN) /pinmux@0,70000868/pinmux/dap2_sclk_pa3 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/dap2_din_pa4
(XEN) /pinmux@0,70000868/pinmux/dap2_din_pa4 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/dap2_dout_pa5
(XEN) /pinmux@0,70000868/pinmux/dap2_dout_pa5 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/sdmmc3_clk_pa6
(XEN) /pinmux@0,70000868/pinmux/sdmmc3_clk_pa6 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/sdmmc3_cmd_pa7
(XEN) /pinmux@0,70000868/pinmux/sdmmc3_cmd_pa7 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pb0
(XEN) /pinmux@0,70000868/pinmux/pb0 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pb1
(XEN) /pinmux@0,70000868/pinmux/pb1 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/sdmmc3_dat3_pb4
(XEN) /pinmux@0,70000868/pinmux/sdmmc3_dat3_pb4 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/sdmmc3_dat2_pb5
(XEN) /pinmux@0,70000868/pinmux/sdmmc3_dat2_pb5 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/sdmmc3_dat1_pb6
(XEN) /pinmux@0,70000868/pinmux/sdmmc3_dat1_pb6 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/sdmmc3_dat0_pb7
(XEN) /pinmux@0,70000868/pinmux/sdmmc3_dat0_pb7 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/uart3_rts_n_pc0
(XEN) /pinmux@0,70000868/pinmux/uart3_rts_n_pc0 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/uart2_txd_pc2
(XEN) /pinmux@0,70000868/pinmux/uart2_txd_pc2 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/uart2_rxd_pc3
(XEN) /pinmux@0,70000868/pinmux/uart2_rxd_pc3 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/gen1_i2c_scl_pc4
(XEN) /pinmux@0,70000868/pinmux/gen1_i2c_scl_pc4 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/gen1_i2c_sda_pc5
(XEN) /pinmux@0,70000868/pinmux/gen1_i2c_sda_pc5 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pc7
(XEN) /pinmux@0,70000868/pinmux/pc7 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pg0
(XEN) /pinmux@0,70000868/pinmux/pg0 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pg1
(XEN) /pinmux@0,70000868/pinmux/pg1 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pg2
(XEN) /pinmux@0,70000868/pinmux/pg2 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pg3
(XEN) /pinmux@0,70000868/pinmux/pg3 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pg4
(XEN) /pinmux@0,70000868/pinmux/pg4 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pg5
(XEN) /pinmux@0,70000868/pinmux/pg5 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pg6
(XEN) /pinmux@0,70000868/pinmux/pg6 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pg7
(XEN) /pinmux@0,70000868/pinmux/pg7 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ph0
(XEN) /pinmux@0,70000868/pinmux/ph0 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ph1
(XEN) /pinmux@0,70000868/pinmux/ph1 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ph2
(XEN) /pinmux@0,70000868/pinmux/ph2 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ph3
(XEN) /pinmux@0,70000868/pinmux/ph3 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ph4
(XEN) /pinmux@0,70000868/pinmux/ph4 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ph5
(XEN) /pinmux@0,70000868/pinmux/ph5 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ph6
(XEN) /pinmux@0,70000868/pinmux/ph6 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ph7
(XEN) /pinmux@0,70000868/pinmux/ph7 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pi0
(XEN) /pinmux@0,70000868/pinmux/pi0 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pi1
(XEN) /pinmux@0,70000868/pinmux/pi1 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pi2
(XEN) /pinmux@0,70000868/pinmux/pi2 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pi3
(XEN) /pinmux@0,70000868/pinmux/pi3 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pi4
(XEN) /pinmux@0,70000868/pinmux/pi4 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pi5
(XEN) /pinmux@0,70000868/pinmux/pi5 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pi6
(XEN) /pinmux@0,70000868/pinmux/pi6 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pi7
(XEN) /pinmux@0,70000868/pinmux/pi7 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pj0
(XEN) /pinmux@0,70000868/pinmux/pj0 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pj2
(XEN) /pinmux@0,70000868/pinmux/pj2 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/uart2_cts_n_pj5
(XEN) /pinmux@0,70000868/pinmux/uart2_cts_n_pj5 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/uart2_rts_n_pj6
(XEN) /pinmux@0,70000868/pinmux/uart2_rts_n_pj6 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pj7
(XEN) /pinmux@0,70000868/pinmux/pj7 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pk0
(XEN) /pinmux@0,70000868/pinmux/pk0 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pk1
(XEN) /pinmux@0,70000868/pinmux/pk1 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pk2
(XEN) /pinmux@0,70000868/pinmux/pk2 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pk3
(XEN) /pinmux@0,70000868/pinmux/pk3 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pk4
(XEN) /pinmux@0,70000868/pinmux/pk4 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/spdif_out_pk5
(XEN) /pinmux@0,70000868/pinmux/spdif_out_pk5 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/spdif_in_pk6
(XEN) /pinmux@0,70000868/pinmux/spdif_in_pk6 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/pk7
(XEN) /pinmux@0,70000868/pinmux/pk7 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/dap1_fs_pn0
(XEN) /pinmux@0,70000868/pinmux/dap1_fs_pn0 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/dap1_din_pn1
(XEN) /pinmux@0,70000868/pinmux/dap1_din_pn1 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/dap1_dout_pn2
(XEN) /pinmux@0,70000868/pinmux/dap1_dout_pn2 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/dap1_sclk_pn3
(XEN) /pinmux@0,70000868/pinmux/dap1_sclk_pn3 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/usb_vbus_en0_pn4
(XEN) /pinmux@0,70000868/pinmux/usb_vbus_en0_pn4 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/usb_vbus_en1_pn5
(XEN) /pinmux@0,70000868/pinmux/usb_vbus_en1_pn5 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/hdmi_int_pn7
(XEN) /pinmux@0,70000868/pinmux/hdmi_int_pn7 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ulpi_data7_po0
(XEN) /pinmux@0,70000868/pinmux/ulpi_data7_po0 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ulpi_data0_po1
(XEN) /pinmux@0,70000868/pinmux/ulpi_data0_po1 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ulpi_data1_po2
(XEN) /pinmux@0,70000868/pinmux/ulpi_data1_po2 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ulpi_data2_po3
(XEN) /pinmux@0,70000868/pinmux/ulpi_data2_po3 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,70000868/pinmux/ulpi_data3_po4
(XEN) /pinmux@0,70000868/pinmux/ulpi_data3_po4 nirq = 0 naddr = 0
(XEN) handle /pinmux@0,700(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-196899-gf6c89b7 (root@menglab6c) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5
) ) #10 SM
(XEN) DOM0: P PREEMPT Fri May 13 21:19:55 EDT 2016
(XEN) DOM0: [ 0.000000] CPU: ARMv7 Processor [413fc0f3] revision 3 (ARMv7), cr=10c5387d
(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 0xbc000000
(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 11 pages/cpu @dbb9c000 s15808 r8192 d21056 u45056
(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
(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: 443216K/524288K available (7109K kernel code, 350K rwdata, 2416K rodata, 312K init, 374K bss,
15536K 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 - 0xc095595c (9527 kB)
(XEN) DOM0: [ 0.000000] .init : 0xc0956000 - 0xc09a4000 ( 312 kB)
(XEN) DOM0: [ 0.000000] .data : 0xc09a4000 - 0xc09fbb40 ( 351 kB)
(XEN) DOM0: [ 0.000000] .bss : 0xc09fe000 - 0xc0a5ba94 ( 375 kB)
(XEN) DOM0: [ 0.000000] Preemptible hierarchical RCU implementation.
(XEN) DOM0: [ 0.000000] Additional per-CPU info printed with stalls.
(XEN) DOM0: [ 0.000000] Build-time adjustment of leaf fanout to 32.
(XEN) DOM0: [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
(XEN) DOM0: [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=1
(XEN) DOM0: [ 0.000000] NR_IRQS:16 nr_irqs:16 16
(XEN) DOM0: [ 0.000000] /interrupt-controller@60004000: 160 interrupts forwarded to /interrupt-controller
(XEN) DOM0: [ 0.000000] L2C: failed to init: -19
(XEN) DOM0: [ 0.000000] Architected cp15 timer(s) running at 12.00MHz (virt).
(XEN) DOM0: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2c47f4ee7, max_idle_ns: 440795202
497 ns
(XEN) DOM0: [ 0.000006] sched_clock: 56 bits at 12MHz, resolution 83ns, wraps every 4398046511096ns
(XEN) DOM0: [ 0.000496] Switching to timer-based delay loop, resolution 83ns
(XEN) DOM0: [ 0.001194] Console: colour dummy device 80x30
(XEN) DOM0: [ 0.001474] console [tty1] enabled
(XEN) DOM0: [ 0.001697] bootconsole [earlycon0] disabled
6xen:grant_table: Grant tables using version 1 layout
Grant table initialized
6xen:events: Using FIFO-based ABI
6Xen: initializing cpu0
6Setting up static identity map for 0xa0008440 - 0xa00084d8
6Tegra Revision: A01 SKU: 129 CPU Process: 1 Core Process: 1
6Brought up 1 CPUs
6SMP: Total of 1 processors activated (24.00 BogoMIPS).
6CPU: All CPU(s) started in SVC mode.
6devtmpfs: initialized
6VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
6clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
6pinctrl core: initialized pinctrl subsystem
6NET: Registered protocol family 16
6DMA: preallocated 256 KiB pool for atomic coherent allocations
4xen:swiotlb_xen: Warning: only able to allocate 4 MB for software IO TLB
6software IO TLB [mem 0xbac00000-0xbb000000] (4MB) mapped at [dac00000-daffffff]
6No ATAGs?4hw-breakpoint: Failed to enable monitor mode on CPU 0.
6xen:balloon: Initialising balloon driver
6xen_balloon: Initialising balloon driver
3+USB0_VBUS_SW: Failed to request enable GPIO108: -517
reg-fixed-voltage regulators:regulator@7: Failed to register regulator: -517
3+5V_USB_HS: Failed to request enable GPIO109: -517
reg-fixed-voltage regulators:regulator@8: Failed to register regulator: -517
3+1.05V_RUN_AVDD_HDMI_PLL: Failed to request enable GPIO63: -517
reg-fixed-voltage regulators:regulator@11: Failed to register regulator: -517
3+5V_HDMI_CON: Failed to request enable GPIO86: -517
reg-fixed-voltage regulators:regulator@12: Failed to register regulator: -517
3+5V_SATA: Failed to request enable GPIO242: -517
reg-fixed-voltage regulators:regulator@13: Failed to register regulator: -517
3+12V_SATA: Failed to request enable GPIO242: -517
reg-fixed-voltage regulators:regulator@14: Failed to register regulator: -517
6vgaarb: loaded
5SCSI subsystem initialized
7libata version 3.00 loaded.
6usbcore: registered new interface driver usbfs
6usbcore: registered new interface driver hub
6usbcore: registered new device driver usb
6Linux video capture interface: v2.00
6pps_core: LinuxPPS API ver. 1 registered
6pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
6PTP clock support registered
6Advanced Linux Sound Architecture Driver Initialized.
6Bluetooth: Core ver 2.20
6NET: Registered protocol family 31
6Bluetooth: HCI device and connection manager initialized
6Bluetooth: HCI socket layer initialized
6Bluetooth: L2CAP socket layer initialized
6Bluetooth: SCO socket layer initialized
6cfg80211: Calling CRDA to update world regulatory domain
6clocksource: Switched to clocksource arch_sys_counter
6NET: Registered protocol family 2
6TCP established hash table entries: 4096 (order: 2, 16384 bytes)
6TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
6TCP: Hash tables configured (established 4096 bind 4096)
6UDP hash table entries: 256 (order: 1, 8192 bytes)
6UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
6NET: Registered protocol family 1
6RPC: Registered named UNIX socket transport module.
6RPC: Registered udp transport module.
6RPC: Registered tcp transport module.
6RPC: Registered tcp NFSv4.1 backchannel transport module.
7PCI: CLS 0 bytes, default 64
6futex hash table entries: 256 (order: 2, 16384 bytes)
6squashfs: version 4.0 (2009/01/31) Phillip Lougher
6io scheduler noop registered (default)
tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration
tegra-pcie 1003000.pcie-controller: Failed to get supply 'avddio-pex': -517
tegra-apbdma 60020000.dma: Tegra20 APB DMA driver register 32 channels
tegra-pmc 7000e400.pmc: emergency thermal reset enabled
6xen:xen_evtchn: Event-channel device installed
[ 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-196899-gf6c89b7 (root@menglab6c) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #10 SMP
PREEMPT Fri May 13 21:19:55 EDT 2016
[ 0.000000] CPU: ARMv7 Processor [413fc0f3] revision 3 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] Machine model: NVIDIA Tegra124 Jetson TK1
[ 0.000000] bootconsole [earlycon0] enabled
[ 0.000000] cma: Reserved 64 MiB at 0xbc000000
[ 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 11 pages/cpu @dbb9c000 s15808 r8192 d21056 u45056
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
[ 0.000000] Kernel command line: console=hvc0 console=tty1 earlyprintk=xen 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: 443216K/524288K available (7109K kernel code, 350K rwdata, 2416K rodata, 312K init, 374K bss, 15536K rese
rved, 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 - 0xc095595c (9527 kB)
[ 0.000000] .init : 0xc0956000 - 0xc09a4000 ( 312 kB)
[ 0.000000] .data : 0xc09a4000 - 0xc09fbb40 ( 351 kB)
[ 0.000000] .bss : 0xc09fe000 - 0xc0a5ba94 ( 375 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Additional per-CPU info printed with stalls.
[ 0.000000] Build-time adjustment of leaf fanout to 32.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=1
[ 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.000006] sched_clock: 56 bits at 12MHz, resolution 83ns, wraps every 4398046511096ns
[ 0.000496] Switching to timer-based delay loop, resolution 83ns
[ 0.001194] Console: colour dummy device 80x30
[ 0.001474] console [tty1] enabled
[ 0.001697] bootconsole [earlycon0] disabled
[ 0.001996] Calibrating delay loop (skipped), value calculated using timer frequency.. 24.00 BogoMIPS (lpj=120000)
[ 0.002029] pid_max: default: 32768 minimum: 301
[ 0.002320] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.002342] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.003724] Initializing cgroup subsys freezer
[ 0.003759] Initializing cgroup subsys debug
[ 0.003822] CPU: Testing write buffer coherency: ok
[ 0.004151] /cpus/cpu@0 missing clock-frequency property
[ 0.004174] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.004401] Xen 4.6 support found, events_irq=19 gnttab_frame=0x68000000
[ 0.004632] xen:grant_table: Grant tables using version 1 layout
[ 0.0tegra-i2c 7000d000.i2c: i2c transfer timed out
[ 1.294942] tegra-i2c 7000d000.i2c: i2c transfer timed out
as3722 4-0040: ASIC_ID1 read failed: -110
[ 1.295025] as3722 4-0040: ASIC_ID1 read failed: -110
4as3722: probe of 4-0040 failed with error -110
[ 1.295181] as3722: probe of 4-0040 failed with error -110
tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517
[ 1.296241] tegra-ahci 70027000.sata: Failed to get supply 'avdd': -517
tegra-ahci 70027000.sata: Failed to get regulators
[ 1.296308] tegra-ahci 70027000.sata: Failed to get regulators
4------------[ cut here ]------------
[ 2.295006] ------------[ cut here ]------------
4WARNING: CPU: 0 PID: 1 at drivers/spi/spi-tegra114.c:838 tegra_spi_transfer_one_message+0x44c/0x47c()
[ 2.295096] WARNING: CPU: 0 PID: 1 at drivers/spi/spi-tegra114.c:838 tegra_spi_transfer_one_message+0x44c/0x47c()
dModules linked in:[ 2.295181] Modules linked in:
dCPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.0-196899-gf6c89b7 #10
[ 2.295247] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.0-196899-gf6c89b7 #10
dHardware name: NVIDIA Tegra SoC (Flattened Device Tree)
[ 2.295321] Hardware name: NVIDIA Tegra SoC (Flattened Device Tree)
[<c0016edc>] (unwind_backtrace) from [<c0012804>] (show_stack+0x10/0x14)
[ 2.295400] [<c0016edc>] (unwind_backtrace) from [<c0012804>] (show_stack+0x10/0x14)
[<c0012804>] (show_stack) from [<c06b5e3c>] (dump_stack+0x7c/0xcc)
[ 2.295490] [<c0012804>] (show_stack) from [<c06b5e3c>] (dump_stack+0x7c/0xcc)
[<c06b5e3c>] (dump_stack) from [<c0027678>] (warn_slowpath_common+0x74/0xac)
[ 2.295578] [<c06b5e3c>] (dump_stack) from [<c0027678>] (warn_slowpath_common+0x74/0xac)
[<c0027678>] (warn_slowpath_common) from [<c00276cc>] (warn_slowpath_null+0x1c/0x24)
[ 2.295665] [<c0027678>] (warn_slowpath_common) from [<c00276cc>] (warn_slowpath_null+0x1c/0x24)
[<c00276cc>] (warn_slowpath_null) from [<c038c8ec>] (tegra_spi_transfer_one_message+0x44c/0x47c)
[ 2.295758] [<c00276cc>] (warn_slowpath_null) from [<c038c8ec>] (tegra_spi_transfer_one_message+0x44c/0x47c)
[<c038c8ec>] (tegra_spi_transfer_one_message) from [<c0389ab8>] (__spi_pump_messages+0x374/0x4f0)
[ 2.295856] [<c038c8ec>] (tegra_spi_transfer_one_message) from [<c0389ab8>] (__spi_pump_messages+0x374/0x4f0)
[<c0389ab8>] (__spi_pump_messages) from [<c0389d48>] (__spi_sync+0x114/0x120)
[ 2.295950] [<c0389ab8>] (__spi_pump_messages) from [<c0389d48>] (__spi_sync+0x114/0x120)
[<c0389d48>] (__spi_sync) from [<c0389e20>] (spi_write_then_read+0xbc/0x168)
[ 2.296031] [<c0389d48>] (__spi_sync) from [<c0389e20>] (spi_write_then_read+0xbc/0x168)
[<c0389e20>] (spi_write_then_read) from [<c0386e5c>] (m25p80_read_reg+0x34/0x64)
[ 2.296112] [<c0389e20>] (spi_write_then_read) from [<c0386e5c>] (m25p80_read_reg+0x34/0x64)
[<c0386e5c>] (m25p80_read_reg) from [<c0387544>] (spi_nor_read_id+0x20/0xb0)
[ 2.296198] [<c0386e5c>] (m25p80_read_reg) from [<c0387544>] (spi_nor_read_id+0x20/0xb0)
[<c0387544>] (spi_nor_read_id) from [<c0387b54>] (spi_nor_scan+0x4b4/0x838)
[ 2.296278] [<c0387544>] (spi_nor_read_id) from [<c0387b54>] (spi_nor_scan+0x4b4/0x838)
[<c0387b54>] (spi_nor_scan) from [<c0386da8>] (m25p_probe+0xb4/0x134)
[ 2.296357] [<c0387b54>] (spi_nor_scan) from [<c0386da8>] (m25p_probe+0xb4/0x134)
[<c0386da8>] (m25p_probe) from [<c0389498>] (spi_drv_probe+0x58/0x70)
[ 2.296454] [<c0386da8>] (m25p_probe) from [<c0389498>] (spi_drv_probe+0x58/0x70)
[<c0389498>] (spi_drv_probe) from [<c03255e0>] (driver_probe_device+0x1b4/0x26c)
[ 2.296540] [<c0389498>] (spi_drv_probe) from [<c03255e0>] (driver_probe_device+0x1b4/0x26c)
[<c03255e0>] (driver_probe_device) from [<c0323ea0>] (bus_for_each_drv+0x5c/0x88)
[ 2.296630] [<c03255e0>] (driver_probe_device) from [<c0323ea0>] (bus_for_each_drv+0x5c/0x88)
[<c0323ea0>] (bus_for_each_drv) from [<c03253bc>] (__device_attach+0x88/0xd4)
[ 2.296720] [<c0323ea0>] (bus_for_each_drv) from [<c03253bc>] (__device_attach+0x88/0xd4)
[<c03253bc>] (__device_attach) from [<c0324b7c>] (bus_probe_device+0x84/0x8c)
[ 2.296804] [<c03253bc>] (__device_attach) from [<c0324b7c>] (bus_probe_device+0x84/0x8c)
[<c0324b7c>] (bus_probe_device) from [<c03230e0>] (device_add+0x324/0x51c)
[ 2.296887] [<c0324b7c>] (bus_probe_device) from [<c03230e0>] (device_add+0x324/0x51c)
[<c03230e0>] (device_add) from [<c0389314>] (spi_add_device+0x88/0x130)
[ 2.296968] [<c03230e0>] (device_add) from [<c0389314>] (spi_add_device+0x88/0x130)
[<c0389314>] (spi_add_device) from [<c038a8a0>] (spi_register_master+0x53c/0x6f0)
[ 2.297049] [<c0389314>] (spi_add_device) from [<c038a8a0>] (spi_register_master+0x53c/0x6f0)
[<c038a8a0>] (spi_register_master) from [<c038aa84>] (devm_spi_register_master+0x30/0x64)
[ 2.297136] [<c038a8a0>] (spi_register_master) from [<c038aa84>] (devm_spi_register_master+0x30/0x64)
[<c038aa84>] (devm_spi_register_master) from [<c038b52c>] (tegra_spi_probe+0x29c/0x350)
[ 2.297225] [<c038aa84>] (devm_spi_register_master) from [<c038b52c>] (tegra_spi_probe+0x29c/0x350)
[<c038b52c>] (tegra_spi_probe) from [<c0326a98>] (platform_drv_probe+0x48/0x98)
[ 2.297313] [<c038b52c>] (tegra_spi_probe) from [<c0326a98>] (platform_drv_probe+0x48/0x98)
[<c0326a98>] (platform_drv_probe) from [<c03255e0>] (driver_probe_device+0x1b4/0x26c)
[ 2.297396] [<c0326a98>] (platform_drv_probe) from [<c03255e0>] (driver_probe_device+0x1b4/0x26c)
[<c03255e0>] (driver_probe_device) from [<c0325724>] (__driver_attach+0x8c/0x90)
[ 2.297487] [<c03255e0>] (driver_probe_device) from [<c0325724>] (__driver_attach+0x8c/0x90)
[<c0325724>] (__driver_attach) from [<c0323f20>] (bus_for_each_dev+0x54/0x88)
[ 2.297575] [<c0325724>] (__driver_attach) from [<c0323f20>] (bus_for_each_dev+0x54/0x88)
[<c0323f20>] (bus_for_each_dev) from [<c0324dd4>] (bus_add_driver+0x15c/0x1f0)
[ 2.297659] [<c0323f20>] (bus_for_each_dev) from [<c0324dd4>] (bus_add_driver+0x15c/0x1f0)
[<c0324dd4>] (bus_add_driver) from [<c0325eec>] (driver_register+0x78/0xf4)
[ 2.297743] [<c0324dd4>] (bus_add_driver) from [<c0325eec>] (driver_register+0x78/0xf4)
[<c0325eec>] (driver_register) from [<c00096e4>] (do_one_initcall+0x80/0x1d0)
[ 2.297845] [<c0325eec>] (driver_register) from [<c00096e4>] (do_one_initcall+0x80/0x1d0)
[<c00096e4>] (do_one_initcall) from [<c0956d7c>] (kernel_init_freeable+0x110/0x1dc)
[ 2.297927] [<c00096e4>] (do_one_initcall) from [<c0956d7c>] (kernel_init_freeable+0x110/0x1dc)
[<c0956d7c>] (kernel_init_freeable) from [<c06b1830>] (kernel_init+0x8/0xe4)
[ 2.298016] [<c0956d7c>] (kernel_init_freeable) from [<c06b1830>] (kernel_init+0x8/0xe4)
[<c06b1830>] (kernel_init) from [<c000fc68>] (ret_from_fork+0x14/0x2c)
[ 2.298119] [<c06b1830>] (kernel_init) from [<c000fc68>] (ret_from_fork+0x14/0x2c)
4---[ end trace 8f0f0331ca65e290 ]---
[ 2.298203] ---[ end trace 8f0f0331ca65e290 ]---
spi-tegra114 7000da00.spi: spi trasfer timeout, err 0
[ 2.298261] spi-tegra114 7000da00.spi: spi trasfer timeout, err 0
spi_master spi32765: failed to transfer one message from queue
[ 2.298335] spi_master spi32765: failed to transfer one message from queue
m25p80 spi32765.0: error -5 reading 9f
[ 2.298401] m25p80 spi32765.0: error -5 reading 9f
4m25p80: probe of spi32765.0 failed with error -5
[ 2.298471] m25p80: probe of spi32765.0 failed with error -5
6CAN device driver interface
[ 2.300556] CAN device driver interface
6igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k
[ 2.300755] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.2.15-k
6igb: Copyright (c) 2007-2014 Intel Corporation.
[ 2.300821] igb: Copyright (c) 2007-2014 Intel Corporation.
6xen_netfront: Initialising Xen virtual ethernet driver
[ 2.301237] xen_netfront: Initialising Xen virtual ethernet driver
6pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[ 2.301625] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
6usbcore: registered new interface driver pegasus
[ 2.301842] usbcore: registered new interface driver pegasus
6usbcore: registered new interface driver asix
[ 2.302103] usbcore: registered new interface driver asix
6usbcore: registered new interface driver ax88179_178a
[ 2.302301] usbcore: registered new interface driver ax88179_178a
6usbcore: registered new interface driver cdc_ether
[ 2.302496] usbcore: registered new interface driver cdc_ether
6usbcore: registered new interface driver smsc75xx
[ 2.302738] usbcore: registered new interface driver smsc75xx
6usbcore: registered new interface driver smsc95xx
[ 2.302991] usbcore: registered new interface driver smsc95xx
6usbcore: registered new interface driver net1080
[ 2.303184] usbcore: registered new interface driver net1080
6usbcore: registered new interface driver cdc_subset
[ 2.303396] usbcore: registered new interface driver cdc_subset
6usbcore: registered new interface driver zaurus
[ 2.303589] usbcore: registered new interface driver zaurus
6usbcore: registered new interface driver cdc_ncm
[ 2.303840] usbcore: registered new interface driver cdc_ncm
tegra-phy 7d004000.usb-phy: no vbus regulator[ 2.304195] tegra-phy 7d004000.usb-phy: no vbus regulator
6ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.304808] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
6ehci-pci: EHCI PCI platform driver
[ 2.304884] ehci-pci: EHCI PCI platform driver
6tegra-ehci: Tegra EHCI driver
[ 2.305146] tegra-ehci: Tegra EHCI driver
tegra-ehci 7d004000.usb: EHCI Host Controller
[ 2.305547] tegra-ehci 7d004000.usb: EHCI Host Controller
tegra-ehci 7d004000.usb: new USB bus registered, assigned bus number 1
[ 2.305654] tegra-ehci 7d004000.usb: new USB bus registered, assigned bus number 1
tegra-ehci 7d004000.usb: irq 342, io mem 0x7d004000
[ 2.306049] tegra-ehci 7d004000.usb: irq 342, io mem 0x7d004000
tegra-ehci 7d004000.usb: USB 2.0 started, EHCI 1.10
[ 2.324946] tegra-ehci 7d004000.usb: USB 2.0 started, EHCI 1.10
hub 1-0:1.0: USB hub found
[ 2.326770] hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
[ 2.326865] hub 1-0:1.0: 1 port detected
6usbcore: registered new interface driver cdc_acm
[ 2.328356] usbcore: registered new interface driver cdc_acm
6cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 2.328419] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
6usbcore: registered new interface driver cdc_wdm
[ 2.328631] usbcore: registered new interface driver cdc_wdm
6usbcore: registered new interface driver usb-storage
[ 2.328891] usbcore: registered new interface driver usb-storage
6mousedev: PS/2 mouse device common for all mice
[ 2.329779] mousedev: PS/2 mouse device common for all mice
tegra_rtc 7000e000.rtc: rtc core: registered 7000e000.rtc as rtc1
[ 2.332879] tegra_rtc 7000e000.rtc: rtc core: registered 7000e000.rtc as rtc1
tegra_rtc 7000e000.rtc: Tegra internal Real Time Clock
[ 2.333058] tegra_rtc 7000e000.rtc: Tegra internal Real Time Clock
6i2c /dev entries driver
[ 2.333554] i2c /dev entries driver
6usbcore: registered new interface driver uvcvideo
[ 2.335983] usbcore: registered new interface driver uvcvideo
6USB Video Class driver (1.1.1)
[ 2.336045] USB Video Class driver (1.1.1)
6gspca_main: v2.14.0 registered
[ 2.336100] gspca_main: v2.14.0 registered
40-004c supply vcc not found, using dummy regulator
[ 2.336973] 0-004c supply vcc not found, using dummy regulator
6cfg80211: Calling CRDA to update world regulatory domain
[ 3.335027] cfg80211: Calling CRDA to update world regulatory domain
tegra-i2c 7000c000.i2c: i2c transfer timed out
[ 3.335170] tegra-i2c 7000c000.i2c: i2c transfer timed out
lm90 0-004c: Register 0x4 read failed (-110)
[ 3.335249] lm90 0-004c: Register 0x4 read failed (-110)
lm90 0-004c: Failed to read convrate register!
[ 3.335304] lm90 0-004c: Failed to read convrate register!
tegra-i2c 7000c000.i2c: i2c transfer timed out
[ 4.335013] tegra-i2c 7000c000.i2c: i2c transfer timed out
tegra-i2c 7000c000.i2c: i2c transfer timed out
[ 5.335012] tegra-i2c 7000c000.i2c: i2c transfer timed out
lm90 0-004c: Register 0x3 read failed (-110)
[ 5.335113] lm90 0-004c: Register 0x3 read failed (-110)
lm90 0-004c: Initialization failed!
[ 5.335168] lm90 0-004c: Initialization failed!
6sdhci: Secure Digital Host Controller Interface driver
[ 5.336679] sdhci: Secure Digital Host Controller Interface driver
6sdhci: Copyright(c) Pierre Ossman
[ 5.336741] sdhci: Copyright(c) Pierre Ossman
6sdhci-pltfm: SDHCI platform and OF driver helper
[ 5.336801] sdhci-pltfm: SDHCI platform and OF driver helper
sdhci-tegra 700b0400.sdhci: Got CD GPIO
[ 5.337175] sdhci-tegra 700b0400.sdhci: Got CD GPIO
sdhci-tegra 700b0400.sdhci: Got WP GPIO
[ 5.337250] sdhci-tegra 700b0400.sdhci: Got WP GPIO
3mmc0: Unknown controller version (3). You may experience problems.
[ 5.337361] mmc0: Unknown controller version (3). You may experience problems.
sdhci-tegra 700b0400.sdhci: No vmmc regulator found
[ 5.337520] sdhci-tegra 700b0400.sdhci: No vmmc regulator found
3mmc0: Unknown controller version (3). You may experience problems.
[ 5.337826] mmc0: Unknown controller version (3). You may experience problems.
sdhci-tegra 700b0600.sdhci: No vmmc regulator found
[ 5.337962] sdhci-tegra 700b0600.sdhci: No vmmc regulator found
sdhci-tegra 700b0600.sdhci: No vqmmc regulator found
[ 5.338025] sdhci-tegra 700b0600.sdhci: No vqmmc regulator found
4mmc0: Invalid maximum block size, assuming 512 bytes
[ 5.338085] mmc0: Invalid maximum block size, assuming 512 bytes
6mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit
[ 5.385060] mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit
6usbcore: registered new interface driver usbhid
[ 5.386273] usbcore: registered new interface driver usbhid
6usbhid: USB HID core driver
[ 5.386328] usbhid: USB HID core driver
6cfg80211: Calling CRDA to update world regulatory domain
[ 6.495024] cfg80211: Calling CRDA to update world regulatory domain
tegra-hda 70030000.hda: azx_get_response timeout, switching to polling mode: last cmd=0x300f0001
[ 8.475013] 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.916860] input: tegra-hda HDMI/DP,pcm=3 as /devices/soc0/70030000.hda/sound/card0/input0
6cfg80211: Calling CRDA to update world regulatory domain
[ 9.655022] cfg80211: Calling CRDA to update world regulatory domain
tegra-i2c 7000c000.i2c: i2c transfer timed out
[ 10.535012] tegra-i2c 7000c000.i2c: i2c transfer timed out
rt5640 0-001c: Device with ID register 0 is not rt5640/39
[ 10.535113] rt5640 0-001c: Device with ID register 0 is not rt5640/39
tegra30-i2s 70301100.i2s: DMA channels sourced from device 70300000.ahub[ 10.538503] tegra30-i2s 70301100.i2s: DMA channels so
urced from device 70300000.ahub
tegra-snd-rt5640 sound: ASoC: CODEC DAI rt5640-aif1 not registered
[ 10.539159] tegra-snd-rt5640 sound: ASoC: CODEC DAI rt5640-aif1 not registered
tegra-snd-rt5640 sound: snd_soc_register_card failed (-517)
[ 10.539260] tegra-snd-rt5640 sound: snd_soc_register_card failed (-517)
6NET: Registered protocol family 10
[ 10.541010] NET: Registered protocol family 10
6mip6: Mobile IPv6
[ 10.542510] mi
[-- Attachment #4: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-15 19:35 Question about running Xen on NVIDIA Jetson-TK1 Meng Xu
@ 2016-05-16 11:33 ` Julien Grall
2016-05-16 16:33 ` Meng Xu
0 siblings, 1 reply; 12+ messages in thread
From: Julien Grall @ 2016-05-16 11:33 UTC (permalink / raw)
To: Meng Xu, xen-devel, Ian Campbell; +Cc: Dushyant K Behl, Stefano Stabellini
On 15/05/16 20:35, Meng Xu wrote:
> Hi Julien and Ian,
Hello Meng,
>
> I'm trying to run Xen on NVIDIA Jetson TK1 board. (Right now, Xen does
> not support the Jetson board officially. But I'm thinking it may be
> very interesting and useful to see it happens, since it has GPU inside
> which is quite popular in automotive.)
>
> Now I encountered some problem to boot dom0 in Xen environment. I want
> to debug the issues and maybe fix the issues, but I'm not so sure how
> I should debug the issue more efficiently. I really appreciate it if
> you advise me a little bit about the method of how to fix the issue.
> :-)
>
> ---Below is the details----
>
> I noticed the Dushyant from IBM also tried to run Xen on the Jetson
> board. (http://www.gossamer-threads.com/lists/xen/devel/422519). I
> used the same Linux kernel (Jan Kiszka's development tree -
> http://git.kiszka.org/linux.git/, branch queues/assorted) and Ian's
> Xen repo. with the hack for Jetson board. I can see the dom0 kernel
> can boot to some extend and then "stall/spin" before the dom0 kernel
> fully boot up.
>
> In order to figure out the possible issue, I boot the exact same Linux
> kernel in native environment on one CPU and collected the boot log
> information in [1]. I also boot the same Linux kernel as dom0 in Xen
> environment and collected the boot log information in [2].
>
> In Xen environment, dom0 hangs after the following message
> [ 10.541010] NET: Registered protocol family 10
> 6mip6: Mobile IPv6
> [ 10.542510] mi
>
> In native environment, the kernel has the following log after initializing NET.
> [ 2.934693] NET: Registered protocol family 10
> [ 2.940611] mip6: Mobile IPv6
> [ 2.943645] sit: IPv6 over IPv4 tunneling driver
> [ 2.951303] NET: Registered protocol family 17
> [ 2.955800] NET: Registered protocol family 15
> [ 2.960257] can: controller area network core (rev 20120528 abi 9)
> [ 2.966617] NET: Registered protocol family 29
> [ 2.971098] can: raw protocol (rev 20120528)
> [ 2.975384] can: broadcast manager protocol (rev 20120528 t)
> [ 2.981088] can: netlink gateway (rev 20130117) max_hops=1
> [ 2.986734] Bluetooth: RFCOMM socket layer initialized
> [ 2.991979] Bluetooth: RFCOMM ver 1.11
> [ 2.995757] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [ 3.001109] Bluetooth: BNEP socket layer initialized
> [ 3.006089] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
> [ 3.012052] Bluetooth: HIDP socket layer initialized
> [ 3.017894] Registering SWP/SWPB emulation handler
> [ 3.029675] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration
> [ 3.036586] +3.3V_SYS: supplied by +VDD_MUX
> [ 3.040857] +3.3V_LP0: supplied by +3.3V_SYS
> [ 3.045509] +1.35V_LP0(sd2): supplied by +5V_SYS
> [ 3.050201] +1.05V_RUN_AVDD: supplied by +1.35V_LP0(sd2)
> [ 3.057131] tegra-pcie 1003000.pcie-controller: probing port 0, using 2 lanes
> [ 3.066479] tegra-pcie 1003000.pcie-controller: Slot present pin
> change, signature: 00000008
>
> I'm suspecting that my dom0 kernel hangs when it tries to initialize
> "can: controller area network core ". However, from Dushyant's post at
> http://www.gossamer-threads.com/lists/xen/devel/422519, it seems
> Dushyant's dom0 kernel hangs when it tries to initialize pci_bus. (The
> linux config I used may be different form Dushyant's. That could be
> the reason.)
>
> Right now, the system just hangs and has no output indicating what the
> problem could be. Although there are a lot of error message before the
> system hangs, I'm not that sure if I should start with solving all of
> those error messages. Maybe some errors can be ignored?
>
> My questions are:
> 1) Do you have suggestion on how to see more information about the
> reason why the dom0 hangs?
Have you tried to dump the registers using Xen console (CTLR-x 3 times
then 0) and see where it get stucks?
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-16 11:33 ` Julien Grall
@ 2016-05-16 16:33 ` Meng Xu
2016-05-16 17:26 ` Konrad Rzeszutek Wilk
2016-05-16 17:33 ` Julien Grall
0 siblings, 2 replies; 12+ messages in thread
From: Meng Xu @ 2016-05-16 16:33 UTC (permalink / raw)
To: Julien Grall; +Cc: xen-devel, Dushyant K Behl, Stefano Stabellini, Ian Campbell
On Mon, May 16, 2016 at 7:33 AM, Julien Grall <julien.grall@arm.com> wrote:
>
> On 15/05/16 20:35, Meng Xu wrote:
>>
>> Hi Julien and Ian,
>
>
> Hello Meng,
Hi Julien,
>
>>
>> I'm trying to run Xen on NVIDIA Jetson TK1 board. (Right now, Xen does
>> not support the Jetson board officially. But I'm thinking it may be
>> very interesting and useful to see it happens, since it has GPU inside
>> which is quite popular in automotive.)
>>
>> Now I encountered some problem to boot dom0 in Xen environment. I want
>> to debug the issues and maybe fix the issues, but I'm not so sure how
>> I should debug the issue more efficiently. I really appreciate it if
>> you advise me a little bit about the method of how to fix the issue.
>> :-)
>>
>> ---Below is the details----
>>
>> I noticed the Dushyant from IBM also tried to run Xen on the Jetson
>> board. (http://www.gossamer-threads.com/lists/xen/devel/422519). I
>> used the same Linux kernel (Jan Kiszka's development tree -
>> http://git.kiszka.org/linux.git/, branch queues/assorted) and Ian's
>> Xen repo. with the hack for Jetson board. I can see the dom0 kernel
>> can boot to some extend and then "stall/spin" before the dom0 kernel
>> fully boot up.
>>
>> In order to figure out the possible issue, I boot the exact same Linux
>> kernel in native environment on one CPU and collected the boot log
>> information in [1]. I also boot the same Linux kernel as dom0 in Xen
>> environment and collected the boot log information in [2].
>>
>> In Xen environment, dom0 hangs after the following message
>> [ 10.541010] NET: Registered protocol family 10
>> 6mip6: Mobile IPv6
>> [ 10.542510] mi
>>
>> In native environment, the kernel has the following log after initializing NET.
>> [ 2.934693] NET: Registered protocol family 10
>> [ 2.940611] mip6: Mobile IPv6
>> [ 2.943645] sit: IPv6 over IPv4 tunneling driver
>> [ 2.951303] NET: Registered protocol family 17
>> [ 2.955800] NET: Registered protocol family 15
>> [ 2.960257] can: controller area network core (rev 20120528 abi 9)
>> [ 2.966617] NET: Registered protocol family 29
>> [ 2.971098] can: raw protocol (rev 20120528)
>> [ 2.975384] can: broadcast manager protocol (rev 20120528 t)
>> [ 2.981088] can: netlink gateway (rev 20130117) max_hops=1
>> [ 2.986734] Bluetooth: RFCOMM socket layer initialized
>> [ 2.991979] Bluetooth: RFCOMM ver 1.11
>> [ 2.995757] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>> [ 3.001109] Bluetooth: BNEP socket layer initialized
>> [ 3.006089] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
>> [ 3.012052] Bluetooth: HIDP socket layer initialized
>> [ 3.017894] Registering SWP/SWPB emulation handler
>> [ 3.029675] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration
>> [ 3.036586] +3.3V_SYS: supplied by +VDD_MUX
>> [ 3.040857] +3.3V_LP0: supplied by +3.3V_SYS
>> [ 3.045509] +1.35V_LP0(sd2): supplied by +5V_SYS
>> [ 3.050201] +1.05V_RUN_AVDD: supplied by +1.35V_LP0(sd2)
>> [ 3.057131] tegra-pcie 1003000.pcie-controller: probing port 0, using 2 lanes
>> [ 3.066479] tegra-pcie 1003000.pcie-controller: Slot present pin
>> change, signature: 00000008
>>
>> I'm suspecting that my dom0 kernel hangs when it tries to initialize
>> "can: controller area network core ". However, from Dushyant's post at
>> http://www.gossamer-threads.com/lists/xen/devel/422519, it seems
>> Dushyant's dom0 kernel hangs when it tries to initialize pci_bus. (The
>> linux config I used may be different form Dushyant's. That could be
>> the reason.)
>>
>> Right now, the system just hangs and has no output indicating what the
>> problem could be. Although there are a lot of error message before the
>> system hangs, I'm not that sure if I should start with solving all of
>> those error messages. Maybe some errors can be ignored?
>>
>> My questions are:
>> 1) Do you have suggestion on how to see more information about the
>> reason why the dom0 hangs?
>
>
> Have you tried to dump the registers using Xen console (CTLR-x 3 times then 0) and see where it get stucks?
I tried to type CTLR -x 3 times and then 0, nothing happens... :-(
Just to confirm, once the system got stuck, I directly type Ctrl-x for
three times on the host's screen. Am I correct?
Maybe the serial console is not correctly set up?
The serial console configuration I used is as follows, could you have
a quick look to see if it's because I configure the serial
incorrectly?
I used screen program to attach to the serial port.
The command I used is $screen /dev/ttyUSB0 115200n8 on the host machine.
On the board, I set up the device tree's /chosen node as follows:
#
fdt print /chosen
chosen {
xen,xen-bootargs = "console=dtuart dtuart=serial0
dom0_mem=512M loglvl=all guest_loglvl=all dom0_max_vcpus=1
dom0_vcpus_pin maxcpus=1";
bootargs = "console=dtuart dtuart=serial0 dom0_mem=512M
loglvl=all guest_loglvl=all dom0_max_vcpus=1 dom0_vcpus_pin
maxcpus=1";
module {
bootargs = "console=hvc0 console=tty1 earlyprintk=xen
root=/dev/mmcblk0p1 rw rootwait";
reg = <0x00000000 0x81000000 0x00000000 0x004f2b70>;
compatible = "xen,linux-zimage", "xen,multiboot-module";
};
};
Thank you very much for your time and help!
Best Regards,
Meng
-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-16 16:33 ` Meng Xu
@ 2016-05-16 17:26 ` Konrad Rzeszutek Wilk
2016-05-16 17:30 ` Julien Grall
2016-05-16 17:33 ` Julien Grall
1 sibling, 1 reply; 12+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-05-16 17:26 UTC (permalink / raw)
To: Meng Xu
Cc: xen-devel, Julien Grall, Stefano Stabellini, Dushyant K Behl,
Ian Campbell
> >
> > Have you tried to dump the registers using Xen console (CTLR-x 3 times then 0) and see where it get stucks?
>
>
> I tried to type CTLR -x 3 times and then 0, nothing happens... :-(
> Just to confirm, once the system got stuck, I directly type Ctrl-x for
> three times on the host's screen. Am I correct?
I think it is 'Ctrl-A', and since you are using screen you need to
'pass'through the Ctrl-A by doing 'ctrl-a-A' or something like that
three or six times.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-16 17:26 ` Konrad Rzeszutek Wilk
@ 2016-05-16 17:30 ` Julien Grall
0 siblings, 0 replies; 12+ messages in thread
From: Julien Grall @ 2016-05-16 17:30 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk, Meng Xu
Cc: xen-devel, Dushyant K Behl, Stefano Stabellini, Ian Campbell
On 16/05/16 18:26, Konrad Rzeszutek Wilk wrote:
>>>
>>> Have you tried to dump the registers using Xen console (CTLR-x 3 times then 0) and see where it get stucks?
>>
>>
>> I tried to type CTLR -x 3 times and then 0, nothing happens... :-(
>> Just to confirm, once the system got stuck, I directly type Ctrl-x for
>> three times on the host's screen. Am I correct?
>
> I think it is 'Ctrl-A', and since you are using screen you need to
> 'pass'through the Ctrl-A by doing 'ctrl-a-A' or something like that
> three or six times.
Hmmm yes, I forgot that I modified the switching character on my
configuration. Sorry for the noise.
Meng, you can pass conswitch=x to Xen command line to havet he
'pass'through problem.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-16 16:33 ` Meng Xu
2016-05-16 17:26 ` Konrad Rzeszutek Wilk
@ 2016-05-16 17:33 ` Julien Grall
2016-05-16 19:39 ` Meng Xu
1 sibling, 1 reply; 12+ messages in thread
From: Julien Grall @ 2016-05-16 17:33 UTC (permalink / raw)
To: Meng Xu
Cc: xen-devel, Dushyant K Behl, Stefano Stabellini, Kyle Temkin,
Ian Campbell
(CC Kyle who is also working on Tegra?)
Hi Meng,
Many people are working on Nvidia platform with different issues :/. I
have CCed another person which IIRC is also working on it.
On 16/05/16 17:33, Meng Xu wrote:
> On Mon, May 16, 2016 at 7:33 AM, Julien Grall <julien.grall@arm.com> wrote:
>>
>> On 15/05/16 20:35, Meng Xu wrote:
>>>
>>> I'm trying to run Xen on NVIDIA Jetson TK1 board. (Right now, Xen does
>>> not support the Jetson board officially. But I'm thinking it may be
>>> very interesting and useful to see it happens, since it has GPU inside
>>> which is quite popular in automotive.)
>>>
>>> Now I encountered some problem to boot dom0 in Xen environment. I want
>>> to debug the issues and maybe fix the issues, but I'm not so sure how
>>> I should debug the issue more efficiently. I really appreciate it if
>>> you advise me a little bit about the method of how to fix the issue.
>>> :-)
>>>
>>> ---Below is the details----
>>>
>>> I noticed the Dushyant from IBM also tried to run Xen on the Jetson
>>> board. (http://www.gossamer-threads.com/lists/xen/devel/422519). I
>>> used the same Linux kernel (Jan Kiszka's development tree -
>>> http://git.kiszka.org/linux.git/, branch queues/assorted) and Ian's
>>> Xen repo. with the hack for Jetson board. I can see the dom0 kernel
>>> can boot to some extend and then "stall/spin" before the dom0 kernel
>>> fully boot up.
>>>
>>> In order to figure out the possible issue, I boot the exact same Linux
>>> kernel in native environment on one CPU and collected the boot log
>>> information in [1]. I also boot the same Linux kernel as dom0 in Xen
>>> environment and collected the boot log information in [2].
>>>
>>> In Xen environment, dom0 hangs after the following message
>>> [ 10.541010] NET: Registered protocol family 10
>>> 6mip6: Mobile IPv6
>>> [ 10.542510] mi
>>>
>>> In native environment, the kernel has the following log after initializing NET.
>>> [ 2.934693] NET: Registered protocol family 10
>>> [ 2.940611] mip6: Mobile IPv6
>>> [ 2.943645] sit: IPv6 over IPv4 tunneling driver
>>> [ 2.951303] NET: Registered protocol family 17
>>> [ 2.955800] NET: Registered protocol family 15
>>> [ 2.960257] can: controller area network core (rev 20120528 abi 9)
>>> [ 2.966617] NET: Registered protocol family 29
>>> [ 2.971098] can: raw protocol (rev 20120528)
>>> [ 2.975384] can: broadcast manager protocol (rev 20120528 t)
>>> [ 2.981088] can: netlink gateway (rev 20130117) max_hops=1
>>> [ 2.986734] Bluetooth: RFCOMM socket layer initialized
>>> [ 2.991979] Bluetooth: RFCOMM ver 1.11
>>> [ 2.995757] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>>> [ 3.001109] Bluetooth: BNEP socket layer initialized
>>> [ 3.006089] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
>>> [ 3.012052] Bluetooth: HIDP socket layer initialized
>>> [ 3.017894] Registering SWP/SWPB emulation handler
>>> [ 3.029675] tegra-pcie 1003000.pcie-controller: 2x1, 1x1 configuration
>>> [ 3.036586] +3.3V_SYS: supplied by +VDD_MUX
>>> [ 3.040857] +3.3V_LP0: supplied by +3.3V_SYS
>>> [ 3.045509] +1.35V_LP0(sd2): supplied by +5V_SYS
>>> [ 3.050201] +1.05V_RUN_AVDD: supplied by +1.35V_LP0(sd2)
>>> [ 3.057131] tegra-pcie 1003000.pcie-controller: probing port 0, using 2 lanes
>>> [ 3.066479] tegra-pcie 1003000.pcie-controller: Slot present pin
>>> change, signature: 00000008
>>>
>>> I'm suspecting that my dom0 kernel hangs when it tries to initialize
>>> "can: controller area network core ". However, from Dushyant's post at
>>> http://www.gossamer-threads.com/lists/xen/devel/422519, it seems
>>> Dushyant's dom0 kernel hangs when it tries to initialize pci_bus. (The
>>> linux config I used may be different form Dushyant's. That could be
>>> the reason.)
>>>
>>> Right now, the system just hangs and has no output indicating what the
>>> problem could be. Although there are a lot of error message before the
>>> system hangs, I'm not that sure if I should start with solving all of
>>> those error messages. Maybe some errors can be ignored?
>>>
>>> My questions are:
>>> 1) Do you have suggestion on how to see more information about the
>>> reason why the dom0 hangs?
>>
>>
>> Have you tried to dump the registers using Xen console (CTLR-x 3 times then 0) and see where it get stucks?
>
>
> I tried to type CTLR -x 3 times and then 0, nothing happens... :-(
> Just to confirm, once the system got stuck, I directly type Ctrl-x for
> three times on the host's screen. Am I correct?
Sorry, I forgot the default way to switch console is CTLR-a three times.
On my configuration I modified the default character to avoid issue with
screen.
>
> Maybe the serial console is not correctly set up?
It's likely to be a problem with the serial drivers in driver. Can you
tried CTLR-a before the kernel is booting?
> The serial console configuration I used is as follows, could you have
> a quick look to see if it's because I configure the serial
> incorrectly?
I am not familiar with the Nvidia board. If the serial configuration is
working for baremetal, then it should work for Xen.
>
> I used screen program to attach to the serial port.
> The command I used is $screen /dev/ttyUSB0 115200n8 on the host machine.
>
> On the board, I set up the device tree's /chosen node as follows:
> #
> fdt print /chosen
>
> chosen {
>
> xen,xen-bootargs = "console=dtuart dtuart=serial0
> dom0_mem=512M loglvl=all guest_loglvl=all dom0_max_vcpus=1
> dom0_vcpus_pin maxcpus=1";
>
> bootargs = "console=dtuart dtuart=serial0 dom0_mem=512M
> loglvl=all guest_loglvl=all dom0_max_vcpus=1 dom0_vcpus_pin
> maxcpus=1";
FIY, this property is not necessary.
> module {
>
> bootargs = "console=hvc0 console=tty1 earlyprintk=xen
> root=/dev/mmcblk0p1 rw rootwait";
Can you try to add "clk_ignore_unused" on the Linux command line?
This parameter will avoid DOM0 to disable clock for unused devices such
as the UART used by Xen.
>
> reg = <0x00000000 0x81000000 0x00000000 0x004f2b70>;
>
> compatible = "xen,linux-zimage", "xen,multiboot-module";
>
> };
>
> };
>
> Thank you very much for your time and help!
>
> Best Regards,
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-16 17:33 ` Julien Grall
@ 2016-05-16 19:39 ` Meng Xu
2016-05-16 23:27 ` Kyle Temkin
0 siblings, 1 reply; 12+ messages in thread
From: Meng Xu @ 2016-05-16 19:39 UTC (permalink / raw)
To: Julien Grall
Cc: xen-devel, Dushyant K Behl, Stefano Stabellini, Kyle Temkin,
Ian Campbell
Hi Julien,
On Mon, May 16, 2016 at 1:33 PM, Julien Grall <julien.grall@arm.com> wrote:
> (CC Kyle who is also working on Tegra?)
>
> Hi Meng,
>
> Many people are working on Nvidia platform with different issues :/. I have
> CCed another person which IIRC is also working on it.
Sure. It's good to know others are also interested in this platform.
It will be more useful to fix it... :-)
>
> On 16/05/16 17:33, Meng Xu wrote:
>>
>> On Mon, May 16, 2016 at 7:33 AM, Julien Grall <julien.grall@arm.com>
>> wrote:
>>>
>>>
>>> On 15/05/16 20:35, Meng Xu wrote:
>>>>
>>>>
>>>> I'm trying to run Xen on NVIDIA Jetson TK1 board. (Right now, Xen does
>>>> not support the Jetson board officially. But I'm thinking it may be
>>>> very interesting and useful to see it happens, since it has GPU inside
>>>> which is quite popular in automotive.)
>>>>
>>>> Now I encountered some problem to boot dom0 in Xen environment. I want
>>>> to debug the issues and maybe fix the issues, but I'm not so sure how
>>>> I should debug the issue more efficiently. I really appreciate it if
>>>> you advise me a little bit about the method of how to fix the issue.
>>>> :-)
>>>>
>>>> ---Below is the details----
>>>>
>>>> I noticed the Dushyant from IBM also tried to run Xen on the Jetson
>>>> board. (http://www.gossamer-threads.com/lists/xen/devel/422519). I
>>>> used the same Linux kernel (Jan Kiszka's development tree -
>>>> http://git.kiszka.org/linux.git/, branch queues/assorted) and Ian's
>>>> Xen repo. with the hack for Jetson board. I can see the dom0 kernel
>>>> can boot to some extend and then "stall/spin" before the dom0 kernel
>>>> fully boot up.
>>>>
>>>> In order to figure out the possible issue, I boot the exact same Linux
>>>> kernel in native environment on one CPU and collected the boot log
>>>> information in [1]. I also boot the same Linux kernel as dom0 in Xen
>>>> environment and collected the boot log information in [2].
>>>>
>>>> In Xen environment, dom0 hangs after the following message
>>>> [ 10.541010] NET: Registered protocol family 10
>>>> 6mip6: Mobile IPv6
>>>> [ 10.542510] mi
>>>>
>>>> In native environment, the kernel has the following log after
>>>> initializing NET.
>>>> [ 2.934693] NET: Registered protocol family 10
>>>> [ 2.940611] mip6: Mobile IPv6
>>>> [ 2.943645] sit: IPv6 over IPv4 tunneling driver
>>>> [ 2.951303] NET: Registered protocol family 17
>>>> [ 2.955800] NET: Registered protocol family 15
>>>> [ 2.960257] can: controller area network core (rev 20120528 abi 9)
>>>> [ 2.966617] NET: Registered protocol family 29
>>>> [ 2.971098] can: raw protocol (rev 20120528)
>>>> [ 2.975384] can: broadcast manager protocol (rev 20120528 t)
>>>> [ 2.981088] can: netlink gateway (rev 20130117) max_hops=1
>>>> [ 2.986734] Bluetooth: RFCOMM socket layer initialized
>>>> [ 2.991979] Bluetooth: RFCOMM ver 1.11
>>>> [ 2.995757] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>>>> [ 3.001109] Bluetooth: BNEP socket layer initialized
>>>> [ 3.006089] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
>>>> [ 3.012052] Bluetooth: HIDP socket layer initialized
>>>> [ 3.017894] Registering SWP/SWPB emulation handler
>>>> [ 3.029675] tegra-pcie 1003000.pcie-controller: 2x1, 1x1
>>>> configuration
>>>> [ 3.036586] +3.3V_SYS: supplied by +VDD_MUX
>>>> [ 3.040857] +3.3V_LP0: supplied by +3.3V_SYS
>>>> [ 3.045509] +1.35V_LP0(sd2): supplied by +5V_SYS
>>>> [ 3.050201] +1.05V_RUN_AVDD: supplied by +1.35V_LP0(sd2)
>>>> [ 3.057131] tegra-pcie 1003000.pcie-controller: probing port 0, using
>>>> 2 lanes
>>>> [ 3.066479] tegra-pcie 1003000.pcie-controller: Slot present pin
>>>> change, signature: 00000008
>>>>
>>>> I'm suspecting that my dom0 kernel hangs when it tries to initialize
>>>> "can: controller area network core ". However, from Dushyant's post at
>>>> http://www.gossamer-threads.com/lists/xen/devel/422519, it seems
>>>> Dushyant's dom0 kernel hangs when it tries to initialize pci_bus. (The
>>>> linux config I used may be different form Dushyant's. That could be
>>>> the reason.)
>>>>
>>>> Right now, the system just hangs and has no output indicating what the
>>>> problem could be. Although there are a lot of error message before the
>>>> system hangs, I'm not that sure if I should start with solving all of
>>>> those error messages. Maybe some errors can be ignored?
>>>>
>>>> My questions are:
>>>> 1) Do you have suggestion on how to see more information about the
>>>> reason why the dom0 hangs?
>>>
>>>
>>>
>>> Have you tried to dump the registers using Xen console (CTLR-x 3 times
>>> then 0) and see where it get stucks?
>>
>>
>>
>> I tried to type CTLR -x 3 times and then 0, nothing happens... :-(
>> Just to confirm, once the system got stuck, I directly type Ctrl-x for
>> three times on the host's screen. Am I correct?
>
>
> Sorry, I forgot the default way to switch console is CTLR-a three times.
>
> On my configuration I modified the default character to avoid issue with
> screen.
>
Ah-ha, typing "Ctrl -a, a" for three times, I can switch to the Xen
console now. :-)
Thank you for the clarification. :-)
>>
>> Maybe the serial console is not correctly set up?
>
>
> It's likely to be a problem with the serial drivers in driver. Can you tried
> CTLR-a before the kernel is booting?
>
>> The serial console configuration I used is as follows, could you have
>> a quick look to see if it's because I configure the serial
>> incorrectly?
>
>
> I am not familiar with the Nvidia board. If the serial configuration is
> working for baremetal, then it should work for Xen.
>
>>
>> I used screen program to attach to the serial port.
>> The command I used is $screen /dev/ttyUSB0 115200n8 on the host machine.
>>
>> On the board, I set up the device tree's /chosen node as follows:
>> #
>> fdt print /chosen
>>
>> chosen {
>>
>> xen,xen-bootargs = "console=dtuart dtuart=serial0
>> dom0_mem=512M loglvl=all guest_loglvl=all dom0_max_vcpus=1
>> dom0_vcpus_pin maxcpus=1";
>>
>> bootargs = "console=dtuart dtuart=serial0 dom0_mem=512M
>> loglvl=all guest_loglvl=all dom0_max_vcpus=1 dom0_vcpus_pin
>> maxcpus=1";
>
>
> FIY, this property is not necessary.
>
>> module {
>>
>> bootargs = "console=hvc0 console=tty1 earlyprintk=xen
>> root=/dev/mmcblk0p1 rw rootwait";
>
>
> Can you try to add "clk_ignore_unused" on the Linux command line?
Yes. After trying it, it gives me some different,but more useful log
information.
In the kernel booting log, it first shows this message:
---start of the message----
[ 10.607251] Waiting for root device /dev/mmcblk0p1...
... /* I omit some other unrelated message */
[ 5.347354] sdhci-tegra 700b0400.sdhci: Got WP GPIO
3mmc0: Unknown controller version (3). You may experience problems.
[ 5.347464] mmc0: Unknown controller version (3). You may
experience problems.
sdhci-tegra 700b0400.sdhci: No vmmc regulator found
[ 5.347647] sdhci-tegra 700b0400.sdhci: No vmmc regulator found
3mmc0: Unknown controller version (3). You may experience problems.
[ 5.347933] mmc0: Unknown controller version (3). You may
experience problems.
sdhci-tegra 700b0600.sdhci: No vmmc regulator found
[ 5.348099] sdhci-tegra 700b0600.sdhci: No vmmc regulator found
sdhci-tegra 700b0600.sdhci: No vqmmc regulator found
[ 5.348162] sdhci-tegra 700b0600.sdhci: No vqmmc regulator found
4mmc0: Invalid maximum block size, assuming 512 bytes
[ 5.348222] mmc0: Invalid maximum block size, assuming 512 bytes
6mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit
[ 5.395208] mmc0: SDHCI controller on 700b0600.sdhci
[700b0600.sdhci] using ADMA 64-bit
6usbcore: registered new interface driver usbhid
---end of the message----
It seems that mmc0 is not correctly recognized by dom0.
Later the dom0 kernel keeps printing this message:
[ 426.405136] mmc0: Timeout waiting for hardware interrupt.
Dom0 actually hangs here, because it cannot read the eMMC device. :-(
Is it because the device tree is not properly recreated by Xen?
Do you happen to know how to fix this issue or have some idea about
how to fix it? I can have a look at it.
BTW, dom0 didn't recognize the mmc1 controller either.
Thank you very much for your time and help in this! :-)
Best Regards,
Meng
-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-16 19:39 ` Meng Xu
@ 2016-05-16 23:27 ` Kyle Temkin
2016-05-17 3:27 ` Meng Xu
2016-05-17 13:37 ` Konrad Rzeszutek Wilk
0 siblings, 2 replies; 12+ messages in thread
From: Kyle Temkin @ 2016-05-16 23:27 UTC (permalink / raw)
To: Meng Xu
Cc: Stefano Stabellini, Dushyant K Behl, Chris Patterson,
Julien Grall, Ian Campbell, xen-devel
Hi, Meng:
Julien is correct-- a coworker and I are working on support for Tegra
SoCs, and we've made pretty good progress; there's work yet to be
done, but we have dom0 and guests booting on the Jetson TK1, Jetson
TX1, and the Google Pixel C. We hope to get a patch set out soon--
unfortunately, our employer has to take some time to verify that
everything's okay to be open-sourced, so I can't send out our
work-in-progress just yet. We'll have an RFC patchset out soon, I
hope!
There are two main hardware differences that cause Tegra SoCs to have
trouble with Xen:
- The primary interrupt controller for those systems isn't a single
GIC, as Xen expects. Instead, there's an NVIDIA Legacy Interrupt
Controller (LIC, or ICTLR) that gates all peripheral interrupts before
passing them to a standard GICv2. This interrupt controller has to be
programmed to ensure Xen can receive interrupts from the hardware
(e.g. serial), programmed to ensure that interrupts for pass-through
devices are correctly unmasked, and virtualized so dom0 can program
the "sections" related to interrupts not being routed to Xen or to a
domain for hardware passthrough.
- The serial controller on the Tegra SoCs doesn't behave in the same
was as most NS16550-compatibles; it actually adheres to the NS16550
spec a little more rigidly than most compatible controllers. A
coworker (Chris Patterson, cc'd) figured out what was going on; from
what I understand, most 16550s generate the "transmit ready" interrupt
once, when the device first can accept new FIFO entries. Both the
original 16550 and the Tegra implementation generate the "transmit
ready" interrupt /continuously/ when there's space available in the
FIFO, slewing the CPU with a stream of constant interrupts.
What you're seeing is likely a symptom of the first difference. In
your logs, you see messages that indicate Xen is having trouble
correctly routing IRQ that are parented by the legacy interrupt
controller:
> irq 0 not connected to primary controller.Connected to /interrupt-controller@60004000
The issue here is that Xen is currently explicitly opting not to route
legacy-interrupt-controller interrupts, as they don't belong to the
primary GIC. As a result, these interrupts never make it to dom0. The
logic that needs to be tweaked is here:
http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/arch/arm/domain_build.c;h=00dc07af637b67153d33408f34331700dff84f93;hb=HEAD#l1137
We re-write this logic in our forthcoming patch-set to be more
general. As an interim workaround, you might opt to rewrite that logic
so LIC interrupts (which have an interrupt-parent compatible with
"tegra124-ictlr", in your case) can be routed by Xen, as well. Off the
top of my head, a workaround might look like:
/*
* Don't map IRQ that have no physical meaning
* ie: IRQ whose controller is not the GIC
*/
- if ( rirq.controller != dt_interrupt_controller )
+if ( (rirq.controller != dt_interrupt_controller) &&
(!dt_device_is_compatible(rirq.controller, "tegra124-ictlr") )
Of course, that's off-the-cuff code I haven't tried, but hopefully it
should help to get you started.
--Kyle
On Mon, May 16, 2016 at 3:39 PM, Meng Xu <xumengpanda@gmail.com> wrote:
> Hi Julien,
>
> On Mon, May 16, 2016 at 1:33 PM, Julien Grall <julien.grall@arm.com> wrote:
>> (CC Kyle who is also working on Tegra?)
>>
>> Hi Meng,
>>
>> Many people are working on Nvidia platform with different issues :/. I have
>> CCed another person which IIRC is also working on it.
>
> Sure. It's good to know others are also interested in this platform.
> It will be more useful to fix it... :-)
>
>>
>> On 16/05/16 17:33, Meng Xu wrote:
>>>
>>> On Mon, May 16, 2016 at 7:33 AM, Julien Grall <julien.grall@arm.com>
>>> wrote:
>>>>
>>>>
>>>> On 15/05/16 20:35, Meng Xu wrote:
>>>>>
>>>>>
>>>>> I'm trying to run Xen on NVIDIA Jetson TK1 board. (Right now, Xen does
>>>>> not support the Jetson board officially. But I'm thinking it may be
>>>>> very interesting and useful to see it happens, since it has GPU inside
>>>>> which is quite popular in automotive.)
>>>>>
>>>>> Now I encountered some problem to boot dom0 in Xen environment. I want
>>>>> to debug the issues and maybe fix the issues, but I'm not so sure how
>>>>> I should debug the issue more efficiently. I really appreciate it if
>>>>> you advise me a little bit about the method of how to fix the issue.
>>>>> :-)
>>>>>
>>>>> ---Below is the details----
>>>>>
>>>>> I noticed the Dushyant from IBM also tried to run Xen on the Jetson
>>>>> board. (http://www.gossamer-threads.com/lists/xen/devel/422519). I
>>>>> used the same Linux kernel (Jan Kiszka's development tree -
>>>>> http://git.kiszka.org/linux.git/, branch queues/assorted) and Ian's
>>>>> Xen repo. with the hack for Jetson board. I can see the dom0 kernel
>>>>> can boot to some extend and then "stall/spin" before the dom0 kernel
>>>>> fully boot up.
>>>>>
>>>>> In order to figure out the possible issue, I boot the exact same Linux
>>>>> kernel in native environment on one CPU and collected the boot log
>>>>> information in [1]. I also boot the same Linux kernel as dom0 in Xen
>>>>> environment and collected the boot log information in [2].
>>>>>
>>>>> In Xen environment, dom0 hangs after the following message
>>>>> [ 10.541010] NET: Registered protocol family 10
>>>>> 6mip6: Mobile IPv6
>>>>> [ 10.542510] mi
>>>>>
>>>>> In native environment, the kernel has the following log after
>>>>> initializing NET.
>>>>> [ 2.934693] NET: Registered protocol family 10
>>>>> [ 2.940611] mip6: Mobile IPv6
>>>>> [ 2.943645] sit: IPv6 over IPv4 tunneling driver
>>>>> [ 2.951303] NET: Registered protocol family 17
>>>>> [ 2.955800] NET: Registered protocol family 15
>>>>> [ 2.960257] can: controller area network core (rev 20120528 abi 9)
>>>>> [ 2.966617] NET: Registered protocol family 29
>>>>> [ 2.971098] can: raw protocol (rev 20120528)
>>>>> [ 2.975384] can: broadcast manager protocol (rev 20120528 t)
>>>>> [ 2.981088] can: netlink gateway (rev 20130117) max_hops=1
>>>>> [ 2.986734] Bluetooth: RFCOMM socket layer initialized
>>>>> [ 2.991979] Bluetooth: RFCOMM ver 1.11
>>>>> [ 2.995757] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>>>>> [ 3.001109] Bluetooth: BNEP socket layer initialized
>>>>> [ 3.006089] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
>>>>> [ 3.012052] Bluetooth: HIDP socket layer initialized
>>>>> [ 3.017894] Registering SWP/SWPB emulation handler
>>>>> [ 3.029675] tegra-pcie 1003000.pcie-controller: 2x1, 1x1
>>>>> configuration
>>>>> [ 3.036586] +3.3V_SYS: supplied by +VDD_MUX
>>>>> [ 3.040857] +3.3V_LP0: supplied by +3.3V_SYS
>>>>> [ 3.045509] +1.35V_LP0(sd2): supplied by +5V_SYS
>>>>> [ 3.050201] +1.05V_RUN_AVDD: supplied by +1.35V_LP0(sd2)
>>>>> [ 3.057131] tegra-pcie 1003000.pcie-controller: probing port 0, using
>>>>> 2 lanes
>>>>> [ 3.066479] tegra-pcie 1003000.pcie-controller: Slot present pin
>>>>> change, signature: 00000008
>>>>>
>>>>> I'm suspecting that my dom0 kernel hangs when it tries to initialize
>>>>> "can: controller area network core ". However, from Dushyant's post at
>>>>> http://www.gossamer-threads.com/lists/xen/devel/422519, it seems
>>>>> Dushyant's dom0 kernel hangs when it tries to initialize pci_bus. (The
>>>>> linux config I used may be different form Dushyant's. That could be
>>>>> the reason.)
>>>>>
>>>>> Right now, the system just hangs and has no output indicating what the
>>>>> problem could be. Although there are a lot of error message before the
>>>>> system hangs, I'm not that sure if I should start with solving all of
>>>>> those error messages. Maybe some errors can be ignored?
>>>>>
>>>>> My questions are:
>>>>> 1) Do you have suggestion on how to see more information about the
>>>>> reason why the dom0 hangs?
>>>>
>>>>
>>>>
>>>> Have you tried to dump the registers using Xen console (CTLR-x 3 times
>>>> then 0) and see where it get stucks?
>>>
>>>
>>>
>>> I tried to type CTLR -x 3 times and then 0, nothing happens... :-(
>>> Just to confirm, once the system got stuck, I directly type Ctrl-x for
>>> three times on the host's screen. Am I correct?
>>
>>
>> Sorry, I forgot the default way to switch console is CTLR-a three times.
>>
>> On my configuration I modified the default character to avoid issue with
>> screen.
>>
>
> Ah-ha, typing "Ctrl -a, a" for three times, I can switch to the Xen
> console now. :-)
>
> Thank you for the clarification. :-)
>
>>>
>>> Maybe the serial console is not correctly set up?
>>
>>
>> It's likely to be a problem with the serial drivers in driver. Can you tried
>> CTLR-a before the kernel is booting?
>>
>>> The serial console configuration I used is as follows, could you have
>>> a quick look to see if it's because I configure the serial
>>> incorrectly?
>>
>>
>> I am not familiar with the Nvidia board. If the serial configuration is
>> working for baremetal, then it should work for Xen.
>>
>>>
>>> I used screen program to attach to the serial port.
>>> The command I used is $screen /dev/ttyUSB0 115200n8 on the host machine.
>>>
>>> On the board, I set up the device tree's /chosen node as follows:
>>> #
>>> fdt print /chosen
>>>
>>> chosen {
>>>
>>> xen,xen-bootargs = "console=dtuart dtuart=serial0
>>> dom0_mem=512M loglvl=all guest_loglvl=all dom0_max_vcpus=1
>>> dom0_vcpus_pin maxcpus=1";
>>>
>>> bootargs = "console=dtuart dtuart=serial0 dom0_mem=512M
>>> loglvl=all guest_loglvl=all dom0_max_vcpus=1 dom0_vcpus_pin
>>> maxcpus=1";
>>
>>
>> FIY, this property is not necessary.
>>
>>> module {
>>>
>>> bootargs = "console=hvc0 console=tty1 earlyprintk=xen
>>> root=/dev/mmcblk0p1 rw rootwait";
>>
>>
>> Can you try to add "clk_ignore_unused" on the Linux command line?
>
> Yes. After trying it, it gives me some different,but more useful log
> information.
>
> In the kernel booting log, it first shows this message:
>
> ---start of the message----
>
> [ 10.607251] Waiting for root device /dev/mmcblk0p1...
>
> ... /* I omit some other unrelated message */
>
> [ 5.347354] sdhci-tegra 700b0400.sdhci: Got WP GPIO
>
> 3mmc0: Unknown controller version (3). You may experience problems.
>
> [ 5.347464] mmc0: Unknown controller version (3). You may
> experience problems.
>
> sdhci-tegra 700b0400.sdhci: No vmmc regulator found
>
> [ 5.347647] sdhci-tegra 700b0400.sdhci: No vmmc regulator found
>
> 3mmc0: Unknown controller version (3). You may experience problems.
>
> [ 5.347933] mmc0: Unknown controller version (3). You may
> experience problems.
>
> sdhci-tegra 700b0600.sdhci: No vmmc regulator found
>
> [ 5.348099] sdhci-tegra 700b0600.sdhci: No vmmc regulator found
>
> sdhci-tegra 700b0600.sdhci: No vqmmc regulator found
>
> [ 5.348162] sdhci-tegra 700b0600.sdhci: No vqmmc regulator found
>
> 4mmc0: Invalid maximum block size, assuming 512 bytes
>
> [ 5.348222] mmc0: Invalid maximum block size, assuming 512 bytes
>
> 6mmc0: SDHCI controller on 700b0600.sdhci [700b0600.sdhci] using ADMA 64-bit
>
> [ 5.395208] mmc0: SDHCI controller on 700b0600.sdhci
> [700b0600.sdhci] using ADMA 64-bit
>
> 6usbcore: registered new interface driver usbhid
>
> ---end of the message----
>
> It seems that mmc0 is not correctly recognized by dom0.
>
> Later the dom0 kernel keeps printing this message:
>
> [ 426.405136] mmc0: Timeout waiting for hardware interrupt.
>
> Dom0 actually hangs here, because it cannot read the eMMC device. :-(
>
> Is it because the device tree is not properly recreated by Xen?
> Do you happen to know how to fix this issue or have some idea about
> how to fix it? I can have a look at it.
>
> BTW, dom0 didn't recognize the mmc1 controller either.
>
> Thank you very much for your time and help in this! :-)
>
> Best Regards,
>
> Meng
> -----------
> Meng Xu
> PhD Student in Computer and Information Science
> University of Pennsylvania
> http://www.cis.upenn.edu/~mengxu/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-16 23:27 ` Kyle Temkin
@ 2016-05-17 3:27 ` Meng Xu
2016-05-17 13:37 ` Konrad Rzeszutek Wilk
1 sibling, 0 replies; 12+ messages in thread
From: Meng Xu @ 2016-05-17 3:27 UTC (permalink / raw)
To: Kyle Temkin
Cc: Stefano Stabellini, Dushyant K Behl, Chris Patterson,
Julien Grall, Ian Campbell, xen-devel
On Mon, May 16, 2016 at 7:27 PM, Kyle Temkin <ktemkin@binghamton.edu> wrote:
> Hi, Meng:
>
Hi Kyle,
> Julien is correct-- a coworker and I are working on support for Tegra
> SoCs, and we've made pretty good progress; there's work yet to be
> done, but we have dom0 and guests booting on the Jetson TK1, Jetson
> TX1, and the Google Pixel C. We hope to get a patch set out soon--
> unfortunately, our employer has to take some time to verify that
> everything's okay to be open-sourced, so I can't send out our
> work-in-progress just yet. We'll have an RFC patchset out soon, I
> hope!
Looking forward to your RFC patchset... Could you please cc. me when
you send out your RFC patchset. I really love to have a look at (maybe
review) it.
>
> There are two main hardware differences that cause Tegra SoCs to have
> trouble with Xen:
>
> - The primary interrupt controller for those systems isn't a single
> GIC, as Xen expects. Instead, there's an NVIDIA Legacy Interrupt
> Controller (LIC, or ICTLR) that gates all peripheral interrupts before
> passing them to a standard GICv2. This interrupt controller has to be
> programmed to ensure Xen can receive interrupts from the hardware
> (e.g. serial), programmed to ensure that interrupts for pass-through
> devices are correctly unmasked, and virtualized so dom0 can program
> the "sections" related to interrupts not being routed to Xen or to a
> domain for hardware passthrough.
>
> - The serial controller on the Tegra SoCs doesn't behave in the same
> was as most NS16550-compatibles; it actually adheres to the NS16550
> spec a little more rigidly than most compatible controllers. A
> coworker (Chris Patterson, cc'd) figured out what was going on; from
> what I understand, most 16550s generate the "transmit ready" interrupt
> once, when the device first can accept new FIFO entries. Both the
> original 16550 and the Tegra implementation generate the "transmit
> ready" interrupt /continuously/ when there's space available in the
> FIFO, slewing the CPU with a stream of constant interrupts.
I see. Thank you very much for explaining this so clearly! :-)
>
> What you're seeing is likely a symptom of the first difference. In
> your logs, you see messages that indicate Xen is having trouble
> correctly routing IRQ that are parented by the legacy interrupt
> controller:
>
>> irq 0 not connected to primary controller.Connected to /interrupt-controller@60004000
Right. I see the root issue now. Thank you so much for pointing it out!
>
> The issue here is that Xen is currently explicitly opting not to route
> legacy-interrupt-controller interrupts, as they don't belong to the
> primary GIC. As a result, these interrupts never make it to dom0. The
> logic that needs to be tweaked is here:
>
> http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/arch/arm/domain_build.c;h=00dc07af637b67153d33408f34331700dff84f93;hb=HEAD#l1137
>
> We re-write this logic in our forthcoming patch-set to be more
> general. As an interim workaround, you might opt to rewrite that logic
> so LIC interrupts (which have an interrupt-parent compatible with
> "tegra124-ictlr", in your case) can be routed by Xen, as well. Off the
> top of my head, a workaround might look like:
>
> /*
> * Don't map IRQ that have no physical meaning
> * ie: IRQ whose controller is not the GIC
> */
> - if ( rirq.controller != dt_interrupt_controller )
> +if ( (rirq.controller != dt_interrupt_controller) &&
> (!dt_device_is_compatible(rirq.controller, "tegra124-ictlr") )
It should have "nvidia" before "tegra124-ictlr". ;-)
After change it to
!dt_device_is_compatible(rirq.controller, "nvidia , tegra124-ictlr")
dom0 boots up~~~ :-D
>
> Of course, that's off-the-cuff code I haven't tried, but hopefully it
> should help to get you started.
Sure! It does work and get me started! I really appreciate your help
and explanation!
Looking forward to your RFC patch set. :-)
Thank you again for your help and time in this issue! It helps a lot!
Best Regards,
Meng
-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-16 23:27 ` Kyle Temkin
2016-05-17 3:27 ` Meng Xu
@ 2016-05-17 13:37 ` Konrad Rzeszutek Wilk
2016-05-17 16:31 ` Chris Patterson
1 sibling, 1 reply; 12+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-05-17 13:37 UTC (permalink / raw)
To: Kyle Temkin
Cc: Stefano Stabellini, Dushyant K Behl, Chris Patterson,
Julien Grall, Meng Xu, Ian Campbell, xen-devel
> - The serial controller on the Tegra SoCs doesn't behave in the same
> was as most NS16550-compatibles; it actually adheres to the NS16550
> spec a little more rigidly than most compatible controllers. A
> coworker (Chris Patterson, cc'd) figured out what was going on; from
> what I understand, most 16550s generate the "transmit ready" interrupt
> once, when the device first can accept new FIFO entries. Both the
> original 16550 and the Tegra implementation generate the "transmit
> ready" interrupt /continuously/ when there's space available in the
> FIFO, slewing the CPU with a stream of constant interrupts.
That may also be an issue on x86 I would think.
Is there some simple 16550 'fix' for this? As in reprogram it
to not be soo ready?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-17 13:37 ` Konrad Rzeszutek Wilk
@ 2016-05-17 16:31 ` Chris Patterson
2016-05-17 18:47 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 12+ messages in thread
From: Chris Patterson @ 2016-05-17 16:31 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: Kyle Temkin, Stefano Stabellini, Dushyant K Behl, Julien Grall,
Meng Xu, Ian Campbell, xen-devel
On Tue, May 17, 2016 at 9:37 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
>> - The serial controller on the Tegra SoCs doesn't behave in the same
>> was as most NS16550-compatibles; it actually adheres to the NS16550
>> spec a little more rigidly than most compatible controllers. A
>> coworker (Chris Patterson, cc'd) figured out what was going on; from
>> what I understand, most 16550s generate the "transmit ready" interrupt
>> once, when the device first can accept new FIFO entries. Both the
>> original 16550 and the Tegra implementation generate the "transmit
>> ready" interrupt /continuously/ when there's space available in the
>> FIFO, slewing the CPU with a stream of constant interrupts.
>
> That may also be an issue on x86 I would think.
>
On the x86 serial I have tested, it appears that the THRE interrupt
goes low after the IIR read reset, and doesn't re-assert until
UART_IER is flipped (or data is transmitted). On the Tegra, the
interrupt persists (or immediately re-asserts) after the IIR read
reset. I suppose this could be a problem on x86 if this behaviour
exists in another uart.
> Is there some simple 16550 'fix' for this? As in reprogram it
> to not be soo ready?
Yes, I do have a patch in my queue to address this. It simply
implements the start_tx and stop_tx hooks and sets or masks
UART_IER_ETHREI accordingly. I believe this behaviour is consistent
with the Linux kernel. I have done some limited testing on it with
both x86 and the Tegra (with additional patches for Tegra support) and
things appear to work well. I can RFC it when our employer gives us
approval. Apologies for the delay.
Have a good day!
-Chris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Question about running Xen on NVIDIA Jetson-TK1
2016-05-17 16:31 ` Chris Patterson
@ 2016-05-17 18:47 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 12+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-05-17 18:47 UTC (permalink / raw)
To: Chris Patterson
Cc: Kyle Temkin, Stefano Stabellini, Dushyant K Behl, Julien Grall,
Meng Xu, Ian Campbell, xen-devel
On Tue, May 17, 2016 at 12:31:10PM -0400, Chris Patterson wrote:
> On Tue, May 17, 2016 at 9:37 AM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> >> - The serial controller on the Tegra SoCs doesn't behave in the same
> >> was as most NS16550-compatibles; it actually adheres to the NS16550
> >> spec a little more rigidly than most compatible controllers. A
> >> coworker (Chris Patterson, cc'd) figured out what was going on; from
> >> what I understand, most 16550s generate the "transmit ready" interrupt
> >> once, when the device first can accept new FIFO entries. Both the
> >> original 16550 and the Tegra implementation generate the "transmit
> >> ready" interrupt /continuously/ when there's space available in the
> >> FIFO, slewing the CPU with a stream of constant interrupts.
> >
> > That may also be an issue on x86 I would think.
> >
>
> On the x86 serial I have tested, it appears that the THRE interrupt
> goes low after the IIR read reset, and doesn't re-assert until
> UART_IER is flipped (or data is transmitted). On the Tegra, the
> interrupt persists (or immediately re-asserts) after the IIR read
> reset. I suppose this could be a problem on x86 if this behaviour
> exists in another uart.
>
> > Is there some simple 16550 'fix' for this? As in reprogram it
> > to not be soo ready?
>
> Yes, I do have a patch in my queue to address this. It simply
> implements the start_tx and stop_tx hooks and sets or masks
> UART_IER_ETHREI accordingly. I believe this behaviour is consistent
> with the Linux kernel. I have done some limited testing on it with
> both x86 and the Tegra (with additional patches for Tegra support) and
> things appear to work well. I can RFC it when our employer gives us
> approval. Apologies for the delay.
Awesome! Looking forward to them and reviewing them!
>
> Have a good day!
> -Chris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2016-05-17 18:48 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-15 19:35 Question about running Xen on NVIDIA Jetson-TK1 Meng Xu
2016-05-16 11:33 ` Julien Grall
2016-05-16 16:33 ` Meng Xu
2016-05-16 17:26 ` Konrad Rzeszutek Wilk
2016-05-16 17:30 ` Julien Grall
2016-05-16 17:33 ` Julien Grall
2016-05-16 19:39 ` Meng Xu
2016-05-16 23:27 ` Kyle Temkin
2016-05-17 3:27 ` Meng Xu
2016-05-17 13:37 ` Konrad Rzeszutek Wilk
2016-05-17 16:31 ` Chris Patterson
2016-05-17 18:47 ` Konrad Rzeszutek Wilk
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.