Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 324 subscribers
  • Views 1720 views
  • Users 0 members are here
Related

Kernel Panic

dat63

Hello,

I built the petalinux image files from your bsp uz7ev_evcc_2020_1.bsp without modifying any configuration. I built it with the command:

petalinux-build -c avnet-image-full

During the boot of my UltraZed-EV SOM at a certain point I get the  kernel panic reported in the following:

......................................

   12.808660] b318        15558144 mmcblk1
[   12.808661]  driver: mmcblk
[   12.815452]   b319        15554048 mmcblk1p1 5f175d8d-01
[   12.815454]
[   12.822235] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,26)
[   12.830751] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-xilinx-v2020.1 #1
[   12.837873] Hardware name: xlnx,zynqmp (DT)
[   12.842040] Call trace:
[   12.844476]  dump_backtrace+0x0/0x140
[   12.848126]  show_stack+0x14/0x20
[   12.851427]  dump_stack+0xac/0xd0
[   12.854733]  panic+0x140/0x2f8
[   12.857771]  mount_block_root+0x1d0/0x284
[   12.861762]  mount_root+0x124/0x158
[   12.865235]  prepare_namespace+0x15c/0x1a4
[   12.869314]  kernel_init_freeable+0x234/0x258
[   12.873655]  kernel_init+0x10/0xfc
[   12.877041]  ret_from_fork+0x10/0x18
[   12.880600] SMP: stopping secondary CPUs
[   12.884513] Kernel Offset: disabled
[   12.887985] CPU features: 0x0002,20002004
[   12.891976] Memory Limit: none
[   12.895019] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,26) ]---

Do you know what is wrong here?

Thank you

Daniele

  • 0

    Hello Daniele,

    Looks like Linux can't mount the rootfs, it could be a problem with the BSP or the sd card.

    Before we try to reproduce the issue, please provide additional info:

    • What boot method are you trying to achieve? (boot methods are described here https://github.com/Avnet/petalinux/blob/2020.1/documentation/uz/how_to_boot.txt) 
    • Did you try another boot method?
    • What was written on the sd card and how? Possibly the sd card is malfunctioning, could be worth to try a different one
    • You are using the 2020.1 BSP. Which version of Xilinx Vivado, Vitis, and PetaLinux are you using?

    Bryan

  • 0 in reply to bhfletcher

    Regarding the "What was written on the sd card and how?" question, I'll share some recent observations while testing an Ultra96-V2 board (and may apply to other boards)...

    The WIC image (full SD card image) generated from the initial build using Avnet's scripts for generating hardware description files (XSAs) and BSPs will construct a bootable image when the WIC from the BSP is written to an SD card (I used Rufus 3.18).

    However, when I created a new project from the generated BSP and ran "petalinux-build -c avnet-image-full" the WIC in the output files (*.wic) booted to the kernel panic you saw above.  If the SD image was prepared with the partitions (either manually or from the previous WIC) and then the individual partitions updated according to the instructions (i.e., add boot.bin, et al., to the boot partition; unpack the rootfs tar onto the rootfs partition), then the image was bootable and with the latest build data.

    TLDR: I observed issues with the WIC images produced by petalinux-build -c avnet-image-full; if you are using the WIC to write your SD Card, try the more manual method with individual file outputs written/unpacked to partitions and try again.

    Regards, Matt

  • 0 in reply to mtkeener

    Hello,

    I followed both your suggestions; I changed the SD card and I manually created the partitions and now the boot runs smoothly.

    Thank you very much

    Regards

    Daniele