• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 98 subscribers
  • Views 529 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.

DRA725: The kernel crash during driving causes the car to have a black screen

HeZiJian
Prodigy 90 points
Part Number: DRA725

Kernel panic, prompting that init related boot file cannot be found, as far as I know, the init file is placed in a read-only partition, why is the data corrupted without upgrading

Please help to explain the reason for the kernel panic, thank you

The following error message is displayed：

789.84> U-Boot SPL 2016.05 (Sep 12 2023 - 18:00:41)
789.84> DRA722-GP ES2.0 DDR-1
789.90> Trying to boot from SPI
789.90> Get: magic=0x81488148 flag=0x00000000
790.04>
790.04> starting kernel ...
790.65> [ 0.001373] /cpus/cpu@0 missing clock-frequency property
790.65> [ 0.393934] dra7-pcie 51000000.pcie_rc: link is not up
790.68> [ 0.426085] panel-dpi display_fpd: failed to find video source
791.00> [ 0.740786] omap_voltage_late_init: Voltage driver support not added
791.00> [ 0.748038] ti_oppdm 4a003b20.oppdm: Unable to get vdd regulator:-517
791.54> [ 1.203799] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
791.54> [ 1.216986] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.45 #2
791.54> [ 1.222928] Hardware name: Generic DRA72X (Flattened Device Tree)
791.54> [ 1.229043] Backtrace:
791.54> [ 1.231502] Function entered at [<c0013a44>] from [<c0013c30>]
791.54> [ 1.237357] r7:00000000 r6:60000093 r5:00000000 r4:c06f293c
791.54> [ 1.243068] Function entered at [<c0013c18>] from [<c023b50c>]
791.54> [ 1.248921] Function entered at [<c023b480>] from [<c00c0604>]
791.54> [ 1.254774] r7:00000000 r6:00000000 r5:c0722ce8 r4:c0722ce8
791.54> [ 1.260484] Function entered at [<c00c0560>] from [<c0562c00>]
791.54> [ 1.266338] r3:00000000 r2:c06cbb94 r1:2efb8000 r0:c05d010c
791.54> [ 1.272043] r7:00000000
791.54> [ 1.274588] Function entered at [<c0562b0c>] from [<c000fb98>]
791.54> [ 1.280440] r5:c0562b0c r4:00000000
791.54> [ 1.284044] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
842.95: |--- Mark:01 --- COM-Error --- Date: 19.12.2023 --- Time: 15:58:25.71 ---|

  • 0
    TI__Guru**** 162450 points

    Hi,

    HeZiJian said:
    791.54> [ 1.203799] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.

    A few questions:

    • Typically you need to give something like init=/sbin/init in your bootargs. Can you share your bootargs?
    • Where is your filesystem located? Can you check if init path exists?
    • Also was it working previously & stopped failing now? If yes please check if the filesystem is corrupt and try re-flashing it.
    • Does this happen every boot?

    - Keerthy

  • 0 in reply to Keerthy J
    Prodigy 90 points

    hi Keerthy,

        Thanks for your reply, I revisited your proposal

        1、I found the project linux configuration file dra72-g5r2.dts, the bootargs in it are as shown below, but I can't find a configuration like init=/sbin/init, should these be added to the configuration?

       2、Regarding the contents of the filesystem, I did an experiment. It is to prepare a good machine with the same software version to compare with the machine in question, I exported the mmcblk2 partition data through the dd command, and then mounted it on my ubuntu, I found that the init file also exists in the bad partition.

    The file system mount directory of the problematic machine：

      

    The file system mount directory of the normal machine：

    3、Because the problem machine is black during the user's driving, I judge that init turns out to be normal, and then I don't know what factors triggered it, which caused the kernel to panic. I don't have any other ideas for this part for the time being, but I would like to ask you for advice。I've tried to re-upgrade the machine to the same software and it will work back

    4、As long as a kernel panic occurs, it is the same no matter how many times you restart。It will not be able to return to normal unless I follow the method in step 3 and overwrite the EMMC partition with an SD upgrade card

  • 0 in reply to HeZiJian
    TI__Guru**** 162450 points

    Hi,

    Yes if the init part is corrupt you won't be able to boot to kernel and hence you see the hang. So to double confirm redoing step 3 working for you right? If yes then you will need to check why eMMC or SD init is getting messed up. May be some health check but not sure on that eMMC part. So request to check with the eMMC vendor.

    Thanks! Closing this thread. Feel free to reopen if needed.

    Best Regards,

    Keerthy 

  • 0 in reply to Keerthy J
    Prodigy 90 points

    hi ，

       I agree with you, I have been in contact with the EMMC vendor about the reason for the failure. But they need me to provide the LBA for the init part, I don't know how to look it up, do you have a good suggestion over there?

  • 0 in reply to HeZiJian
    TI__Guru**** 162450 points

    Hi,

    We do not have expertise in this. A quick search: https://superuser.com/questions/1416648/about-emmc-file-block-mapping

    Please check if that helps you.

    - Keerthy

  • 0 in reply to Keerthy J
    Prodigy 90 points

    hello，

            Thanks for your approach, I seem to have found a path similar to rootfs LBA in the car machine system.

    cat ./sys/devices/platform/44000000.ocp/480b4000.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p2/start

    67584

    I query this number to output the starting logical block address of the partition.