• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 259 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.

AM4376: watchdog reset and tracing before reboot

Gunter Schmer
Genius 14202 points
Part Number: AM4376

Hi,

a customer's system is using the AM4376 and Linux 5.4 using a ti-linux-kernel.

We are running into occasional (seemingly random) watchdog resets, but do NOT see dmesg or syslog traces showing what led to the reset. There are no kernel dumps on the console either before the watchdog occurs.

We are trying to enable more tracing, and want to use the watchdog interrupt  handler or a function to print further information to the console before the watchdog reset occurs.

How could this be done?

Thanks!

--Gunter

  • 0
    TI__Guru**** 167441 points

    Hi Gunter,

    I would let the watchdog timer expert to comment about the watchdog reset. But regarding kernel dumps, it is up to the kernel modules to show any information. All kernel messages are in the kernel dmesg buffer, they may not show up on the Linux console depending on the settings of "/proc/sys/kernel/printk".

    Some kernel modules have "DEBUG" messages, but by default they likely are not enabled. It is up to the modules on how to enable the DEBUG messages, some have Kconfig options to control them, other don't, so you would have to manually modify the kernel source code to enable them, for example adding "#define DEBUG" in the beginning of a .c file.

  • 0 in reply to Bin Liu
    TI__Genius 14202 points

    Thanks, Bin. 

    We will take a look at the enabled driver debug messages, and enable some strategically.

    In the meantime, I am adding the current kernel config file. If you could take a quick look is something obvious could be enabled, that would be helpful.

    Thanks!

    --Gunter

    4213.config

  • 0 in reply to Gunter Schmer
    TI__Genius 14202 points

    Hi Bin,

    comparing the customers kernel config file, it shows all the crash dump configs we are using in the TI kernel as well. So it is surprising why the customer does not see at least a crash dump before the system resets with watchdog expiring.

    Please let us know if you see any other items that could be enabled.

    Thanks!

    --Gunter

  • 0 in reply to Gunter Schmer
    TI__Guru** 100660 points

    Hello Gunter,

    Has the customer taken a look at the excellent Linux debug training Bin put together here?
    https://training.ti.com/debugging-embedded-linux-systems-training-series

    Is there any potentially useful debug logs or terminal output that the customer has captured at this point?

    Regards,

    Nick