cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
garbisingla
Contributor
Contributor
1,605 Views
Registered: ‎02-24-2016

Kernel panic with pre-built images - petalinux 2017.2 & ZC706

Jump to solution

HI all,

 

Simple, I get a kernel panic when booting with the pre-built images from the ZC706 BSP (xilinx-zc706-v2017.2-final.bsp). I have quite some experience with previous versions of petalinux but now I'm trying 2017.2.

 

I followed UG1144, pg 31., so I copy boot.bin and image.ub (and also system.dtb, BTW...). Boot, and kernel panic...

 

This just should work, isn't it? I am using the provided SD card that I used million times to boot. The SD has two partitions, 'boot' in FAT32 with 1GB, and 'rootfs' with the rest.

 

Please, can you support me here? 

I need to evaluate the new petalinux and try some AMP designs asap...

 

Thanks,
Garbí

 

VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
0100           16384 ram0  (driver?)
mmc0: new high speed SDHC card at address aaaa
mmcblk0: mmc0:aaaa SU08G 7.40 GiB 
0101           16384 ram1  (driver?)
0102           16384 ram2  (driver?)
0103           16384 ram3  (driver?)
0104           16384 ram4  (driver?)
0105           16384 ram5  mmcblk0: p1 p2
 (driver?)
0106           16384 ram6  (driver?)
0107           16384 ram7  (driver?)
0108           16384 ram8  (driver?)
0109           16384 ram9  (driver?)
010a           16384 ram10  (driver?)
010b           16384 ram11  (driver?)
010c           16384 ram12  (driver?)
010d           16384 ram13  (driver?)
010e           16384 ram14  (driver?)
010f           16384 ram15  (driver?)
1f00            4096 mtdblock0  (driver?)
1f01           14336 mtdblock1  (driver?)
1f02             128 mtdblock2  (driver?)
1f03           10752 mtdblock3  (driver?)
1f04            7552 mtdblock4  (driver?)
b300         7761920 mmcblk0  driver: mmcblk
  b301         1048576 mmcblk0p1 9c63b350-01
  b302         6709248 mmcblk0p2 9c63b350-02
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
CPU1: stopping
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.9.0-xilinx-v2017.2 #1
Hardware name: Xilinx Zynq Platform
[<c010e244>] (unwind_backtrace) from [<c010a4a4>] (show_stack+0x10/0x14)
[<c010a4a4>] (show_stack) from [<c02dc2b0>] (dump_stack+0x80/0x9c)
[<c02dc2b0>] (dump_stack) from [<c010c9f8>] (ipi_cpu_stop+0x3c/0x70)
[<c010c9f8>] (ipi_cpu_stop) from [<c010d210>] (handle_IPI+0x64/0x84)
[<c010d210>] (handle_IPI) from [<c0101420>] (gic_handle_irq+0x78/0x94)
[<c0101420>] (gic_handle_irq) from [<c010ae8c>] (__irq_svc+0x6c/0xa8)
Exception stack(0xef075f70 to 0xef075fb8)
5f60:                                     00000000 00000000 2ee9f000 ef7e09c0
5f80: 9275dff3 00000000 ef7dfe40 00000001 9192bb9b 00000000 00000000 00000001
5fa0: 0000000b ef075fc0 c04b0f40 c04b0f64 60000113 ffffffff
[<c010ae8c>] (__irq_svc) from [<c04b0f64>] (cpuidle_enter_state+0xe4/0x1b0)
[<c04b0f64>] (cpuidle_enter_state) from [<c014c834>] (cpu_startup_entry+0x17c/0x19c)
[<c014c834>] (cpu_startup_entry) from [<001014cc>] (0x1014cc)
---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
0 Kudos
1 Solution

Accepted Solutions
rfs613
Scholar
Scholar
2,214 Views
Registered: ‎05-28-2013

I have no experience with those particular pre-built images... however based on the error message, you need to modify the kernel command line to tell it where the root filesystem is located.

root=/dev/mmcblk0p2

This would typically be done in uboot environment.

Naturally, once you add this, the contents of the 2nd partition (mmcblk0p2) will become important. A suitable filesystem will need to exist there, with /sbin/init and so on...

 

[Note that historically, Petalinux images have always booted from ramdisk. I dunno if that has changed recently...]

View solution in original post

0 Kudos
2 Replies
rfs613
Scholar
Scholar
2,215 Views
Registered: ‎05-28-2013

I have no experience with those particular pre-built images... however based on the error message, you need to modify the kernel command line to tell it where the root filesystem is located.

root=/dev/mmcblk0p2

This would typically be done in uboot environment.

Naturally, once you add this, the contents of the 2nd partition (mmcblk0p2) will become important. A suitable filesystem will need to exist there, with /sbin/init and so on...

 

[Note that historically, Petalinux images have always booted from ramdisk. I dunno if that has changed recently...]

View solution in original post

0 Kudos
garbisingla
Contributor
Contributor
1,569 Views
Registered: ‎02-24-2016

Very good appreciation, I think you must be right. I think I will just forget the pre-built images and do it myself. I posted this question also because I was kind of surprised for not being able of using the given images from the bsp...I just imagined that I could use them to evaluate the new petalinux.  Anyway :-/.

 

At the time I posted this I was already able to boot with the kernel and rootfs that I compiled and so on. However, I had problems when trying to execute the openamp examples...(and still have...). I wanted to try the given images to be sure that I was able to correctly configure bsps and libraries, etc., etc., to locate the issue.

 

Thanks for your reply. Now that you mention, I'm sure that the problem is that my SD card has two partitions...jummm. Maybe it should be specified somewhere that for running the pre-built images you must have just one partition... Whatever! I'll accept your answer!

 

Regards,

Garbí

0 Kudos