Kernel crash while untar the rootfs after bootup

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

Kernel crash while untar the rootfs after bootup

556 Views
ManikandanRama
Contributor I

I have created four partitions on my i.MX8MP board. The first partition contains the kernel Image and other DTB files. The next two partitions are used for the root filesystem.

After booting the device, I update the root filesystem using the following commands:
the Current mount partition is  mmcblk2p2.i just untar the file. i am running QT also.without QT it is working fine i am able to untar.But with QT package it gone to crash.


mount /dev/mmcblk2p3 p3
tar -xvf rootfs.tar -C p3

Sometimes the update works correctly, but other times the kernel crashes.I have 4 GB RAM. i have attached Log.

****-----------------------------*****
./usr/lib/opkg/alternatives/sync
./usr/lib/opkg/alternatives/sysctl
./usr/lib/opkg/alternatives/syslogd
./usr/lib/opkg/alternatives/tac
./usr/lib/opkg/alternatives/tail
./usr/lib/opkg/alternatives/tar
./usr/lib/opkg/[ 88.650509] Internal error: Oops - Undefined instruction: 0000000002000000 [#1] PREEMPT SMP
[ 88.661042] Modules linked in:
[ 88.664100] CPU: 3 UID: 0 PID: 316 Comm: swupdate-progre Not tainted 6.12.49-lts-next-ga2ae9d0ae881 #1
[ 88.673408] Hardware name: NXP i.MX8MPlus EVK board (DT)
[ 88.678718] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 88.685682] pc : task_fpsimd_load+0xa4/0x208
[ 88.689959] lr : fpsimd_restore_current_state+0xa8/0xc8
[ 88.695188] sp : ffff8000847e3e30
[ 88.698500] x29: ffff8000847e3e30 x28: ffff0000d500b300 x27: 0000000000000000
[ 88.705643] x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000
[ 88.712785] x23: 0000000080000000 x22: 0000000000000020 x21: ffff8000847e3eb0
[ 88.719927] x20: ffff0000d500b300 x19: 000000000000020c x18: ffff800082a95400
[ 88.727066] x17: 0000000000000060 x16: 0000000000000018 x15: 0000000000010000
[ 88.734208] x14: 000000000001e000 x13: ffff0000d500b380 x12: 0000000000000000
[ 88.741348] x11: 00000000000000c0 x10: 0000000000000a70 x9 : ffff8000847e3c00
[ 88.748493] x8 : ffff0000d500bdd0 x7 : 0000000000000000 x6 : 0000000000400100
[ 88.755634] x5 : 0000000000000020 x4 : 0000000000000000 x3 : 0000000000000200
[ 88.762775] x2 : 0000000000000008 x1 : 0000000000000208 x0 : 0000000000000000
[ 88.769917] Call trace:
[ 88.772362] task_fpsimd_load+0xa4/0x208
[ 88.776286] fpsimd_restore_current_state+0xa8/0xc8
[ 88.781167] do_notify_resume+0xc4/0x148
[ 88.785090] el0_svc+0xd4/0x100
[ 88.788234] el0t_64_sync_handler+0x120/0x12c
[ 88.792591] el0t_64_sync+0x190/0x194
[ 88.796259] Code: d5384101 f9457821 00000000 00000000 (00000000)
[ 88.802355] ---[ end trace 0000000000000000 ]---
[ 88.806974] Kernel panic - not syncing: Oops - Undefined instruction: Fatal exception in interrupt
[ 88.815931] SMP: stopping secondary CPUs
[ 89.819855] SMP: failed to stop secondary CPUs 0,2
[ 89.824649] Kernel Offset: disabled
[ 89.828134] CPU features: 0x00,00000080,00200000,4200420b
[ 89.833534] Memory Limit: none
[ 89.836589] ---[ end Kernel panic - not syncing: Oops - Undefined instruction: Fatal exception in interrupt ]---

 

 

Tags (2)
0 Kudos
Reply
2 Replies

480 Views
Chavira
NXP TechSupport
NXP TechSupport

Hi @ManikandanRama,

Thank you for contacting NXP Support!

Could you please share how you are partitioning your SD card/eMMC?


I recommend following the instructions in Chapter 4.3 of our Linux User Guide to ensure your system is flashed correctly.


Best regards,
Chavira

0 Kudos
Reply

460 Views
ManikandanRama
Contributor I

Hi @Chavira 

   I am using a 16 GB eMMC, and I have created partitions using a .wks file as shown below:

 

part u-boot --source rawcopy --sourceparams="file=imx-boot.tagged" --ondisk mmcblk --no-table --align 33

# Boot (128MB)
part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label boot --active --align 8192 --fixed-size 128

# RootFS A (3GB)
part / --source rootfs --ondisk mmcblk --fstype=ext4 --label rootfsA --align 8192 --size 3072

# RootFS B (3GB)
part / --source rootfs --ondisk mmcblk --fstype=ext4 --label rootfsB --align 8192 --size 3072

# Recovery (500MB)
part /recovery --ondisk mmcblk --fstype=ext4 --label recovery --align 8192 --fixed-size 500

