kernel panic when trying to emulate imx6q with qemu-system-arm

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

kernel panic when trying to emulate imx6q with qemu-system-arm

Jump to solution
1,118 Views
sokvulu
Contributor I

the panic occurs in the caam module as shown in the log below:

qemu-system-arm -M sabrelite -kernel "zImage" -nographic -dtb zImage.dtb

 

caam 2100000.caam: ERA undetermined!.

caam 2100000.caam: device ID = 0x0000000000000000 (Era -524)

job rings = 2, qi = 0

caam_jr 2101000.jr0: failed to flush job ring 0

caam_jr: probe of 2101000.jr0 failed with error -5

caam_jr 2102000.jr1: failed to flush job ring 1

caam_jr: probe of 2102000.jr1 failed with error -5

caam algorithms registered in /proc/crypto

Unable to handle kernel NULL pointer dereference at virtual address 00000010

pgd = 80004000

[00000010] *pgd=00000000

Internal error: Oops: 5 [#1] PREEMPT SMP ARM

Modules linked in:

CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.88 #1

Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)

task: 8206ce00 task.stack: 82062000

PC is at caam_sm_startup+0x260/0x47c

LR is at 0x0

pc : [<80640b3c>]    lr : [<00000000>]    psr: 60000013

sp : 82063eb8  ip : 00000001  fp : 00000000

r10: 82418400  r9 : 80b9fd40  r8 : 00000000

r7 : 8241eb10  r6 : 00000000  r5 : 00000005  r4 : 823efb40

r3 : 82418400  r2 : 00000000  r1 : 000000f4  r0 : 82418400

Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none

Control: 10c53c7d  Table: 10004059  DAC: 00000051

Process swapper/0 (pid: 1, stack limit = 0x82062210)

Stack: (0x82063eb8 to 0x82064000)

3ea0:                                                       82199810 80568e70

3ec0: 82418400 82424600 00000000 80b04108 00000000 ffffe000 80a3b83c 80a28c28

3ee0: 000000ba 80add6bc 00000000 80a28c78 80b04108 801017f0 80b04108 820aef80

3f00: 80802d4c 00000011 80b0fea4 00000000 cccccccd 80283a8c 808f1094 820ae780

3f20: 00000000 80b0e014 8081e794 87ffca88 000000ba 801448a8 8099d518 8093146c

3f40: 808ed1a8 00000006 00000006 00040958 80b0dffc 80b3e000 80b3e000 80a3b834

3f60: 80a3b83c 00000007 000000ba 80add6bc 00000000 80a00e44 00000006 00000006

3f80: 00000000 80a005cc 00000000 807f0c70 00000000 00000000 00000000 00000000

3fa0: 00000000 807f0c78 00000000 80107d50 00000000 00000000 00000000 00000000

3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

3fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000

[<80640b3c>] (caam_sm_startup) from [<80a28c78>] (caam_sm_init+0x50/0x58)

[<80a28c78>] (caam_sm_init) from [<801017f0>] (do_one_initcall+0x54/0x194)

[<801017f0>] (do_one_initcall) from [<80a00e44>] (kernel_init_freeable+0x158/0x1e4)

[<80a00e44>] (kernel_init_freeable) from [<807f0c78>] (kernel_init+0x8/0x110)

[<807f0c78>] (kernel_init) from [<80107d50>] (ret_from_fork+0x14/0x24)

Code: e3855005 e35100f4 1affffcc e5d9c000 (e5961010)

---[ end trace b70259ac88ba94b4 ]---

Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b



---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

 

0 Kudos
1 Solution
1,108 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello Sokvulu,

There is something bad in your device tree check if the cam is correctly defined, however QEMU it is a generic emulator, so you can emulate the CORTEX A9, but there is not support for QEMU from NXP. I apologize for the inconvenience.

 

Regards

 

 

View solution in original post

0 Kudos
1 Reply
1,109 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello Sokvulu,

There is something bad in your device tree check if the cam is correctly defined, however QEMU it is a generic emulator, so you can emulate the CORTEX A9, but there is not support for QEMU from NXP. I apologize for the inconvenience.

 

Regards

 

 

0 Kudos