UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
853 Views
Registered: ‎06-04-2018

Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

Hi forum,

I am not able to boot a NON-prebuilt image.ub, using a custom made HDF. My Vivado project is basically the same steps as in UG1209 Tutorial, besides additional AXI slaves. The same project worked on 2017.4. Here is the log, I hope someone can maybe point to a specific place to debug:

Xilinx Zynq MP First Stage Boot Loader
Release 2018.3 Feb 7 2019 - 13:36:19
RPU waiting 0
NOTICE: ATF running on XCZU9EG/silicon v4/RTL5.1 at 0xfffea000
NOTICE: BL31: Secure code at 0x0
NOTICE: BL31: Non secure code at 0x10080000
NOTICE: BL31: v1.5(release):xilinx-v2018.2-919-g08560c36
NOTICE: BL31: Built : 13:36:41, Feb 7 2019
PMUFW: v1.1


U-Boot 2018.01 (Feb 07 2019 - 13:33:58 +0000) Xilinx ZynqMP ZCU102 rev1.0

I2C: ready
DRAM: 4 GiB
EL Level: EL2
Chip ID: zu9eg
MMC: mmc@ff170000: 0 (SD)
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: LVL_SHFT_SD_MODE1
Net: ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id

Warning: ethernet@ff0e0000 MAC addresses don't match:
Address in ROM is 00:0a:35:04:ba:c1
Address in environment is 00:0a:35:00:22:01
eth0: ethernet@ff0e0000
U-BOOT for xilinx-zcu102-2018_3

