• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 596 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux/AM5718: kernal crashing

ALWALA MOUNIKA
Intellectual 280 points

Part Number: AM5718

Tool/software: Linux

Hi,

We are developing a custom board with am5718 using ti-processor-sdk-linux-am57xx-evm-05.02.00.10 and able to enter into the root with a bootable sd card with a kernal getting crashed and the related log is attached below.

Please have thorough glance at the following mentioned sort of issues and suggest us how to resolve individual errors in a detailed manner separately.

1) [   10.675589] WARNING: CPU: 0 PID: 198 at drivers/bus/omap_l3_noc.c:147 l3_interrupt_handler+0x254/0x370
[   10.684937] 44000000.ocp:L3 Custom Error: MASTER MPU TARGET L4_PER3_P3 (Idle): Data Access in User mode during Functional access

 

2) [  193.171379] asoc-simple-card sound@0: tlv320aic3x-hifi <-> 48468000.mcasp mapping ok
[  193.179192] asoc-simple-card sound@0: ASoC: no DMI vendor name!
[  193.202326] extcon-usb-gpio extcon_usb1: GPIO lookup for consumer id
[  193.208715] extcon-usb-gpio extcon_usb1: using device tree for GPIO lookup
[  193.231370] extcon-usb-gpio extcon_usb1: lookup for GPIO id failed
[  193.237588] extcon-usb-gpio extcon_usb1: GPIO lookup for consumer vbus
[  193.267238] extcon-usb-gpio extcon_usb1: using device tree for GPIO lookup
[  193.280792] of_get_named_gpiod_flags: can't parse 'vbus-gpios' property of node '/extcon_usb1[0]'
[  193.289709] of_get_named_gpiod_flags: can't parse 'vbus-gpio' property of node '/extcon_usb1[0]'
[  193.320741] extcon-usb-gpio extcon_usb1: using lookup tables for GPIO lookup
[  193.327825] extcon-usb-gpio extcon_usb1: lookup for GPIO vbus failed
[  193.351164] extcon-usb-gpio extcon_usb2: GPIO lookup for consumer id
[  193.357553] extcon-usb-gpio extcon_usb2: using device tree for GPIO lookup
[  193.385715] extcon-usb-gpio extcon_usb2: lookup for GPIO id failed
[  193.398878] extcon-usb-gpio extcon_usb2: GPIO lookup for consumer vbus


3) [  889.943190] Unable to handle kernel paging request at virtual address 08800123
2553.kernalcrash.zip

Thanks and regards,

A.Mounika

  • 0
    TI__Guru 55345 points

    Hello ALWALA,

    Please, see this thread.

    Best regards,
    Kemal

  • 0 in reply to Kemal R. Shakir
    Intellectual 280 points
    Hi,
    In the thread that you have suggested for us has conveyed that by changing am57xx-evm-cmem-am571x.dtsi instead of am57xx-evm-cmem.dtsi. in the dts files has resolved the issue but in our dts files it is already there as same as am57xx-evm-cmem-am571x.dtsi and it is a custom error and also we are using the am571x-idk.dts file. So please tell us in what way we need to proceed further inorder to solve it.

    Thanks and regards,
    A.Mounika.
  • 0 in reply to ALWALA MOUNIKA
    TI__Guru 55345 points

    Please, also refer to this and this thread and make sure that you have the used IP blocks like i2c and gpio in the device tree enabled and the register dump show the same.

  • 0 in reply to Kemal R. Shakir
    Intellectual 280 points
    Hi,
    [ 10.684937] 44000000.ocp:L3 Custom Error: MASTER MPU TARGET L4_PER3_P3 (Idle): Data Access in User mode during Functional access
    We are able to solve the custom error related issue mentioned above and able to clear half of the crash.

    But we are unable to solve the crash mentioned below and guide us how to solve the crash due to Backtrace in the log

    0.223158] ------------[ cut here ]------------
    [ 0.223178] WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c:2494 _init.constprop.21+0x1e4/0x4a8
    [ 0.223186] omap_hwmod: rtcss: doesn't have mpu register target base
    [ 0.223193] Modules linked in:
    [ 0.223210] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.79-gbde58ab01e #11
    [ 0.223218] Hardware name: Generic DRA72X (Flattened Device Tree)
    [ 0.223225] Backtrace:
    [ 0.223243] [<c020b4dc>] (dump_backtrace) from [<c020b7c0>] (show_stack+0x18/0x1c)
    [ 0.223255] r7:00000009 r6:60000013 r5:00000000 r4:c1053d10
    [ 0.223270] [<c020b7a8>] (show_stack) from [<c0931328>] (dump_stack+0x90/0xa4)
    [ 0.223283] [<c0931298>] (dump_stack) from [<c022b9cc>] (__warn+0xec/0x104)
    [ 0.223293] r7:00000009 r6:c0ba994c r5:00000000 r4:ef07de20
    [ 0.223303] [<c022b8e0>] (__warn) from [<c022ba24>] (warn_slowpath_fmt+0x40/0x48)
    [ 0.223313] r9:000000d2 r8:c0e4a824 r7:00000000 r6:c100f1bc r5:00000000 r4:c0ba9c4c
    [ 0.223326] [<c022b9e8>] (warn_slowpath_fmt) from [<c0e0c2c4>] (_init.constprop.21+0x1e4/0x4a8)
    [ 0.223334] r3:c0babb14 r2:c0ba9c4c
    [ 0.223342] r4:c100f178
    [ 0.223356] [<c0e0c0e0>] (_init.constprop.21) from [<c0e0cabc>] (__omap_hwmod_setup_all+0x48/0x108)
    [ 0.223366] r10:c1058000 r9:000000d2 r8:c0e4a824 r7:c1058000 r6:c0e0ca74 r5:c1009288
    [ 0.223373] r4:c100f178
    [ 0.223387] [<c0e0ca74>] (__omap_hwmod_setup_all) from [<c02019fc>] (do_one_initcall+0x4c/0x170)
    [ 0.223395] r5:00000000 r4:ffffe000
    [ 0.223406] [<c02019b0>] (do_one_initcall) from [<c0e00f80>] (kernel_init_freeable+0x1d8/0x274)
    [ 0.223416] r8:c0e4a824 r7:c1058000 r6:00000003 r5:c0e5c9a0 r4:c0c7f0a4
    [ 0.223429] [<c0e00da8>] (kernel_init_freeable) from [<c0944330>] (kernel_init+0x10/0x114)
    [ 0.223439] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c0944320
    [ 0.223446] r4:00000000
    [ 0.223460] [<c0944320>] (kernel_init) from [<c0207d18>] (ret_from_fork+0x14/0x3c)
    [ 0.223467] r5:c0944320 r4:00000000
    [ 0.223479] ---[ end trace c626075d16e1d881 ]---
    [ 0.233444] omap_hwmod: dcan1: _wait_target_disable failed

    Thanks and regards,
    A.Mounika
  • 0 in reply to ALWALA MOUNIKA
    TI__Guru 55345 points

    The backtrace reports that something is wrong with the RTC subsystem. Please, see this similar thread for some possible causes.

  • 0 in reply to Kemal R. Shakir
    TI__Guru 55345 points

    Hello ALWALA,

    Were you able to fix the last crash?

    Best regards,
    Kemal

  • 0 in reply to Kemal R. Shakir
    TI__Guru 55345 points

    Hi ALWALA,

    I’ve not heard back from you for a month. I hope we were able to help. I’m going to close the thread now and mark the issue resolved. If you have any follow-up questions, please reply to this thread or start a new thread.

    Thanks,
    Kemal