bootloader --ptable msdos

 

Currently, the system is running from Partition 2 (rootfsA).

To update a new root filesystem image, I am using the following steps:

 

mkdir p3
mount /dev/mmcblk2p3 p3

tar -xvf rootfs.tar -C p3

     in that time i am getting this issue.i am using 2 GB RAM with QT application.is there any dts or kernel changes are needed?

 



Tags (1)
0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2347000%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EKernel%20crash%20while%20untar%20the%20rootfs%20after%20bootup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2347000%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3EI%20have%20created%20four%20partitions%20on%20my%20i.MX8MP%20board.%20The%20first%20partition%20contains%20the%20kernel%20Image%20and%20other%20DTB%20files.%20The%20next%20two%20partitions%20are%20used%20for%20the%20root%20filesystem.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EAfter%20booting%20the%20device%2C%20I%20update%20the%20root%20filesystem%20using%20the%20following%20commands%3A%3C%2FSPAN%3E%3CBR%20%2F%3Ethe%20Current%20mount%20partition%20is%26nbsp%3B%26nbsp%3B%3CSPAN%3Emmcblk2p2.i%20just%20untar%20the%20file.%20i%20am%20running%20QT%20also.without%20QT%20it%20is%20working%20fine%20i%20am%20able%20to%20untar.But%20with%20QT%20package%20it%20gone%20to%20crash.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSPAN%3Emount%20%2Fdev%2Fmmcblk2p3%20p3%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3Etar%20-xvf%20rootfs.tar%20-C%20p3%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3ESometimes%20the%20update%20works%20correctly%2C%20but%20other%20times%20the%20kernel%20crashes.I%20have%204%20GB%20RAM.%20i%20have%20attached%20Log.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E****-----------------------------*****%3CBR%20%2F%3E%3CSPAN%3E.%2Fusr%2Flib%2Fopkg%2Falternatives%2Fsync%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E.%2Fusr%2Flib%2Fopkg%2Falternatives%2Fsysctl%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E.%2Fusr%2Flib%2Fopkg%2Falternatives%2Fsyslogd%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E.%2Fusr%2Flib%2Fopkg%2Falternatives%2Ftac%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E.%2Fusr%2Flib%2Fopkg%2Falternatives%2Ftail%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E.%2Fusr%2Flib%2Fopkg%2Falternatives%2Ftar%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E.%2Fusr%2Flib%2Fopkg%2F%5B%2088.650509%5D%20Internal%20error%3A%20Oops%20-%20Undefined%20instruction%3A%200000000002000000%20%5B%231%5D%20PREEMPT%20SMP%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.661042%5D%20Modules%20linked%20in%3A%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.664100%5D%20CPU%3A%203%20UID%3A%200%20PID%3A%20316%20Comm%3A%20swupdate-progre%20Not%20tainted%206.12.49-lts-next-ga2ae9d0ae881%20%231%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.673408%5D%20Hardware%20name%3A%20NXP%20i.MX8MPlus%20EVK%20board%20(DT)%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.678718%5D%20pstate%3A%2060000005%20(nZCv%20daif%20-PAN%20-UAO%20-TCO%20-DIT%20-SSBS%20BTYPE%3D--)%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.685682%5D%20pc%20%3A%20task_fpsimd_load%2B0xa4%2F0x208%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.689959%5D%20lr%20%3A%20fpsimd_restore_current_state%2B0xa8%2F0xc8%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.695188%5D%20sp%20%3A%20ffff8000847e3e30%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.698500%5D%20x29%3A%20ffff8000847e3e30%20x28%3A%20ffff0000d500b300%20x27%3A%200000000000000000%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.705643%5D%20x26%3A%200000000000000000%20x25%3A%200000000000000000%20x24%3A%200000000000000000%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.712785%5D%20x23%3A%200000000080000000%20x22%3A%200000000000000020%20x21%3A%20ffff8000847e3eb0%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.719927%5D%20x20%3A%20ffff0000d500b300%20x19%3A%20000000000000020c%20x18%3A%20ffff800082a95400%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.727066%5D%20x17%3A%200000000000000060%20x16%3A%200000000000000018%20x15%3A%200000000000010000%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.734208%5D%20x14%3A%20000000000001e000%20x13%3A%20ffff0000d500b380%20x12%3A%200000000000000000%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.741348%5D%20x11%3A%2000000000000000c0%20x10%3A%200000000000000a70%20x9%20%3A%20ffff8000847e3c00%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.748493%5D%20x8%20%3A%20ffff0000d500bdd0%20x7%20%3A%200000000000000000%20x6%20%3A%200000000000400100%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.755634%5D%20x5%20%3A%200000000000000020%20x4%20%3A%200000000000000000%20x3%20%3A%200000000000000200%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.762775%5D%20x2%20%3A%200000000000000008%20x1%20%3A%200000000000000208%20x0%20%3A%200000000000000000%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.769917%5D%20Call%20trace%3A%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.772362%5D%20task_fpsimd_load%2B0xa4%2F0x208%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.776286%5D%20fpsimd_restore_current_state%2B0xa8%2F0xc8%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.781167%5D%20do_notify_resume%2B0xc4%2F0x148%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.785090%5D%20el0_svc%2B0xd4%2F0x100%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.788234%5D%20el0t_64_sync_handler%2B0x120%2F0x12c%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.792591%5D%20el0t_64_sync%2B0x190%2F0x194%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.796259%5D%20Code%3A%20d5384101%20f9457821%2000000000%2000000000%20(00000000)%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.802355%5D%20---%5B%20end%20trace%200000000000000000%20%5D---%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.806974%5D%20Kernel%20panic%20-%20not%20syncing%3A%20Oops%20-%20Undefined%20instruction%3A%20Fatal%20exception%20in%20interrupt%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2088.815931%5D%20SMP%3A%20stopping%20secondary%20CPUs%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2089.819855%5D%20SMP%3A%20failed%20to%20stop%20secondary%20CPUs%200%2C2%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2089.824649%5D%20Kernel%20Offset%3A%20disabled%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2089.828134%5D%20CPU%20features%3A%200x00%2C00000080%2C00200000%2C4200420b%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2089.833534%5D%20Memory%20Limit%3A%20none%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%5B%2089.836589%5D%20---%5B%20end%20Kernel%20panic%20-%20not%20syncing%3A%20Oops%20-%20Undefined%20instruction%3A%20Fatal%20exception%20in%20interrupt%20%5D---%3C%2FSPAN%3E%3C%2FP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2348565%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Kernel%20crash%20while%20untar%20the%20rootfs%20after%20bootup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2348565%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F261190%22%20target%3D%22_blank%22%3E%40ManikandanRama%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20contacting%20NXP%20Support!%3CBR%20%2F%3E%3CBR%20%2F%3ECould%20you%20please%20share%20how%20you%20are%20partitioning%20your%20SD%20card%2FeMMC%3F%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EI%20recommend%20following%20the%20instructions%20in%20Chapter%204.3%20of%20our%20%3CA%20href%3D%22https%3A%2F%2Fwww.nxp.com%2Fdocs%2Fen%2Fuser-guide%2FUG10163.pdf%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ELinux%20User%20Guide%3C%2FA%3E%20to%20ensure%20your%20system%20is%20flashed%20correctly.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EBest%20regards%2C%3CBR%20%2F%3EChavira%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2348959%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Kernel%20crash%20while%20untar%20the%20rootfs%20after%20bootup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2348959%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F206761%22%20target%3D%22_blank%22%3E%40Chavira%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3BI%20am%20using%20a%20%3CSTRONG%3E16%20GB%20eMMC%3C%2FSTRONG%3E%2C%20and%20I%20have%20created%20partitions%20using%20a%20.wks%20file%20as%20shown%20below%3A%3C%2FP%3E%3CBR%20%2F%3E%3CP%3Epart%20u-boot%20--source%20rawcopy%20--sourceparams%3D%22file%3Dimx-boot.tagged%22%20--ondisk%20mmcblk%20--no-table%20--align%2033%3C%2FP%3E%3CP%3E%23%20Boot%20(128MB)%3CBR%20%2F%3Epart%20%2Fboot%20--source%20bootimg-partition%20--ondisk%20mmcblk%20--fstype%3Dvfat%20--label%20boot%20--active%20--align%208192%20--fixed-size%20128%3C%2FP%3E%3CP%3E%23%20RootFS%20A%20(3GB)%3CBR%20%2F%3Epart%20%2F%20--source%20rootfs%20--ondisk%20mmcblk%20--fstype%3Dext4%20--label%20rootfsA%20--align%208192%20--size%203072%3C%2FP%3E%3CP%3E%23%20RootFS%20B%20(3GB)%3CBR%20%2F%3Epart%20%2F%20--source%20rootfs%20--ondisk%20mmcblk%20--fstype%3Dext4%20--label%20rootfsB%20--align%208192%20--size%203072%3C%2FP%3E%3CP%3E%23%20Recovery%20(500MB)%3CBR%20%2F%3Epart%20%2Frecovery%20--ondisk%20mmcblk%20--fstype%3Dext4%20--label%20recovery%20--align%208192%20--fixed-size%20500%3C%2FP%3E%3CP%3Ebootloader%20--ptable%20msdos%3C%2FP%3E%3CBR%20%2F%3E%3CP%3ECurrently%2C%20the%20system%20is%20running%20from%20%3CSTRONG%3EPartition%202%20(rootfsA)%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3ETo%20update%20a%20new%20root%20filesystem%20image%2C%20I%20am%20using%20the%20following%20steps%3A%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CSTRONG%3Emkdir%20p3%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Emount%20%2Fdev%2Fmmcblk2p3%20p3%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3Etar%20-xvf%20rootfs.tar%20-C%20p3%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3Bin%20that%20time%20i%20am%20getting%20this%20issue.i%20am%20using%202%20GB%20RAM%20with%20QT%20application.is%20there%20any%20dts%20or%20kernel%20changes%20are%20needed%3F%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E