* [Xen-devel] Errors with Loading Xen at a Certain Address
@ 2019-10-02 0:32 Brian Woods
[not found] ` <48c9fc54-553e-3b6b-bad2-dbad35991df0@arm.com>
0 siblings, 1 reply; 14+ messages in thread
From: Brian Woods @ 2019-10-02 0:32 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
Hello,
While testing some things out, I found a possible bug in Xen. Xen would
successfully run when loaded (from u-boot) at some addresses but not
others. I didn't observe this issue in 4.11 stable, so I did a bisect
and found that:
commit f60658c6ae47e74792e6cc48ea2effac8bb52826
Author: Julien Grall <julien.grall@arm.com>
Date: Tue Dec 18 13:07:39 2018 +0000
xen/arm: Stop relocating Xen
was what was causing it to fail when it was loaded to that certain
address.
I've attached the logs from a build from staging (about a week or so
ago) with both a passing and failing address.
--
Brian Woods
[-- Attachment #2: xen_good_addr.log --]
[-- Type: text/plain, Size: 41688 bytes --]
PMU Firmware 2019.1 May 25 2019 06:57:33
PMU_ROM Version: xpbr-v8.1.0-0
NOTICE: ATF running on XCZUUNKN/QEMU v4/RTL0.0 at 0xfffea000
NOTICE: BL31: Secure code at 0x60000000
NOTICE: BL31: Non secure code at 0x10080000
NOTICE: BL31: v2.0(release):xilinx-v2018.3-720-g80d1c790
NOTICE: BL31: Built : 06:54:23, May 25 2019
PMUFW: v1.1
U-Boot 2019.01 (May 25 2019 - 06:55:09 +0000)
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
DRAM: 4 GiB
EL Level: EL2
Chip ID: unknown
MMC: mmc@ff170000: 0
Loading Environment from SPI Flash... SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
*** Warning - bad CRC, using default environment
In: serial@ff000000
Out: serial@ff000000
Err: serial@ff000000
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
Bootmode: JTAG_MODE
Reset reason: EXTERNAL
Net: ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for xilinx-zcu102-2019_1
BOOTP broadcast 1
DHCP client bound to address 10.0.5.15 (1 ms)
Hit any key to stop autoboot: 4 \b\b\b 0
ZynqMP> setenv serverip 10.0.5.2; tftpb 1280000 xen-qemu-mod.dtb; tftpb 0x80000 yocto-Image; tftpb 4200000 xen-custom.ub; tftpb 9000000 yocto-rootfs.cpio.gz.ub; bootm 4200000 9000000 1280000
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'xen-qemu-mod.dtb'.
Load address: 0x1280000
Loading: *\b###
12.1 MiB/s
done
Bytes transferred = 38019 (9483 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'yocto-Image'.
Load address: 0x80000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#########################################
32.9 MiB/s
done
Bytes transferred = 18215424 (115f200 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'xen-custom.ub'.
Load address: 0x4200000
Loading: *\b#################################################################
####
32.4 MiB/s
done
Bytes transferred = 984464 (f0590 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'yocto-rootfs.cpio.gz.ub'.
Load address: 0x9000000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#####################
32.7 MiB/s
done
Bytes transferred = 9569188 (9203a4 hex)
## Booting kernel from Legacy Image at 04200000 ...
Image Name:
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 984400 Bytes = 961.3 KiB
Load Address: 04200000
Entry Point: 04200000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 09000000 ...
Image Name:
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 9569124 Bytes = 9.1 MiB
Load Address: 09000000
Entry Point: 09000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01280000
Booting using the fdt blob at 0x1280000
Loading Kernel Image ... OK
Loading Ramdisk to 076df000, end 07fff364 ... OK
Loading Device Tree to 00000000076d2000, end 00000000076de482 ... OK
Starting kernel ...
Xen 4.13-unstable
(XEN) Xen version 4.13-unstable (woods@xilinx.com) (aarch64-unknown-linux-gnu-gcc (crosstool-NG 1.24.0.6-afaf7b9) 8.3.0) debug=y Wed Sep 25 16:02:26 PDT 2019
(XEN) Latest ChangeSet: Tue Sep 24 15:46:48 2019 +0000 git:4333876
(XEN) build-id: a026a3bc865f1c93f67de50e71b7aea86f79e5b9
(XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev 0x4
(XEN) 64-bit Execution:
(XEN) Processor Features: 1100000000002222 0000000000000000
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN) Debug Features: 0000000010305106 0000000000000000
(XEN) Auxiliary Features: 0000000000000000 0000000000000000
(XEN) Memory Model Features: 0000000000001122 0000000000000000
(XEN) ISA Features: 0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN) Processor Features: 00001231:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
(XEN) Extensions: GenericTimer Security
(XEN) Debug Features: 03010066
(XEN) Auxiliary Features: 00000000
(XEN) Memory Model Features: 10101105 40000000 01260000 02102211
(XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using SMC Calling Convention v1.1
(XEN) Using PSCI v1.1
(XEN) SMP: Allowing 4 CPUs
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 65000 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=00000000f9010000
(XEN) gic_cpu_addr=00000000f9020000
(XEN) gic_hyp_addr=00000000f9040000
(XEN) gic_vcpu_addr=00000000f9060000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: Adjusting CPU interface base to 0xf902f000
(XEN) GICv2: 192 lines, 4 cpus (IID 00000000).
(XEN) XSM Framework v1.0.0 initialized
(XEN) Initialising XSM SILO mode
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) load_precision_shift: 18
(XEN) load_window_shift: 30
(XEN) underload_balance_tolerance: 0
(XEN) overload_balance_tolerance: -3
(XEN) runqueues arrangement: socket
(XEN) cap enforcement granularity: 10ms
(XEN) load tracking window length 1073741824 ns
(XEN) Allocated console ring of 32 KiB.
(XEN) CPU0: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU1
(XEN) CPU1: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU2
(XEN) CPU 1 booted.
(XEN) CPU2: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU3
(XEN) CPU 2 booted.
(XEN) CPU3: Guest atomics will try 1 times before pausing the domain
(XEN) Brought up 4 CPUs
(XEN) CPU 3 booted.
(XEN) P2M: 40-bit IPA with 40-bit PA and 8-bit VMID
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) smmu: /smmu@fd800000: probing hardware configuration...
(XEN) smmu: /smmu@fd800000: SMMUv2 with:
(XEN) smmu: /smmu@fd800000: stage 2 translation
(XEN) smmu: /smmu@fd800000: stream matching with 48 register groups, mask 0x7fff
(XEN) smmu: /smmu@fd800000: 16 context banks (0 stage-2 only)
(XEN) smmu: /smmu@fd800000: Stage-2: 40-bit IPA -> 48-bit PA
(XEN) smmu: /smmu@fd800000: registered 26 master devices
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) Adding cpu 0 to runqueue 0
(XEN) First cpu on runqueue, activating
(XEN) Adding cpu 1 to runqueue 0
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 3 to runqueue 0
(XEN) alternatives: Patching with alt table 00000000002c3e68 -> 00000000002c4528
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading d0 kernel from boot module @ 0000000000080000
(XEN) Loading ramdisk from boot module @ 00000000076df000
(XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
(XEN) BANK[0] 0x00000020000000-0x00000060000000 (1024MB)
(XEN) Grant table range: 0x00000004200000-0x00000004240000
(XEN) smmu: /smmu@fd800000: d0: p2maddr 0x000000087bf9a000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading zImage from 0000000000080000 to 0000000020080000-0000000023180000
(XEN) Loading dom0 initrd from 00000000076df000 to 0x0000000028200000-0x0000000028b20364
(XEN) Loading dom0 DTB to 0x0000000028000000-0x0000000028008db3
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 332kB init memory.
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER4
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER8
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER12
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER16
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER20
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 4.19.0-xilinx-v2019.1 (oe-user@oe-host) (gcc version 8.3.0 (GCC)) #1 SMP Mon Sep 16 21:16:49 UTC 2019
[ 0.000000] Machine model: ZynqMP ZCU102 Rev1.0
[ 0.000000] Xen 4.13 support found
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] cma: Reserved 256 MiB at 0x0000000050000000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: Trusted OS migration not required
[ 0.000000] psci: SMC Calling Convention v1.1
[ 0.000000] random: get_random_bytes called from start_kernel+0x94/0x3f8 with crng_init=0
[ 0.000000] percpu: Embedded 23 pages/cpu @(____ptrval____) s53656 r8192 d32360 u94208
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: enabling workaround for ARM erratum 843419
[ 0.000000] CPU features: enabling workaround for ARM erratum 845719
[ 0.000000] Speculative Store Bypass Disable mitigation not required
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 258560
[ 0.000000] Kernel command line: console=hvc0 earlycon=xen earlyprintk=xen clk_ignore_unused
[ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.000000] Memory: 727836K/1048576K available (10812K kernel code, 636K rwdata, 5436K rodata, 832K init, 316K bss, 58596K reserved, 262144K cma-reserved)
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU event tracing is enabled.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] arch_timer: cp15 timer(s) running at 65.00MHz (virt).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xefdb196da, max_idle_ns: 440795204367 ns
[ 0.000187] sched_clock: 56 bits at 65MHz, resolution 15ns, wraps every 2199023255550ns
[ 0.014877] Console: colour dummy device 80x25
[ 0.038027] console [hvc0] enabled
[ 0.039888] Calibrating delay loop (skipped), value calculated using timer frequency.. 130.00 BogoMIPS (lpj=260000)
[ 0.041386] pid_max: default: 32768 minimum: 301
[ 0.044785] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.045963] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.095986] ASID allocator initialised with 32768 entries
[ 0.125944] xen:grant_table: Grant tables using version 1 layout
[ 0.128575] Grant table initialized
[ 0.130614] xen:events: Using FIFO-based ABI
[ 0.133101] Xen: initializing cpu0
[ 0.136546] rcu: Hierarchical SRCU implementation.
[ 0.144127] EFI services will not be available.
[ 0.148328] smp: Bringing up secondary CPUs ...
(XEN) d0v1: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
(XEN) d0v2: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
(XEN) d0v3: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
[ 0.157088] Detected VIPT I-cache on CPU1
[ 0.160631] Xen: initializing cpu1
[ 0.161124] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.176014] Detected VIPT I-cache on CPU2
[ 0.177413] Xen: initializing cpu2
[ 0.177683] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.189775] Detected VIPT I-cache on CPU3
[ 0.191512] Xen: initializing cpu3
[ 0.191873] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.196127] smp: Brought up 1 node, 4 CPUs
[ 0.202335] SMP: Total of 4 processors activated.
[ 0.203328] CPU features: detected: 32-bit EL0 Support
[ 0.207121] CPU: All CPU(s) started at EL1
[ 0.209995] alternatives: patching kernel code
[ 0.241280] devtmpfs: initialized
[ 0.274871] Duplicate name in base, renamed to "memory#1"
[ 0.291631] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.292955] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.326137] xor: measuring software checksum speed
[ 0.368712] 8regs : 1570.000 MB/sec
[ 0.411173] 8regs_prefetch: 670.000 MB/sec
[ 0.453717] 32regs : 1473.000 MB/sec
[ 0.496061] 32regs_prefetch: 1487.000 MB/sec
[ 0.496820] xor: using function: 8regs (1570.000 MB/sec)
[ 0.497848] pinctrl core: initialized pinctrl subsystem
[ 0.531356] NET: Registered protocol family 16
[ 0.542985] audit: initializing netlink subsys (disabled)
[ 0.551328] audit: type=2000 audit(0.480:1): state=initialized audit_enabled=0 res=1
[ 0.579037] vdso: 2 pages (1 code @ (____ptrval____), 1 data @ (____ptrval____))
[ 0.582688] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.609680] DMA: preallocated 256 KiB pool for atomic allocations
[ 0.612524] xen:swiotlb_xen: Warning: only able to allocate 4 MB for software IO TLB
[ 0.626620] software IO TLB: mapped [mem 0x4d400000-0x4d800000] (4MB)
[ 0.922838] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 1.014553] raid6: int64x1 gen() 713 MB/s
[ 1.094148] raid6: int64x1 xor() 451 MB/s
[ 1.173144] raid6: int64x2 gen() 911 MB/s
[ 1.253055] raid6: int64x2 xor() 517 MB/s
[ 1.337241] raid6: int64x4 gen() 1439 MB/s
[ 1.420751] raid6: int64x4 xor() 394 MB/s
[ 1.501362] raid6: int64x8 gen() 1073 MB/s
[ 1.588967] raid6: int64x8 xor() 483 MB/s
[ 1.671314] raid6: neonx1 gen() 555 MB/s
[ 1.755222] raid6: neonx1 xor() 327 MB/s
[ 1.837742] raid6: neonx2 gen() 675 MB/s
[ 1.917942] raid6: neonx2 xor() 351 MB/s
[ 2.002178] raid6: neonx4 gen() 707 MB/s
[ 2.086068] raid6: neonx4 xor() 378 MB/s
[ 2.169306] raid6: neonx8 gen() 678 MB/s
[ 2.256944] raid6: neonx8 xor() 324 MB/s
[ 2.257797] raid6: using algorithm int64x4 gen() 1439 MB/s
[ 2.258864] raid6: .... xor() 394 MB/s, rmw enabled
[ 2.259623] raid6: using neon recovery algorithm
[ 2.268414] xen:balloon: Initialising balloon driver
[ 2.280389] SCSI subsystem initialized
[ 2.286679] usbcore: registered new interface driver usbfs
[ 2.289433] usbcore: registered new interface driver hub
[ 2.292037] usbcore: registered new device driver usb
[ 2.294868] media: Linux media interface: v0.10
[ 2.296800] videodev: Linux video capture interface: v2.00
[ 2.297925] pps_core: LinuxPPS API ver. 1 registered
[ 2.299068] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 2.301473] PTP clock support registered
[ 2.302868] EDAC MC: Ver: 3.0.0
[ 2.325066] zynqmp-ipi-mbox mailbox@ff990400: Probed ZynqMP IPI Mailbox driver.
[ 2.332219] FPGA manager framework
[ 2.339159] Advanced Linux Sound Architecture Driver Initialized.
[ 2.355807] Bluetooth: Core ver 2.22
[ 2.357352] NET: Registered protocol family 31
[ 2.358190] Bluetooth: HCI device and connection manager initialized
[ 2.359932] Bluetooth: HCI socket layer initialized
[ 2.361133] Bluetooth: L2CAP socket layer initialized
[ 2.362570] Bluetooth: SCO socket layer initialized
[ 2.381595] clocksource: Switched to clocksource arch_sys_counter
[ 2.387863] VFS: Disk quotas dquot_6.6.0
[ 2.389835] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 2.539774] NET: Registered protocol family 2
[ 2.555479] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes)
[ 2.557302] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 2.558762] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[ 2.560158] TCP: Hash tables configured (established 8192 bind 8192)
[ 2.566089] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 2.567470] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 2.571551] NET: Registered protocol family 1
[ 2.592826] RPC: Registered named UNIX socket transport module.
[ 2.594557] RPC: Registered udp transport module.
[ 2.595355] RPC: Registered tcp transport module.
[ 2.595902] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 2.614851] Trying to unpack rootfs image as initramfs...
[ 4.740251] Freeing initrd memory: 9344K
[ 4.765443] Initialise system trusted keyrings
[ 4.770758] workingset: timestamp_bits=62 max_order=18 bucket_order=0
[ 4.803719] NFS: Registering the id_resolver key type
[ 4.805475] Key type id_resolver registered
[ 4.806079] Key type id_legacy registered
[ 4.806808] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 4.808279] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 6.453560] NET: Registered protocol family 38
[ 6.607526] Key type asymmetric registered
[ 6.608394] Asymmetric key parser 'x509' registered
[ 6.610910] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[ 6.612076] io scheduler noop registered
[ 6.613116] io scheduler deadline registered
[ 6.614108] io scheduler cfq registered (default)
[ 6.614686] io scheduler mq-deadline registered
[ 6.615223] io scheduler kyber registered
[ 6.648343] OF: /amba/dma@fd500000: could not find phandle
[ 6.650762] OF: /amba/dma@fd510000: could not find phandle
[ 6.652047] OF: /amba/dma@fd520000: could not find phandle
[ 6.654383] OF: /amba/dma@fd530000: could not find phandle
[ 6.655616] OF: /amba/dma@fd540000: could not find phandle
[ 6.657589] OF: /amba/dma@fd550000: could not find phandle
[ 6.659022] OF: /amba/dma@fd560000: could not find phandle
[ 6.660296] OF: /amba/dma@fd570000: could not find phandle
[ 6.677808] xen:xen_evtchn: Event-channel device installed
[ 8.679402] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 8.888333] brd: module loaded
[ 8.957493] loop: module loaded
[ 8.975211] mtdoops: mtd device (mtddev=name/number) must be supplied
[ 8.984150] OF: /amba/spi@ff0f0000: could not find phandle
[ 9.005750] libphy: Fixed MDIO Bus: probed
[ 9.031025] tun: Universal TUN/TAP device driver, 1.6
[ 9.051550] CAN device driver interface
[ 9.065683] xen_netfront: Initialising Xen virtual ethernet driver
[ 9.067527] usbcore: registered new interface driver asix
[ 9.069506] usbcore: registered new interface driver ax88179_178a
[ 9.071320] usbcore: registered new interface driver cdc_ether
[ 9.073852] usbcore: registered new interface driver net1080
[ 9.075284] usbcore: registered new interface driver cdc_subset
[ 9.077488] usbcore: registered new interface driver zaurus
[ 9.078861] usbcore: registered new interface driver cdc_ncm
[ 9.097405] usbcore: registered new interface driver uas
[ 9.098956] usbcore: registered new interface driver usb-storage
[ 9.123263] rtc_zynqmp ffa60000.rtc: rtc core: registered ffa60000.rtc as rtc0
[ 9.126336] i2c /dev entries driver
[ 9.168401] usbcore: registered new interface driver uvcvideo
[ 9.170219] USB Video Class driver (1.1.1)
[ 9.189011] Bluetooth: HCI UART driver ver 2.3
[ 9.190300] Bluetooth: HCI UART protocol H4 registered
[ 9.190887] Bluetooth: HCI UART protocol BCSP registered
[ 9.193790] Bluetooth: HCI UART protocol LL registered
[ 9.194212] Bluetooth: HCI UART protocol ATH3K registered
[ 9.195268] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 9.198265] Bluetooth: HCI UART protocol Intel registered
[ 9.199806] Bluetooth: HCI UART protocol QCA registered
[ 9.202233] usbcore: registered new interface driver bcm203x
[ 9.203677] usbcore: registered new interface driver bpa10x
[ 9.205870] usbcore: registered new interface driver bfusb
[ 9.207416] usbcore: registered new interface driver btusb
[ 9.207991] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[ 9.210060] usbcore: registered new interface driver ath3k
[ 9.215315] EDAC MC: ECC not enabled
[ 9.219734] EDAC ZynqMP-OCM: ECC not enabled - Disabling EDAC driver
[ 9.226639] cpu cpu0: failed to get clock: -2
[ 9.227455] cpufreq-dt: probe of cpufreq-dt failed with error -2
[ 9.233655] sdhci: Secure Digital Host Controller Interface driver
[ 9.234310] sdhci: Copyright(c) Pierre Ossman
[ 9.234782] sdhci-pltfm: SDHCI platform and OF driver helper
[ 9.252074] ledtrig-cpu: registered to indicate activity on CPUs
[ 9.256443] zynqmp_firmware_probe Platform Management API v1.1
[ 9.258526] zynqmp_firmware_probe Trustzone version v1.0
[ 9.416122] zynqmp-pinctrl firmware:zynqmp-firmware:pinctrl: zynqmp pinctrl initialized
[ 10.351793] zynqmp_clk_mux_get_parent() getparent failed for clock: lpd_wdt, ret = -22
[ 10.374747] alg: No test for xilinx-zynqmp-aes (zynqmp-aes)
[ 10.379006] zynqmp_aes zynqmp_aes: AES Successfully Registered
[ 10.379006]
[ 10.395910] alg: No test for xilinx-keccak-384 (zynqmp-keccak-384)
[ 10.411748] alg: No test for xilinx-zynqmp-rsa (zynqmp-rsa)
[ 10.423719] usbcore: registered new interface driver usbhid
[ 10.424338] usbhid: USB HID core driver
[ 10.490912] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[ 10.503819] usbcore: registered new interface driver snd-usb-audio
[ 10.532250] pktgen: Packet Generator for packet performance testing. Version: 2.75
[ 10.569213] Initializing XFRM netlink socket
[ 10.571617] NET: Registered protocol family 10
[ 10.592010] Segment Routing with IPv6
[ 10.597834] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 10.607228] NET: Registered protocol family 17
[ 10.608363] NET: Registered protocol family 15
[ 10.611095] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 10.619177] can: controller area network core (rev 20170425 abi 9)
[ 10.622296] NET: Registered protocol family 29
[ 10.623320] can: raw protocol (rev 20170425)
[ 10.624039] can: broadcast manager protocol (rev 20170425 t)
[ 10.626776] can: netlink gateway (rev 20170425) max_hops=1
[ 10.635096] Bluetooth: RFCOMM TTY layer initialized
[ 10.638144] Bluetooth: RFCOMM socket layer initialized
[ 10.639447] Bluetooth: RFCOMM ver 1.11
[ 10.640526] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.642514] Bluetooth: BNEP filters: protocol multicast
[ 10.643292] Bluetooth: BNEP socket layer initialized
[ 10.644150] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 10.645902] Bluetooth: HIDP socket layer initialized
[ 10.651298] 9pnet: Installing 9P2000 support
[ 10.653393] Key type dns_resolver registered
[ 10.675782] registered taskstats version 1
[ 10.677688] Loading compiled-in X.509 certificates
[ 10.685503] Btrfs loaded, crc32c=crc32c-generic
[ 10.777889] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 42, base_baud = 2479910) is a xuartps
[ 10.831149] of-fpga-region fpga-full: FPGA Region probed
[ 10.855207] nwl-pcie fd0e0000.pcie: Link is UP
[ 10.857587] nwl-pcie fd0e0000.pcie: host bridge /amba/pcie@fd0e0000 ranges:
[ 10.859285] nwl-pcie fd0e0000.pcie: MEM 0xe0000000..0xefffffff -> 0xe0000000
[ 10.861504] nwl-pcie fd0e0000.pcie: MEM 0x600000000..0x7ffffffff -> 0x600000000
[ 10.878305] nwl-pcie fd0e0000.pcie: PCI host bridge to bus 0000:00
[ 10.879776] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 10.881949] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 10.882745] pci_bus 0000:00: root bus resource [mem 0x600000000-0x7ffffffff pref]
[ 10.939267] xilinx-dpdma fd4c0000.dma: Xilinx DPDMA engine is probed
[ 10.942636] OF: /amba/dma@fd500000: could not find phandle
[ 10.952392] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success
[ 10.955784] OF: /amba/dma@fd510000: could not find phandle
[ 10.959604] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success
[ 10.963155] OF: /amba/dma@fd520000: could not find phandle
[ 10.967328] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success
[ 10.972127] OF: /amba/dma@fd530000: could not find phandle
[ 10.984219] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success
[ 10.990969] OF: /amba/dma@fd540000: could not find phandle
[ 10.998890] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success
[ 11.003722] OF: /amba/dma@fd550000: could not find phandle
[ 11.008451] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success
[ 11.014072] OF: /amba/dma@fd560000: could not find phandle
[ 11.018192] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success
[ 11.022348] OF: /amba/dma@fd570000: could not find phandle
[ 11.026906] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success
[ 11.038217] xilinx-zynqmp-dma ffa80000.dma: ZynqMP DMA driver Probe success
[ 11.047419] xilinx-zynqmp-dma ffa90000.dma: ZynqMP DMA driver Probe success
[ 11.054780] xilinx-zynqmp-dma ffaa0000.dma: ZynqMP DMA driver Probe success
[ 11.060455] xilinx-zynqmp-dma ffab0000.dma: ZynqMP DMA driver Probe success
[ 11.067010] xilinx-zynqmp-dma ffac0000.dma: ZynqMP DMA driver Probe success
[ 11.073652] xilinx-zynqmp-dma ffad0000.dma: ZynqMP DMA driver Probe success
[ 11.078947] xilinx-zynqmp-dma ffae0000.dma: ZynqMP DMA driver Probe success
[ 11.085621] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success
[ 11.098980] xilinx-psgtr fd400000.zynqmp_phy: Lane:1 type:8 protocol:4 pll_locked:yes
[ 11.177334] zynqmp_clk_divider_set_rate() set divider failed for ams_ref_div1, ret = -13
[ 11.288143] xilinx-dp-snd-codec fd4a0000.zynqmp-display:zynqmp_dp_snd_codec0: Failed to get required clock freq
[ 11.294376] xilinx-dp-snd-codec: probe of fd4a0000.zynqmp-display:zynqmp_dp_snd_codec0 failed with error -22
[ 11.302811] xilinx-dp-snd-pcm zynqmp_dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed
[ 11.309766] xilinx-dp-snd-pcm zynqmp_dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed
[ 11.317681] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: ASoC: CPU DAI (null) not registered
[ 11.322825] OF: graph: no port node found in /amba/zynqmp-display@fd4a0000
[ 11.333499] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 11.334622] [drm] No driver support for vblank timestamp query.
[ 11.341007] xlnx-drm xlnx-drm.0: bound fd4a0000.zynqmp-display (ops 0xffffff8008bcf5e0)
[ 11.591223] Console: switching to colour frame buffer device 128x48
[ 11.623881] zynqmp-display fd4a0000.zynqmp-display: fb0: frame buffer device
[ 11.632004] [drm] Initialized xlnx 1.0.0 20130509 for fd4a0000.zynqmp-display on minor 0
[ 11.634724] zynqmp-display fd4a0000.zynqmp-display: ZynqMP DisplayPort Subsystem driver probed
[ 11.653595] xilinx-psgtr fd400000.zynqmp_phy: Lane:3 type:3 protocol:2 pll_locked:yes
[ 11.659283] ahci-ceva fd0c0000.ahci: AHCI 0001.0000 32 slots 2 ports 1.5 Gbps 0x3 impl platform mode
[ 11.661161] ahci-ceva fd0c0000.ahci: flags: 64bit ncq only
[ 11.691718] scsi host0: ahci-ceva
[ 11.701756] scsi host1: ahci-ceva
[ 11.706625] ata1: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x100 irq 40
[ 11.707844] ata2: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x180 irq 40
[ 11.713473] OF: /amba/spi@ff0f0000: could not find phandle
[ 11.758795] m25p80 spi0.0: n25q512a (131072 Kbytes)
[ 11.761881] 3 fixed-partitions partitions found on MTD device spi0.0
[ 11.763015] Creating 3 MTD partitions on "spi0.0":
[ 11.763926] 0x000000000000-0x000001e00000 : "boot"
[ 11.783917] 0x000001e00000-0x000001e40000 : "bootenv"
[ 11.802300] 0x000001e40000-0x000004240000 : "kernel"
[ 11.928974] OF: /amba/ethernet@ff0e0000: could not find phandle
[ 11.942285] macb ff0e0000.ethernet: Not enabling partial store and forward
[ 11.943803] macb: GEM doesn't support hardware ptp.
[ 11.958257] libphy: MACB_mii_bus: probed
[ 12.035793] ata2: SATA link down (SStatus 0 SControl 300)
[ 12.042107] ata1: SATA link down (SStatus 0 SControl 300)
[ 12.198649] Marvell 88E1118 ff0e0000.ethernet-ffffffff:0c: attached PHY driver [Marvell 88E1118] (mii_bus:phy_addr=ff0e0000.ethernet-ffffffff:0c, irq=POLL)
[ 12.201283] macb ff0e0000.ethernet eth0: Cadence GEM rev 0x40070106 at 0xff0e0000 irq 25 (00:0a:35:00:22:01)
[ 12.209855] xilinx-axipmon ffa00000.perf-monitor: Probed Xilinx APM
[ 12.218817] xilinx-axipmon fd0b0000.perf-monitor: Probed Xilinx APM
[ 12.227413] xilinx-axipmon fd490000.perf-monitor: Probed Xilinx APM
[ 12.235184] xilinx-axipmon ffa10000.perf-monitor: Probed Xilinx APM
[ 12.355418] OF: /amba/usb0@ff9d0000/dwc3@fe200000: could not find phandle
[ 12.364085] dwc3 fe200000.dwc3: Failed to get clk 'ref': -2
[ 12.387237] dwc3 fe200000.dwc3: Configuration mismatch. dr_mode forced to gadget
[ 12.389498] dwc3 fe200000.dwc3: this is not a DesignWare USB3 DRD Core
[ 12.391165] dwc3 fe200000.dwc3: failed to initialize core
[ 12.432037] pca953x 0-0020: 0-0020 supply vcc not found, using dummy regulator
[ 12.435311] pca953x 0-0020: Linked as a consumer to regulator.0
[ 12.450872] pca953x 0-0021: 0-0021 supply vcc not found, using dummy regulator
[ 12.452052] pca953x 0-0021: Linked as a consumer to regulator.0
[ 12.481056] ina2xx 3-0040: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.490833] ina2xx 3-0041: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.498810] ina2xx 3-0042: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.506734] ina2xx 3-0043: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.515770] ina2xx 3-0044: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.524179] ina2xx 3-0045: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.531713] ina2xx 3-0046: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.539135] ina2xx 3-0047: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.547721] ina2xx 3-004a: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.558475] ina2xx 3-004b: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.560204] i2c i2c-0: Added multiplexed i2c bus 3
[ 12.572260] ina2xx 4-0040: power monitor ina226 (Rshunt = 2000 uOhm)
[ 12.582877] ina2xx 4-0041: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.591273] ina2xx 4-0042: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.598863] ina2xx 4-0043: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.607568] ina2xx 4-0044: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.615698] ina2xx 4-0045: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.623637] ina2xx 4-0046: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.631058] ina2xx 4-0047: power monitor ina226 (Rshunt = 5000 uOhm)
[ 12.633609] i2c i2c-0: Added multiplexed i2c bus 4
[ 12.671705] max20751 5-0072: Failed to identify chip capabilities
[ 12.683220] max20751 5-0073: Failed to identify chip capabilities
[ 12.684374] i2c i2c-0: Added multiplexed i2c bus 5
[ 12.688412] i2c i2c-0: Added multiplexed i2c bus 6
[ 12.690222] pca954x 0-0075: registered 4 multiplexed busses for I2C mux pca9544
[ 12.692209] cdns-i2c ff020000.i2c: 400 kHz mmio ff020000 irq 27
[ 12.749448] at24 7-0054: 1024 byte 24c08 EEPROM, writable, 1 bytes/write
[ 12.751221] i2c i2c-1: Added multiplexed i2c bus 7
[ 12.758081] i2c i2c-1: Added multiplexed i2c bus 8
[ 12.795535] si570 9-005d: registered, current frequency 300000000 Hz
[ 12.798892] i2c i2c-1: Added multiplexed i2c bus 9
[ 12.842746] si570 10-005d: registered, current frequency 148500000 Hz
[ 12.845526] i2c i2c-1: Added multiplexed i2c bus 10
[ 12.851693] si5324 11-0069: si5328 probed
[ 12.959905] si5324 11-0069: si5328 probe successful
[ 12.962602] i2c i2c-1: Added multiplexed i2c bus 11
[ 12.967159] i2c i2c-1: Added multiplexed i2c bus 12
[ 12.971903] i2c i2c-1: Added multiplexed i2c bus 13
[ 12.975988] i2c i2c-1: Added multiplexed i2c bus 14
[ 12.977810] pca954x 1-0074: registered 8 multiplexed busses for I2C switch pca9548
[ 12.986526] i2c i2c-1: Added multiplexed i2c bus 15
[ 12.993749] i2c i2c-1: Added multiplexed i2c bus 16
[ 12.998045] i2c i2c-1: Added multiplexed i2c bus 17
[ 13.011805] i2c i2c-1: Added multiplexed i2c bus 18
[ 13.016105] i2c i2c-1: Added multiplexed i2c bus 19
[ 13.022575] i2c i2c-1: Added multiplexed i2c bus 20
[ 13.030834] i2c i2c-1: Added multiplexed i2c bus 21
[ 13.039436] i2c i2c-1: Added multiplexed i2c bus 22
[ 13.040192] pca954x 1-0075: registered 8 multiplexed busses for I2C switch pca9548
[ 13.043055] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 28
[ 13.059767] cdns-wdt fd4d0000.watchdog: Xilinx Watchdog Timer at (____ptrval____) with timeout 60s
[ 13.071290] cdns-wdt ff150000.watchdog: Xilinx Watchdog Timer at (____ptrval____) with timeout 10s
[ 13.155397] OF: /amba/mmc@ff170000: could not find phandle
[ 13.225799] mmc0: SDHCI controller on ff170000.mmc [ff170000.mmc] using ADMA 64-bit
[ 13.256193] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: ASoC: CPU DAI (null) not registered
[ 13.263536] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: ASoC: CPU DAI (null) not registered
[ 13.305681] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 13.319376] rtc_zynqmp ffa60000.rtc: setting system clock to 2019-09-25 23:11:02 UTC (1569453062)
[ 13.321397] of_cfs_init
[ 13.322618] of_cfs_init: OK
[ 13.323972] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 13.332430] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: ASoC: CPU DAI (null) not registered
[ 13.640023] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 13.642385] clk: Not disabling unused clocks
[ 13.643172] ALSA device list:
[ 13.643558] No soundcards found.
[ 13.653880] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 13.656345] cfg80211: failed to load regulatory.db
[ 13.735227] Freeing unused kernel memory: 832K
[ 13.773488] Run /init as init process
\rINIT: version 2.88 booting
[ 13.983079] random: fast init done
Starting udev
[ 16.738379] udevd[1953]: starting version 3.2.7
[ 16.750045] random: udevd: uninitialized urandom read (16 bytes read)
[ 16.755853] random: udevd: uninitialized urandom read (16 bytes read)
[ 16.758589] random: udevd: uninitialized urandom read (16 bytes read)
[ 16.816342] udevd[1953]: specified group 'kvm' unknown
[ 16.886994] udevd[1954]: starting eudev-3.2.7
[ 17.079037] udevd[1954]: specified group 'kvm' unknown
[ 18.047529] urandom_read: 3 callbacks suppressed
[ 18.048148] random: udevd: uninitialized urandom read (16 bytes read)
[ 19.929071] random: udevd: uninitialized urandom read (16 bytes read)
[ 37.429717] random: dd: uninitialized urandom read (512 bytes read)
Configuring packages on first boot....
(This may take several minutes. Please do not power off the machine.)
Running postinst /etc/rpm-postinsts/100-sysvinit-inittab...
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
Removing any system startup links for run-postinsts ...
/etc/rcS.d/S99run-postinsts
\rINIT: Entering runlevel: 5
Configuring network interfaces... [ 42.089608] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc: started, v1.30.1
udhcpc: sending discover
[ 43.202444] macb ff0e0000.ethernet eth0: link up (100/Full)
[ 43.204166] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
udhcpc: sending discover
udhcpc: sending select for 10.0.5.15
udhcpc: lease of 10.0.5.15 obtained, lease time 86400
/etc/udhcpc.d/50default: Adding DNS 10.0.5.3
done.
Starting Dropbear SSH server: [ 47.689556] random: dropbearkey: uninitialized urandom read (32 bytes read)
Generating 2048 bit rsa key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCmxEx8MqHJk6dl+uPH6JYn6sQJo0+Bf9qqpPeWzNHV/8CLtKnohuuv2aKj+Y1Nhi969+OYef9SY7KM6Gttb7i45a3tqtSomML/Ccnn26LcANdO9DkAoX48oukdRDIdqKIirD8c0eiKbj48oVcNcmoXfprIIKqnQktpk1y5tzX7dQJ8/8X5sBQ7BUw1pQuoToipO9hhjz+d5Yow+F8TfcmsI/2ffpPCjGy9jZll/h19YnLf7f16pNxm+GT5lOqIyxQr3BUnV4nYVhUG9Ae3Ke5pL9H/kX11saiGt21abwILSL8ek4IxqDWQADPmJuoJ42Jo6Znv8twY0BKCKsMcb+07 root@zcu102-zynqmp
Fingerprint: sha1!! bf:ed:5d:2a:0e:fc:e6:6c:9b:db:3a:74:ba:91:12:f4:11:92:36:d8
dropbear.
Starting syslogd/klogd: done
Starting /usr/sbin/xenstored...
Setting domain 0 name, domid and JSON config...
WARNING: Failed to open connection to gnttab
Done setting up Dom0
Starting xenconsoled...
Starting QEMU as disk backend for dom0
/etc/rc5.d/S80xencommons: line 73: /usr/bin/qemu-system-i386: No such file or directory
Starting domain watchdog daemon: xenwatchdogd startup
[done]
Poky (Yocto Project Reference Distro) 2.7.1 zcu102-zynqmp /dev/hvc0
\rzcu102-zynqmp login: root
rroot@zcu102-zynqmp:~# root\b \b\b \b\b \b\b \bpowerof\af
\a
Broadcast message from root@zcu102-zynqmp (hvc0) (Wed Sep 25 23:11:53 2019):\r\rThe system is going down for system halt NOW!
root@zcu102-zynqmp:~# \rINIT: Switching to runlevel: 0
\rINIT: Sending processes the TERM signal
logout
Stopping Dropbear SSH server: stopped /usr/sbin/dropbear (pid 2194)
dropbear.
Stopping syslogd/klogd: stopped syslogd (pid 2202)
stopped klogd (pid 2205)
done
Deconfiguring network interfaces... [ 68.520044] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 68.535851] macb ff0e0000.ethernet eth0: link up (100/Full)
[ 68.550329] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
done.
Stopping xenconsoled
Stopping QEMU
WARNING: Not stopping xenstored, as it cannot be restarted.
Stopping domain watchdog daemon: xenwatchdogd stop
Shutting down Xen domains:[done]
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Unmounting remote filesystems...
Deactivating swap...
Unmounting local filesystems...
[ 82.799302] Console: switching to colour dummy device 80x25
[ 82.847327] reboot: Power down
(XEN) Hardware Dom0 halted: halting machine
[-- Attachment #3: xen_bad_addr.log --]
[-- Type: text/plain, Size: 13858 bytes --]
PMU Firmware 2019.1 May 25 2019 06:57:33
PMU_ROM Version: xpbr-v8.1.0-0
NOTICE: ATF running on XCZUUNKN/QEMU v4/RTL0.0 at 0xfffea000
NOTICE: BL31: Secure code at 0x60000000
NOTICE: BL31: Non secure code at 0x10080000
NOTICE: BL31: v2.0(release):xilinx-v2018.3-720-g80d1c790
NOTICE: BL31: Built : 06:54:23, May 25 2019
PMUFW: v1.1
U-Boot 2019.01 (May 25 2019 - 06:55:09 +0000)
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
DRAM: 4 GiB
EL Level: EL2
Chip ID: unknown
MMC: mmc@ff170000: 0
Loading Environment from SPI Flash... SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
*** Warning - bad CRC, using default environment
In: serial@ff000000
Out: serial@ff000000
Err: serial@ff000000
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
Bootmode: JTAG_MODE
Reset reason: EXTERNAL
Net: ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for xilinx-zcu102-2019_1
BOOTP broadcast 1
DHCP client bound to address 10.0.5.15 (2 ms)
Hit any key to stop autoboot: 4 \b\b\b 3 \b\b\b 0
ZynqMP> setenv serverip 10.0.5.2; tftpb 1280000 xen-qemu-mod.dtb; tftpb 0x80000 yocto-Image; tftpb 1400000 xen-custom.ub; tftpb 9000000 yocto-rootfs.cpio.gz.ub; bootm 1400000 9000000 1280000
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'xen-qemu-mod.dtb'.
Load address: 0x1280000
Loading: *\b###
18.1 MiB/s
done
Bytes transferred = 38019 (9483 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'yocto-Image'.
Load address: 0x80000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#########################################
36.4 MiB/s
done
Bytes transferred = 18215424 (115f200 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'xen-custom.ub'.
Load address: 0x1400000
Loading: *\b#################################################################
####
36.1 MiB/s
done
Bytes transferred = 984464 (f0590 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'yocto-rootfs.cpio.gz.ub'.
Load address: 0x9000000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#####################
37.1 MiB/s
done
Bytes transferred = 9569188 (9203a4 hex)
## Booting kernel from Legacy Image at 01400000 ...
Image Name:
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 984400 Bytes = 961.3 KiB
Load Address: 01400000
Entry Point: 01400000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 09000000 ...
Image Name:
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 9569124 Bytes = 9.1 MiB
Load Address: 09000000
Entry Point: 09000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01280000
Booting using the fdt blob at 0x1280000
Loading Kernel Image ... OK
Loading Ramdisk to 076df000, end 07fff364 ... OK
Loading Device Tree to 00000000076d2000, end 00000000076de482 ... OK
Starting kernel ...
Xen 4.13-unstable
(XEN) Xen version 4.13-unstable (woods@xilinx.com) (aarch64-unknown-linux-gnu-gcc (crosstool-NG 1.24.0.6-afaf7b9) 8.3.0) debug=y Wed Sep 25 16:02:26 PDT 2019
(XEN) Latest ChangeSet: Tue Sep 24 15:46:48 2019 +0000 git:4333876
(XEN) build-id: a026a3bc865f1c93f67de50e71b7aea86f79e5b9
(XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev 0x4
(XEN) 64-bit Execution:
(XEN) Processor Features: 1100000000002222 0000000000000000
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN) Debug Features: 0000000010305106 0000000000000000
(XEN) Auxiliary Features: 0000000000000000 0000000000000000
(XEN) Memory Model Features: 0000000000001122 0000000000000000
(XEN) ISA Features: 0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN) Processor Features: 00001231:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
(XEN) Extensions: GenericTimer Security
(XEN) Debug Features: 03010066
(XEN) Auxiliary Features: 00000000
(XEN) Memory Model Features: 10101105 40000000 01260000 02102211
(XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using SMC Calling Convention v1.1
(XEN) Using PSCI v1.1
(XEN) SMP: Allowing 4 CPUs
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 65000 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=00000000f9010000
(XEN) gic_cpu_addr=00000000f9020000
(XEN) gic_hyp_addr=00000000f9040000
(XEN) gic_vcpu_addr=00000000f9060000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: Adjusting CPU interface base to 0xf902f000
(XEN) GICv2: 192 lines, 4 cpus (IID 00000000).
(XEN) XSM Framework v1.0.0 initialized
(XEN) Initialising XSM SILO mode
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) load_precision_shift: 18
(XEN) load_window_shift: 30
(XEN) underload_balance_tolerance: 0
(XEN) overload_balance_tolerance: -3
(XEN) runqueues arrangement: socket
(XEN) cap enforcement granularity: 10ms
(XEN) load tracking window length 1073741824 ns
(XEN) Allocated console ring of 32 KiB.
(XEN) CPU0: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU1
(XEN) CPU1: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU2
(XEN) CPU 1 booted.
(XEN) CPU2: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU3
(XEN) CPU 2 booted.
(XEN) CPU3: Guest atomics will try 1 times before pausing the domain
(XEN) Brought up 4 CPUs
(XEN) CPU 3 booted.
(XEN) P2M: 40-bit IPA with 40-bit PA and 8-bit VMID
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) smmu: /smmu@fd800000: probing hardware configuration...
(XEN) smmu: /smmu@fd800000: SMMUv2 with:
(XEN) smmu: /smmu@fd800000: stage 2 translation
(XEN) smmu: /smmu@fd800000: stream matching with 48 register groups, mask 0x7fff
(XEN) smmu: /smmu@fd800000: 16 context banks (0 stage-2 only)
(XEN) smmu: /smmu@fd800000: Stage-2: 40-bit IPA -> 48-bit PA
(XEN) smmu: /smmu@fd800000: registered 26 master devices
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) Adding cpu 0 to runqueue 0
(XEN) First cpu on runqueue, activating
(XEN) Adding cpu 1 to runqueue 0
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 3 to runqueue 0
(XEN) alternatives: Patching with alt table 00000000002c3e68 -> 00000000002c4528
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading d0 kernel from boot module @ 0000000000080000
(XEN) Loading ramdisk from boot module @ 00000000076df000
(XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
(XEN) BANK[0] 0x00000020000000-0x00000060000000 (1024MB)
(XEN) Grant table range: 0x00000001400000-0x00000001440000
(XEN) smmu: /smmu@fd800000: d0: p2maddr 0x000000087bf9a000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading zImage from 0000000000080000 to 0000000020080000-0000000023180000
(XEN) Loading dom0 initrd from 00000000076df000 to 0x0000000028200000-0x0000000028b20364
(XEN) Loading dom0 DTB to 0x0000000028000000-0x0000000028008db3
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) pg[0] MFN 01533 c=0x180000000000000 o=0 v=0x7ffff t=0
(XEN) Xen BUG at page_alloc.c:1422
(XEN) ----[ Xen-4.13-unstable arm64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) PC: 000000000021bfcc page_alloc.c#free_heap_pages+0x1b4/0x5ec
(XEN) LR: 000000000021bfcc
(XEN) SP: 00008000fbff7d10
(XEN) CPSR: 60000249 MODE:64-bit EL2h (Hypervisor, handler)
(XEN) X0: 00000000002a1558 X1: 0000000000000068 X2: 0000000000000000
(XEN) X3: 0000000000000000 X4: 0000000000000000 X5: 0000000000000012
(XEN) X6: 0000000000000080 X7: fefefefefefeff09 X8: 7f7f7f7f7f7f7f7f
(XEN) X9: 731f646b61606d54 X10: 7f7f7f7f7f7f7f7f X11: 0101010101010101
(XEN) X12: 0000000000000008 X13: 000000000027c8c0 X14: 0000000000000020
(XEN) X15: 0000000000000000 X16: 00000000002a3000 X17: 00000000002a3000
(XEN) X18: 00000000002a3000 X19: 0000000000000000 X20: 0000000000000000
(XEN) X21: 000000080004a328 X22: 0000000000000000 X23: 6db6db6db6db6db7
(XEN) X24: fffffff800000000 X25: 3d3d3d3d3d3d3d3d X26: 00000000002a3000
(XEN) X27: 00000000002a3000 X28: 00000000002a3000 FP: 00008000fbff7d10
(XEN)
(XEN) VTCR_EL2: 80023558
(XEN) VTTBR_EL2: 0000000000000000
(XEN)
(XEN) SCTLR_EL2: 30cd183d
(XEN) HCR_EL2: 0000000000000038
(XEN) TTBR0_EL2: 000000000152c000
(XEN)
(XEN) ESR_EL2: f2000001
(XEN) HPFAR_EL2: 0000000000000000
(XEN) FAR_EL2: 0000000000000000
(XEN)
(XEN) Xen stack trace from sp=00008000fbff7d10:
(XEN) 00008000fbff7d80 000000000021e6f0 000000080004a328 00000000000014b3
(XEN) 00000000002fad40 0000000000003100 00000000002a3488 0000000800001c00
(XEN) 0000000000000000 00000000000fff00 00000000002d03c0 6db6db6db6db6db7
(XEN) 00000000002a10f8 0000000d002a1118 00008000fbff7df0 000000000021e914
(XEN) 0000000000000002 0000000000000002 0000000000080000 0000000003180000
(XEN) 000000000021e880 00000000002fa000 0000000003180000 00000000000fff00
(XEN) 00000000002d03c0 ffffffffffffffff 0000000000000001 00000000002fad90
(XEN) 00008000fbff7e00 00000000002b8354 00008000fbff7e50 00000000002b886c
(XEN) 00000000002d0408 0000000000000003 0000000000080000 00000000002a34b8
(XEN) 00000000002d03c0 000000000021e880 00000000076df000 0000000007fff364
(XEN) 00008000fbff7ea0 00000000002609dc 00000000002a2000 0000000000000004
(XEN) 00000000002a2380 000000000032d430 0000000000000004 0000000000296e58
(XEN) 0000000000000002 00000000002609d8 00000000002efde0 00000000002b94d4
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<000000000021bfcc>] page_alloc.c#free_heap_pages+0x1b4/0x5ec (PC)
(XEN) [<000000000021bfcc>] page_alloc.c#free_heap_pages+0x1b4/0x5ec (LR)
(XEN) [<000000000021e6f0>] page_alloc.c#init_heap_pages+0x3d4/0x564
(XEN) [<000000000021e914>] init_domheap_pages+0x94/0x9c
(XEN) [<00000000002b8354>] 00000000002b8354
(XEN) [<00000000002b886c>] 00000000002b886c
(XEN) [<00000000002609dc>] setup.c#init_done+0x10/0x20
(XEN) [<00000000002b94d4>] 00000000002b94d4
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at page_alloc.c:1422
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
[-- Attachment #4: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
[not found] ` <48c9fc54-553e-3b6b-bad2-dbad35991df0@arm.com>
@ 2019-10-02 16:52 ` Julien Grall
2019-10-02 18:56 ` Brian Woods
0 siblings, 1 reply; 14+ messages in thread
From: Julien Grall @ 2019-10-02 16:52 UTC (permalink / raw)
To: Brian Woods, Stefano Stabellini, xen-devel
Sorry I forgot to CC xen-devel back.
On 10/2/19 5:52 PM, Julien Grall wrote:
> On 10/2/19 1:32 AM, Brian Woods wrote:
>> Hello,
>
> Hi Brian,
>
> Thank you for report.
>
> I guess this Arm specific, right? If so, please try to CC
> the relevant maintainers and possibly add "arm" in the
> subject to avoid any delay (Xen-Devel has quite an high
> volume of e-mail!).
>
> May I also ask to avoiding sending attachment on the mailing
> list and instead upload the log somewhere (e.g. pastebin,
> your own webserver...)?
>
>>
>> While testing some things out, I found a possible bug in Xen. Xen would
>> successfully run when loaded (from u-boot) at some addresses but not
>> others. I didn't observe this issue in 4.11 stable, so I did a bisect
>> and found that:
>> commit f60658c6ae47e74792e6cc48ea2effac8bb52826
>> Author: Julien Grall <julien.grall@arm.com>
>> Date: Tue Dec 18 13:07:39 2018 +0000
>>
>> xen/arm: Stop relocating Xen
>>
>> was what was causing it to fail when it was loaded to that certain
>> address.
>
> This patch is basically changing how Xen is using the
> physical address space. So it exercise more part of Xen
> code and most likely a red-herring :).
>
> However, the logs are quite interesting:
>
> (XEN) pg[0] MFN 01533 c=0x180000000000000 o=0 v=0x7ffff t=0
>
> If I am not mistaken, the page state is PGC_state_free.
> So this seems to suggest that the page were already
> handed over to the allocator.
>
> Would you mind to apply the patch below and paste the log?
>
> Hopefully, you see see two WARN_ON() before Xen is crashing.
>
> Note the patch is assuming the MFN will stay the same after
> the patch has been applied. If not, you may need to slightly
> tweak it.
>
> diff --git a/xen/common/page_alloc.c b/xen/common/page_alloc.c
> index 7cb1bd368b..4bf0dbc727 100644
> --- a/xen/common/page_alloc.c
> +++ b/xen/common/page_alloc.c
> @@ -1389,6 +1389,9 @@ static void free_heap_pages(
>
> for ( i = 0; i < (1 << order); i++ )
> {
> +
> + WARN_ON(mfn_x(page_to_mfn(pg + 1)) == 0x01533);
> +
> /*
> * Cannot assume that count_info == 0, as there are some corner cases
> * where it isn't the case and yet it isn't a bug:
>
> Cheers,
>
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-02 16:52 ` Julien Grall
@ 2019-10-02 18:56 ` Brian Woods
2019-10-02 19:59 ` Julien Grall
0 siblings, 1 reply; 14+ messages in thread
From: Brian Woods @ 2019-10-02 18:56 UTC (permalink / raw)
To: Julien Grall
Cc: Brian Woods, Stefano Stabellini, Volodymyr Babchuk, xen-devel
[-- Attachment #1: Type: text/plain, Size: 2840 bytes --]
On 10/2/19 5:52 PM, Julien Grall wrote:
>On 10/2/19 1:32 AM, Brian Woods wrote:
>>Hello,
>
>Hi Brian,
>
>Thank you for report.
>
>I guess this Arm specific, right? If so, please try to CC
>the relevant maintainers and possibly add "arm" in the
>subject to avoid any delay (Xen-Devel has quite an high
>volume of e-mail!).
>
>May I also ask to avoiding sending attachment on the mailing
>list and instead upload the log somewhere (e.g. pastebin,
>your own webserver...)?
>
I did include all the ARM maintainers, although I forgot to CC
Volodymyr. Sorry about that. Also, I'm not sure if this is strictly an
ARM or general Xen bug so I left ARM. I guess I should have mentioned
that in the email though.
I prefer having them as attachments due to the fact I can see everything
in mutt. Although if there's a strong community consensus that logs
shouldn't be emailed as attachments, I will start using a pastebin like
service to post them.
>>
>>While testing some things out, I found a possible bug in Xen. Xen would
>>successfully run when loaded (from u-boot) at some addresses but not
>>others. I didn't observe this issue in 4.11 stable, so I did a bisect
>>and found that:
>>commit f60658c6ae47e74792e6cc48ea2effac8bb52826
>>Author: Julien Grall <julien.grall@arm.com>
>>Date: Tue Dec 18 13:07:39 2018 +0000
>>
>> xen/arm: Stop relocating Xen
>>
>>was what was causing it to fail when it was loaded to that certain
>>address.
>
>This patch is basically changing how Xen is using the
>physical address space. So it exercise more part of Xen
>code and most likely a red-herring :).
>
>However, the logs are quite interesting:
>
>(XEN) pg[0] MFN 01533 c=0x180000000000000 o=0 v=0x7ffff t=0
>
>If I am not mistaken, the page state is PGC_state_free.
>So this seems to suggest that the page were already
>handed over to the allocator.
>
>Would you mind to apply the patch below and paste the log?
>
>Hopefully, you see see two WARN_ON() before Xen is crashing.
>
>Note the patch is assuming the MFN will stay the same after
>the patch has been applied. If not, you may need to slightly
>tweak it.
>
>diff --git a/xen/common/page_alloc.c b/xen/common/page_alloc.c
>index 7cb1bd368b..4bf0dbc727 100644
>--- a/xen/common/page_alloc.c
>+++ b/xen/common/page_alloc.c
>@@ -1389,6 +1389,9 @@ static void free_heap_pages(
> for ( i = 0; i < (1 << order); i++ )
> {
>+
>+ WARN_ON(mfn_x(page_to_mfn(pg + 1)) == 0x01533);
>+
> /*
> * Cannot assume that count_info == 0, as there are some corner cases
> * where it isn't the case and yet it isn't a bug:
>
>Cheers,
>
>--
>Julien Grall
Attached are the logs of loading patched Xen at the good and bad
address. It appears the MFN has stayed the same, although there's only
one WARN message for both the good and bad address.
--
Brian Woods
[-- Attachment #2: xen-git_52633db2c5ed-patched-good_addr.log --]
[-- Type: text/plain, Size: 43611 bytes --]
PMU Firmware 2019.1 May 25 2019 06:57:33
PMU_ROM Version: xpbr-v8.1.0-0
NOTICE: ATF running on XCZUUNKN/QEMU v4/RTL0.0 at 0xfffea000
NOTICE: BL31: Secure code at 0x60000000
NOTICE: BL31: Non secure code at 0x10080000
NOTICE: BL31: v2.0(release):xilinx-v2018.3-720-g80d1c790
NOTICE: BL31: Built : 06:54:23, May 25 2019
PMUFW: v1.1
U-Boot 2019.01 (May 25 2019 - 06:55:09 +0000)
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
DRAM: 4 GiB
EL Level: EL2
Chip ID: unknown
MMC: mmc@ff170000: 0
Loading Environment from SPI Flash... SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
*** Warning - bad CRC, using default environment
In: serial@ff000000
Out: serial@ff000000
Err: serial@ff000000
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
Bootmode: JTAG_MODE
Reset reason: EXTERNAL
Net: ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for xilinx-zcu102-2019_1
BOOTP broadcast 1
DHCP client bound to address 10.0.5.15 (1 ms)
Hit any key to stop autoboot: 4 \b\b\b 3 \b\b\b 0
ZynqMP> setenv serverip 10.0.5.2; tftpb 1280000 xen-qemu-mod.dtb; tftpb 0x80000 yocto-Image; tftpb 4200000 xen-custom-patched-ga.ub; tftpb 9000000 yocto-rootfs.cpio.gz.ub; bootm 4200000 9000000 1280000
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'xen-qemu-mod.dtb'.
Load address: 0x1280000
Loading: *\b###
18.1 MiB/s
done
Bytes transferred = 38019 (9483 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'yocto-Image'.
Load address: 0x80000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#########################################
41.3 MiB/s
done
Bytes transferred = 18215424 (115f200 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'xen-custom-patched-ga.ub'.
Load address: 0x4200000
Loading: *\b#################################################################
####
42.7 MiB/s
done
Bytes transferred = 984464 (f0590 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'yocto-rootfs.cpio.gz.ub'.
Load address: 0x9000000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#####################
41.5 MiB/s
done
Bytes transferred = 9569188 (9203a4 hex)
## Booting kernel from Legacy Image at 04200000 ...
Image Name:
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 984400 Bytes = 961.3 KiB
Load Address: 04200000
Entry Point: 04200000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 09000000 ...
Image Name:
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 9569124 Bytes = 9.1 MiB
Load Address: 09000000
Entry Point: 09000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01280000
Booting using the fdt blob at 0x1280000
Loading Kernel Image ... OK
Loading Ramdisk to 076df000, end 07fff364 ... OK
Loading Device Tree to 00000000076d2000, end 00000000076de482 ... OK
Starting kernel ...
Xen 4.13-unstable
(XEN) Xen version 4.13-unstable (woods@xilinx.com) (aarch64-unknown-linux-gnu-gcc (crosstool-NG 1.24.0.6-afaf7b9) 8.3.0) debug=y Wed Oct 2 11:10:29 PDT 2019
(XEN) Latest ChangeSet: Thu Sep 26 11:03:08 2019 +0100 git:52633db-dirty
(XEN) build-id: e6c172151e22766c92205cb9562ec14b33c7b6ed
(XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev 0x4
(XEN) 64-bit Execution:
(XEN) Processor Features: 1100000000002222 0000000000000000
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN) Debug Features: 0000000010305106 0000000000000000
(XEN) Auxiliary Features: 0000000000000000 0000000000000000
(XEN) Memory Model Features: 0000000000001122 0000000000000000
(XEN) ISA Features: 0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN) Processor Features: 00001231:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
(XEN) Extensions: GenericTimer Security
(XEN) Debug Features: 03010066
(XEN) Auxiliary Features: 00000000
(XEN) Memory Model Features: 10101105 40000000 01260000 02102211
(XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using SMC Calling Convention v1.1
(XEN) Using PSCI v1.1
(XEN) SMP: Allowing 4 CPUs
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 65000 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=00000000f9010000
(XEN) gic_cpu_addr=00000000f9020000
(XEN) gic_hyp_addr=00000000f9040000
(XEN) gic_vcpu_addr=00000000f9060000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: Adjusting CPU interface base to 0xf902f000
(XEN) GICv2: 192 lines, 4 cpus (IID 00000000).
(XEN) XSM Framework v1.0.0 initialized
(XEN) Initialising XSM SILO mode
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) load_precision_shift: 18
(XEN) load_window_shift: 30
(XEN) underload_balance_tolerance: 0
(XEN) overload_balance_tolerance: -3
(XEN) runqueues arrangement: socket
(XEN) cap enforcement granularity: 10ms
(XEN) load tracking window length 1073741824 ns
(XEN) Allocated console ring of 32 KiB.
(XEN) CPU0: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU1
(XEN) CPU1: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU2
(XEN) CPU 1 booted.
(XEN) CPU2: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU3
(XEN) CPU 2 booted.
(XEN) CPU3: Guest atomics will try 1 times before pausing the domain
(XEN) Brought up 4 CPUs
(XEN) CPU 3 booted.
(XEN) P2M: 40-bit IPA with 40-bit PA and 8-bit VMID
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) smmu: /smmu@fd800000: probing hardware configuration...
(XEN) smmu: /smmu@fd800000: SMMUv2 with:
(XEN) smmu: /smmu@fd800000: stage 2 translation
(XEN) smmu: /smmu@fd800000: stream matching with 48 register groups, mask 0x7fff
(XEN) smmu: /smmu@fd800000: 16 context banks (0 stage-2 only)
(XEN) smmu: /smmu@fd800000: Stage-2: 40-bit IPA -> 48-bit PA
(XEN) smmu: /smmu@fd800000: registered 26 master devices
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) Adding cpu 0 to runqueue 0
(XEN) First cpu on runqueue, activating
(XEN) Adding cpu 1 to runqueue 0
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 3 to runqueue 0
(XEN) alternatives: Patching with alt table 00000000002c3e78 -> 00000000002c4538
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading d0 kernel from boot module @ 0000000000080000
(XEN) Loading ramdisk from boot module @ 00000000076df000
(XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
(XEN) BANK[0] 0x00000020000000-0x00000060000000 (1024MB)
(XEN) Grant table range: 0x00000004200000-0x00000004240000
(XEN) smmu: /smmu@fd800000: d0: p2maddr 0x000000087bf9a000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading zImage from 0000000000080000 to 0000000020080000-0000000023180000
(XEN) Loading dom0 initrd from 00000000076df000 to 0x0000000028200000-0x0000000028b20364
(XEN) Loading dom0 DTB to 0x0000000028000000-0x0000000028008db3
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Xen WARN at page_alloc.c:1393
(XEN) ----[ Xen-4.13-unstable arm64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) PC: 000000000021bf74 page_alloc.c#free_heap_pages+0x15c/0x648
(XEN) LR: 0000000047ffffff
(XEN) SP: 00008000fbff7d10
(XEN) CPSR: 60000249 MODE:64-bit EL2h (Hypervisor, handler)
(XEN) X0: 0000000000001533 X1: 0000000000000000 X2: 000000080004a2f0
(XEN) X3: 0000000000001533 X4: 0000000000001533 X5: 00000000002a34b8
(XEN) X6: 00000000002a3000 X7: 00000000002a3000 X8: 00000000002a3000
(XEN) X9: 0080000000000000 X10: 0000000000001533 X11: 0000000000000001
(XEN) X12: 000000000007ffff X13: 0000000000000000 X14: 0000000000000000
(XEN) X15: 00000000002a3488 X16: 0000000000000001 X17: 00000000002bcf54
(XEN) X18: 0180000000000000 X19: 0000000000000000 X20: 000000080004a2f0
(XEN) X21: 0000000000000000 X22: 00000000002a3000 X23: 6db6db6db6db6db7
(XEN) X24: fffffff800000000 X25: 3d3d3d3d3d3d3d3d X26: 00000000002a3000
(XEN) X27: 00000000002a3000 X28: 00000000002a3000 FP: 00008000fbff7d10
(XEN)
(XEN) VTCR_EL2: 80023558
(XEN) VTTBR_EL2: 0000000000000000
(XEN)
(XEN) SCTLR_EL2: 30cd183d
(XEN) HCR_EL2: 0000000000000038
(XEN) TTBR0_EL2: 000000000432c000
(XEN)
(XEN) ESR_EL2: f2000001
(XEN) HPFAR_EL2: 0000000000000000
(XEN) FAR_EL2: 0000000000000000
(XEN)
(XEN) Xen stack trace from sp=00008000fbff7d10:
(XEN) 00008000fbff7d80 000000000021e74c 000000080004a2f0 00000000000014b2
(XEN) 00000000002fad40 0000000000003100 00000000002a3488 0000000800001c00
(XEN) 0000000000000000 00000000000fff00 00000000002d03c0 6db6db6db6db6db7
(XEN) 00000000002a10f8 000000010000000d 00008000fbff7df0 000000000021e970
(XEN) 0000000000000002 0000000000000002 0000000000080000 0000000003180000
(XEN) 000000000021e8dc 00000000002fa000 0000000003180000 00000000000fff00
(XEN) 00000000002d03c0 ffffffffffffffff 0000000000000001 00000000002fad90
(XEN) 00008000fbff7e00 00000000002b8398 00008000fbff7e50 00000000002b88b0
(XEN) 00000000002d0408 0000000000000003 0000000000080000 00000000002a34b8
(XEN) 00000000002d03c0 000000000021e8dc 00000000076df000 0000000007fff364
(XEN) 00008000fbff7ea0 00000000002609dc 00000000002a2000 0000000000000004
(XEN) 00000000002a2380 000000000032d430 0000000000000004 0000000000296e40
(XEN) 0000000000000002 00000000002609d8 00000000002efde0 00000000002b9518
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<000000000021bf74>] page_alloc.c#free_heap_pages+0x15c/0x648 (PC)
(XEN) [<0000000047ffffff>] 0000000047ffffff (LR)
(XEN) [<000000000021e74c>] page_alloc.c#init_heap_pages+0x3d4/0x564
(XEN) [<000000000021e970>] init_domheap_pages+0x94/0x9c
(XEN) [<00000000002b8398>] 00000000002b8398
(XEN) [<00000000002b88b0>] 00000000002b88b0
(XEN) [<00000000002609dc>] setup.c#init_done+0x10/0x20
(XEN) [<00000000002b9518>] 00000000002b9518
(XEN)
(XEN) Freed 332kB init memory.
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER4
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER8
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER12
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER16
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER20
(XEN) d0v0: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 4.19.0-xilinx-v2019.1 (oe-user@oe-host) (gcc version 8.3.0 (GCC)) #1 SMP Mon Sep 16 21:16:49 UTC 2019
[ 0.000000] Machine model: ZynqMP ZCU102 Rev1.0
[ 0.000000] Xen 4.13 support found
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] cma: Reserved 256 MiB at 0x0000000050000000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: Trusted OS migration not required
[ 0.000000] psci: SMC Calling Convention v1.1
[ 0.000000] random: get_random_bytes called from start_kernel+0x94/0x3f8 with crng_init=0
[ 0.000000] percpu: Embedded 23 pages/cpu @(____ptrval____) s53656 r8192 d32360 u94208
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: enabling workaround for ARM erratum 843419
[ 0.000000] CPU features: enabling workaround for ARM erratum 845719
[ 0.000000] Speculative Store Bypass Disable mitigation not required
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 258560
[ 0.000000] Kernel command line: console=hvc0 earlycon=xen earlyprintk=xen clk_ignore_unused
[ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.000000] Memory: 727836K/1048576K available (10812K kernel code, 636K rwdata, 5436K rodata, 832K init, 316K bss, 58596K reserved, 262144K cma-reserved)
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU event tracing is enabled.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] arch_timer: cp15 timer(s) running at 65.00MHz (virt).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xefdb196da, max_idle_ns: 440795204367 ns
[ 0.000217] sched_clock: 56 bits at 65MHz, resolution 15ns, wraps every 2199023255550ns
[ 0.016276] Console: colour dummy device 80x25
[ 0.045345] console [hvc0] enabled
[ 0.047368] Calibrating delay loop (skipped), value calculated using timer frequency.. 130.00 BogoMIPS (lpj=260000)
[ 0.049836] pid_max: default: 32768 minimum: 301
[ 0.053384] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.054906] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.105654] ASID allocator initialised with 32768 entries
[ 0.125498] xen:grant_table: Grant tables using version 1 layout
[ 0.127075] Grant table initialized
[ 0.129687] xen:events: Using FIFO-based ABI
[ 0.131356] Xen: initializing cpu0
[ 0.135383] rcu: Hierarchical SRCU implementation.
[ 0.143323] EFI services will not be available.
[ 0.146956] smp: Bringing up secondary CPUs ...
(XEN) d0v1: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
(XEN) d0v2: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
(XEN) d0v3: vGICD: unhandled word write 0x000000ffffffff to ICACTIVER0
[ 0.156590] Detected VIPT I-cache on CPU1
[ 0.159640] Xen: initializing cpu1
[ 0.160434] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.176509] Detected VIPT I-cache on CPU2
[ 0.178259] Xen: initializing cpu2
[ 0.178630] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.190621] Detected VIPT I-cache on CPU3
[ 0.192847] Xen: initializing cpu3
[ 0.193330] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.198181] smp: Brought up 1 node, 4 CPUs
[ 0.204911] SMP: Total of 4 processors activated.
[ 0.205552] CPU features: detected: 32-bit EL0 Support
[ 0.210224] CPU: All CPU(s) started at EL1
[ 0.212376] alternatives: patching kernel code
[ 0.247484] devtmpfs: initialized
[ 0.283311] Duplicate name in base, renamed to "memory#1"
[ 0.300316] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.302974] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.337438] xor: measuring software checksum speed
[ 0.381803] 8regs : 1587.000 MB/sec
[ 0.425268] 8regs_prefetch: 684.000 MB/sec
[ 0.468792] 32regs : 1565.000 MB/sec
[ 0.511673] 32regs_prefetch: 1465.000 MB/sec
[ 0.512346] xor: using function: 8regs (1587.000 MB/sec)
[ 0.513401] pinctrl core: initialized pinctrl subsystem
[ 0.551434] NET: Registered protocol family 16
[ 0.566202] audit: initializing netlink subsys (disabled)
[ 0.576336] audit: type=2000 audit(0.492:1): state=initialized audit_enabled=0 res=1
[ 0.606916] vdso: 2 pages (1 code @ (____ptrval____), 1 data @ (____ptrval____))
[ 0.608857] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.638635] DMA: preallocated 256 KiB pool for atomic allocations
[ 0.641464] xen:swiotlb_xen: Warning: only able to allocate 4 MB for software IO TLB
[ 0.656432] software IO TLB: mapped [mem 0x4d400000-0x4d800000] (4MB)
[ 1.010642] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 1.108077] raid6: int64x1 gen() 677 MB/s
[ 1.189932] raid6: int64x1 xor() 558 MB/s
[ 1.272320] raid6: int64x2 gen() 874 MB/s
[ 1.353864] raid6: int64x2 xor() 615 MB/s
[ 1.434753] raid6: int64x4 gen() 1112 MB/s
[ 1.517246] raid6: int64x4 xor() 424 MB/s
[ 1.597107] raid6: int64x8 gen() 874 MB/s
[ 1.677083] raid6: int64x8 xor() 494 MB/s
[ 1.757937] raid6: neonx1 gen() 490 MB/s
[ 1.839161] raid6: neonx1 xor() 332 MB/s
[ 1.923838] raid6: neonx2 gen() 657 MB/s
[ 2.004087] raid6: neonx2 xor() 391 MB/s
[ 2.083694] raid6: neonx4 gen() 669 MB/s
[ 2.163533] raid6: neonx4 xor() 388 MB/s
[ 2.243046] raid6: neonx8 gen() 629 MB/s
[ 2.322797] raid6: neonx8 xor() 357 MB/s
[ 2.323419] raid6: using algorithm int64x4 gen() 1112 MB/s
[ 2.324423] raid6: .... xor() 424 MB/s, rmw enabled
[ 2.325388] raid6: using neon recovery algorithm
[ 2.331974] xen:balloon: Initialising balloon driver
[ 2.343275] SCSI subsystem initialized
[ 2.349000] usbcore: registered new interface driver usbfs
[ 2.350431] usbcore: registered new interface driver hub
[ 2.352342] usbcore: registered new device driver usb
[ 2.354163] media: Linux media interface: v0.10
[ 2.355835] videodev: Linux video capture interface: v2.00
[ 2.357489] pps_core: LinuxPPS API ver. 1 registered
[ 2.357906] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 2.358849] PTP clock support registered
[ 2.359852] EDAC MC: Ver: 3.0.0
[ 2.381642] zynqmp-ipi-mbox mailbox@ff990400: Probed ZynqMP IPI Mailbox driver.
[ 2.388510] FPGA manager framework
[ 2.393739] Advanced Linux Sound Architecture Driver Initialized.
[ 2.407536] Bluetooth: Core ver 2.22
[ 2.409051] NET: Registered protocol family 31
[ 2.409642] Bluetooth: HCI device and connection manager initialized
[ 2.411229] Bluetooth: HCI socket layer initialized
[ 2.411953] Bluetooth: L2CAP socket layer initialized
[ 2.412979] Bluetooth: SCO socket layer initialized
[ 2.429505] clocksource: Switched to clocksource arch_sys_counter
[ 2.434739] VFS: Disk quotas dquot_6.6.0
[ 2.435712] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 2.664359] NET: Registered protocol family 2
[ 2.679482] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes)
[ 2.681257] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 2.682673] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[ 2.683800] TCP: Hash tables configured (established 8192 bind 8192)
[ 2.687963] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 2.690009] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 2.693157] NET: Registered protocol family 1
[ 2.711877] RPC: Registered named UNIX socket transport module.
[ 2.713600] RPC: Registered udp transport module.
[ 2.714257] RPC: Registered tcp transport module.
[ 2.714825] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 2.731335] Trying to unpack rootfs image as initramfs...
[ 4.803118] Freeing initrd memory: 9344K
[ 4.826910] Initialise system trusted keyrings
[ 4.832770] workingset: timestamp_bits=62 max_order=18 bucket_order=0
[ 4.863940] NFS: Registering the id_resolver key type
[ 4.865607] Key type id_resolver registered
[ 4.866221] Key type id_legacy registered
[ 4.866824] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 4.868225] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 6.435890] NET: Registered protocol family 38
[ 6.578906] Key type asymmetric registered
[ 6.579757] Asymmetric key parser 'x509' registered
[ 6.582136] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[ 6.583175] io scheduler noop registered
[ 6.583724] io scheduler deadline registered
[ 6.585119] io scheduler cfq registered (default)
[ 6.585695] io scheduler mq-deadline registered
[ 6.586162] io scheduler kyber registered
[ 6.616098] OF: /amba/dma@fd500000: could not find phandle
[ 6.618237] OF: /amba/dma@fd510000: could not find phandle
[ 6.619290] OF: /amba/dma@fd520000: could not find phandle
[ 6.621126] OF: /amba/dma@fd530000: could not find phandle
[ 6.622448] OF: /amba/dma@fd540000: could not find phandle
[ 6.623486] OF: /amba/dma@fd550000: could not find phandle
[ 6.625236] OF: /amba/dma@fd560000: could not find phandle
[ 6.626526] OF: /amba/dma@fd570000: could not find phandle
[ 6.641848] xen:xen_evtchn: Event-channel device installed
[ 8.355867] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 8.530569] brd: module loaded
[ 8.620346] loop: module loaded
[ 8.637359] mtdoops: mtd device (mtddev=name/number) must be supplied
[ 8.645730] OF: /amba/spi@ff0f0000: could not find phandle
[ 8.667006] libphy: Fixed MDIO Bus: probed
[ 8.689995] tun: Universal TUN/TAP device driver, 1.6
[ 8.713929] CAN device driver interface
[ 8.726478] xen_netfront: Initialising Xen virtual ethernet driver
[ 8.728323] usbcore: registered new interface driver asix
[ 8.731938] usbcore: registered new interface driver ax88179_178a
[ 8.733854] usbcore: registered new interface driver cdc_ether
[ 8.734950] usbcore: registered new interface driver net1080
[ 8.735979] usbcore: registered new interface driver cdc_subset
[ 8.738710] usbcore: registered new interface driver zaurus
[ 8.740138] usbcore: registered new interface driver cdc_ncm
[ 8.757551] usbcore: registered new interface driver uas
[ 8.759160] usbcore: registered new interface driver usb-storage
[ 8.778957] rtc_zynqmp ffa60000.rtc: rtc core: registered ffa60000.rtc as rtc0
[ 8.782224] i2c /dev entries driver
[ 8.823428] usbcore: registered new interface driver uvcvideo
[ 8.823978] USB Video Class driver (1.1.1)
[ 8.842880] Bluetooth: HCI UART driver ver 2.3
[ 8.843614] Bluetooth: HCI UART protocol H4 registered
[ 8.844239] Bluetooth: HCI UART protocol BCSP registered
[ 8.847159] Bluetooth: HCI UART protocol LL registered
[ 8.847927] Bluetooth: HCI UART protocol ATH3K registered
[ 8.849308] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 8.851237] Bluetooth: HCI UART protocol Intel registered
[ 8.852348] Bluetooth: HCI UART protocol QCA registered
[ 8.854281] usbcore: registered new interface driver bcm203x
[ 8.855322] usbcore: registered new interface driver bpa10x
[ 8.857047] usbcore: registered new interface driver bfusb
[ 8.858321] usbcore: registered new interface driver btusb
[ 8.859154] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[ 8.861216] usbcore: registered new interface driver ath3k
[ 8.865246] EDAC MC: ECC not enabled
[ 8.868148] EDAC ZynqMP-OCM: ECC not enabled - Disabling EDAC driver
[ 8.873982] cpu cpu0: failed to get clock: -2
[ 8.874693] cpufreq-dt: probe of cpufreq-dt failed with error -2
[ 8.880159] sdhci: Secure Digital Host Controller Interface driver
[ 8.881536] sdhci: Copyright(c) Pierre Ossman
[ 8.881881] sdhci-pltfm: SDHCI platform and OF driver helper
[ 8.896109] ledtrig-cpu: registered to indicate activity on CPUs
[ 8.900253] zynqmp_firmware_probe Platform Management API v1.1
[ 8.902029] zynqmp_firmware_probe Trustzone version v1.0
[ 9.039752] zynqmp-pinctrl firmware:zynqmp-firmware:pinctrl: zynqmp pinctrl initialized
[ 9.748137] zynqmp_clk_mux_get_parent() getparent failed for clock: lpd_wdt, ret = -22
[ 9.763240] alg: No test for xilinx-zynqmp-aes (zynqmp-aes)
[ 9.766820] zynqmp_aes zynqmp_aes: AES Successfully Registered
[ 9.766820]
[ 9.778483] alg: No test for xilinx-keccak-384 (zynqmp-keccak-384)
[ 9.787719] alg: No test for xilinx-zynqmp-rsa (zynqmp-rsa)
[ 9.795869] usbcore: registered new interface driver usbhid
[ 9.796326] usbhid: USB HID core driver
[ 9.858271] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[ 9.870760] usbcore: registered new interface driver snd-usb-audio
[ 9.895771] pktgen: Packet Generator for packet performance testing. Version: 2.75
[ 9.928398] Initializing XFRM netlink socket
[ 9.931239] NET: Registered protocol family 10
[ 9.950959] Segment Routing with IPv6
[ 9.955471] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 9.965184] NET: Registered protocol family 17
[ 9.966169] NET: Registered protocol family 15
[ 9.967579] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 9.972192] can: controller area network core (rev 20170425 abi 9)
[ 9.974563] NET: Registered protocol family 29
[ 9.975252] can: raw protocol (rev 20170425)
[ 9.975758] can: broadcast manager protocol (rev 20170425 t)
[ 9.977123] can: netlink gateway (rev 20170425) max_hops=1
[ 9.981998] Bluetooth: RFCOMM TTY layer initialized
[ 9.983012] Bluetooth: RFCOMM socket layer initialized
[ 9.983736] Bluetooth: RFCOMM ver 1.11
[ 9.984250] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.985566] Bluetooth: BNEP filters: protocol multicast
[ 9.986232] Bluetooth: BNEP socket layer initialized
[ 9.986774] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 9.987383] Bluetooth: HIDP socket layer initialized
[ 9.991231] 9pnet: Installing 9P2000 support
[ 9.992011] Key type dns_resolver registered
[ 10.012281] registered taskstats version 1
[ 10.013850] Loading compiled-in X.509 certificates
[ 10.023245] Btrfs loaded, crc32c=crc32c-generic
[ 10.098624] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 42, base_baud = 2479910) is a xuartps
[ 10.146727] of-fpga-region fpga-full: FPGA Region probed
[ 10.166876] nwl-pcie fd0e0000.pcie: Link is UP
[ 10.168137] nwl-pcie fd0e0000.pcie: host bridge /amba/pcie@fd0e0000 ranges:
[ 10.170369] nwl-pcie fd0e0000.pcie: MEM 0xe0000000..0xefffffff -> 0xe0000000
[ 10.171373] nwl-pcie fd0e0000.pcie: MEM 0x600000000..0x7ffffffff -> 0x600000000
[ 10.186511] nwl-pcie fd0e0000.pcie: PCI host bridge to bus 0000:00
[ 10.187575] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 10.188827] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 10.189815] pci_bus 0000:00: root bus resource [mem 0x600000000-0x7ffffffff pref]
[ 10.217470] xilinx-dpdma fd4c0000.dma: Xilinx DPDMA engine is probed
[ 10.219360] OF: /amba/dma@fd500000: could not find phandle
[ 10.227686] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success
[ 10.230458] OF: /amba/dma@fd510000: could not find phandle
[ 10.238046] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success
[ 10.239811] OF: /amba/dma@fd520000: could not find phandle
[ 10.243651] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success
[ 10.246315] OF: /amba/dma@fd530000: could not find phandle
[ 10.250006] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success
[ 10.251912] OF: /amba/dma@fd540000: could not find phandle
[ 10.255609] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success
[ 10.258499] OF: /amba/dma@fd550000: could not find phandle
[ 10.262115] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success
[ 10.264056] OF: /amba/dma@fd560000: could not find phandle
[ 10.267843] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success
[ 10.270607] OF: /amba/dma@fd570000: could not find phandle
[ 10.274170] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success
[ 10.283101] xilinx-zynqmp-dma ffa80000.dma: ZynqMP DMA driver Probe success
[ 10.288214] xilinx-zynqmp-dma ffa90000.dma: ZynqMP DMA driver Probe success
[ 10.293746] xilinx-zynqmp-dma ffaa0000.dma: ZynqMP DMA driver Probe success
[ 10.298550] xilinx-zynqmp-dma ffab0000.dma: ZynqMP DMA driver Probe success
[ 10.303042] xilinx-zynqmp-dma ffac0000.dma: ZynqMP DMA driver Probe success
[ 10.307991] xilinx-zynqmp-dma ffad0000.dma: ZynqMP DMA driver Probe success
[ 10.313378] xilinx-zynqmp-dma ffae0000.dma: ZynqMP DMA driver Probe success
[ 10.318320] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success
[ 10.329804] xilinx-psgtr fd400000.zynqmp_phy: Lane:1 type:8 protocol:4 pll_locked:yes
[ 10.397093] zynqmp_clk_divider_set_rate() set divider failed for ams_ref_div1, ret = -13
[ 10.482227] xilinx-dp-snd-codec fd4a0000.zynqmp-display:zynqmp_dp_snd_codec0: Failed to get required clock freq
[ 10.485461] xilinx-dp-snd-codec: probe of fd4a0000.zynqmp-display:zynqmp_dp_snd_codec0 failed with error -22
[ 10.491249] xilinx-dp-snd-pcm zynqmp_dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed
[ 10.496176] xilinx-dp-snd-pcm zynqmp_dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed
[ 10.502904] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: ASoC: CPU DAI (null) not registered
[ 10.507728] OF: graph: no port node found in /amba/zynqmp-display@fd4a0000
[ 10.515543] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 10.516280] [drm] No driver support for vblank timestamp query.
[ 10.522798] xlnx-drm xlnx-drm.0: bound fd4a0000.zynqmp-display (ops 0xffffff8008bcf5e0)
[ 10.758976] Console: switching to colour frame buffer device 128x48
[ 10.790492] zynqmp-display fd4a0000.zynqmp-display: fb0: frame buffer device
[ 10.800163] [drm] Initialized xlnx 1.0.0 20130509 for fd4a0000.zynqmp-display on minor 0
[ 10.803223] zynqmp-display fd4a0000.zynqmp-display: ZynqMP DisplayPort Subsystem driver probed
[ 10.819834] xilinx-psgtr fd400000.zynqmp_phy: Lane:3 type:3 protocol:2 pll_locked:yes
[ 10.825846] ahci-ceva fd0c0000.ahci: AHCI 0001.0000 32 slots 2 ports 1.5 Gbps 0x3 impl platform mode
[ 10.827139] ahci-ceva fd0c0000.ahci: flags: 64bit ncq only
[ 10.858637] scsi host0: ahci-ceva
[ 10.871948] scsi host1: ahci-ceva
[ 10.878216] ata1: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x100 irq 40
[ 10.879253] ata2: SATA max UDMA/133 mmio [mem 0xfd0c0000-0xfd0c1fff] port 0x180 irq 40
[ 10.883469] OF: /amba/spi@ff0f0000: could not find phandle
[ 10.967945] m25p80 spi0.0: n25q512a (131072 Kbytes)
[ 10.971015] 3 fixed-partitions partitions found on MTD device spi0.0
[ 10.971889] Creating 3 MTD partitions on "spi0.0":
[ 10.973253] 0x000000000000-0x000001e00000 : "boot"
[ 10.991685] 0x000001e00000-0x000001e40000 : "bootenv"
[ 11.003866] 0x000001e40000-0x000004240000 : "kernel"
[ 11.119185] OF: /amba/ethernet@ff0e0000: could not find phandle
[ 11.131974] macb ff0e0000.ethernet: Not enabling partial store and forward
[ 11.134034] macb: GEM doesn't support hardware ptp.
[ 11.147079] libphy: MACB_mii_bus: probed
[ 11.206720] ata2: SATA link down (SStatus 0 SControl 300)
[ 11.211945] ata1: SATA link down (SStatus 0 SControl 300)
[ 11.378354] Marvell 88E1118 ff0e0000.ethernet-ffffffff:0c: attached PHY driver [Marvell 88E1118] (mii_bus:phy_addr=ff0e0000.ethernet-ffffffff:0c, irq=POLL)
[ 11.380341] macb ff0e0000.ethernet eth0: Cadence GEM rev 0x40070106 at 0xff0e0000 irq 25 (00:0a:35:00:22:01)
[ 11.390180] xilinx-axipmon ffa00000.perf-monitor: Probed Xilinx APM
[ 11.398335] xilinx-axipmon fd0b0000.perf-monitor: Probed Xilinx APM
[ 11.403935] xilinx-axipmon fd490000.perf-monitor: Probed Xilinx APM
[ 11.410755] xilinx-axipmon ffa10000.perf-monitor: Probed Xilinx APM
[ 11.524153] OF: /amba/usb0@ff9d0000/dwc3@fe200000: could not find phandle
[ 11.531584] dwc3 fe200000.dwc3: Failed to get clk 'ref': -2
[ 11.559665] dwc3 fe200000.dwc3: Configuration mismatch. dr_mode forced to gadget
[ 11.563198] dwc3 fe200000.dwc3: this is not a DesignWare USB3 DRD Core
[ 11.564318] dwc3 fe200000.dwc3: failed to initialize core
[ 11.602413] pca953x 0-0020: 0-0020 supply vcc not found, using dummy regulator
[ 11.605391] pca953x 0-0020: Linked as a consumer to regulator.0
[ 11.627293] pca953x 0-0021: 0-0021 supply vcc not found, using dummy regulator
[ 11.629484] pca953x 0-0021: Linked as a consumer to regulator.0
[ 11.686379] ina2xx 3-0040: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.695040] ina2xx 3-0041: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.703031] ina2xx 3-0042: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.710657] ina2xx 3-0043: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.719314] ina2xx 3-0044: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.727333] ina2xx 3-0045: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.737689] ina2xx 3-0046: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.746597] ina2xx 3-0047: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.755405] ina2xx 3-004a: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.766625] ina2xx 3-004b: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.769373] i2c i2c-0: Added multiplexed i2c bus 3
[ 11.784198] ina2xx 4-0040: power monitor ina226 (Rshunt = 2000 uOhm)
[ 11.792171] ina2xx 4-0041: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.803184] ina2xx 4-0042: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.813571] ina2xx 4-0043: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.821859] ina2xx 4-0044: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.830188] ina2xx 4-0045: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.839667] ina2xx 4-0046: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.851624] ina2xx 4-0047: power monitor ina226 (Rshunt = 5000 uOhm)
[ 11.854226] i2c i2c-0: Added multiplexed i2c bus 4
[ 11.904851] max20751 5-0072: Failed to identify chip capabilities
[ 11.932196] max20751 5-0073: Failed to identify chip capabilities
[ 11.935110] i2c i2c-0: Added multiplexed i2c bus 5
[ 11.939197] i2c i2c-0: Added multiplexed i2c bus 6
[ 11.940073] pca954x 0-0075: registered 4 multiplexed busses for I2C mux pca9544
[ 11.942937] cdns-i2c ff020000.i2c: 400 kHz mmio ff020000 irq 27
[ 11.999065] at24 7-0054: 1024 byte 24c08 EEPROM, writable, 1 bytes/write
[ 12.001758] i2c i2c-1: Added multiplexed i2c bus 7
[ 12.007717] i2c i2c-1: Added multiplexed i2c bus 8
[ 12.059690] si570 9-005d: registered, current frequency 300000000 Hz
[ 12.063051] i2c i2c-1: Added multiplexed i2c bus 9
[ 12.121008] si570 10-005d: registered, current frequency 148500000 Hz
[ 12.122840] i2c i2c-1: Added multiplexed i2c bus 10
[ 12.129826] si5324 11-0069: si5328 probed
[ 12.287060] si5324 11-0069: si5328 probe successful
[ 12.289462] i2c i2c-1: Added multiplexed i2c bus 11
[ 12.293672] i2c i2c-1: Added multiplexed i2c bus 12
[ 12.297890] i2c i2c-1: Added multiplexed i2c bus 13
[ 12.301478] i2c i2c-1: Added multiplexed i2c bus 14
[ 12.301998] pca954x 1-0074: registered 8 multiplexed busses for I2C switch pca9548
[ 12.311443] i2c i2c-1: Added multiplexed i2c bus 15
[ 12.315759] i2c i2c-1: Added multiplexed i2c bus 16
[ 12.321810] i2c i2c-1: Added multiplexed i2c bus 17
[ 12.334666] i2c i2c-1: Added multiplexed i2c bus 18
[ 12.338986] i2c i2c-1: Added multiplexed i2c bus 19
[ 12.343388] i2c i2c-1: Added multiplexed i2c bus 20
[ 12.347989] i2c i2c-1: Added multiplexed i2c bus 21
[ 12.352448] i2c i2c-1: Added multiplexed i2c bus 22
[ 12.354005] pca954x 1-0075: registered 8 multiplexed busses for I2C switch pca9548
[ 12.355843] cdns-i2c ff030000.i2c: 400 kHz mmio ff030000 irq 28
[ 12.366545] cdns-wdt fd4d0000.watchdog: Xilinx Watchdog Timer at (____ptrval____) with timeout 60s
[ 12.374440] cdns-wdt ff150000.watchdog: Xilinx Watchdog Timer at (____ptrval____) with timeout 10s
[ 12.453831] OF: /amba/mmc@ff170000: could not find phandle
[ 12.538264] mmc0: SDHCI controller on ff170000.mmc [ff170000.mmc] using ADMA 64-bit
[ 12.566543] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: ASoC: CPU DAI (null) not registered
[ 12.571620] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: ASoC: CPU DAI (null) not registered
[ 12.607038] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 12.619691] rtc_zynqmp ffa60000.rtc: setting system clock to 2019-10-02 18:20:00 UTC (1570040400)
[ 12.621436] of_cfs_init
[ 12.622383] of_cfs_init: OK
[ 12.623829] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 12.631679] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: ASoC: CPU DAI (null) not registered
[ 12.862218] random: fast init done
[ 12.926338] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 12.927737] clk: Not disabling unused clocks
[ 12.929489] ALSA device list:
[ 12.930085] No soundcards found.
[ 12.939427] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 12.941786] cfg80211: failed to load regulatory.db
[ 13.015749] Freeing unused kernel memory: 832K
[ 13.058596] Run /init as init process
\rINIT: version 2.88 booting
Starting udev
[ 15.606551] udevd[1953]: starting version 3.2.7
[ 15.616897] random: udevd: uninitialized urandom read (16 bytes read)
[ 15.622933] random: udevd: uninitialized urandom read (16 bytes read)
[ 15.625146] random: udevd: uninitialized urandom read (16 bytes read)
[ 15.678010] udevd[1953]: specified group 'kvm' unknown
[ 15.735912] udevd[1954]: starting eudev-3.2.7
[ 16.264333] udevd[1954]: specified group 'kvm' unknown
[ 16.764968] urandom_read: 3 callbacks suppressed
[ 16.767822] random: udevd: uninitialized urandom read (16 bytes read)
[ 17.403232] random: udevd: uninitialized urandom read (16 bytes read)
[ 22.451641] hrtimer: interrupt took 21946539 ns
[ 33.878490] random: dd: uninitialized urandom read (512 bytes read)
Configuring packages on first boot....
(This may take several minutes. Please do not power off the machine.)
Running postinst /etc/rpm-postinsts/100-sysvinit-inittab...
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
Removing any system startup links for run-postinsts ...
/etc/rcS.d/S99run-postinsts
\rINIT: Entering runlevel: 5
Configuring network interfaces... [ 37.854981] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc: started, v1.30.1
udhcpc: sending discover
[ 38.950846] macb ff0e0000.ethernet eth0: link up (100/Full)
[ 38.952122] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
udhcpc: sending discover
udhcpc: sending select for 10.0.5.15
udhcpc: lease of 10.0.5.15 obtained, lease time 86400
/etc/udhcpc.d/50default: Adding DNS 10.0.5.3
done.
Starting Dropbear SSH server: [ 43.219974] random: dropbearkey: uninitialized urandom read (32 bytes read)
Generating 2048 bit rsa key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDn35aPVMyUXAyftLf4UMbZRdACsWmQ4c5S4Ai4QXcbsCT1ngfKnwhojNH7MBG7ElrI6DeyP5PTGxsM85TyCdU2HXMfJAcC8p+Ly8xq1jPjBV3t/fUD/4t1mJ1BUL8SDPEXYJYNq8wyDoSqQ+NnGZIke6uf40vsjnfgSEYuaCOePyDLSjrhO7SkbZdY/F4ffTSSGYS5phluPWIAgz87m8g50JKWQZIi99vrGR7N7my8yxMxSlAwMKXpO0Oj1qmaF7J86JjfZEXu+Tz+xNYYlHUK6+1o1tZTK4yVphn9fOmoRLBWwyiPtQLiiqx4B2I1yAgMXrQPcLI2Qz8IH6NDVOhV root@zcu102-zynqmp
Fingerprint: sha1!! 75:11:3a:1c:83:8c:0d:fc:91:4d:09:18:bc:ac:32:cc:5a:0e:4e:44
dropbear.
Starting syslogd/klogd: done
Starting /usr/sbin/xenstored...
Setting domain 0 name, domid and JSON config...
WARNING: Failed to open connection to gnttab
Done setting up Dom0
Starting xenconsoled...
Starting QEMU as disk backend for dom0
/etc/rc5.d/S80xencommons: line 73: /usr/bin/qemu-system-i386: No such file or directory
Starting domain watchdog daemon: xenwatchdogd startup
[done]
Poky (Yocto Project Reference Distro) 2.7.1 zcu102-zynqmp /dev/hvc0
\rzcu102-zynqmp login:
[-- Attachment #3: xen-git_52633db2c5ed-patched-bad_addr.log --]
[-- Type: text/plain, Size: 17713 bytes --]
PMU Firmware 2019.1 May 25 2019 06:57:33
PMU_ROM Version: xpbr-v8.1.0-0
NOTICE: ATF running on XCZUUNKN/QEMU v4/RTL0.0 at 0xfffea000
NOTICE: BL31: Secure code at 0x60000000
NOTICE: BL31: Non secure code at 0x10080000
NOTICE: BL31: v2.0(release):xilinx-v2018.3-720-g80d1c790
NOTICE: BL31: Built : 06:54:23, May 25 2019
PMUFW: v1.1
U-Boot 2019.01 (May 25 2019 - 06:55:09 +0000)
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
DRAM: 4 GiB
EL Level: EL2
Chip ID: unknown
MMC: mmc@ff170000: 0
Loading Environment from SPI Flash... SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
*** Warning - bad CRC, using default environment
In: serial@ff000000
Out: serial@ff000000
Err: serial@ff000000
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
Bootmode: JTAG_MODE
Reset reason: EXTERNAL
Net: ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for xilinx-zcu102-2019_1
BOOTP broadcast 1
DHCP client bound to address 10.0.5.15 (1 ms)
Hit any key to stop autoboot: 4 \b\b\b 0
ZynqMP> setenv serverip 10.0.5.2; tftpb 1280000 xen-qemu-mod.dtb; tftpb 0x80000 yocto-Image; tftpb 1400000 xen-custom-patched-ba.ub; tftpb 9000000 yocto-rootfs.cpio.gz.ub; bootm 1400000 9000000 1280000
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'xen-qemu-mod.dtb'.
Load address: 0x1280000
Loading: *\b###
18.1 MiB/s
done
Bytes transferred = 38019 (9483 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'yocto-Image'.
Load address: 0x80000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#########################################
44.9 MiB/s
done
Bytes transferred = 18215424 (115f200 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'xen-custom-patched-ba.ub'.
Load address: 0x1400000
Loading: *\b#################################################################
####
40.8 MiB/s
done
Bytes transferred = 984464 (f0590 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'yocto-rootfs.cpio.gz.ub'.
Load address: 0x9000000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#####################
42.1 MiB/s
done
Bytes transferred = 9569188 (9203a4 hex)
## Booting kernel from Legacy Image at 01400000 ...
Image Name:
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 984400 Bytes = 961.3 KiB
Load Address: 01400000
Entry Point: 01400000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 09000000 ...
Image Name:
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 9569124 Bytes = 9.1 MiB
Load Address: 09000000
Entry Point: 09000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01280000
Booting using the fdt blob at 0x1280000
Loading Kernel Image ... OK
Loading Ramdisk to 076df000, end 07fff364 ... OK
Loading Device Tree to 00000000076d2000, end 00000000076de482 ... OK
Starting kernel ...
Xen 4.13-unstable
(XEN) Xen version 4.13-unstable (woods@xilinx.com) (aarch64-unknown-linux-gnu-gcc (crosstool-NG 1.24.0.6-afaf7b9) 8.3.0) debug=y Wed Oct 2 11:10:29 PDT 2019
(XEN) Latest ChangeSet: Thu Sep 26 11:03:08 2019 +0100 git:52633db-dirty
(XEN) build-id: e6c172151e22766c92205cb9562ec14b33c7b6ed
(XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev 0x4
(XEN) 64-bit Execution:
(XEN) Processor Features: 1100000000002222 0000000000000000
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN) Debug Features: 0000000010305106 0000000000000000
(XEN) Auxiliary Features: 0000000000000000 0000000000000000
(XEN) Memory Model Features: 0000000000001122 0000000000000000
(XEN) ISA Features: 0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN) Processor Features: 00001231:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
(XEN) Extensions: GenericTimer Security
(XEN) Debug Features: 03010066
(XEN) Auxiliary Features: 00000000
(XEN) Memory Model Features: 10101105 40000000 01260000 02102211
(XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using SMC Calling Convention v1.1
(XEN) Using PSCI v1.1
(XEN) SMP: Allowing 4 CPUs
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 65000 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=00000000f9010000
(XEN) gic_cpu_addr=00000000f9020000
(XEN) gic_hyp_addr=00000000f9040000
(XEN) gic_vcpu_addr=00000000f9060000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: Adjusting CPU interface base to 0xf902f000
(XEN) GICv2: 192 lines, 4 cpus (IID 00000000).
(XEN) XSM Framework v1.0.0 initialized
(XEN) Initialising XSM SILO mode
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) load_precision_shift: 18
(XEN) load_window_shift: 30
(XEN) underload_balance_tolerance: 0
(XEN) overload_balance_tolerance: -3
(XEN) runqueues arrangement: socket
(XEN) cap enforcement granularity: 10ms
(XEN) load tracking window length 1073741824 ns
(XEN) Allocated console ring of 32 KiB.
(XEN) CPU0: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU1
(XEN) CPU1: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU2
(XEN) CPU 1 booted.
(XEN) CPU2: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU3
(XEN) CPU 2 booted.
(XEN) CPU3: Guest atomics will try 1 times before pausing the domain
(XEN) Brought up 4 CPUs
(XEN) CPU 3 booted.
(XEN) P2M: 40-bit IPA with 40-bit PA and 8-bit VMID
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) smmu: /smmu@fd800000: probing hardware configuration...
(XEN) smmu: /smmu@fd800000: SMMUv2 with:
(XEN) smmu: /smmu@fd800000: stage 2 translation
(XEN) smmu: /smmu@fd800000: stream matching with 48 register groups, mask 0x7fff
(XEN) smmu: /smmu@fd800000: 16 context banks (0 stage-2 only)
(XEN) smmu: /smmu@fd800000: Stage-2: 40-bit IPA -> 48-bit PA
(XEN) smmu: /smmu@fd800000: registered 26 master devices
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) Adding cpu 0 to runqueue 0
(XEN) First cpu on runqueue, activating
(XEN) Adding cpu 1 to runqueue 0
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 3 to runqueue 0
(XEN) alternatives: Patching with alt table 00000000002c3e78 -> 00000000002c4538
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading d0 kernel from boot module @ 0000000000080000
(XEN) Loading ramdisk from boot module @ 00000000076df000
(XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
(XEN) BANK[0] 0x00000020000000-0x00000060000000 (1024MB)
(XEN) Grant table range: 0x00000001400000-0x00000001440000
(XEN) smmu: /smmu@fd800000: d0: p2maddr 0x000000087bf9a000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading zImage from 0000000000080000 to 0000000020080000-0000000023180000
(XEN) Loading dom0 initrd from 00000000076df000 to 0x0000000028200000-0x0000000028b20364
(XEN) Loading dom0 DTB to 0x0000000028000000-0x0000000028008db3
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Xen WARN at page_alloc.c:1393
(XEN) ----[ Xen-4.13-unstable arm64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) PC: 000000000021bf74 page_alloc.c#free_heap_pages+0x15c/0x648
(XEN) LR: 0000000047ffffff
(XEN) SP: 00008000fbff7d10
(XEN) CPSR: 60000249 MODE:64-bit EL2h (Hypervisor, handler)
(XEN) X0: 0000000000001533 X1: 0000000000000000 X2: 000000080004a2f0
(XEN) X3: 0000000000001533 X4: 0000000000001533 X5: 00000000002a34b8
(XEN) X6: 00000000002a3000 X7: 00000000002a3000 X8: 00000000002a3000
(XEN) X9: 0080000000000000 X10: 0000000000001533 X11: 0000000000000001
(XEN) X12: 000000000007ffff X13: 0000000000000000 X14: 0000000000000000
(XEN) X15: 00000000002a3488 X16: 0000000000000001 X17: 00000000002bcf54
(XEN) X18: 0180000000000000 X19: 0000000000000000 X20: 000000080004a2f0
(XEN) X21: 0000000000000000 X22: 00000000002a3000 X23: 6db6db6db6db6db7
(XEN) X24: fffffff800000000 X25: 3d3d3d3d3d3d3d3d X26: 00000000002a3000
(XEN) X27: 00000000002a3000 X28: 00000000002a3000 FP: 00008000fbff7d10
(XEN)
(XEN) VTCR_EL2: 80023558
(XEN) VTTBR_EL2: 0000000000000000
(XEN)
(XEN) SCTLR_EL2: 30cd183d
(XEN) HCR_EL2: 0000000000000038
(XEN) TTBR0_EL2: 000000000152c000
(XEN)
(XEN) ESR_EL2: f2000001
(XEN) HPFAR_EL2: 0000000000000000
(XEN) FAR_EL2: 0000000000000000
(XEN)
(XEN) Xen stack trace from sp=00008000fbff7d10:
(XEN) 00008000fbff7d80 000000000021e74c 000000080004a2f0 00000000000014b2
(XEN) 00000000002fad40 0000000000003100 00000000002a3488 0000000800001c00
(XEN) 0000000000000000 00000000000fff00 00000000002d03c0 6db6db6db6db6db7
(XEN) 00000000002a10f8 000000010000000d 00008000fbff7df0 000000000021e970
(XEN) 0000000000000002 0000000000000002 0000000000080000 0000000003180000
(XEN) 000000000021e8dc 00000000002fa000 0000000003180000 00000000000fff00
(XEN) 00000000002d03c0 ffffffffffffffff 0000000000000001 00000000002fad90
(XEN) 00008000fbff7e00 00000000002b8398 00008000fbff7e50 00000000002b88b0
(XEN) 00000000002d0408 0000000000000003 0000000000080000 00000000002a34b8
(XEN) 00000000002d03c0 000000000021e8dc 00000000076df000 0000000007fff364
(XEN) 00008000fbff7ea0 00000000002609dc 00000000002a2000 0000000000000004
(XEN) 00000000002a2380 000000000032d430 0000000000000004 0000000000296e40
(XEN) 0000000000000002 00000000002609d8 00000000002efde0 00000000002b9518
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<000000000021bf74>] page_alloc.c#free_heap_pages+0x15c/0x648 (PC)
(XEN) [<0000000047ffffff>] 0000000047ffffff (LR)
(XEN) [<000000000021e74c>] page_alloc.c#init_heap_pages+0x3d4/0x564
(XEN) [<000000000021e970>] init_domheap_pages+0x94/0x9c
(XEN) [<00000000002b8398>] 00000000002b8398
(XEN) [<00000000002b88b0>] 00000000002b88b0
(XEN) [<00000000002609dc>] setup.c#init_done+0x10/0x20
(XEN) [<00000000002b9518>] 00000000002b9518
(XEN)
(XEN) pg[0] MFN 01533 c=0x180000000000000 o=0 v=0x7ffff t=0
(XEN) Xen BUG at page_alloc.c:1425
(XEN) ----[ Xen-4.13-unstable arm64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) PC: 000000000021bff4 page_alloc.c#free_heap_pages+0x1dc/0x648
(XEN) LR: 000000000021bff4
(XEN) SP: 00008000fbff7d10
(XEN) CPSR: 60000249 MODE:64-bit EL2h (Hypervisor, handler)
(XEN) X0: 00000000002a1558 X1: 0000000000000108 X2: 0000000000000000
(XEN) X3: 0000000000000000 X4: 0000000000000000 X5: 0000000000000012
(XEN) X6: 0000000000000080 X7: fefefefefefeff09 X8: 7f7f7f7f7f7f7f7f
(XEN) X9: 731f646b61606d54 X10: 7f7f7f7f7f7f7f7f X11: 0101010101010101
(XEN) X12: 0000000000000008 X13: 000000000027c8c0 X14: 0000000000000020
(XEN) X15: 0000000000000000 X16: 0000000000000001 X17: 00000000002bcf54
(XEN) X18: 0180000000000000 X19: 0000000000000000 X20: 000000080004a328
(XEN) X21: 0000000000000000 X22: 00000000002a3000 X23: 6db6db6db6db6db7
(XEN) X24: fffffff800000000 X25: 3d3d3d3d3d3d3d3d X26: 00000000002a3000
(XEN) X27: 00000000002a3000 X28: 00000000002a3000 FP: 00008000fbff7d10
(XEN)
(XEN) VTCR_EL2: 80023558
(XEN) VTTBR_EL2: 0000000000000000
(XEN)
(XEN) SCTLR_EL2: 30cd183d
(XEN) HCR_EL2: 0000000000000038
(XEN) TTBR0_EL2: 000000000152c000
(XEN)
(XEN) ESR_EL2: f2000001
(XEN) HPFAR_EL2: 0000000000000000
(XEN) FAR_EL2: 0000000000000000
(XEN)
(XEN) Xen stack trace from sp=00008000fbff7d10:
(XEN) 00008000fbff7d80 000000000021e74c 000000080004a328 00000000000014b3
(XEN) 00000000002fad40 0000000000003100 00000000002a3488 0000000800001c00
(XEN) 0000000000000000 00000000000fff00 00000000002d03c0 6db6db6db6db6db7
(XEN) 00000000002a10f8 000000010000000d 00008000fbff7df0 000000000021e970
(XEN) 0000000000000002 0000000000000002 0000000000080000 0000000003180000
(XEN) 000000000021e8dc 00000000002fa000 0000000003180000 00000000000fff00
(XEN) 00000000002d03c0 ffffffffffffffff 0000000000000001 00000000002fad90
(XEN) 00008000fbff7e00 00000000002b8398 00008000fbff7e50 00000000002b88b0
(XEN) 00000000002d0408 0000000000000003 0000000000080000 00000000002a34b8
(XEN) 00000000002d03c0 000000000021e8dc 00000000076df000 0000000007fff364
(XEN) 00008000fbff7ea0 00000000002609dc 00000000002a2000 0000000000000004
(XEN) 00000000002a2380 000000000032d430 0000000000000004 0000000000296e40
(XEN) 0000000000000002 00000000002609d8 00000000002efde0 00000000002b9518
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<000000000021bff4>] page_alloc.c#free_heap_pages+0x1dc/0x648 (PC)
(XEN) [<000000000021bff4>] page_alloc.c#free_heap_pages+0x1dc/0x648 (LR)
(XEN) [<000000000021e74c>] page_alloc.c#init_heap_pages+0x3d4/0x564
(XEN) [<000000000021e970>] init_domheap_pages+0x94/0x9c
(XEN) [<00000000002b8398>] 00000000002b8398
(XEN) [<00000000002b88b0>] 00000000002b88b0
(XEN) [<00000000002609dc>] setup.c#init_done+0x10/0x20
(XEN) [<00000000002b9518>] 00000000002b9518
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at page_alloc.c:1425
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
[-- Attachment #4: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-02 18:56 ` Brian Woods
@ 2019-10-02 19:59 ` Julien Grall
2019-10-02 21:22 ` Brian Woods
0 siblings, 1 reply; 14+ messages in thread
From: Julien Grall @ 2019-10-02 19:59 UTC (permalink / raw)
To: Brian Woods; +Cc: xen-devel, Stefano Stabellini, Volodymyr Babchuk
Hi,
On 10/2/19 7:56 PM, Brian Woods wrote:
> On 10/2/19 5:52 PM, Julien Grall wrote:
>> On 10/2/19 1:32 AM, Brian Woods wrote:
>>> Hello,
>>
>> Hi Brian,
>>
>> Thank you for report.
>>
>> I guess this Arm specific, right? If so, please try to CC
>> the relevant maintainers and possibly add "arm" in the
>> subject to avoid any delay (Xen-Devel has quite an high
>> volume of e-mail!).
>>
>> May I also ask to avoiding sending attachment on the mailing
>> list and instead upload the log somewhere (e.g. pastebin,
>> your own webserver...)?
>>
>
> I did include all the ARM maintainers, although I forgot to CC
> Volodymyr. Sorry about that.
Hmmm, the first e-mail didn't land in my inbox directly (I have a filter
send to a separate directory any e-mail I not CCed on). Did you BCC me
by any change?
> Also, I'm not sure if this is strictly an
> ARM or general Xen bug so I left ARM. I guess I should have mentioned
> that in the email though.
Let see try to troubleshoot it first :).
>
> I prefer having them as attachments due to the fact I can see everything
> in mutt. Although if there's a strong community consensus that logs
> shouldn't be emailed as attachments, I will start using a pastebin like
> service to post them.
Well, any attachment you send on the ML will store to each subscribers
mailbox. I let you do the math here ;)
So yeah, pastebin is always the preferred way when you have to send the
full log.
>
>>>
>>> While testing some things out, I found a possible bug in Xen. Xen would
>>> successfully run when loaded (from u-boot) at some addresses but not
>>> others. I didn't observe this issue in 4.11 stable, so I did a bisect
>>> and found that:
>>> commit f60658c6ae47e74792e6cc48ea2effac8bb52826
>>> Author: Julien Grall <julien.grall@arm.com>
>>> Date: Tue Dec 18 13:07:39 2018 +0000
>>>
>>> xen/arm: Stop relocating Xen
>>>
>>> was what was causing it to fail when it was loaded to that certain
>>> address.
>>
>> This patch is basically changing how Xen is using the
>> physical address space. So it exercise more part of Xen
>> code and most likely a red-herring :).
>>
>> However, the logs are quite interesting:
>>
>> (XEN) pg[0] MFN 01533 c=0x180000000000000 o=0 v=0x7ffff t=0
>>
>> If I am not mistaken, the page state is PGC_state_free.
>> So this seems to suggest that the page were already
>> handed over to the allocator.
>>
>> Would you mind to apply the patch below and paste the log?
>>
>> Hopefully, you see see two WARN_ON() before Xen is crashing.
>>
>> Note the patch is assuming the MFN will stay the same after
>> the patch has been applied. If not, you may need to slightly
>> tweak it.
>>
>> diff --git a/xen/common/page_alloc.c b/xen/common/page_alloc.c
>> index 7cb1bd368b..4bf0dbc727 100644
>> --- a/xen/common/page_alloc.c
>> +++ b/xen/common/page_alloc.c
>> @@ -1389,6 +1389,9 @@ static void free_heap_pages(
>> for ( i = 0; i < (1 << order); i++ )
>> {
>> +
>> + WARN_ON(mfn_x(page_to_mfn(pg + 1)) == 0x01533);
>> +
>> /*
>> * Cannot assume that count_info == 0, as there are some corner cases
>> * where it isn't the case and yet it isn't a bug:
>>
>> Cheers,
>>
>> --
>> Julien Grall
>
> Attached are the logs of loading patched Xen at the good and bad
> address. It appears the MFN has stayed the same, although there's only
> one WARN message for both the good and bad address.
Thank you for the log. So that's probably not a double-init then.
Looking back at the log, the values look quite sane. So I am not
entirely sure what is happening.
I would check that the frametable is correctly zeroed. You could add a
print at the end of setup_frametable_mappings(...) to dump the
count_info for the page. Something like:
mfn_to_page(_mfn(0x01533))->count_info;
If it is correctly initialized, it should be zero.
The next step would be to add a similar print in start_xen()
(xen/arch/arm/setup.c) and see where the value is not 0 anymore.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-02 19:59 ` Julien Grall
@ 2019-10-02 21:22 ` Brian Woods
2019-10-02 23:20 ` Brian Woods
0 siblings, 1 reply; 14+ messages in thread
From: Brian Woods @ 2019-10-02 21:22 UTC (permalink / raw)
To: Julien Grall
Cc: Brian Woods, Stefano Stabellini, Volodymyr Babchuk, xen-devel
On Wed, Oct 02, 2019 at 08:59:28PM +0100, Julien Grall wrote:
> Hi,
>
> On 10/2/19 7:56 PM, Brian Woods wrote:
> >On 10/2/19 5:52 PM, Julien Grall wrote:
> >>On 10/2/19 1:32 AM, Brian Woods wrote:
> >>>Hello,
> >>
> >>Hi Brian,
> >>
> >>Thank you for report.
> >>
> >>I guess this Arm specific, right? If so, please try to CC
> >>the relevant maintainers and possibly add "arm" in the
> >>subject to avoid any delay (Xen-Devel has quite an high
> >>volume of e-mail!).
> >>
> >>May I also ask to avoiding sending attachment on the mailing
> >>list and instead upload the log somewhere (e.g. pastebin,
> >>your own webserver...)?
> >>
> >
> >I did include all the ARM maintainers, although I forgot to CC
> >Volodymyr. Sorry about that.
>
> Hmmm, the first e-mail didn't land in my inbox directly (I have a filter
> send to a separate directory any e-mail I not CCed on). Did you BCC me by
> any change?
That's odd. I know I copied your and Stefano's email addresses from the
MAINTAINERS file but under my sent emails it shows it has having no
CCs... PEBCAK I guess. My apologies.
> > Also, I'm not sure if this is strictly an
> >ARM or general Xen bug so I left ARM. I guess I should have mentioned
> >that in the email though.
>
> Let see try to troubleshoot it first :).
>
> >
> >I prefer having them as attachments due to the fact I can see everything
> >in mutt. Although if there's a strong community consensus that logs
> >shouldn't be emailed as attachments, I will start using a pastebin like
> >service to post them.
>
> Well, any attachment you send on the ML will store to each subscribers
> mailbox. I let you do the math here ;)
>
> So yeah, pastebin is always the preferred way when you have to send the full
> log.
>
> >
> >>>
> >>>While testing some things out, I found a possible bug in Xen. Xen would
> >>>successfully run when loaded (from u-boot) at some addresses but not
> >>>others. I didn't observe this issue in 4.11 stable, so I did a bisect
> >>>and found that:
> >>>commit f60658c6ae47e74792e6cc48ea2effac8bb52826
> >>>Author: Julien Grall <julien.grall@arm.com>
> >>>Date: Tue Dec 18 13:07:39 2018 +0000
> >>>
> >>> xen/arm: Stop relocating Xen
> >>>
> >>>was what was causing it to fail when it was loaded to that certain
> >>>address.
> >>
> >>This patch is basically changing how Xen is using the
> >>physical address space. So it exercise more part of Xen
> >>code and most likely a red-herring :).
> >>
> >>However, the logs are quite interesting:
> >>
> >>(XEN) pg[0] MFN 01533 c=0x180000000000000 o=0 v=0x7ffff t=0
> >>
> >>If I am not mistaken, the page state is PGC_state_free.
> >>So this seems to suggest that the page were already
> >>handed over to the allocator.
> >>
> >>Would you mind to apply the patch below and paste the log?
> >>
> >>Hopefully, you see see two WARN_ON() before Xen is crashing.
> >>
> >>Note the patch is assuming the MFN will stay the same after
> >>the patch has been applied. If not, you may need to slightly
> >>tweak it.
> >>
> >>diff --git a/xen/common/page_alloc.c b/xen/common/page_alloc.c
> >>index 7cb1bd368b..4bf0dbc727 100644
> >>--- a/xen/common/page_alloc.c
> >>+++ b/xen/common/page_alloc.c
> >>@@ -1389,6 +1389,9 @@ static void free_heap_pages(
> >> for ( i = 0; i < (1 << order); i++ )
> >> {
> >>+
> >>+ WARN_ON(mfn_x(page_to_mfn(pg + 1)) == 0x01533);
> >>+
> >> /*
> >> * Cannot assume that count_info == 0, as there are some corner cases
> >> * where it isn't the case and yet it isn't a bug:
> >>
> >>Cheers,
> >>
> >>--
> >>Julien Grall
> >
> >Attached are the logs of loading patched Xen at the good and bad
> >address. It appears the MFN has stayed the same, although there's only
> >one WARN message for both the good and bad address.
>
> Thank you for the log. So that's probably not a double-init then.
>
> Looking back at the log, the values look quite sane. So I am not entirely
> sure what is happening.
>
> I would check that the frametable is correctly zeroed. You could add a print
> at the end of setup_frametable_mappings(...) to dump the count_info for the
> page. Something like:
> mfn_to_page(_mfn(0x01533))->count_info;
>
> If it is correctly initialized, it should be zero.
>
> The next step would be to add a similar print in start_xen()
> (xen/arch/arm/setup.c) and see where the value is not 0 anymore.
>
> Cheers,
>
> --
> Julien Grall
I'll go ahead add those and see if that leads to anything.
--
Brian Woods
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-02 21:22 ` Brian Woods
@ 2019-10-02 23:20 ` Brian Woods
2019-10-03 17:08 ` Julien Grall
0 siblings, 1 reply; 14+ messages in thread
From: Brian Woods @ 2019-10-02 23:20 UTC (permalink / raw)
To: Julien Grall
Cc: Brian Woods, Stefano Stabellini, Volodymyr Babchuk, xen-devel
On Wed, Oct 02, 2019 at 02:22:49PM -0700, Brian Woods wrote:
> On Wed, Oct 02, 2019 at 08:59:28PM +0100, Julien Grall wrote:
> > Hi,
> >
> > On 10/2/19 7:56 PM, Brian Woods wrote:
> >
> > Hmmm, the first e-mail didn't land in my inbox directly (I have a filter
> > send to a separate directory any e-mail I not CCed on). Did you BCC me by
> > any change?
> That's odd. I know I copied your and Stefano's email addresses from the
> MAINTAINERS file but under my sent emails it shows it has having no
> CCs... PEBCAK I guess. My apologies.
> >
> > Let see try to troubleshoot it first :).
> >
> > Well, any attachment you send on the ML will store to each subscribers
> > mailbox. I let you do the math here ;)
> >
> > So yeah, pastebin is always the preferred way when you have to send the full
> > log.
> >
> > Thank you for the log. So that's probably not a double-init then.
> >
> > Looking back at the log, the values look quite sane. So I am not entirely
> > sure what is happening.
> >
> > I would check that the frametable is correctly zeroed. You could add a print
> > at the end of setup_frametable_mappings(...) to dump the count_info for the
> > page. Something like:
> > mfn_to_page(_mfn(0x01533))->count_info;
> >
> > If it is correctly initialized, it should be zero.
> >
> > The next step would be to add a similar print in start_xen()
> > (xen/arch/arm/setup.c) and see where the value is not 0 anymore.
> >
> > Cheers,
> >
> > --
> > Julien Grall
>
> I'll go ahead add those and see if that leads to anything.
>
> --
> Brian Woods
Ok, I added:
printk("BW_DEBUG: 01 count_info=0x%016lx\n",
mfn_to_page(_mfn(0x01533))->count_info);
In some places. I'm not sure about some of the earlier ones (the ones
before the UART is set up), but all of the ones afterwards that
actually get output are:
BW_DEBUG: 11 count_info=0x0180000000000000
Is it worth trying to figure out where the printk buffer is and reading
it really early on?
--
Brian Woods
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-02 23:20 ` Brian Woods
@ 2019-10-03 17:08 ` Julien Grall
2019-10-03 18:15 ` Brian Woods
0 siblings, 1 reply; 14+ messages in thread
From: Julien Grall @ 2019-10-03 17:08 UTC (permalink / raw)
To: Brian Woods; +Cc: xen-devel, Stefano Stabellini, Volodymyr Babchuk
Hi,
On 03/10/2019 00:20, Brian Woods wrote:
> On Wed, Oct 02, 2019 at 02:22:49PM -0700, Brian Woods wrote:
>> On Wed, Oct 02, 2019 at 08:59:28PM +0100, Julien Grall wrote:
>>> Hi,
>>>
>>> On 10/2/19 7:56 PM, Brian Woods wrote:
>>>
>>> Hmmm, the first e-mail didn't land in my inbox directly (I have a filter
>>> send to a separate directory any e-mail I not CCed on). Did you BCC me by
>>> any change?
>> That's odd. I know I copied your and Stefano's email addresses from the
>> MAINTAINERS file but under my sent emails it shows it has having no
>> CCs... PEBCAK I guess. My apologies.
>>>
>>> Let see try to troubleshoot it first :).
>>>
>>> Well, any attachment you send on the ML will store to each subscribers
>>> mailbox. I let you do the math here ;)
>>>
>>> So yeah, pastebin is always the preferred way when you have to send the full
>>> log.
>>>
>>> Thank you for the log. So that's probably not a double-init then.
>>>
>>> Looking back at the log, the values look quite sane. So I am not entirely
>>> sure what is happening.
>>>
>>> I would check that the frametable is correctly zeroed. You could add a print
>>> at the end of setup_frametable_mappings(...) to dump the count_info for the
>>> page. Something like:
>>> mfn_to_page(_mfn(0x01533))->count_info;
>>>
>>> If it is correctly initialized, it should be zero.
>>>
>>> The next step would be to add a similar print in start_xen()
>>> (xen/arch/arm/setup.c) and see where the value is not 0 anymore.
>>>
>>> Cheers,
>>>
>>> --
>>> Julien Grall
>>
>> I'll go ahead add those and see if that leads to anything.
>>
>> --
>> Brian Woods
>
> Ok, I added:
> printk("BW_DEBUG: 01 count_info=0x%016lx\n",
> mfn_to_page(_mfn(0x01533))->count_info);
> In some places. I'm not sure about some of the earlier ones (the ones
> before the UART is set up), but all of the ones afterwards that
> actually get output are:
> BW_DEBUG: 11 count_info=0x0180000000000000
>
> Is it worth trying to figure out where the printk buffer is and reading
> it really early on?
>
If you haven't enable EARLY_PRINTK in Xen, then you may want to do it. This
would help you to understand where the page->count_info is not zeroed.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-03 17:08 ` Julien Grall
@ 2019-10-03 18:15 ` Brian Woods
2019-10-03 19:23 ` Julien Grall
0 siblings, 1 reply; 14+ messages in thread
From: Brian Woods @ 2019-10-03 18:15 UTC (permalink / raw)
To: Julien Grall
Cc: Brian Woods, Stefano Stabellini, Volodymyr Babchuk, xen-devel
On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> Hi,
>
> On 03/10/2019 00:20, Brian Woods wrote:
> >On Wed, Oct 02, 2019 at 02:22:49PM -0700, Brian Woods wrote:
> >>That's odd. I know I copied your and Stefano's email addresses from the
> >>MAINTAINERS file but under my sent emails it shows it has having no
> >>CCs... PEBCAK I guess. My apologies.
> >>
> >>I'll go ahead add those and see if that leads to anything.
> >>
> >>--
> >>Brian Woods
> >
> >Ok, I added:
> > printk("BW_DEBUG: 01 count_info=0x%016lx\n",
> > mfn_to_page(_mfn(0x01533))->count_info);
> >In some places. I'm not sure about some of the earlier ones (the ones
> >before the UART is set up), but all of the ones afterwards that
> >actually get output are:
> > BW_DEBUG: 11 count_info=0x0180000000000000
> >
> >Is it worth trying to figure out where the printk buffer is and reading
> >it really early on?
> >
>
> If you haven't enable EARLY_PRINTK in Xen, then you may want to do it. This
> would help you to understand where the page->count_info is not zeroed.
>
>
> Cheers,
>
> --
> Julien Grall
Ah, I'm not used to some of the Arm-isms in Xen yet.
(XEN) BW_DEBUG: .6 count_info=0x0000000000000000
(XEN) Domain heap initialised
(XEN) BW_DEBUG: 01 count_info=0x0180000000000000
Those debug messages sandwich end_boot_allocator() in start_xen().
--
Brian Woods
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-03 18:15 ` Brian Woods
@ 2019-10-03 19:23 ` Julien Grall
2019-10-03 20:24 ` Brian Woods
0 siblings, 1 reply; 14+ messages in thread
From: Julien Grall @ 2019-10-03 19:23 UTC (permalink / raw)
To: Brian Woods; +Cc: xen-devel, nd, Volodymyr Babchuk, Stefano Stabellini
Hi,
On 03/10/2019 19:15, Brian Woods wrote:
> On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> (XEN) BW_DEBUG: .6 count_info=0x0000000000000000
> (XEN) Domain heap initialised
> (XEN) BW_DEBUG: 01 count_info=0x0180000000000000
>
> Those debug messages sandwich end_boot_allocator() in start_xen().
hmmm, looking back at the thread, the WARN_ON() I suggested is actually
incorrect. :/ Sorry for that. It should be:
WARN_ON(mfn_x(page_to_mfn(pg + i)) == 0x01533);
Note the "i" instead of "1".
If the WARN_ON() is triggered between the two calls, then it would mean
we are giving page to the boot allocator.
This would imply that next_modules() or dt_unreserved_regions() is not
working as expected (i.e. carving out any modules).
Also, could you send your log with early printk enabled?
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-03 19:23 ` Julien Grall
@ 2019-10-03 20:24 ` Brian Woods
2019-10-03 21:20 ` Julien Grall
0 siblings, 1 reply; 14+ messages in thread
From: Brian Woods @ 2019-10-03 20:24 UTC (permalink / raw)
To: Julien Grall
Cc: Brian Woods, nd, Volodymyr Babchuk, Stefano Stabellini, xen-devel
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
On Thu, Oct 03, 2019 at 07:23:23PM +0000, Julien Grall wrote:
> Hi,
>
> On 03/10/2019 19:15, Brian Woods wrote:
> > On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> > (XEN) BW_DEBUG: .6 count_info=0x0000000000000000
> > (XEN) Domain heap initialised
> > (XEN) BW_DEBUG: 01 count_info=0x0180000000000000
> >
> > Those debug messages sandwich end_boot_allocator() in start_xen().
>
> hmmm, looking back at the thread, the WARN_ON() I suggested is actually
> incorrect. :/ Sorry for that. It should be:
>
> WARN_ON(mfn_x(page_to_mfn(pg + i)) == 0x01533);
>
> Note the "i" instead of "1".
>
> If the WARN_ON() is triggered between the two calls, then it would mean
> we are giving page to the boot allocator.
>
> This would imply that next_modules() or dt_unreserved_regions() is not
> working as expected (i.e. carving out any modules).
>
> Also, could you send your log with early printk enabled?
>
> Cheers,
>
> --
> Julien Grall
Attached are the log and diff.
There's a WARN_ON() between the two debug printks calls I shared above.
--
Brian Woods
[-- Attachment #2: xen-git_52633db2c5ed-p8-bad_addr.log --]
[-- Type: text/plain, Size: 23751 bytes --]
PMU Firmware 2019.1 May 25 2019 06:57:33
PMU_ROM Version: xpbr-v8.1.0-0
NOTICE: ATF running on XCZUUNKN/QEMU v4/RTL0.0 at 0xfffea000
NOTICE: BL31: Secure code at 0x60000000
NOTICE: BL31: Non secure code at 0x10080000
NOTICE: BL31: v2.0(release):xilinx-v2018.3-720-g80d1c790
NOTICE: BL31: Built : 06:54:23, May 25 2019
PMUFW: v1.1
U-Boot 2019.01 (May 25 2019 - 06:55:09 +0000)
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
DRAM: 4 GiB
EL Level: EL2
Chip ID: unknown
MMC: mmc@ff170000: 0
Loading Environment from SPI Flash... SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
*** Warning - bad CRC, using default environment
In: serial@ff000000
Out: serial@ff000000
Err: serial@ff000000
Model: ZynqMP ZCU102 Rev1.0
Board: Xilinx ZynqMP
Bootmode: JTAG_MODE
Reset reason: EXTERNAL
Net: ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for xilinx-zcu102-2019_1
BOOTP broadcast 1
DHCP client bound to address 10.0.5.15 (2 ms)
Hit any key to stop autoboot: 4 \b\b\b 3 \b\b\b 0
ZynqMP> setenv serverip 10.0.5.2; tftpb 1280000 xen-qemu-mod.dtb; tftpb 0x80000 yocto-Image; tftpb 1400000 xen-custom.ub; tftpb 9000000 yocto-rootfs.cpio.gz.ub; bootm 1400000 9000000 1280000
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'xen-qemu-mod.dtb'.
Load address: 0x1280000
Loading: *\b###
6 MiB/s
done
Bytes transferred = 38019 (9483 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'yocto-Image'.
Load address: 0x80000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#########################################
36.6 MiB/s
done
Bytes transferred = 18215424 (115f200 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'xen-custom.ub'.
Load address: 0x1400000
Loading: *\b#################################################################
####
22.4 MiB/s
done
Bytes transferred = 984464 (f0590 hex)
Using ethernet@ff0e0000 device
TFTP from server 10.0.5.2; our IP address is 10.0.5.15
Filename 'yocto-rootfs.cpio.gz.ub'.
Load address: 0x9000000
Loading: *\b#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#####################
36.4 MiB/s
done
Bytes transferred = 9569188 (9203a4 hex)
## Booting kernel from Legacy Image at 01400000 ...
Image Name:
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 984400 Bytes = 961.3 KiB
Load Address: 01400000
Entry Point: 01400000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 09000000 ...
Image Name:
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 9569124 Bytes = 9.1 MiB
Load Address: 09000000
Entry Point: 09000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01280000
Booting using the fdt blob at 0x1280000
Loading Kernel Image ... OK
Loading Ramdisk to 076df000, end 07fff364 ... OK
Loading Device Tree to 00000000076d2000, end 00000000076de482 ... OK
Starting kernel ...
- UART enabled -
- Boot CPU booting -
- Current EL 00000008 -
- Initialize CPU -
- Turning on paging -
- Zero BSS -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) Initrd 00000000076df000-0000000007fff364
(XEN) RAM: 0000000000000000 - 000000007fefffff
(XEN) RAM: 0000000800000000 - 000000087fffffff
(XEN)
(XEN) MODULE[0]: 0000000001400000 - 00000000015328f1 Xen
(XEN) MODULE[1]: 00000000076d2000 - 00000000076dc080 Device Tree
(XEN) MODULE[2]: 00000000076df000 - 0000000007fff364 Ramdisk
(XEN) MODULE[3]: 0000000000080000 - 0000000003180000 Kernel
(XEN) RESVD[0]: 00000000076d2000 - 00000000076dc000
(XEN) RESVD[1]: 00000000076df000 - 0000000007fff364
(XEN)
(XEN)
(XEN) Command line: console=dtuart dtuart=serial0 dom0_mem=1G bootscrub=0 timer_slop=0
(XEN) PFN compression on bits 19...22
(XEN) BW_DEBUG: 00 count_info=0x0000000000000000
(XEN) BW_DEBUG: .3 count_info=0x0000000000000000
(XEN) BW_DEBUG: .6 count_info=0x0000000000000000
(XEN) Xen WARN at page_alloc.c:1392
(XEN) ----[ Xen-4.13-unstable arm64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) PC: 000000000021c144 page_alloc.c#free_heap_pages+0x144/0x614
(XEN) LR: 0180000000000000
(XEN) SP: 00000000002efcc0
(XEN) CPSR: 600003c9 MODE:64-bit EL2h (Hypervisor, handler)
(XEN) X0: 000000080004a328 X1: 0000000000000000 X2: 000000080004a328
(XEN) X3: 0000000000001533 X4: 00000000002a34b8 X5: 00000000002a3000
(XEN) X6: 00000000002a3000 X7: 00000000002a3000 X8: 0080000000000000
(XEN) X9: 0000000000001533 X10: 6db6db6db6db6db7 X11: fffffff800000000
(XEN) X12: 0000000000000001 X13: 0000000000001533 X14: 0000000000001533
(XEN) X15: 000000000007ffff X16: 00000000002a3488 X17: 0000000000000001
(XEN) X18: 000000007dda9de8 X19: 0000000000000000 X20: 0000000000000000
(XEN) X21: 000000080004a328 X22: 0000000000000000 X23: 0000000047ffffff
(XEN) X24: 00000000002a3000 X25: 3d3d3d3d3d3d3d3d X26: 00000000002a3000
(XEN) X27: 00000000002a3000 X28: 00000000002a3000 FP: 00000000002efcc0
(XEN)
(XEN) VTCR_EL2: 00000000
(XEN) VTTBR_EL2: 0000000000000000
(XEN)
(XEN) SCTLR_EL2: 30cd183d
(XEN) HCR_EL2: 0000000000000038
(XEN) TTBR0_EL2: 000000000152c000
(XEN)
(XEN) ESR_EL2: f2000001
(XEN) HPFAR_EL2: 0000000000000000
(XEN) FAR_EL2: 0000000000000000
(XEN)
(XEN) Xen stack trace from sp=00000000002efcc0:
(XEN) 00000000002efd30 000000000021e900 000000080004a328 0000000000000000
(XEN) 00000000002fad40 000000000000619f 00000000002a3488 000000080004a328
(XEN) 0000000000000000 00000000000fff00 00000000002d03c0 6db6db6db6db6db7
(XEN) 00000000002a10f8 000000010000000d 00000000002efda0 00000000002a6dbc
(XEN) 0000000000000001 00000000002c8000 00000000002a34b8 00000000002a3000
(XEN) 00000000002a3000 00000000002a3000 0000000000000002 00000000000fff00
(XEN) 00000000002d03c0 ffffffffffffffff 00000000002efda0 00000000002fad90
(XEN) 00000000002efde0 00000000002b8e60 0000000000001533 0000000800000000
(XEN) 00000000002a3000 00000000002a3000 00000000002a3000 fefefefefefeff09
(XEN) 000000007dd9e890 00000000002001b4 0000000001400000 0000000001200000
(XEN) 00000000076d2000 0000000000000000 0000000000400000 0000000000000003
(XEN) 0000000000000001 0000000000000000 0000000001400000 0000000001400040
(XEN) 0000000000000000 00000000002a63b8 00000000002d03c0 00000000002d03d8
(XEN) 00000000076d2000 000000000000a080 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000300000000 0000000000000000 00000040ffffffff
(XEN) 0000000000000400 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<000000000021c144>] page_alloc.c#free_heap_pages+0x144/0x614 (PC)
(XEN) [<0180000000000000>] 0180000000000000 (LR)
(XEN) [<000000000021e900>] page_alloc.c#init_heap_pages+0x3d4/0x564
(XEN) [<00000000002a6dbc>] end_boot_allocator+0x114/0x21c
(XEN) [<00000000002b8e60>] start_xen+0x47c/0x108c
(XEN) [<00000000002001b4>] arm64/head.o#primary_switched+0xc/0x2c
(XEN)
(XEN) Domain heap initialised
(XEN) BW_DEBUG: 01 count_info=0x0180000000000000
(XEN) Booting using Device Tree
(XEN) Platform: Xilinx ZynqMP
(XEN) BW_DEBUG: 02 count_info=0x0180000000000000
(XEN) Looking for dtuart at "serial0", options ""
Xen 4.13-unstable
(XEN) Xen version 4.13-unstable (woods@xilinx.com) (aarch64-unknown-linux-gnu-gcc (crosstool-NG 1.24.0.6-afaf7b9) 8.3.0) debug=y Thu Oct 3 12:59:18 PDT 2019
(XEN) Latest ChangeSet: Thu Sep 26 11:03:08 2019 +0100 git:52633db-dirty
(XEN) build-id: 15b5303bb7014b2f2e5973278c679dac8b3bd1c8
(XEN) BW_DEBUG:2.5 count_info=0x0180000000000000
(XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev 0x4
(XEN) 64-bit Execution:
(XEN) Processor Features: 1100000000002222 0000000000000000
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN) Debug Features: 0000000010305106 0000000000000000
(XEN) Auxiliary Features: 0000000000000000 0000000000000000
(XEN) Memory Model Features: 0000000000001122 0000000000000000
(XEN) ISA Features: 0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN) Processor Features: 00001231:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
(XEN) Extensions: GenericTimer Security
(XEN) Debug Features: 03010066
(XEN) Auxiliary Features: 00000000
(XEN) Memory Model Features: 10101105 40000000 01260000 02102211
(XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using SMC Calling Convention v1.1
(XEN) Using PSCI v1.1
(XEN) SMP: Allowing 4 CPUs
(XEN) BW_DEBUG: 03 count_info=0x0180000000000000
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 65000 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=00000000f9010000
(XEN) gic_cpu_addr=00000000f9020000
(XEN) gic_hyp_addr=00000000f9040000
(XEN) gic_vcpu_addr=00000000f9060000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: Adjusting CPU interface base to 0xf902f000
(XEN) GICv2: 192 lines, 4 cpus (IID 00000000).
(XEN) BW_DEBUG: 04 count_info=0x0180000000000000
(XEN) XSM Framework v1.0.0 initialized
(XEN) Initialising XSM SILO mode
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) load_precision_shift: 18
(XEN) load_window_shift: 30
(XEN) underload_balance_tolerance: 0
(XEN) overload_balance_tolerance: -3
(XEN) runqueues arrangement: socket
(XEN) cap enforcement granularity: 10ms
(XEN) load tracking window length 1073741824 ns
(XEN) BW_DEBUG: 05 count_info=0x0180000000000000
(XEN) Allocated console ring of 32 KiB.
(XEN) CPU0: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU1
- CPU 00000001 booting -
- Current EL 00000008 -
- Initialize CPU -
- Turning on paging -
- Ready -
(XEN) CPU1: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU2
(XEN) CPU 1 booted.
- CPU 00000002 booting -
- Current EL 00000008 -
- Initialize CPU -
- Turning on paging -
- Ready -
(XEN) CPU2: Guest atomics will try 1 times before pausing the domain
(XEN) Bringing up CPU3
(XEN) CPU 2 booted.
- CPU 00000003 booting -
- Current EL 00000008 -
- Initialize CPU -
- Turning on paging -
- Ready -
(XEN) CPU3: Guest atomics will try 1 times before pausing the domain
(XEN) Brought up 4 CPUs
(XEN) CPU 3 booted.
(XEN) BW_DEBUG: 06 count_info=0x0180000000000000
(XEN) P2M: 40-bit IPA with 40-bit PA and 8-bit VMID
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) smmu: /smmu@fd800000: probing hardware configuration...
(XEN) smmu: /smmu@fd800000: SMMUv2 with:
(XEN) smmu: /smmu@fd800000: stage 2 translation
(XEN) smmu: /smmu@fd800000: stream matching with 48 register groups, mask 0x7fff
(XEN) smmu: /smmu@fd800000: 16 context banks (0 stage-2 only)
(XEN) smmu: /smmu@fd800000: Stage-2: 40-bit IPA -> 48-bit PA
(XEN) smmu: /smmu@fd800000: registered 26 master devices
(XEN) I/O virtualisation enabled
(XEN) - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) Adding cpu 0 to runqueue 0
(XEN) First cpu on runqueue, activating
(XEN) Adding cpu 1 to runqueue 0
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 3 to runqueue 0
(XEN) alternatives: Patching with alt table 00000000002c3e78 -> 00000000002c4538
(XEN) BW_DEBUG: 07 count_info=0x0180000000000000
(XEN) BW_DEBUG: 08 count_info=0x0180000000000000
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading d0 kernel from boot module @ 0000000000080000
(XEN) Loading ramdisk from boot module @ 00000000076df000
(XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
(XEN) BANK[0] 0x00000020000000-0x00000060000000 (1024MB)
(XEN) Grant table range: 0x00000001400000-0x00000001440000
(XEN) smmu: /smmu@fd800000: d0: p2maddr 0x000000087bf9a000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading zImage from 0000000000080000 to 0000000020080000-0000000023180000
(XEN) Loading dom0 initrd from 00000000076df000 to 0x0000000028200000-0x0000000028b20364
(XEN) Loading dom0 DTB to 0x0000000028000000-0x0000000028008db3
(XEN) BW_DEBUG: 09 count_info=0x0180000000000000
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) BW_DEBUG: 10 count_info=0x0180000000000000
(XEN) BW_DEBUG: 11 count_info=0x0180000000000000
(XEN) Xen WARN at page_alloc.c:1392
(XEN) ----[ Xen-4.13-unstable arm64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) PC: 000000000021c144 page_alloc.c#free_heap_pages+0x144/0x614
(XEN) LR: 0180000000000000
(XEN) SP: 00008000fbff7d10
(XEN) CPSR: 60000249 MODE:64-bit EL2h (Hypervisor, handler)
(XEN) X0: 000000080004a328 X1: 0000000000000000 X2: 000000080004a328
(XEN) X3: 0000000000001533 X4: 00000000002a34b8 X5: 00000000002a3000
(XEN) X6: 00000000002a3000 X7: 00000000002a3000 X8: 0080000000000000
(XEN) X9: 0000000000001533 X10: 6db6db6db6db6db7 X11: fffffff800000000
(XEN) X12: 0000000000000001 X13: 0000000000001533 X14: 0000000000001533
(XEN) X15: 000000000007ffff X16: 00000000002a3488 X17: 0000000000000001
(XEN) X18: 000000007dda9de8 X19: 0000000000000000 X20: 0000000000000000
(XEN) X21: 000000080004a328 X22: 0000000000000000 X23: 0000000047ffffff
(XEN) X24: 00000000002a3000 X25: 3d3d3d3d3d3d3d3d X26: 00000000002a3000
(XEN) X27: 00000000002a3000 X28: 00000000002a3000 FP: 00008000fbff7d10
(XEN)
(XEN) VTCR_EL2: 80023558
(XEN) VTTBR_EL2: 0000000000000000
(XEN)
(XEN) SCTLR_EL2: 30cd183d
(XEN) HCR_EL2: 0000000000000038
(XEN) TTBR0_EL2: 000000000152c000
(XEN)
(XEN) ESR_EL2: f2000001
(XEN) HPFAR_EL2: 0000000000000000
(XEN) FAR_EL2: 0000000000000000
(XEN)
(XEN) Xen stack trace from sp=00008000fbff7d10:
(XEN) 00008000fbff7d80 000000000021e900 000000080004a328 00000000000014b3
(XEN) 00000000002fad40 0000000000003100 00000000002a3488 0000000800001c00
(XEN) 0000000000000000 00000000000fff00 00000000002d03c0 6db6db6db6db6db7
(XEN) 00000000002a10f8 000000010000000d 00008000fbff7df0 000000000021eb24
(XEN) 0000000000000002 0000000000000002 0000000000080000 0000000003180000
(XEN) 000000000021ea90 00000000002fa000 0000000003180000 00000000000fff00
(XEN) 00000000002d03c0 ffffffffffffffff 0000000000000001 00000000002fad90
(XEN) 00008000fbff7e00 00000000002b83ec 00008000fbff7e50 00000000002b8904
(XEN) 00000000002d0408 0000000000000003 0000000000080000 00000000002a34b8
(XEN) 00000000002d03c0 000000000021ea90 00000000076df000 0000000007fff364
(XEN) 00008000fbff7ea0 0000000000260a3c 00000000002a2000 000000080004a328
(XEN) 00000000002a3000 00000000002a3000 00000000002a3000 00008000fbf9d000
(XEN) 00000000002a3000 0000000000260a38 00000000002efde0 00000000002b99ac
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<000000000021c144>] page_alloc.c#free_heap_pages+0x144/0x614 (PC)
(XEN) [<0180000000000000>] 0180000000000000 (LR)
(XEN) [<000000000021e900>] page_alloc.c#init_heap_pages+0x3d4/0x564
(XEN) [<000000000021eb24>] init_domheap_pages+0x94/0x9c
(XEN) [<00000000002b83ec>] 00000000002b83ec
(XEN) [<00000000002b8904>] 00000000002b8904
(XEN) [<0000000000260a3c>] setup.c#init_done+0x10/0x20
(XEN) [<00000000002b99ac>] 00000000002b99ac
(XEN)
(XEN) pg[0] MFN 01533 c=0x180000000000000 o=0 v=0x7ffff t=0
(XEN) Xen BUG at page_alloc.c:1424
(XEN) ----[ Xen-4.13-unstable arm64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) PC: 000000000021c1a8 page_alloc.c#free_heap_pages+0x1a8/0x614
(XEN) LR: 000000000021c1a8
(XEN) SP: 00008000fbff7d10
(XEN) CPSR: 60000249 MODE:64-bit EL2h (Hypervisor, handler)
(XEN) X0: 00000000002a1558 X1: 00000000000001c1 X2: 0000000000000000
(XEN) X3: 0000000000000000 X4: 0000000000000000 X5: 0000000000000012
(XEN) X6: 0000000000000080 X7: fefefefefefeff09 X8: 7f7f7f7f7f7f7f7f
(XEN) X9: 731f646b61606d54 X10: 7f7f7f7f7f7f7f7f X11: 0101010101010101
(XEN) X12: 0000000000000008 X13: 000000000027c8c0 X14: 0000000000000020
(XEN) X15: 0000000000000000 X16: 00000000002a3488 X17: 0000000000000001
(XEN) X18: 000000007dda9de8 X19: 0000000000000000 X20: 0000000000000000
(XEN) X21: 000000080004a328 X22: 0000000000000000 X23: 0000000047ffffff
(XEN) X24: 00000000002a3000 X25: 3d3d3d3d3d3d3d3d X26: 00000000002a3000
(XEN) X27: 00000000002a3000 X28: 00000000002a3000 FP: 00008000fbff7d10
(XEN)
(XEN) VTCR_EL2: 80023558
(XEN) VTTBR_EL2: 0000000000000000
(XEN)
(XEN) SCTLR_EL2: 30cd183d
(XEN) HCR_EL2: 0000000000000038
(XEN) TTBR0_EL2: 000000000152c000
(XEN)
(XEN) ESR_EL2: f2000001
(XEN) HPFAR_EL2: 0000000000000000
(XEN) FAR_EL2: 0000000000000000
(XEN)
(XEN) Xen stack trace from sp=00008000fbff7d10:
(XEN) 00008000fbff7d80 000000000021e900 000000080004a328 00000000000014b3
(XEN) 00000000002fad40 0000000000003100 00000000002a3488 0000000800001c00
(XEN) 0000000000000000 00000000000fff00 00000000002d03c0 6db6db6db6db6db7
(XEN) 00000000002a10f8 000000010000000d 00008000fbff7df0 000000000021eb24
(XEN) 0000000000000002 0000000000000002 0000000000080000 0000000003180000
(XEN) 000000000021ea90 00000000002fa000 0000000003180000 00000000000fff00
(XEN) 00000000002d03c0 ffffffffffffffff 0000000000000001 00000000002fad90
(XEN) 00008000fbff7e00 00000000002b83ec 00008000fbff7e50 00000000002b8904
(XEN) 00000000002d0408 0000000000000003 0000000000080000 00000000002a34b8
(XEN) 00000000002d03c0 000000000021ea90 00000000076df000 0000000007fff364
(XEN) 00008000fbff7ea0 0000000000260a3c 00000000002a2000 000000080004a328
(XEN) 00000000002a3000 00000000002a3000 00000000002a3000 00008000fbf9d000
(XEN) 00000000002a3000 0000000000260a38 00000000002efde0 00000000002b99ac
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN) [<000000000021c1a8>] page_alloc.c#free_heap_pages+0x1a8/0x614 (PC)
(XEN) [<000000000021c1a8>] page_alloc.c#free_heap_pages+0x1a8/0x614 (LR)
(XEN) [<000000000021e900>] page_alloc.c#init_heap_pages+0x3d4/0x564
(XEN) [<000000000021eb24>] init_domheap_pages+0x94/0x9c
(XEN) [<00000000002b83ec>] 00000000002b83ec
(XEN) [<00000000002b8904>] 00000000002b8904
(XEN) [<0000000000260a3c>] setup.c#init_done+0x10/0x20
(XEN) [<00000000002b99ac>] 00000000002b99ac
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Xen BUG at page_alloc.c:1424
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
[-- Attachment #3: debug.patch --]
[-- Type: text/x-diff, Size: 5145 bytes --]
diff --git a/xen/arch/arm/mm.c b/xen/arch/arm/mm.c
index 65552da..4d27cc3 100644
--- a/xen/arch/arm/mm.c
+++ b/xen/arch/arm/mm.c
@@ -915,6 +915,8 @@ void __init setup_frametable_mappings(paddr_t ps, paddr_t pe)
frametable_size - (nr_pdxs * sizeof(struct page_info)));
frametable_virt_end = FRAMETABLE_VIRT_START + (nr_pdxs * sizeof(struct page_info));
+
+ printk("BW_DEBUG: 00 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
}
void *__init arch_vmap_virt_end(void)
diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index fca7e68..c0ef166 100644
--- a/xen/arch/arm/setup.c
+++ b/xen/arch/arm/setup.c
@@ -829,11 +829,17 @@ void __init start_xen(unsigned long boot_phys_offset,
setup_mm();
+ printk("BW_DEBUG: .3 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
/* Parse the ACPI tables for possible boot-time configuration */
acpi_boot_table_init();
+ printk("BW_DEBUG: .6 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
end_boot_allocator();
+ printk("BW_DEBUG: 01 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
/*
* The memory subsystem has been initialized, we can now switch from
* early_boot -> boot.
@@ -858,6 +864,8 @@ void __init start_xen(unsigned long boot_phys_offset,
platform_init();
+ printk("BW_DEBUG: 02 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
preinit_xen_time();
gic_preinit();
@@ -866,6 +874,7 @@ void __init start_xen(unsigned long boot_phys_offset,
console_init_preirq();
console_init_ring();
+ printk("BW_DEBUG:2.5 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
processor_id();
smp_init_cpus();
@@ -873,6 +882,8 @@ void __init start_xen(unsigned long boot_phys_offset,
printk(XENLOG_INFO "SMP: Allowing %u CPUs\n", cpus);
nr_cpu_ids = cpus;
+ printk("BW_DEBUG: 03 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
/*
* Some errata relies on SMCCC version which is detected by psci_init()
* (called from smp_init_cpus()).
@@ -887,6 +898,8 @@ void __init start_xen(unsigned long boot_phys_offset,
tasklet_subsys_init();
+ printk("BW_DEBUG: 04 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
if ( xsm_dt_init() != 1 )
warning_add("WARNING: SILO mode is not enabled.\n"
"It has implications on the security of the system,\n"
@@ -904,6 +917,8 @@ void __init start_xen(unsigned long boot_phys_offset,
setup_system_domains();
+ printk("BW_DEBUG: 05 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
local_irq_enable();
local_abort_enable();
@@ -928,6 +943,8 @@ void __init start_xen(unsigned long boot_phys_offset,
printk("Brought up %ld CPUs\n", (long)num_online_cpus());
/* TODO: smp_cpus_done(); */
+ printk("BW_DEBUG: 06 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
setup_virt_paging();
rc = iommu_setup();
@@ -943,6 +960,8 @@ void __init start_xen(unsigned long boot_phys_offset,
apply_alternatives_all();
enable_errata_workarounds();
+ printk("BW_DEBUG: 07 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
/* Create initial domain 0. */
/* The vGIC for DOM0 is exactly emulating the hardware GIC */
dom0_cfg.arch.gic_version = XEN_DOMCTL_CONFIG_GIC_NATIVE;
@@ -963,9 +982,13 @@ void __init start_xen(unsigned long boot_phys_offset,
if ( IS_ERR(dom0) || (alloc_dom0_vcpu0(dom0) == NULL) )
panic("Error creating domain 0\n");
+ printk("BW_DEBUG: 08 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
if ( construct_dom0(dom0) != 0)
panic("Could not set up DOM0 guest OS\n");
+ printk("BW_DEBUG: 09 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
heap_init_late();
init_trace_bufs();
@@ -974,6 +997,8 @@ void __init start_xen(unsigned long boot_phys_offset,
console_endboot();
+ printk("BW_DEBUG: 10 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
/* Hide UART from DOM0 if we're using it */
serial_endboot();
@@ -983,6 +1008,8 @@ void __init start_xen(unsigned long boot_phys_offset,
domain_unpause_by_systemcontroller(dom0);
+ printk("BW_DEBUG: 11 count_info=0x%016lx\n", mfn_to_page(_mfn(0x01533))->count_info);
+
/* Switch on to the dynamically allocated stack for the idle vcpu
* since the static one we're running on is about to be freed. */
memcpy(idle_vcpu[0]->arch.cpu_info, get_cpu_info(),
diff --git a/xen/common/page_alloc.c b/xen/common/page_alloc.c
index 7cb1bd3..95e874d 100644
--- a/xen/common/page_alloc.c
+++ b/xen/common/page_alloc.c
@@ -1389,6 +1389,8 @@ static void free_heap_pages(
for ( i = 0; i < (1 << order); i++ )
{
+ WARN_ON(mfn_x(page_to_mfn(pg + i)) == 0x01533);
+
/*
* Cannot assume that count_info == 0, as there are some corner cases
* where it isn't the case and yet it isn't a bug:
[-- Attachment #4: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply related [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-03 20:24 ` Brian Woods
@ 2019-10-03 21:20 ` Julien Grall
2019-10-04 0:25 ` Brian Woods
0 siblings, 1 reply; 14+ messages in thread
From: Julien Grall @ 2019-10-03 21:20 UTC (permalink / raw)
To: Brian Woods; +Cc: xen-devel, nd, Volodymyr Babchuk, Stefano Stabellini
Hi Brian,
On 10/3/19 9:24 PM, Brian Woods wrote:
> On Thu, Oct 03, 2019 at 07:23:23PM +0000, Julien Grall wrote:
> There's a WARN_ON() between the two debug printks calls I shared above.
Looking at the log, the MFN seems to correspond to the one right after
Xen (0000000001400000 - 00000000015328f1) in memory.
So it is normal to have the page given to the boot allocator. However, I
am not entirely sure which bit of init_done() is giving the page again
to xenheap.
It is unlikely to be free_init_memory() because it deal with the init
section that is not at the end of the binary.
This would leave discard_initial_modules() but there are a check to skip
Xen module.
The call stack only print the address and not the symbol because it
unregistered the symbols for init. See unregister_init_virtual_memory().
(XEN) Xen call trace:
(XEN) [<000000000021c1a8>] page_alloc.c#free_heap_pages+0x1a8/0x614 (PC)
(XEN) [<000000000021c1a8>] page_alloc.c#free_heap_pages+0x1a8/0x614 (LR)
(XEN) [<000000000021e900>] page_alloc.c#init_heap_pages+0x3d4/0x564
(XEN) [<000000000021eb24>] init_domheap_pages+0x94/0x9c
(XEN) [<00000000002b83ec>] 00000000002b83ec
(XEN) [<00000000002b8904>] 00000000002b8904
(XEN) [<0000000000260a3c>] setup.c#init_done+0x10/0x20
(XEN) [<00000000002b99ac>] 00000000002b99ac
You should be able to use addr2line on the address with Xen binary.
I have the feeling this will point to discard_initial_modules() as this
is an init function and the symbol should not be printed.
But, I can't see anything obviously wrong in the function... So I am not
entirely sure what could be the next steps.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-03 21:20 ` Julien Grall
@ 2019-10-04 0:25 ` Brian Woods
2019-10-04 9:49 ` Julien Grall
0 siblings, 1 reply; 14+ messages in thread
From: Brian Woods @ 2019-10-04 0:25 UTC (permalink / raw)
To: Julien Grall
Cc: Brian Woods, nd, Volodymyr Babchuk, Stefano Stabellini, xen-devel
On Thu, Oct 03, 2019 at 10:20:36PM +0100, Julien Grall wrote:
> Hi Brian,
>
> On 10/3/19 9:24 PM, Brian Woods wrote:
> >On Thu, Oct 03, 2019 at 07:23:23PM +0000, Julien Grall wrote:
> >There's a WARN_ON() between the two debug printks calls I shared above.
>
> Looking at the log, the MFN seems to correspond to the one right after Xen
> (0000000001400000 - 00000000015328f1) in memory.
>
> So it is normal to have the page given to the boot allocator. However, I am
> not entirely sure which bit of init_done() is giving the page again to
> xenheap.
>
> It is unlikely to be free_init_memory() because it deal with the init
> section that is not at the end of the binary.
>
> This would leave discard_initial_modules() but there are a check to skip Xen
> module.
>
> The call stack only print the address and not the symbol because it
> unregistered the symbols for init. See unregister_init_virtual_memory().
>
> (XEN) Xen call trace:
> (XEN) [<000000000021c1a8>] page_alloc.c#free_heap_pages+0x1a8/0x614 (PC)
> (XEN) [<000000000021c1a8>] page_alloc.c#free_heap_pages+0x1a8/0x614 (LR)
> (XEN) [<000000000021e900>] page_alloc.c#init_heap_pages+0x3d4/0x564
> (XEN) [<000000000021eb24>] init_domheap_pages+0x94/0x9c
> (XEN) [<00000000002b83ec>] 00000000002b83ec
> (XEN) [<00000000002b8904>] 00000000002b8904
> (XEN) [<0000000000260a3c>] setup.c#init_done+0x10/0x20
> (XEN) [<00000000002b99ac>] 00000000002b99ac
>
> You should be able to use addr2line on the address with Xen binary.
> I have the feeling this will point to discard_initial_modules() as this is
> an init function and the symbol should not be printed.
>
> But, I can't see anything obviously wrong in the function... So I am not
> entirely sure what could be the next steps.
>
> Cheers,
>
> --
> Julien Grall
In the log, there's:
(XEN) MODULE[0]: 0000000001400000 - 00000000015328f1 Xen
(XEN) MODULE[1]: 00000000076d2000 - 00000000076dc080 Device Tree
(XEN) MODULE[2]: 00000000076df000 - 0000000007fff364 Ramdisk
(XEN) MODULE[3]: 0000000000080000 - 0000000003180000 Kernel
(XEN) RESVD[0]: 00000000076d2000 - 00000000076dc000
(XEN) RESVD[1]: 00000000076df000 - 0000000007fff364
Linux kernel -> 8_0000 - 318_0000
Xen -> 140_0000 - 153_28f1
There's something not quite right here... I'm guessing Xen was working
at the address before because it was out of the "range" of the Linux
kernel. Now I guess I need to look into if it's a Xen or u-boot issue.
--
Brian Woods
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-04 0:25 ` Brian Woods
@ 2019-10-04 9:49 ` Julien Grall
2019-10-04 15:36 ` Brian Woods
0 siblings, 1 reply; 14+ messages in thread
From: Julien Grall @ 2019-10-04 9:49 UTC (permalink / raw)
To: Brian Woods; +Cc: xen-devel, nd, Volodymyr Babchuk, Stefano Stabellini
Hi Brian,
On 04/10/2019 01:25, Brian Woods wrote:
> On Thu, Oct 03, 2019 at 10:20:36PM +0100, Julien Grall wrote:
>> Hi Brian,
>>
>> On 10/3/19 9:24 PM, Brian Woods wrote:
>>> On Thu, Oct 03, 2019 at 07:23:23PM +0000, Julien Grall wrote:
>>> There's a WARN_ON() between the two debug printks calls I shared above.
>>
>> Looking at the log, the MFN seems to correspond to the one right after Xen
>> (0000000001400000 - 00000000015328f1) in memory.
>>
>> So it is normal to have the page given to the boot allocator. However, I am
>> not entirely sure which bit of init_done() is giving the page again to
>> xenheap.
>>
>> It is unlikely to be free_init_memory() because it deal with the init
>> section that is not at the end of the binary.
>>
>> This would leave discard_initial_modules() but there are a check to skip Xen
>> module.
>>
>> The call stack only print the address and not the symbol because it
>> unregistered the symbols for init. See unregister_init_virtual_memory().
>>
>> (XEN) Xen call trace:
>> (XEN) [<000000000021c1a8>] page_alloc.c#free_heap_pages+0x1a8/0x614 (PC)
>> (XEN) [<000000000021c1a8>] page_alloc.c#free_heap_pages+0x1a8/0x614 (LR)
>> (XEN) [<000000000021e900>] page_alloc.c#init_heap_pages+0x3d4/0x564
>> (XEN) [<000000000021eb24>] init_domheap_pages+0x94/0x9c
>> (XEN) [<00000000002b83ec>] 00000000002b83ec
>> (XEN) [<00000000002b8904>] 00000000002b8904
>> (XEN) [<0000000000260a3c>] setup.c#init_done+0x10/0x20
>> (XEN) [<00000000002b99ac>] 00000000002b99ac
>>
>> You should be able to use addr2line on the address with Xen binary.
>> I have the feeling this will point to discard_initial_modules() as this is
>> an init function and the symbol should not be printed.
>>
>> But, I can't see anything obviously wrong in the function... So I am not
>> entirely sure what could be the next steps.
>>
>> Cheers,
>>
>> --
>> Julien Grall
>
> In the log, there's:
> (XEN) MODULE[0]: 0000000001400000 - 00000000015328f1 Xen
> (XEN) MODULE[1]: 00000000076d2000 - 00000000076dc080 Device Tree
> (XEN) MODULE[2]: 00000000076df000 - 0000000007fff364 Ramdisk
> (XEN) MODULE[3]: 0000000000080000 - 0000000003180000 Kernel
> (XEN) RESVD[0]: 00000000076d2000 - 00000000076dc000
> (XEN) RESVD[1]: 00000000076df000 - 0000000007fff364
>
> Linux kernel -> 8_0000 - 318_0000
> Xen -> 140_0000 - 153_28f1
>
> There's something not quite right here... I'm guessing Xen was working
> at the address before because it was out of the "range" of the Linux
> kernel. Now I guess I need to look into if it's a Xen or u-boot issue.
The loading address you wrote match the ones you seem to have requested in U-boot:
Filename 'yocto-Image'.
Load address: 0x80000
Filename 'xen-custom.ub'.
Load address: 0x1400000
But the size does not match the one you provided in the Device-Tree:
Bytes transferred = 18215424 (115f200 hex)
vs
0x0000000003180000 - 0x0000000000080000 = 0x3100000
This is always a risk when you write in advance the size of the binaries and
location in the Device-Tree. If you are using tftp/load from FS, it is much less
risky to provide a U-boot script that will generate the Xen DT node.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Xen-devel] Errors with Loading Xen at a Certain Address
2019-10-04 9:49 ` Julien Grall
@ 2019-10-04 15:36 ` Brian Woods
0 siblings, 0 replies; 14+ messages in thread
From: Brian Woods @ 2019-10-04 15:36 UTC (permalink / raw)
To: Julien Grall
Cc: Brian Woods, nd, Volodymyr Babchuk, Stefano Stabellini, xen-devel
On Fri, Oct 04, 2019 at 10:49:28AM +0100, Julien Grall wrote:
> Hi Brian,
>
> On 04/10/2019 01:25, Brian Woods wrote:
> >
> >In the log, there's:
> >(XEN) MODULE[0]: 0000000001400000 - 00000000015328f1 Xen
> >(XEN) MODULE[1]: 00000000076d2000 - 00000000076dc080 Device Tree
> >(XEN) MODULE[2]: 00000000076df000 - 0000000007fff364 Ramdisk
> >(XEN) MODULE[3]: 0000000000080000 - 0000000003180000 Kernel
> >(XEN) RESVD[0]: 00000000076d2000 - 00000000076dc000
> >(XEN) RESVD[1]: 00000000076df000 - 0000000007fff364
> >
> >Linux kernel -> 8_0000 - 318_0000
> >Xen -> 140_0000 - 153_28f1
> >
> >There's something not quite right here... I'm guessing Xen was working
> >at the address before because it was out of the "range" of the Linux
> >kernel. Now I guess I need to look into if it's a Xen or u-boot issue.
>
> The loading address you wrote match the ones you seem to have requested in U-boot:
>
> Filename 'yocto-Image'.
> Load address: 0x80000
>
> Filename 'xen-custom.ub'.
> Load address: 0x1400000
>
> But the size does not match the one you provided in the Device-Tree:
>
> Bytes transferred = 18215424 (115f200 hex)
>
> vs
>
> 0x0000000003180000 - 0x0000000000080000 = 0x3100000
>
> This is always a risk when you write in advance the size of the binaries and
> location in the Device-Tree. If you are using tftp/load from FS, it is much
> less risky to provide a U-boot script that will generate the Xen DT node.
>
> Cheers,
>
> --
> Julien Grall
Yeah. When I went in and changed the end address in the device tree and
it all worked. I'm guessing Xen could use some warnings and some other
things to alert the user that the device tree may need tweaking or at
the very least some checks. It seems that the blame wasn't primarily on
Xen, although it didn't do anyone any favors.
--
Brian Woods
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2019-10-04 15:37 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-02 0:32 [Xen-devel] Errors with Loading Xen at a Certain Address Brian Woods
[not found] ` <48c9fc54-553e-3b6b-bad2-dbad35991df0@arm.com>
2019-10-02 16:52 ` Julien Grall
2019-10-02 18:56 ` Brian Woods
2019-10-02 19:59 ` Julien Grall
2019-10-02 21:22 ` Brian Woods
2019-10-02 23:20 ` Brian Woods
2019-10-03 17:08 ` Julien Grall
2019-10-03 18:15 ` Brian Woods
2019-10-03 19:23 ` Julien Grall
2019-10-03 20:24 ` Brian Woods
2019-10-03 21:20 ` Julien Grall
2019-10-04 0:25 ` Brian Woods
2019-10-04 9:49 ` Julien Grall
2019-10-04 15:36 ` Brian Woods
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.