TX1 box reboot error

Autonomous Machines Jetson & Embedded Systems Jetson TX1
21

Is this the log you wanted to point out?
This is the only one I could think of as a fatal error.

Apr  2 19:44:04 tegra-ubuntu kernel: [  998.001443] systemd invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=0
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.011929] systemd cpuset=/ mems_allowed=0
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.017133] CPU: 1 PID: 1 Comm: systemd Not tainted 4.4.38-tegra #1
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.024187] Hardware name: jetson_tx1 (DT)
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.029055] Call trace:
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.032287] [<ffffffc000088fc8>] dump_backtrace+0x0/0xf4
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.038391] [<ffffffc0000890d0>] show_stack+0x14/0x1c
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.044294] [<ffffffc0003769ac>] dump_stack+0xac/0xe4
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.050264] [<ffffffc0001c8460>] dump_header.isra.7+0x60/0x1a4
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.056888] [<ffffffc00016fe24>] oom_kill_process+0x94/0x434
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.063335] [<ffffffc0001704dc>] out_of_memory+0x298/0x2e0
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.069615] [<ffffffc00017517c>] __alloc_pages_nodemask+0xa64/0xa8c
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.076734] [<ffffffc00016ec38>] filemap_fault+0x308/0x47c
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.083022] [<ffffffc00024af18>] ext4_filemap_fault+0x34/0x50
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.089595] [<ffffffc000196adc>] __do_fault+0x3c/0xa4
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.095443] [<ffffffc00019a5bc>] handle_mm_fault+0x764/0x154c
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.102005] [<ffffffc00009912c>] do_page_fault+0x1a8/0x454
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.108316] [<ffffffc000080b98>] do_mem_abort+0x40/0x9c
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.114339] [<ffffffc00008445c>] el0_da+0x18/0x1c
Apr  2 19:44:07 tegra-ubuntu kernel: [  998.120453] Mem-Info:
22

maybe it’s not related HDMI part,the picture is just a reference that we catch on site support.

23

Is my log in #21 the error you wanted to point out? Other reboots in your log don’t have any error log before reboot. It just reboot under a one-hour period.

24

FYI, “systemd invoked oom-killer” is not a crash, the system is running out of memory. Messages related to xusb firmware would be purely USB and not cause a reboot, but running out of memory could cause a reboot even (or especially) with the system killing processes to try to live with lack of memory (for example, the watchdog timer could fail to respond and reboot the system because what it depends on was killed in order to survive lack of memory). All of the HDMI message I can see is purely from normal operation and is not an error. I cannot see the full messages, so I can’t even speculate on why it ran out of memory.

Have you profiled memory use?

25

Do you still need our help to resolve this issue?