This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: SDK8.2: Kernel Panic

Part Number: TDA4VM

Hi TI team,

We have observed kernel panic once, board just booted without running any visteon applications, system was basically idle with whatever default services/processes were started upon startup.

If it is reproduced, I wil submit the log again, I tried reproducing for 2 to 3 hours mutiple times but did not reproduce.

But development team can look at the possible reasons for the kernel panic with the help of the attached log.

Regards

Mahipal

  • root@j7-evm:~# [   35.145370] Initializing XFRM netlink socket
    [ 2822.400102] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
    [ 3688.971781] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
    [ 3911.338247] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
    [ 3941.514081] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
    [ 7761.347138] virtio_rpmsg_bus virtio2: msg received with no recipient
    [ 7761.354074] virtio_rpmsg_bus virtio4: msg received with no recipient
    [ 7761.360638] virtio_rpmsg_bus virtio2: msg received with no recipient
    [ 7761.367042] virtio_rpmsg_bus virtio2: msg received with no recipient
    [ 7761.373487] virtio_rpmsg_bus virtio2: msg received with no recipient
    [ 8801.763052] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010
    [ 8801.771830] Mem abort info:
    [ 8801.774612]   ESR = 0x96000047
    [ 8801.777655]   EC = 0x25: DABT (current EL), IL = 32 bits
    [ 8801.782949]   SET = 0, FnV = 0
    [ 8801.785996]   EA = 0, S1PTW = 0
    [ 8801.789124] Data abort info:
    [ 8801.791998] xhci-hcd xhci-hcd.2.auto: WARN Successful completion on short TX for slot 2 ep 6: needs XHCI_TRUST_TX_LENGTH quirk?
    [ 8801.792002] xhci-hcd xhci-hcd.2.auto: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 1
    [ 8801.792006] xhci-hcd xhci-hcd.2.auto: Looking for event-dma 00000008a50066a0 trb-start 00000008a58566a0 trb-end 00000008a58566a0 seg-start 00000008a5856000 seg-end 00000008a5856ff0
    [ 8801.803458] Unable to handle kernel paging request at virtual address ffbf800123fffcc8
    [ 8801.803460] Mem abort info:
    [ 8801.803461]   ESR = 0x96000004
    [ 8801.803463]   EC = 0x25: DABT (current EL), IL = 32 bits
    [ 8801.803465]   SET = 0, FnV = 0
    [ 8801.803466]   EA = 0, S1PTW = 0
    [ 8801.803467] Data abort info:
    [ 8801.803468]   ISV = 0, ISS = 0x00000004
    [ 8801.803470]   CM = 0, WnR = 0
    [ 8801.803472] [ffbf800123fffcc8] address between user and kernel address ranges
    [ 8801.803475] Internal error: Oops: 96000004 [#1] PREEMPT SMP
    [ 8801.803477] Modules linked in: xfrm_user xfrm_algo cdc_ether usbnet r8152 xhci_plat_hcd xhci_hcd ti_am335x_adc kfifo_buf omap_rng rng_core rpmsg_char cdns3 udc_core roles irq_pruss_intc pru_rproc icss_iep usbcore usb_common crct10dif_ce ti_j721e_cpsw_virt_mac phy_can_transceiver md5 ecb aes_neon_bs aes_neon_blk des_generic libdes cbc ti_k3_r5_remoteproc ti_am335x_tscadc pvrsrvkm(O) pruss vxe_enc vxd_dec sa2ul videobuf2_dma_sg ti_k3_dsp_remoteproc v4l2_mem2mem sha512_generic videobuf2_dma_contig authenc virtio_rpmsg_bus videobuf2_memops videobuf2_v4l2 cdns_dphy videobuf2_common cdns3_ti snd_soc_pcm3168a_i2c snd_soc_pcm3168a m_can_platform m_can can_dev rti_wdt overlay sch_fq_codel rpmsg_kdrv_switch cryptodev(O) ipv6
    [ 8801.803558] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G           O      5.10.100-g7a7a3af903 #1
    [ 8801.803560] Hardware name: Texas Instruments K3 J721E SoC (DT)
    [ 8801.803564] pstate: 80000085 (Nzcv daIf -PAN -UAO -TCO BTYPE=--)
    [ 8801.803577] pc : rb_next+0x34/0x60
    [ 8801.803580] lr : timerqueue_del+0x64/0x78
    [ 8801.803581] sp : ffff80001142f510
    [ 8801.803583] x29: ffff80001142f510 x28: ffff00087fa583b8
    [ 8801.803587] x27: ffff00087fa58300 x26: 0000000000000004
    [ 8801.803591] x25: 0000000000000001 x24: 0000000000000080
    [ 8801.803594] x23: 000008014e971a83 x22: ffff00087fa58300
    [ 8801.803597] x21: 0000000000000000 x20: ffff00087fa58360
    [ 8801.803600] x19: ffff80012108fdc0 x18: 0000000000000010
    [ 8801.803604] x17: 0000000000000000 x16: 0000000000000000
    [ 8801.803607] x15: ffff8000111dbef0 x14: 206e6f206e6f6974
    [ 8801.803610] x13: 656c706d6f63206c x12: 6f6c7320726f6620
    [ 8801.803613] x11: 0000000000000040 x10: ffff80001125a400
    [ 8801.803617] x9 : ffff80001125a3f8 x8 : ffff000840000270
    [ 8801.803620] x7 : 0000000000000000 x6 : 0000000000000000
    [ 8801.803623] x5 : 0000000005000000 x4 : 0000000000000000
    [ 8801.803626] x3 : 0000000000000000 x2 : ffff80001756f830
    [ 8801.803630] x1 : ffff80012108fdc0 x0 : ffbf800123fffcc0
    [ 8801.803634] Call trace:
    [ 8801.803639] Code: f9400821 b5ffffc1 d50323bf d65f03c0 (f9400401)
    [ 8801.803647] ---[ end trace adea238533564827 ]---
    [ 8801.803649] Kernel panic - not syncing: Oops: Fatal exception in interrupt
    [ 8801.803652] SMP: stopping secondary CPUs
    [ 8802.866155] SMP: failed to stop secondary CPUs 0-1
    [ 8802.866162] Kernel Offset: disabled
    [ 8802.866164] CPU features: 0x0040022,20006008
    [ 8802.866166] Memory Limit: none
    [ 8803.153080] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]---

  • Hi Mahipal,

    We have observed kernel panic once, board just booted without running any visteon applications, system was basically idle with whatever default services/processes were started upon startup.

    So we just need to leave the TDA4VM idle & this crash should be seen on 8.2 SDK?

    Let us know if this is PSDK RTOS on top of Linux or just the Linux SDK. Please share the complete boot logs.

    Regards,
    Keerthy

  • Hi Keerthy,

    Yes system was just idle , then this crash was seen, but I am not able to reproduce it so far.

    We do not have complete boot log, above attached is the only log available.

    Yes PSDK RTOS on top of Linux.

    Rgds

    Mahipal

  • Hi Mahipal,


    I have not observed on the TDA4_EVM that i use. I will leave PSDK RTOS overnight tomorrow & get back if I am able to reproduce the issue.
    In the meantime please try to reproduce the issue & if you manage to do that please share complete boot logs.


    - Keerthy

  • Hi Mahipal,

    I could not reproduce the above crash. Have you tried reproducing on the PSDK Linux? Let me know.

    - Keerthy

  • Hi Keerthy,

    No it was not reproduced again.

    Rgds

    Mahipal

  • Hi Mahipal,

    Please share the full logs the next time you reproduce. That will help us debug.
    Closing this for now but feel free to re-open with full logs next time you are able to reproduce.

    - Keerthy