Xavier AGX dev kit
Jetpack - 4.3
Hello,
For the last 2 Tuesdays my Xavier has turned itself off at about 1pm, with no warning. Running deepstream at the time. not just idling.
Any ideas what it could be?
Are there any system logs I can have a look at to try and find out what’s going on?
If it was updates it wouldn’t just switch itself off completely… would it?
Thanks Chris
hello chrisdevday,
please share the logs during system reboot for reference,
you may setup a terminal to check the kernel messages,
please enable $ dmesg --follow to check instant kernel logs.
thanks
My second unit has now turned itself off as well, this one has not wiped the syslog - the end of the log is below:
Went off at 07:21
Apr 20 06:39:30 jetson-00-04-4b-cb-e4-91 dbus-daemon[4758]: [system] Activating via systemd: service name=‘org.freedesktop.fwupd’ unit=‘fwupd.service’ requested by ‘:1.103’ (uid=1000 pid=7882 comm="/usr/bin/gnome-software --gapplication-service ")
Apr 20 06:39:30 jetson-00-04-4b-cb-e4-91 systemd[1]: Starting Firmware update daemon…
Apr 20 06:39:31 jetson-00-04-4b-cb-e4-91 fwupd[12291]: 05:39:31:0088 FuEngine Failed to load SMBIOS: Failed to open file “/sys/firmware/dmi/tables/smbios_entry_point”: No such file or directory
Apr 20 06:39:31 jetson-00-04-4b-cb-e4-91 dbus-daemon[4758]: [system] Successfully activated service ‘org.freedesktop.fwupd’
Apr 20 06:39:31 jetson-00-04-4b-cb-e4-91 systemd[1]: Started Firmware update daemon.
Apr 20 06:39:31 jetson-00-04-4b-cb-e4-91 gnome-software[7882]: failed to call gs_plugin_refresh on fwupd: [/cabinet//source/fwupd/] failed to download https://cdn.fwupd.org/downloads/firmware.xml.gz.asc: Cannot connect to destination
Apr 20 06:39:31 jetson-00-04-4b-cb-e4-91 gnome-software[7882]: failed to call gs_plugin_refresh on shell-extensions: [///source/shell-extensions/] failed to download https://extensions.gnome.org//static/extensions.json: Cannot connect to destination
Apr 20 06:39:31 jetson-00-04-4b-cb-e4-91 gnome-software[7882]: failed to call gs_plugin_refresh on odrs: [///source/odrs/*] failed to download https://odrs.gnome.org/1.0/reviews/api/ratings: Cannot connect to destination
Apr 20 06:43:51 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 195.13.1.153:123 (0.pool.ntp.org).
Apr 20 06:44:02 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 109.68.160.220:123 (0.pool.ntp.org).
Apr 20 06:44:12 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 185.153.43.4:123 (0.pool.ntp.org).
Apr 20 06:44:22 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 195.130.132.19:123 (0.pool.ntp.org).
Apr 20 06:44:32 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 194.0.5.123:123 (1.pool.ntp.org).
Apr 20 06:44:43 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 129.250.35.251:123 (1.pool.ntp.org).
Apr 20 06:44:53 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 158.43.128.33:123 (1.pool.ntp.org).
Apr 20 06:45:03 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 95.215.175.2:123 (1.pool.ntp.org).
Apr 20 06:45:13 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 51.158.147.92:123 (0.fr.pool.ntp.org).
Apr 20 06:45:24 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 82.64.196.91:123 (0.fr.pool.ntp.org).
Apr 20 06:45:34 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 178.33.111.49:123 (0.fr.pool.ntp.org).
Apr 20 06:45:44 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 51.210.80.126:123 (0.fr.pool.ntp.org).
Apr 20 07:03:36 jetson-00-04-4b-cb-e4-91 systemd[1]: Started Run anacron jobs.
Apr 20 07:03:36 jetson-00-04-4b-cb-e4-91 anacron[18416]: Anacron 2.3 started on 2021-04-20
Apr 20 07:03:36 jetson-00-04-4b-cb-e4-91 anacron[18416]: Normal exit (0 jobs run)
Apr 20 07:17:01 jetson-00-04-4b-cb-e4-91 CRON[9588]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 20 07:20:03 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 45.87.77.15:123 (0.pool.ntp.org).
Apr 20 07:20:13 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 109.68.160.220:123 (0.pool.ntp.org).
Apr 20 07:20:13 jetson-00-04-4b-cb-e4-91 systemd[1]: Starting Message of the Day…
Apr 20 07:20:13 jetson-00-04-4b-cb-e4-91 systemd[1]: Started Message of the Day.
Apr 20 07:20:23 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 45.87.76.3:123 (0.pool.ntp.org).
Apr 20 07:20:33 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 94.224.67.24:123 (0.pool.ntp.org).
Apr 20 07:20:44 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 91.121.96.146:123 (1.pool.ntp.org).
Apr 20 07:20:46 jetson-00-04-4b-cb-e4-91 gnome-session[6914]: gnome-session-binary[6914]: WARNING: Client ‘/org/gnome/SessionManager/Client3’ failed to reply before timeout
Apr 20 07:20:46 jetson-00-04-4b-cb-e4-91 gnome-session-binary[6914]: WARNING: Client ‘/org/gnome/SessionManager/Client3’ failed to reply before timeout
Apr 20 07:20:54 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 143.107.229.210:123 (1.pool.ntp.org).
Apr 20 07:21:04 jetson-00-04-4b-cb-e4-91 systemd-timesyncd[13538]: Timed out waiting for reply from 85.199.214.101:123 (1.pool.ntp.org).
Apr 20 07:21:09 jetson-00-04-4b-cb-e4-91 unity-settings-[6872]: Failed to call Shutdown on session manager: Timeout was reached
Apr 20 09:37:52 jetson-00-04-4b-cb-e4-91 systemd-modules-load[2391]: Inserted module ‘bluedroid_pm’
Thanks
hello chrisdevday,
I don’t see any suspicious error according to those system logs.
did you have a chance to setup a terminal to check instant kernel logs for more details?
thanks
I’ve done that now waiting for it to happen again
what does “Failed to call Shutdown on session manager: Timeout was reached” mean?
As that was the thing to happen - and it shutdown at exactly that time
thanks
The dmesg lots are now showing a few warnings and mentions of powerdown?
[247261.707828] tegradc 15200000.nvdisplay: hdmi: tmds rate:148500K prod-setting:prod_c_hdmi_111m_223m
[247261.709336] tegradc 15200000.nvdisplay: hdmi: get RGB quant from EDID.
[247261.709343] tegradc 15200000.nvdisplay: hdmi: get YCC quant from EDID.
[247261.751291] extcon-disp-state external-connection:disp-state: cable 48 state 1
[247261.751296] Extcon AUX2(HDMI) enable
[247261.751352] tegradc 15200000.nvdisplay: unblank
[247261.751362] tegradc 15210000.nvdisplay: blank - powerdown
[247261.751369] tegradc 15220000.nvdisplay: blank - powerdown
[247261.778666] tegradc 15200000.nvdisplay: unblank
[247261.778678] tegradc 15210000.nvdisplay: blank - powerdown
[247261.778684] tegradc 15220000.nvdisplay: blank - powerdown
[247278.539473] nvmap_alloc_handle: PID 1728: ds-viewer: WARNING: All NvMap Allocations must have a tag to identify the subsystem allocating memory.Please pass the tag to the API call NvRmMemHanldeAllocAttr() or relevant.
[247307.165291] FAN cooling trip_level:1 cur_temp:54950 trip_temps[2]:63000
[247365.641637] nvmap_alloc_handle: PID 1819: ds-viewer: WARNING: All NvMap Allocations must have a tag to identify the subsystem allocating memory.Please pass the tag to the API call NvRmMemHanldeAllocAttr() or relevant.
[247394.525284] FAN rising trip_level:2 cur_temp:63350 trip_temps[3]:72000
[247684.605304] FAN rising trip_level:3 cur_temp:72000 trip_temps[4]:81000
[248224.235552] nvmap_alloc_handle: PID 17408: ds-viewer: WARNING: All NvMap Allocations must have a tag to identify the subsystem allocating memory.Please pass the tag to the API call NvRmMemHanldeAllocAttr() or relevant.
[248230.111690] usb 1-4: USB disconnect, device number 14
[248230.111704] usb 1-4.4: USB disconnect, device number 15
[248230.111712] usb 1-4.4.1: USB disconnect, device number 16
[248230.294890] usb 1-4.4.4: USB disconnect, device number 17
[248230.509015] usb usb1: usb_suspend_both: status 0
[248230.509036] tegra-xusb 3610000.xhci: entering ELPG
[248230.516398] tegra-xusb 3610000.xhci: entering ELPG done
[261147.037472] FAN cooling trip_level:2 cur_temp:63750 trip_temps[3]:72000
[261194.077270] FAN cooling trip_level:1 cur_temp:54950 trip_temps[2]:63000
[261197.067121] nvmap_alloc_handle: PID 18366: ds-viewer: WARNING: All NvMap Allocations must have a tag to identify the subsystem allocating memory.Please pass the tag to the API call NvRmMemHanldeAllocAttr() or relevant.
[261225.437443] FAN rising trip_level:2 cur_temp:63400 trip_temps[3]:72000
[289046.241495] FAN rising trip_level:3 cur_temp:72000 trip_temps[4]:81000
[290951.357248] FAN cooling trip_level:2 cur_temp:63950 trip_temps[3]:72000
hello chrisdevday,
for easy reading,
you may enable code-block to attach the logs, for example, <code>LOGs</code>
thanks
ah ok thank you
sorry
[247261.751362] tegradc 15210000.nvdisplay: blank - powerdown
[247261.751369] tegradc 15220000.nvdisplay: blank - powerdown
These logs are just to blank display drivers that are not in use. Nothing to do with the reboot of devkit.