iMX8MQ custom board getting kernel panic

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

iMX8MQ custom board getting kernel panic

1,147 Views
Saravanans1
Contributor III

We have using the iMx8MQ custom board while booting the board from emmc it was stuck in the kernel and showed the Kernel panic errors. Attached log for reference

[2023-05-02 18:29:26.814] [ 3.368409] EXT4-fs (mmcblk0p2): error loading journal
[2023-05-02 18:29:26.814] [ 3.378764] VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error -5
[2023-05-02 18:29:26.814] [ 3.386690] Please append a correct "root=" boot option; here are the available partitions:
[2023-05-02 18:29:26.814] [ 3.395070] 1f00 32768 mtdblock0
[2023-05-02 18:29:26.814] [ 3.395072] (driver?)
[2023-05-02 18:29:26.814] [ 3.401641] b300 30535680 mmcblk0
[2023-05-02 18:29:26.814] [ 3.401643] driver: mmcblk
[2023-05-02 18:29:26.814] [ 3.408467] b301 5452596 mmcblk0p1 fb8f6d72-01
[2023-05-02 18:29:26.814] [ 3.408468]
[2023-05-02 18:29:26.814] [ 3.415279] b302 5452596 mmcblk0p2 fb8f6d72-02
[2023-05-02 18:29:26.814] [ 3.415280]
[2023-05-02 18:29:26.814] [ 3.422124] b303 17825792 mmcblk0p3 fb8f6d72-03
[2023-05-02 18:29:26.814] [ 3.422125]
[2023-05-02 18:29:26.814] [ 3.428939] b304 1048576 mmcblk0p4 fb8f6d72-04
[2023-05-02 18:29:26.814] [ 3.428940]
[2023-05-02 18:29:26.814] [ 3.435761] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[2023-05-02 18:29:26.814] [ 3.444199] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.4.70-2.3.2+ #1
[2023-05-02 18:29:26.814] [ 3.450725] Hardware name: NXP i.MX8MQ EVK (DT)
[2023-05-02 18:29:26.814] [ 3.455253] Call trace:
[2023-05-02 18:29:26.814] [ 3.457706] dump_backtrace+0x0/0x140
[2023-05-02 18:29:26.832] [ 3.461369] show_stack+0x14/0x20
[2023-05-02 18:29:26.832] [ 3.464685] dump_stack+0xb4/0x114
[2023-05-02 18:29:26.832] [ 3.468087] panic+0x158/0x324
[2023-05-02 18:29:26.832] [ 3.471143] mount_block_root+0x1d0/0x284
[2023-05-02 18:29:26.832] [ 3.475150] mount_root+0x124/0x158
[2023-05-02 18:29:26.832] [ 3.478636] prepare_namespace+0x12c/0x18c
[2023-05-02 18:29:26.832] [ 3.482732] kernel_init_freeable+0x210/0x23c
[2023-05-02 18:29:26.832] [ 3.487089] kernel_init+0x10/0x100
[2023-05-02 18:29:26.832] [ 3.490578] ret_from_fork+0x10/0x1c
[2023-05-02 18:29:26.832] [ 3.494157] SMP: stopping secondary CPUs
[2023-05-02 18:29:26.832] [ 3.498597] Kernel Offset: disabled
[2023-05-02 18:29:26.832] [ 3.502084] CPU features: 0x0002,2000200c
[2023-05-02 18:29:26.832] [ 3.506092] Memory Limit: none
[2023-05-02 18:29:26.832] [ 3.509149] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2) ]---

Labels (1)
0 Kudos
Reply
5 Replies

1,065 Views
Saravanans1
Contributor III

Hi,

We have flashed the binary again using uuu tool in serial download mode. Now the kernel panic problem is solved.

0 Kudos
Reply

1,048 Views
Dhruvit
NXP TechSupport
NXP TechSupport

Hi @Saravanans1,

I hope you are doing well.

As this case is solved, can I mark this as close?

Thanks & Regards,
Dhruvit Vasavada

0 Kudos
Reply

1,006 Views
Saravanans1
Contributor III

Hi,

Thank you. It was solved.

0 Kudos
Reply

1,106 Views
Dhruvit
NXP TechSupport
NXP TechSupport

Hi @Saravanans1,

I hope you are doing well.

One can rebuild the journal but you will need a Linux machine to do it.

One can check if the kernel parameter for root= is pointing to the correct partition.

One can try to re-image the card and try again.

If you are using a driver on u-boot, you need to match the version on kernel side.

In other words, you might have to use the same version among u-boot, kernel, and rootfs to prevent boot failure issues.
 
Thanks & Regards,
Dhruvit Vasavada
0 Kudos
Reply

1,080 Views
Saravanans1
Contributor III

Thanks for your quick response. We will check and update you.

 

 

Thanks & Regards,

Saravanan S

0 Kudos
Reply