ethernet@ff0e0000 Waiting for PHY auto negotiation to complete.RPU waiting 0
....RPU waiting 0
.. done
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.0.34 (257 ms)
Hit any key to stop autoboot: 4 RPU waiting 0
2 RPU waiting 0
0
Device: mmc@ff170000
Manufacturer ID: 3
OEM: 5344
Name: SB16G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 14.8 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
reading image.ub
RPU waiting 0
13581808 bytes read in 886 ms (14.6 MiB/s)
## Loading kernel from FIT Image at 10000000 ...
Using 'conf@system-top.dtb' configuration
Trying 'kernel@1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x10000108
Data Size: 7083879 Bytes = 6.8 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x00080000
Entry Point: 0x00080000
Hash algo: sha1
Hash value: 5aac9c0e617666a346d54ebbd8bd8a5ba42b5a43
Verifying Hash Integrity ... sha1+ OK
## Loading ramdisk from FIT Image at 10000000 ...
Using 'conf@system-top.dtb' configuration
Trying 'ramdisk@1' ramdisk subimage
Description: petalinux-user-image
Type: RAMDisk Image
Compression: gzip compressed
Data Start: 0x106cd2f4
Data Size: 6448491 Bytes = 6.1 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: 81898c2e82db54fb12f9fc76ff93dd1a77bfb3e0
Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 10000000 ...
Using 'conf@system-top.dtb' configuration
Trying 'fdt@system-top.dtb' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x106c1974
Data Size: 47290 Bytes = 46.2 KiB
Architecture: AArch64
Hash algo: sha1
Hash value: 6b8590328f664dfef2b809091bde10bf05a34256
Verifying Hash Integrity ... sha1+ OK
Booting using the fdt blob at 0x106c1974
Uncompressing Kernel Image ... OK
Loading Ramdisk to 079d9000, end 07fff56b ... OK
Loading Device Tree to 00000000079ca000, end 00000000079d88b9 ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.14.0-xilinx-v2018.3 (oe-user@oe-host) (gcc version 7.3.0 (GCC)) #1 SMP Thu
Feb 7 13:23:01 UTC 2019
[ 0.000000] Boot CPU: AArch64 Processor [410fd034]
[ 0.000000] Machine model: ZynqMP ZCU102 Rev1.0
[ 0.000000] earlycon: cdns0 at MMIO 0x00000000ff000000 (options '115200n8')
[ 0.000000] bootconsole [cdns0] enabled
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] cma: Reserved 256 MiB at 0x000000006fc00000
[ 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: MIGRATE_INFO_TYPE not supported.
[ 0.000000] percpu: Embedded 21 pages/cpu @ffffffc87ff5d000 s46488 r8192 d31336 u86016
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: enabling workaround for ARM erratum 845719
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1033987
[ 0.000000] Kernel command line: earlycon console=ttyPS0,115200 clk_ignore_unused
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.000000] software IO TLB [mem 0x6bc00000-0x6fc00000] (64MB) mapped at [ffffffc06bc00000-ffffffc06fb
fffff]
[ 0.000000] Memory: 3777920K/4193280K available (10108K kernel code, 664K rwdata, 3224K rodata, 512K i
nit, 2167K bss, 153216K reserved, 262144K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] modules : 0xffffff8000000000 - 0xffffff8008000000 ( 128 MB)
[ 0.000000] vmalloc : 0xffffff8008000000 - 0xffffffbebfff0000 ( 250 GB)
[ 0.000000] .text : 0xffffff8008080000 - 0xffffff8008a60000 ( 10112 KB)
[ 0.000000] .rodata : 0xffffff8008a60000 - 0xffffff8008d90000 ( 3264 KB)
[ 0.000000] .init : 0xffffff8008d90000 - 0xffffff8008e10000 ( 512 KB)
[ 0.000000] .data : 0xffffff8008e10000 - 0xffffff8008eb6200 ( 665 KB)
[ 0.000000] .bss : 0xffffff8008eb6200 - 0xffffff80090d40b0 ( 2168 KB)
[ 0.000000] fixed : 0xffffffbefe7fd000 - 0xffffffbefec00000 ( 4108 KB)
[ 0.000000] PCI I/O : 0xffffffbefee00000 - 0xffffffbeffe00000 ( 16 MB)
[ 0.000000] vmemmap : 0xffffffbf00000000 - 0xffffffc000000000 ( 4 GB maximum)
[ 0.000000] 0xffffffbf00000000 - 0xffffffbf1dc00000 ( 476 MB actual)
[ 0.000000] memory : 0xffffffc000000000 - 0xffffffc880000000 ( 34816 MB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU event tracing is enabled.
[ 0.000000] 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] GIC: Adjusting CPU interface base to 0x00000000f902f000
[ 0.000000] GIC: Using split EOI/Deactivate mode
[ 0.000000] arch_timer: cp15 timer(s) running at 99.99MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x170f8de2d3, max_idle_n
s: 440795206112 ns
[ 0.000003] sched_clock: 56 bits at 99MHz, resolution 10ns, wraps every 4398046511101ns
[ 0.008343] Console: colour dummy device 80x25
[ 0.012389] Calibrating delay loop (skipped), value calculated using timer frequency.. 199.98 BogoMIPS
(lpj=399960)
[ 0.022757] pid_max: default: 32768 minimum: 301
[ 0.027438] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.034012] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.041678] ASID allocator initialised with 65536 entries
[ 0.046510] Hierarchical SRCU implementation.
[ 0.051140] EFI services will not be available.
[ 0.055303] zynqmp_plat_init Platform Management API v1.1
[ 0.060649] zynqmp_plat_init Trustzone version v1.0
[ 0.065586] smp: Bringing up secondary CPUs ...
[ 0.070231] Detected VIPT I-cache on CPU1
[ 0.070261] CPU1: Booted secondary processor [410fd034]
[ 0.070528] Detected VIPT I-cache on CPU2
[ 0.070546] CPU2: Booted secondary processor [410fd034]
[ 0.070801] Detected VIPT I-cache on CPU3
[ 0.070819] CPU3: Booted secondary processor [410fd034]
[ 0.070860] smp: Brought up 1 node, 4 CPUs
[ 0.101565] SMP: Total of 4 processors activated.
[ 0.106239] CPU features: detected feature: 32-bit EL0 Support
[ 0.112037] CPU: All CPU(s) started at EL2
[ 0.116109] alternatives: patching kernel code
[ 0.121211] devtmpfs: initialized
[ 0.128615] random: get_random_u32 called from bucket_table_alloc+0x108/0x260 with crng_init=0
[ 0.132523] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417851000
00 ns
[ 0.142063] futex hash table entries: 1024 (order: 5, 131072 bytes)
[ 0.153660] xor: measuring software checksum speed
[ 0.192349] 8regs : 2302.000 MB/sec
[ 0.232377] 8regs_prefetch: 2052.000 MB/sec
[ 0.272409] 32regs : 2830.000 MB/sec
[ 0.312439] 32regs_prefetch: 2381.000 MB/sec
[ 0.312468] xor: using funitio0
32regs (2830.000 MB/sec)
[ 0.316840] pinctrl core: initialized pinctrl subsystem
[ 0.316959] random: fast init done
[ 0.325808] NET: Registered protocol family 16
[ 0.330349] cpuidle: using governor menu
[ 0.334212] vdso: 2 pages (1 code @ ffffff8008a66000, 1 data @ ffffff8008e14000)
[ 0.341010] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.348201] DMA: preallocated 256 KiB pool for atomic allocations
[ 0.375076] reset_zynqmp reset-controller: Xilinx zynqmp reset driver probed
[ 0.377076] ARM CCI_400_r1 PMU driver probed
[ 0.382019] zynqmp-pinctrl ff180000.pinctrl: zynqmp pinctrl initialized
[ 0.395860] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.462136] raid6: int64x1 gen() 401 MB/s
[ 0.530175] raid6: int64x1 xor() 445 MB/s
[ 0.598277] raid6: int64x2 gen() 688 MB/s
[ 0.666305] raid6: int64x2 xor() 603 MB/s
[ 0.734346] raid6: int64x4 gen() 1042 MB/s
[ 0.802386] raid6: int64x4 xor() 742 MB/s
[ 0.870436] raid6: int64x8 gen() 980 MB/s
[ 0.938463] raid6: int64x8 xor() 745 MB/s
[ 1.006553] raid6: neonx1 gen() 727 MB/s
[ 1.074547] raid6: neonx1 xor() 852 MB/s
[ 1.142620] raid6: neonx2 gen() 1169 MB/s
[ 1.210655] raid6: neonx2 xor() 1207 MB/s
[ 1.278722] raid6: neonx4 gen() 1506 MB/s
[ 1.346751] raid6: neonx4 xor() 1441 MB/s
[ 1.414798] raid6: neonx8 gen() 1651 MB/s
[ 1.482838] raid6: neonx8 xor() 1532 MB/s
[ 1.482865] raid6: using algorithm neonx8 gen() 1651 MB/s
[ 1.486827] raid6: .... xor() 1532 MB/s, rmw enabled
[ 1.491759] raid6: using neon recovery algorithm
[ 1.497848] SCSI subsystem initialized
[ 1.500222] usbcore: registered new interface driver usbfs
[ 1.505545] usbcore: registered new interface driver hub
[ 1.510820] usbcore: registered new device driver usb
[ 1.515863] media: Linux media interface: v0.10
[ 1.520325] Linux video capture interface: v2.00
[ 1.524922] pps_core: LinuxPPS API ver. 1 registered
[ 1.529823] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 1.538916] PTP clock support registered
[ 1.542814] EDAC MC: Ver: 3.0.0
[ 1.546199] zynqmp-ipi ff9905c0.mailbox: Probed ZynqMP IPI Mailbox driver.
[ 1.552903] FPGA manager framework
[ 1.556220] fpga-region fpga-full: FPGA Region probed
[ 1.561275] Advanced Linux Sound Architecture Driver Initialized.
[ 1.567425] Bluetooth: Core ver 2.22
[ 1.570757] NET: Registered protocol family 31
[ 1.575155] Bluetooth: HCI device and connection manager initialized
[ 1.581471] Bluetooth: HCI socket layer initialized
[ 1.586314] Bluetooth: L2CAP socket layer initialized
[ 1.591341] Bluetooth: SCO socket layer initialized
[ 1.596666] clocksource: Switched to clocksource arch_sys_counter
[ 1.602302] VFS: Disk quotas dquot_6.6.0
[ 1.606169] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 1.616849] NET: Registered protocol family 2
[ 1.617555] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
[ 1.624669] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
[ 1.631412] TCP: Hash tables configured (established 32768 bind 32768)
[ 1.637591] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[ 1.643564] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[ 1.650038] NET: Registered protocol family 1
[ 1.654398] RPC: Registered named UNIX socket transport module.
[ 1.660110] RPC: Registered udp transport module.
[ 1.664777] RPC: Registered tcp transport module.
[ 1.669448] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.675952] Trying to unpack rootfs image as initramfs...
[ 1.933424] Freeing initrd memory: 6296K
[ 1.933815] hw perfevents: no interrupt-affinity property for /pmu, guessing.
[ 1.938955] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[ 1.947234] audit: initializing netlink subsys (disabled)
[ 1.951933] audit: type=2000 audit(1.891:1): state=initialized audit_enabled=0 res=1
[ 1.952242] workingset: timestamp_bits=62 max_order=20 bucket_order=0
[ 1.966599] NFS: Registering the id_resolver key type
[ 1.970999] Key type id_resolver registered
[ 1.975136] Key type id_legacy registered
[ 1.979120] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 1.985788] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 2.018198] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[ 2.019944] io scheduler noop registered
[ 2.023845] io scheduler deadline registered
[ 2.028092] io scheduler cfq registered (default)
[ 2.032751] io scheduler mq-deadline registered
[ 2.037248] io scheduler kyber registered
[ 2.041868] nwl-pcie fd0e0000.pcie: Link is DOWN
[ 2.045855] OF: PCI: host bridge /amba/pcie@fd0e0000 ranges:
[ 2.051451] OF: PCI: MEM 0xe0000000..0xefffffff -> 0xe0000000
[ 2.057326] OF: PCI: MEM 0x600000000..0x7ffffffff -> 0x600000000
[ 2.063589] nwl-pcie fd0e0000.pcie: PCI host bridge to bus 0000:00
[ 2.069609] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 2.075055] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 2.081888] pci_bus 0000:00: root bus resource [mem 0x600000000-0x7ffffffff pref]
[ 2.089573] pci 0000:00:00.0: PCI bridge to [bus 01-0c]
[ 2.095425] xilinx-dpdma fd4c0000.dma: Xilinx DPDMA engine is probed
[ 2.101206] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success
[ 2.107909] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success
[ 2.114825] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success
[ 2.121743] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success
[ 2.128673] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success
[ 2.135584] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success
[ 2.142504] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success
[ 2.149425] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success
[ 2.156399] xilinx-zynqmp-dma ffa80000.dma: ZynqMP DMA driver Probe success
[ 2.163270] xilinx-zynqmp-dma ffa90000.dma: ZynqMP DMA driver Probe success
[ 2.170184] xilinx-zynqmp-dma ffaa0000.dma: ZynqMP DMA driver Probe success
[ 2.177110] xilinx-zynqmp-dma ffab0000.dma: ZynqMP DMA driver Probe success
[ 2.184030] xilinx-zynqmp-dma ffac0000.dma: ZynqMP DMA driver Probe success
[ 2.190952] xilinx-zynqmp-dma ffad0000.dma: ZynqMP DMA driver Probe success
[ 2.197870] xilinx-zynqmp-dma ffae0000.dma: ZynqMP DMA driver Probe success
[ 2.204803] xilinx-zynqmp-dma ffaf0000.dma: ZynqMP DMA driver Probe success
[ 2.236183] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 2.238264] Unable to handle kernel NULL pointer dereference at virtual address 00000038
[ 2.244950] Mem abort info:
[ 2.247703] Exception class = DABT (current EL), IL = 32 bits
[ 2.253592] SET = 0, FnV = 0
[ 2.256612] EA = 0, S1PTW = 0
[ 2.259732] Data abort info:
[ 2.262585] ISV = 0, ISS = 0x00000005
[ 2.266393] CM = 0, WnR = 0
[ 2.269337] [0000000000000038] user address but active_mm is swapper
[ 2.275652] Internal error: Oops: 96000005 [#1] SMP
[ 2.280488] Modules linked in:
[ 2.283520] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.0-xilinx-v2018.3 #1
[ 2.290696] Hardware name: ZynqMP ZCU102 Rev1.0 (DT)
[ 2.295628] task: ffffffc87b848d00 task.stack: ffffff8008038000
[ 2.301517] PC is at uart_unregister_driver+0x10/0x70
[ 2.306530] LR is at ulite_probe+0x1d8/0x5d0
9468>] pstate: a0000045fffff800850a2a0>] lr : P<ffafff8g085
[ 2.318119] sp : ffffff800803bbd0
[ 2.321407] x29: ffffff800803bbd0 x28: 00000000fffffffa
[ 2.326683] x27: 0000000000000001 x26: ffffff80090bb000
[ 2.331961] x25: ffffffc879f29498 x24: ffffffc87b175800
[ 2.337238] x23: ffffffc87aee6a98 x22: ffffff8008e4a000
[ 2.342515] x21: ffffffc87b175810 x20: 0000000000000000
[ 2.347792] x19: ffffffc87b174c80 x18: 0000000000000001
[ 2.353069] x17: 0000000000000001 x16: 0000000000000019
[ 2.358346] x15: ffffffffffffffff x14: ffffffc87aee6d9f
[ 2.363623] x13: ffffffc87aee6d9e x12: 0000000000000000
[ 2.368900] x11: 0000000000000005 x10: 0101010101010101
[ 2.374177] x9 : fffffffffffffffe x8 : 7f7f7f7f7f7f7f7f
[ 2.379454] x7 : fefefeff646c606d x6 : 070f1900f2f2f5f0
[ 2.384731] x5 : 7075727200190f07 x4 : ffffffc87b174c80
[ 2.390008] x3 : 0000000000000001 x2 : 0000000000000200
[ 2.395285] x1 : 0000000000000200 x0 : 0000000000000000
[ 2.400563] Process swapper/0 (pid: 1, stack limit = 0xffffff8008038000)
[ 2.407223] Call trace:
[ 2.409647] Exception stack(0xffffff800803ba90 to 0xffffff800803bbd0)
[ 2.416049] ba80: 0000000000000000 0000000000000200
[ 2.423835] baa0: 0000000000000200 0000000000000001 ffffffc87b174c80 7075727200190f07
[ 2.431621] bac0: 070f1900f2f2f5f0 fefefeff646c606d 7f7f7f7f7f7f7f7f fffffffffffffffe
[ 2.439407] bae0: 0101010101010101 0000000000000005 0000000000000000 ffffffc87aee6d9e
[ 2.447192] bb00: ffffffc87aee6d9f ffffffffffffffff 0000000000000019 0000000000000001
[ 2.454978] bb20: 0000000000000001 ffffffc87b174c80 0000000000000000 ffffffc87b175810
[ 2.462764] bb40: ffffff8008e4a000 ffffffc87aee6a98 ffffffc87b175800 ffffffc879f29498
[ 2.470550] bb60: ffffff80090bb000 0000000000000001 00000000fffffffa ffffff800803bbd0
[ 2.478336] bb80: ffffff8008519468 ffffff800803bbd0 ffffff800850a2a0 00000000a0000045
[ 2.486121] bba0: ffffffc87b175810 ffffffc879f80800 ffffffffffffffff 0cc000017aee6a98
[ 2.493906] bbc0: ffffff800803bbd0 ffffff800850a2a0
[ 2.498752] [<ffffff800850a2a0>] uart_unregister_driver+0x10/0x70
[ 2.504807] [<ffffff8008519468>] ulite_probe+0x1d8/0x5d0
[ 2.510085] [<ffffff8008586368>] platform_drv_probe+0x58/0xb8
[ 2.515795] [<ffffff800858474c>] driver_probe_device+0x22c/0x2d8
[ 2.521764] [<ffffff80085848b4>] __driver_attach+0xbc/0xc0
[ 2.527214] [<ffffff800858288c>] bus_for_each_dev+0x4c/0x98
[ 2.532750] [<ffffff8008584048>] driver_attach+0x20/0x28
[ 2.538027] [<ffffff8008583b98>] bus_add_driver+0x1b8/0x228
[ 2.543563] [<ffffff8008585260>] driver_register+0x60/0xf8
[ 2.549013] [<ffffff80085862b8>] __platform_driver_register+0x40/0x48
[ 2.555416] [<ffffff8008db383c>] ulite_init+0x18/0x20
[ 2.560434] [<ffffff8008083980>] do_one_initcall+0x38/0x128
[ 2.565969] [<ffffff8008d90cc4>] kernel_init_freeable+0x138/0x1d8
[ 2.572024] [<ffffff8008a51b48>] kernel_init+0x10/0x100
[ 2.577215] [<ffffff8008084a90>] ret_from_fork+0x10/0x18
[ 2.582493] Code: a9bd7bfd 910003fd a90153f3 aa0003f4 (f9401c13)
[ 2.588550] ---[ end trace 8561d9e7642b4c83 ]---
[ 2.593160] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 2.593160]
[ 2.602215] SMP: stopping secondary CPUs
[ 2.606109] Kernel Offset: disabled
[ 2.609568] CPU features: 0x002004
[ 2.612941] Memory Limit: none
[ 2.615971] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 2.615971]

 

 

