Tx1 Watchdog Reset

Hi, I recently faced an issue in Jetson Tx1 getting Watchdog reset and couldn’t figure out the reason for the same. The issue is very rare and don’t know how to reproduce it.

System Details :
Nvidia Tx1
JetPack 3.3.0

Linux nvidia 4.4.38-tegra #1 SMP PREEMPT Thu Mar 1 20:44:58 PST 2018 aarch64 aarch64 aarch64 GNU/Linux

#R28 (release), REVISION: 2.0, GCID: 10567845, BOARD: t210ref, EABI: aarch64, DATE: Fri Mar 2 04:58:16 UTC 2018

Logs:

Syslog Just before crash is

Jun  8 16:13:49 bot-8581 systemd[1]: Started Session 114 of user gor.
Jun  8 16:13:49 bot-8581 ofonod[658]: ofonod[658]: plugins/accounts-settings.c:get_active_seat_uid() seat seat0 with uid 1001
Jun  8 16:13:49 bot-8581 ofonod[658]: ofonod[658]: plugins/accounts-settings.c:get_active_seat_uid() seat seat0 with uid 1001
Jun  8 16:13:49 bot-8581 ofonod[658]: plugins/accounts-settings.c:get_active_seat_uid() seat seat0 with uid 1001
Jun  8 16:13:49 bot-8581 ofonod[658]: ofonod[658]: plugins/accounts-settings.c:get_active_seat_uid() seat seat0 with uid 1001
Jun  8 16:13:49 bot-8581 ofonod[658]: plugins/accounts-settings.c:get_active_seat_uid() seat seat0 with uid 1001
Jun  8 16:13:49 bot-8581 ofonod[658]: plugins/accounts-settings.c:get_active_seat_uid() seat seat0 with uid 1001


After Reboot It prints the reset reason as Watchdog

Jun  8 16:16:47 bot-8581 kernel: [    0.221320] tegra-pmc 7000e400.pmc: i2c-thermtrip node not found, emergency thermal reset disabled.
Jun  8 16:16:47 bot-8581 kernel: [    0.221365] tegra-pmc 7000e400.pmc: scratch reg offset dts data not present
Jun  8 16:16:47 bot-8581 kernel: [    0.221391] tegra-pmc: ### PMC reset source: Watchdog
Jun  8 16:16:47 bot-8581 systemd[1]: Started Update UTMP about System Boot/Shutdown.
Jun  8 16:16:47 bot-8581 kernel: [    0.221414] tegra-pmc: ### PMC reset status reg: 0x1
Jun  8 16:16:47 bot-8581 kernel: [    0.264351] padctrl padctrl.0: Pad control driver tegra-pmc-padctrl registered
Jun  8 16:16:47 bot-8581 kernel: [    0.264387] tegra-pmc: Clear bootloader IO dpd settings
Jun  8 16:16:47 bot-8581 kernel: [    0.264418] tegra-pmc 7000e400.pmc: IO padctrl driver initialized
Jun  8 16:16:47 bot-8581 kernel: [    0.264489] tegra-pmc 7000e400.pmc: PMC: Successfully configure bootrom reset commands
Jun  8 16:16:47 bot-8581 kernel: [    0.267671] platform 1003000.pcie-controller: domain=ffffffc0fa286018 allocates as[0]=ffffffc0fa17c4b8
Jun  8 16:16:47 bot-8581 kernel: [    0.269936] platform sdhci-tegra.3: domain=ffffffc0fa2db118 allocates as[0]=ffffffc0fa17c520
Jun  8 16:16:47 bot-8581 systemd[1]: Reached target System Initialization.
Jun  8 16:16:47 bot-8581 kernel: [    0.270509] platform sdhci-tegra.0: domain=ffffffc0fa2db518 allocates as[0]=ffffffc0fa17c588
Jun  8 16:16:47 bot-8581 kernel: [    0.277294] vdd-ac-bat: 5000 mV 
Jun  8 16:16:47 bot-8581 kernel: [    0.278460] vdd-cpu-fixed: 1000 mV 
Jun  8 16:16:47 bot-8581 systemd[1]: Listening on RPCbind Server Activation Socket.
Jun  8 16:16:47 bot-8581 kernel: [    0.282301] irq: no irq domain found for /soctherm@0x700E2000 !
Jun  8 16:16:47 bot-8581 wpa_supplicant[567]: Successfully initialized wpa_supplicant
Jun  8 16:16:47 bot-8581 kernel: [    0.282637] irq: no irq domain found for /soctherm@0x700E2000 !
Jun  8 16:16:47 bot-8581 kernel: [    0.305527] ACPI: Interpreter disabled.
Jun  8 16:16:47 bot-8581 kernel: [    0.306303] SCSI subsystem initialized
Jun  8 16:16:47 bot-8581 systemd[1]: Listening on OpenBSD Secure Shell server socket.

Can someone point out the cause of watchdog here?
syslog-instace1.log (279.7 KB)

It’s could be the system hang cause the watch dog trigger. Try to disable the watchdog to run your case to confirm it.

Yes, but could we know from some logs what actually caused the system hang at the first place?

Can’t tell what’s cause the hang up from the log. But from the log before reset system the latest task is relative DHCP server.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.