1、启动rootfs时候报错,之前好好的,郁闷呀
mmcblk0: p1(u-boot.bin) p2(kernel) p3(rootfs.ext4) p4(app) p5(param) p6(backup.param) p7(data)
invn_irq_handler INT triggered in wrong mode
invn_process_dri_data INT triggered in wrong mode 0
invn_irq_handler INT triggered in wrong mode
invn_process_dri_data INT triggered in wrong mode 0
invn_irq_handler INT triggered in wrong mode
invn_process_dri_data INT triggered in wrong mode 0
invn_irq_handler INT triggered in wrong mode
invn_process_dri_data INT triggered in wrong mode 0
invn_irq_handler INT triggered in wrong mode
invn_process_dri_data INT triggered in wrong mode 0
invn_irq_handler INT triggered in wrong mode
invn_process_dri_data INT triggered in wrong mode 0
hibvt_rtc 180b0000.rtc: setting system clock to 1970-01-01 01:10:15 UTC (4215)
clk: Not disabling unused clocks
uart-pl011 12100000.uart: no DMA platform data
EXT4-fs (mmcblk0p3): recovery complete
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:3.
Freeing unused kernel memory: 384K (ffffffc004840000 - ffffffc0048a0000)
Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.9.37 #35
Hardware name: Hisilicon HI3559AV100 DEMO Board (DT)
Call trace:
[<ffffff8008088de8>] dump_backtrace+0x0/0x198
[<ffffff800808908c>] show_stack+0x14/0x20
[<ffffff8008338824>] dump_stack+0x94/0xb8
[<ffffff800812c324>] panic+0x114/0x264
[<ffffff8008659ebc>] kernel_init+0xec/0x100
[<ffffff8008082ee0>] ret_from_fork+0x10/0x30
SMP: stopping secondary CPUs
Kernel Offset: disabled
Memory Limit: 512 MB
---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
2、问题原因
a.初步怀疑是分区文件过来,造成引导文件系统错误;
b.rootfs文件权限问题;
c.文件系统类型是否与uboot参数是否一致;
3、解决方法
目前没有彻底解决,只是从板子上拷贝了一份rootfs,重新打包烧录是正常的。