I am able to boot using prebuilt images using JTAG or SD card.

 

Thanks for your help

0 Kudos
1 Solution

Accepted Solutions
707 Views
Registered: ‎06-04-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

Well, I'm closing this thread. I don't how it got solved or how it was created but I disconnected all axi master/slaves, reset block diagram Output, then it booted correctly. Then I added my AXI DMA master to the Zynq MPSoC slave port, performed reset generated output then tested again. It works, the image is fine. I added incrementelly the other slaves and it goes Ok, for the moment.

0 Kudos
11 Replies
Participant gosha-z
Participant
841 Views
Registered: ‎09-07-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

Looks like you haven't specified RAMDisk load and entry addresses in .its file:

Type: RAMDisk Image
Compression: gzip compressed
Data Start: 0x106cd2f4
Data Size: 6448491 Bytes = 6.1 MiB
Architecture: AArch64
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha1
Hash value: 81898c2e82db54fb12f9fc76ff93dd1a77bfb3e0
Verifying Hash Integrity ... sha1+ OK

Try to set it to 0x80000000 (second half of your memory space), rebuild FIT and load again

0 Kudos
812 Views
Registered: ‎06-04-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

Hi again gosha-z!

Indeed, in the rootfs.its, there isn't any "load" or "entry" address:

