AnsweredAssumed Answered

Kernel Panic on Pre-Built Linux SDCard image for MCIMX8M-EVK: Evaluation Kit?

Question asked by GLEN CORNELL on Aug 14, 2018
Latest reply on Sep 10, 2018 by Ling guan

It appears that the pre-built Linux SDcard image for the #i.MX 8M evaluation kit downloaded from the NXP website fails with a kernel panic.  Is anyone else seeing the same thing?

 

We recently purchased the MCIMX8M-EVK: Evaluation Kit for the i.MX 8M Applications Processor, downloaded the pre-built Linux BSP (https://www.nxp.com/webapp/Download?colCode=L4.9.88_2.0.0_MX8MQ&appType=license&Parent_nodeId=1513109797983730444282&Par… ), and performed the following, according to the documentation:

 

  1. extracted the L4.9.88_2.0.0_images_MX8MQ.tar.gz tarball (md5sum: e7fd9c911d12bf3807bba3b040eb0f2a)

    tar zxvf L4.9.88_2.0.0_images_MX8MQ.tar.gz

  2. decompressed the SD card image: 

    cd L4.9.88_2.0.0_images_MX8MQ

    bunzip2 fsl-image-qt5-validation-imx-xwayland-imx8mqevk.sdcard.bz2

  3. Copied the image to an SD card:

    sudo dd if=fsl-image-qt5-validation-imx-xwayland-imx8mqevk.sdcard of=/dev/mmcblk0

I placed the SDcard in the evaluation board, set the jumpers for the proper boot, and applied power to the card.  I found two problems.  First, the monitor showed nothing on the screen (the monitor indicated that it received no signal).  "systemctl status" indicated no error with any processes. 2. The kernel panicked about 4 minutes into the boot process (output of serial port is attached):

[ 242.786648] INFO: task systemd-udevd:2801 blocked for more than 120 seconds.
[ 242.793723] Tainted: G O 4.9.88-imx_4.9.88_2.0.0_ga+g5e23f9d #1
[ 242.801430] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 242.809452] systemd-udevd D 0 2801 1771 0x0000020d
[ 242.815083] Call trace:
[ 242.817544] [<ffff000008085e98>] __switch_to+0x90/0xc0
[ 242.822810] [<ffff000008c653f0>] __schedule+0x178/0x590
[ 242.828159] [<ffff000008c65844>] schedule+0x3c/0xa8
[ 242.833157] [<ffff000008c688e4>] schedule_timeout+0x174/0x248
[ 242.839025] [<ffff000008c67680>] __down+0x58/0x90
[ 242.843852] [<ffff000008102e74>] down+0x4c/0x68
[ 242.849478] [<ffff000000f4155c>] HIFExchangeBMIMsg+0x20c/0x330 [wlan]
[ 242.856971] [<ffff000000f47ac4>] bmi_download_firmware+0x64/0x130 [wlan]
[ 242.864708] [<ffff000000edff9c>] vos_open+0x174/0x6c0 [wlan]
[ 242.871378] [<ffff000000d9bca4>] hdd_wlan_startup+0x5ac/0x12e0 [wlan]
[ 242.878462] [<ffff000000f45cc8>] hif_pci_probe+0x5f8/0x858 [wlan]
[ 242.884685] [<ffff000008486c4c>] pci_device_probe+0x9c/0x140
[ 242.890461] [<ffff000008649a40>] driver_probe_device+0x1d0/0x2c8
[ 242.896580] [<ffff000008649bf4>] __driver_attach+0xbc/0xc0
[ 242.902181] [<ffff000008647b34>] bus_for_each_dev+0x4c/0x98
[ 242.907867] [<ffff0000086493b8>] driver_attach+0x20/0x28
[ 242.913294] [<ffff000008648fa8>] bus_add_driver+0x1b8/0x228
[ 242.918976] [<ffff00000864a578>] driver_register+0x60/0xf8
[ 242.924576] [<ffff0000084857a8>] __pci_register_driver+0x38/0x40
[ 242.931321] [<ffff000000f45630>] hif_register_driver+0x18/0x38 [wlan]
[ 242.938482] [<ffff000000d93d80>] hdd_hif_register_driver+0x30/0x78 [wlan]
[ 242.946002] [<ffff0000012010b4>] hdd_module_init+0xb4/0x1000 [wlan]
[ 242.952416] [<ffff000008083a50>] do_one_initcall+0x38/0x130
[ 242.958110] [<ffff0000081767d8>] do_init_module+0x5c/0x1bc
[ 242.963714] [<ffff000008139650>] load_module+0x1c50/0x20f8
[ 242.969315] [<ffff000008139d78>] SyS_finit_module+0xa8/0xc0
[ 242.975003] [<ffff0000080838d8>] __sys_trace_return+0x0/0x4

 

Has anyone seen this problem?  Incidentally, a co-worker independently found the same problem.  It would be nice to know if I'm either mis-reading the instructions or the image has an error.

 

Thanks,

Glen

Attachments

Outcomes