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: 
Participant pgielmuda
Participant
1,006 Views
Registered: ‎10-18-2017

Linux boot hangs at: raid6: using intx1 recovery algorithm

Hi,

I working on Ultrazed-EG board from Avnet. I'm using their BSP for Petalinux 2017.2.Building images of linux is successful. 

I downloading generated image files with jtag_boot.tcl script from this page. After downloading all files successfully I try to run: 
booti 0x80000 - 0x4000000

command from uboot console. The booting logs are such

[Xilinx Zynq MP First Stage Boot Loader
Release 2017.2   Apr 24 2018  -  09:23:02
NOTICE:  ATF running on XCZU3EG/silicon v4/RTL5.1 at 0xfffea000, with PMU firmware
NOTICE:  BL31: Secure code at 0x60000000
NOTICE:  BL31: Non secure code at 0x8000000
NOTICE:  BL31: v1.3(release):0d9d51a
NOTICE:  BL31: Built : 15:25:08, Apr 27 2018


U-Boot 2017.01 (Apr 27 2018 - 17:22:49 +0200) Xilinx ZynqMP ZCU102 revB

I2C:   Error, wrong i2c adapter 0 max 0 possible
Error, wrong i2c adapter 0 max 0 possible
ready
DRAM:  2 GiB
EL Level:       EL2
Chip ID:        xczu3eg
MMC:   sdhci@ff160000: 0 (eMMC), sdhci@ff170000: 1 (SD)
SF: Detected n25q256a with page size 512 Bytes, erase size 128 KiB, total 64 MiB
*** Warning - bad CRC, using default environment

Error, wrong i2c adapter 0 max 0 possible
Error, wrong i2c adapter 0 max 0 possible
In:    serial
Out:   serial
Err:   serial
Bootmode: JTAG_MODE
Net:   ZYNQ GEM: ff0e0000, phyaddr 9, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for uz3eg-iocc-2017-2

ethernet@ff0e0000 Waiting for PHY auto negotiation to complete......................................... TIMEOUT !
Hit any key to stop autoboot:  0
ZynqMP> booti 0x80000 - 0x4000000
## Flattened Device Tree blob at 04000000
   Booting using the fdt blob at 0x4000000
   Loading Device Tree to 0000000007ff4000, end 0000000007fff41f ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.0-xilinx-v2017.2 (pgielmuda@212698321VB) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #10 SMP Fri Apr 27 17:27:34 CEST 2018
[    0.000000] Boot CPU: AArch64 Processor [410fd034]
[    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 128 MiB at 0x0000000078000000
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.0 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 @ffffffc077f74000 s48152 r8192 d29672 u86016
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: enabling workaround for ARM erratum 845719
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 513024
[    0.000000] Kernel command line: earlycon console=ttyPS0,115200
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] Memory: 1890296K/2080768K available (9020K kernel code, 574K rwdata, 2816K rodata, 14144K init, 394K bss, 59400K reserved, 131072K 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 - 0xffffff8008950000   (  9024 KB)
[    0.000000]     .rodata : 0xffffff8008950000 - 0xffffff8008c20000   (  2880 KB)
[    0.000000]       .init : 0xffffff8008c20000 - 0xffffff80099f0000   ( 14144 KB)
[    0.000000]       .data : 0xffffff80099f0000 - 0xffffff8009a7fa00   (   575 KB)
[    0.000000]        .bss : 0xffffff8009a7fa00 - 0xffffff8009ae252c   (   395 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 - 0xffffffbf01c00000   (    28 MB actual)
[    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc080000000   (  2048 MB)
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 64.
[    0.000000]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[    0.000000] NR_IRQS:64 nr_irqs:64 0
[    0.000000] GIC: Adjusting CPU interface base to 0x00000000f902f000
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 99.99MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x171015c90f, max_idle_ns: 440795203080 ns
[    0.000003] sched_clock: 56 bits at 99MHz, resolution 10ns, wraps every 4398046511101ns
[    0.008267] Console: colour dummy device 80x25
[    0.012538] Calibrating delay loop (skipped), value calculated using timer frequency.. 199.99 BogoMIPS (lpj=399996)
[    0.022896] pid_max: default: 32768 minimum: 301
[    0.027592] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
[    0.034148] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
[    0.041895] ASID allocator initialised with 65536 entries
[    0.047660] zynqmp_plat_init Power management API v0.3
[    0.052685] EFI services will not be available.
[    0.057472] Detected VIPT I-cache on CPU1
[    0.057501] CPU1: Booted secondary processor [410fd034]
[    0.057787] Detected VIPT I-cache on CPU2
[    0.057806] CPU2: Booted secondary processor [410fd034]
[    0.058080] Detected VIPT I-cache on CPU3
[    0.058099] CPU3: Booted secondary processor [410fd034]
[    0.058137] Brought up 4 CPUs
[    0.088420] SMP: Total of 4 processors activated.
[    0.093097] CPU features: detected feature: 32-bit EL0 Support
[    0.098893] CPU: All CPU(s) started at EL2
[    0.102966] alternatives: patching kernel code
[    0.107875] devtmpfs: initialized
[    0.115706] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.128196] xor: measuring software checksum speed
[    0.172876]    8regs     :  2111.000 MB/sec
[    0.212906]    8regs_prefetch:  1882.000 MB/sec
[    0.257275]    32regs    :  2594.000 MB/sec
[    0.297307]    32regs_prefetch:  2181.000 MB/sec
[    0.301735] xor: using function: 32regs (2594.000 MB/sec)
[    0.307190] pinctrl core: initialized pinctrl subsystem
[    0.312928] NET: Registered protocol family 16
[    0.335595] cpuidle: using governor menu
[    0.339547] Failed to initialise IOMMU /amba/smmu@fd800000
[    0.344985] vdso: 2 pages (1 code @ ffffff8008957000, 1 data @ ffffff80099f4000)
[    0.352199] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.359541] DMA: preallocated 256 KiB pool for atomic allocations
[    0.376147] reset_zynqmp reset-controller: Xilinx zynqmp reset driver probed
[    0.383414] ARM CCI_400_r1 PMU driver probed[    0.390771] zynqmp-pinctrl ff180000.pinctrl: zynqmp pinctrl initialized
[    0.425454] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.496567] raid6: int64x1  gen()   374 MB/s
[    0.568548] raid6: int64x1  xor()   408 MB/s
[    0.640615] raid6: int64x2  gen()   621 MB/s
[    0.712640] raid6: int64x2  xor()   552 MB/s
[    0.784744] raid6: int64x4  gen()   906 MB/s
[    0.856782] raid6: int64x4  xor()   680 MB/s
[    0.928812] raid6: int64x8  gen()  1053 MB/s
[    1.000855] raid6: int64x8  xor()   685 MB/s
[    1.072944] raid6: neonx1   gen()   666 MB/s
[    1.144989] raid6: neonx1   xor()   699 MB/s
[    1.217011] raid6: neonx2   gen()  1075 MB/s
[    1.289073] raid6: neonx2   xor()   952 MB/s
[    1.361113] raid6: neonx4   gen()  1386 MB/s
[    1.433179] raid6: neonx4   xor()  1085 MB/s
[    1.505223] raid6: neonx8   gen()  1457 MB/s
[    1.577268] raid6: neonx8   xor()  1120 MB/s
[    1.581351] raid6: using algorithm neonx8 gen() 1457 MB/s
[    1.586713] raid6: .... xor() 1120 MB/s, rmw enabled
[    1.591643] raid6: using intx1 recovery algorithm
[

After that booting process hangs. 

I already google it sever times. I found this topic and I tried to modified my fpga configuration. I also tried project based on not modified bsp. I'm starting to thinking that I do something wrong in booting/downloading process. However I'm not an expert in linux and I do not know the possible reason of such problem. 

Do you know what could be a reason of that? Any idea how to fix that? 

0 Kudos
5 Replies
Participant pgielmuda
Participant
970 Views
Registered: ‎10-18-2017

Re: Linux boot hangs at: raid6: using intx1 recovery algorithm

One update:

If make few compilation and one of them work (at least do not hangs on above problem). If I copy system.dtb from this compilation of linux than in others this stage of booting pass without hanging.

 

However this is not the solution to my problem. I do not understand the reason of hanging on:

 

[    1.591643] raid6: using intx1 recovery algorithm

and even If I recompile "working" project with new configs (which I need) then the problem returns. I need to clear this up to go further. Any clues will be helpful. 

 

 

I noticed this issue  but I doubt that this is the same issue since it corresponds to SD boot. But I might be wrong. 

0 Kudos
823 Views
Registered: ‎06-13-2018

Re: Linux boot hangs at: raid6: using intx1 recovery algorithm

Hi,

Were you ever able to determine the cause of your issues, or their solution?

0 Kudos
Moderator
Moderator
815 Views
Registered: ‎04-24-2017

Re: Linux boot hangs at: raid6: using intx1 recovery algorithm

Hi @pgielmuda,

 

  1. Enable CPU IDLE off when booting linux connected with JTAG https://www.xilinx.com/support/answers/69143.html
  2. When you use booti command this means you should be using Image ( kernel + rootfs ) + dtb images generated from petalinux. Then from u-boot you can run booti ${kernel_Image_address} -${dtb_address}
  3. Which images are you using?

 

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------
0 Kudos
Observer mrm
Observer
540 Views
Registered: ‎05-09-2018

Re: Linux boot hangs at: raid6: using intx1 recovery algorithm

Hi,

 

It hangs at this point, if PL GPIOS are used in device tree and its corresponding PL bitstream file is not loaded. You were able to boot it fully using some other dtb file, because that dtb was not using PL.

 

Thank you

Regards

Mariam

0 Kudos
Observer lakshmi.aiyer
Observer
262 Views
Registered: ‎05-13-2018

Re: Linux boot hangs at: raid6: using intx1 recovery algorithm

I am having similar issue where the petalinux boot hangs after raid6: using itx1 recovery algorithm when i ported from 2018.2 to 2018.3(both FPGA & kernel). Appreciate if you can share the details on how/whether you resolved it. Thanks!

0 Kudos