image.png

Which is very strange, I never had to bother with that before. Maybe it is linked with the following warning I have since 2018.3 update:

image.png

It looked suspicious at first but AR# 71110 does mention that it can be ignored

https://www.xilinx.com/support/answers/71110.html.

Such file "rootfs.its" doesn't even exist in the prebuilt folder, so I can't compare if all this is normal.

 

I will double check on my 2017.4 setup if rootfs.its was correctly generated and modify my rootfs in 2018.3 accordingly and post the results.

 

 

 

 

0 Kudos
805 Views
Registered: ‎06-04-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

Update: I compared the "rootfs.its" and still, no load and entry address is defined, and it is booting fine. Since the pre-built "BOOT.bin" and "image.ub" from the pre-built folder are working, I tried them and compared the boot logs.

 

First, both logs have the "Load Address" and "Entry Address" set as unavailable. 

image.png

So, I inspected further and the logs are different starting at a specific point which is related to cache check:

image.png

So at this point, I tried following UG1209 steps and generated the petalinux image. It boots fine, so it is either linked to my PL logic somehow since UG1209 doesn't use any bitstream or the HDF. I tried an SD boot with my custom design files but W/O loading the bitstream and it still doesn't work. So it seems to be related to my HDF file somehow... I'll investigate further

 

0 Kudos
769 Views
Registered: ‎06-04-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

New update:

If I remove all AXI connections (slaves and master), I don't have the kernel panic anymore, so definitly linked to my .hdf file. If I add a simple slave, compile the hdf then configure my petalinux project with it, the generated kernel crashes. 

 

Any ideas?

0 Kudos
Participant gosha-z
Participant
764 Views
Registered: ‎09-07-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

can you show kernel bootargs?

0 Kudos
761 Views
Registered: ‎06-04-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

I am booting using SD card method, using BOOT.BIN and image.ub. I use the following commands

image.png

So, I am not sure how to find these boot arguments. I would gladly provide them to you but I al not sure where to find them.

0 Kudos
Participant gosha-z
Participant
759 Views
Registered: ‎09-07-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

Did you see your AXI DMA drivers in Device Tree?

0 Kudos
751 Views
Registered: ‎06-04-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

In pl.dtsi, I do have all my AXI slaves. In system-conf.dtsi, I have the &qspi and the &gem3 declarations. Should I look at other files?

0 Kudos
Participant gosha-z
Participant
749 Views
Registered: ‎09-07-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

decompile final .dtb and look into it

0 Kudos
Highlighted
735 Views
Registered: ‎06-04-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

I performed the following command;

fdtdump system.dtb

In my images/ folder and I do see all my slaves devices, at the correct addresses. 

0 Kudos
708 Views
Registered: ‎06-04-2018

Re: Kernel panic using fresh image.ub on generated with Petalinux 2018.3 ZCU102

Jump to solution

Well, I'm closing this thread. I don't how it got solved or how it was created but I disconnected all axi master/slaves, reset block diagram Output, then it booted correctly. Then I added my AXI DMA master to the Zynq MPSoC slave port, performed reset generated output then tested again. It works, the image is fine. I added incrementelly the other slaves and it goes Ok, for the moment.

0 Kudos