Jetson TX2 rebooting due to corrupted rootfs - any pointers to recover it?

Hi All,
Our NVIDIA Jetson TX2 board has been rebooting continuously with the following message during startup.

Looks like the rootfs is corrupted and some mount points and files are missing from it.

Could you provide info on how the board can be recovered?

I would like to know the full approach from you so that I can bringup the board without any issues.

[ 01:00:51 ] Rootfs mounted over mmcblk0p1
mount: mount point /mnt/proc does not exist
mount: mount point /mnt/sys does not exist
mount: mount point /mnt/dev does not exist
cp: cannot create regular file ‘etc/resolv.conf’: No such file or directory
[ 01:00:51 ] Switching from initrd to actual rootfs
chroot: failed to run command ‘/sbin/init’: No such file or directory
[ 12.184351] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 12.184351]
[ 12.196525] CPU0: stopping
[ 12.200717] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.15-tegra #1
[ 12.208662] Hardware name: quill (DT)
[ 12.213805] Call trace:

[ 12.217728] [] dump_backtrace+0x0/0x100
[ 12.224595] [] show_stack+0x14/0x1c
[ 12.231069] [] dump_stack+0x90/0xb4
[ 12.237548] [] handle_IPI+0x300/0x30c
[ 12.244214] [] gic_handle_irq+0x9c/0xb4
[ 12.251042] [] el1_irq+0x68/0xd8
[ 12.257250] [] cpuidle_enter+0x18/0x20
[ 12.263977] [] call_cpuidle+0x28/0x50
[ 12.270592] [] cpu_startup_entry+0x17c/0x340
[ 12.277819] [] rest_init+0x84/0x8c
[ 12.284160] [] start_kernel+0x39c/0x3b0
[ 12.290934] [<0000000080a63000>] 0x80a63000
[ 12.296492] CPU5: stopping
[ 12.300573] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.4.15-tegra #1
[ 12.308423] Hardware name: quill (DT)
[ 12.313461] Call trace:
[ 12.317257] [] dump_backtrace+0x0/0x100
[ 12.324023] [] show_stack+0x14/0x1c
[ 12.330432] [] dump_stack+0x90/0xb4
[ 12.336827] [] handle_IPI+0x300/0x30c
[ 12.343411] [] gic_handle_irq+0x9c/0xb4
[ 12.350175] [] el1_irq+0x68/0xd8
[ 12.356344] [] cpuidle_enter+0x18/0x20
[ 12.363050] [] call_cpuidle+0x28/0x50
[ 12.369674] [] cpu_startup_entry+0x17c/0x340
[ 12.376914] [] secondary_start_kernel+0x130/0x168
[ 12.384597] [<000000008008192c>] 0x8008192c
[ 12.390203] CPU4: stopping
[ 12.394342] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 4.4.15-tegra #1

Thanks
M

Are you positive the file system didn’t just fill up? Writing necessary temp files can cause some unexpected failures when the file system is full.

First, you may be interested in cloning the root partition (the “APP” partition). You can loopback mount this and see if it is corrupt during the mount operation. If not, then you can also use “df -H” on the mount point and see if it is full. TK1 clone information is good, but the specific clone procedure differs from a TX2. The TK1 clone info is here:
http://elinux.org/Jetson/Cloning
…the TX2 procedure:
https://devtalk.nvidia.com/default/topic/1000105/jetson-tx2/tx2-cloning/

Note that there is a patch for the flash.sh there (it adds the “-G” option for cloning). There is a new release which just came out today which probably fixed this (was R27.1, today you can now flash R28.1). See:
https://developer.nvidia.com/embedded/linux-tegra-archive

When you flash you have the option of generating a new image…this is the default. You can also choose to “reuse” an old image, and this saves time. The clone can be used for the “reuse” option…if it is just a full file system then you can save everything and flash with the fixed clone.

Some cheat sheet notes for command line flash:
https://devtalk.nvidia.com/default/topic/1001583/jetson-tx2/jetson-tx2-not-recognized-installation-inside-docker-error-8-error-return-value-8-command-tegrarcm_v2-chip-0x18-rcm-rcm_list_signed-xml-skipuid-reading-board-information-failed-/post/5116716/#5116716

Much of this is done for you if you use JetPack (a front end for flash and extra package installs).

The above approach worked. Thanks for the directions!

@MoBah, has your problem returned at all? I have a similar problem and have seen it on a couple of different TX2s. I’m trying to narrow down if it is a power supply problem, a software problem or something else.

This means that the file system could not be read, or if it was read, it was incomplete or corrupt.
The “/sbin/init” executable is the first program that the kernel starts, it gets PID 1 and lives for as long as the machine is up.
If that’s not there or readable, nothing will work. The reason for it not being there/readable may be harder to figure out – but it’s typically a botched root file system.

Losing “/sbin/init” would tend to imply the file system could not be mounted at all. Don’t think of this file as being an issue, think of the entire rootfs image being unmountable and in need of repair. Which L4T version is it, e.g., R27.1 or R28.1? For R28.1 the driver package had the needed changes for cloning added to it without a need to patch flash.sh (you can check the official Documentation downloaded with R28.1 for the steps…there might be some changes versus earlier releases).

My problem was similar in that the Jetson ultimately got stuck in a reboot loop. My /sbin/init is was fine as far as I know. I’m using 27.1, but in an effort to recover some files from the Jetson in question, I did patch flash.sh and read the flash. Using fsck I found that the file system was definitely corrupted. I confirmed this by looking at the /var/log/syslog (pasted excerpt from beginning). For this particular log, the boot hung at ~15s on a line related to the USB drivers. I was able to re-flash the Jetson and use for a half day, but then it failed again when I came in the next morning… this time in a reboot loop for which I don’t currently have the flash contents. I’m starting to think I need to take a careful look at my lab power supply to see if it is causing my recurring problems with the flash.

Aug 16 18:38:38 tegra-ubuntu /usr/lib/snapd/snapd[806]: snapmgr.go:422: No snaps to auto-refresh found
Aug 16 18:38:38 tegra-ubuntu snapd[806]: 2017/08/16 18:38:38.322066 snapmgr.go:422: No snaps to auto-refresh found
Aug 16 18:38:38 tegra-ubuntu anacron[724]: Job `cron.daily' terminated
Aug 16 18:38:38 tegra-ubuntu anacron[724]: Normal exit (1 job run)
Aug 16 18:38:42 tegra-ubuntu kernel: [  323.449901] usb 1-2.3: new low-speed USB device number 5 using xhci-tegra
Aug 16 18:38:42 tegra-ubuntu kernel: [  323.566293] usb 1-2.3: New USB device found, idVendor=046d, idProduct=c077
Aug 16 18:38:42 tegra-ubuntu kernel: [  323.573301] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 16 18:38:42 tegra-ubuntu kernel: [  323.580691] usb 1-2.3: Product: USB Optical Mouse
Aug 16 18:38:43 tegra-ubuntu kernel: [  323.585518] usb 1-2.3: Manufacturer: Logitech
Aug 16 18:38:43 tegra-ubuntu kernel: [  323.590603] usb 1-2.3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
Aug 16 18:38:43 tegra-ubuntu kernel: [  323.602681] input: Logitech USB Optical Mouse as /devices/3530000.xhci/usb1/1-2/1-2.3/1-2.3:1.0/0003:046D:C077.0003/input/input6
Aug 16 18:38:43 tegra-ubuntu kernel: [  323.614666] hid-generic 0003:046D:C077.0003: input,hidraw2: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-3530000.xhci-2.3/input0
Aug 16 18:38:43 tegra-ubuntu mtp-probe: checking bus 1, device 5: "/sys/devices/3530000.xhci/usb1/1-2/1-2.3"
Aug 16 18:38:43 tegra-ubuntu mtp-probe: bus: 1, device: 5 was not an MTP device
Aug 16 18:38:51 tegra-ubuntu systemd[1]: Stopping User Manager for UID 106...
Aug 16 18:38:51 tegra-ubuntu systemd[949]: Stopped target Default.
Aug 16 18:38:51 tegra-ubuntu systemd[949]: Stopped target Basic System.
Aug 16 18:38:51 tegra-ubuntu systemd[949]: Stopped target Timers.
Aug 16 18:38:51 tegra-ubuntu systemd[949]: Stopped target Paths.
Aug 16 18:38:51 tegra-ubuntu systemd[949]: Stopped target Sockets.
Aug 16 18:38:51 tegra-ubuntu systemd[949]: Reached target Shutdown.
Aug 16 18:38:51 tegra-ubuntu systemd[949]: Starting Exit the Session...
Aug 16 18:38:51 tegra-ubuntu systemd[949]: Received SIGRTMIN+24 from PID 2630 (kill).
Aug 16 18:38:51 tegra-ubuntu systemd[1]: Stopped User Manager for UID 106.
Aug 16 18:38:51 tegra-ubuntu systemd[1]: Removed slice User Slice of lightdm.
Aug 16 18:38:54 tegra-ubuntu org.gnome.zeitgeist.Engine[1958]: Performing VACUUM operation... OK
Aug 16 18:38:54 tegra-ubuntu kernel: [  335.397767] EXT4-fs error: 12 callbacks suppressed
Aug 16 18:38:54 tegra-ubuntu kernel: [  335.402616] EXT4-fs error (device mmcblk0p1) in ext4_free_inode:383: Corrupt filesystem
Aug 16 18:38:54 tegra-ubuntu kernel: [  335.413217] EXT4-fs error (device mmcblk0p1) in ext4_free_inode:383: Corrupt filesystem
Aug 16 18:38:54 tegra-ubuntu org.gnome.zeitgeist.Engine[1958]: ** (zeitgeist-datahub:2661): WARNING **: zeitgeist-datahub.vala:229: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
Aug 16 18:38:57 tegra-ubuntu kernel: [  337.984421] EXT4-fs error (device mmcblk0p1) in ext4_free_inode:383: Corrupt filesystem
Aug 16 18:38:57 tegra-ubuntu kernel: [  337.996681] EXT4-fs error (device mmcblk0p1) in ext4_free_inode:383: Corrupt filesystem
Aug 16 18:38:57 tegra-ubuntu kernel: [  338.005995] EXT4-fs error (device mmcblk0p1) in ext4_free_inode:383: Corrupt filesystem
Aug 16 18:38:57 tegra-ubuntu kernel: [  338.015334] EXT4-fs error (device mmcblk0p1) in ext4_free_inode:383: Corrupt filesystem
Aug 16 18:39:08 tegra-ubuntu kernel: [  349.051894] EXT4-fs error (device mmcblk0p1) in ext4_free_inode:383: Corrupt filesystem
Aug 16 18:39:08 tegra-ubuntu kernel: [  349.061972] EXT4-fs error (device mmcblk0p1) in ext4_free_inode:383: Corrupt filesystem
Aug 16 18:39:08 tegra-ubuntu kernel: [  349.071291] EXT4-fs error (device mmcblk0p1) in ext4_free_inode:383: Corrupt filesystem
Aug 16 18:39:08 tegra-ubuntu kernel: [  349.080532] EXT4-fs error (device mmcblk0p1) in ext4_free_inode:383: Corrupt filesystem
Aug 16 18:39:17 tegra-ubuntu dbus[775]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Aug 16 18:38:38 tegra-ubuntu rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="738" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Aug 16 18:39:17 tegra-ubuntu rsyslogd-2007: action 'action 9' suspended, next retry is Wed Aug 16 18:39:47 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Aug 16 18:39:17 tegra-ubuntu systemd[1]: Starting Hostname Service...
Aug 16 18:39:17 tegra-ubuntu dbus[775]: [system] Successfully activated service 'org.freedesktop.hostname1'
Aug 16 18:39:17 tegra-ubuntu systemd[1]: Started Hostname Service.
Aug 16 18:39:18 tegra-ubuntu dhclient[1768]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0xd97eb148)
Aug 16 18:39:20 tegra-ubuntu org.gtk.vfs.Daemon[1958]: ** (gvfsd:2028): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Failed to retrieve share list from server: Connection refused
Aug 16 18:39:20 tegra-ubuntu org.gtk.vfs.Daemon[1958]: ** (process:2778): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Aug 16 18:39:21 tegra-ubuntu dhclient[1768]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0xd97eb148)
Aug 16 18:39:23 tegra-ubuntu org.gtk.vfs.Daemon[1958]: ** (gvfsd:2028): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Failed to retrieve share list from server: Connection refused
Aug 16 18:39:23 tegra-ubuntu org.gtk.vfs.Daemon[1958]: ** (process:2767): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Aug 16 18:39:24 tegra-ubuntu gnome-session[2084]: gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session[2084]: gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session[2084]: gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session[2084]: gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session[2084]: gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session[2084]: gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu gnome-session-binary[2084]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Save/Restore Sound Card State...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopped target Sound Card.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopped target Timers.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping User Manager for UID 1001...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopped Timer to automatically refresh installed snaps.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopped Daily apt activities.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopped target System Time Synchronized.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Daemon for power management...
Aug 16 18:39:24 tegra-ubuntu systemd[1182]: Stopped target Default.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Session 1 of user nvidia.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopped target Graphical Interface.
Aug 16 18:39:24 tegra-ubuntu systemd[1182]: Stopping Sound Service...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopped target Multi-User System.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping GPS (Global Positioning System) Daemon...
Aug 16 18:39:24 tegra-ubuntu ModemManager[774]: <info>  Caught signal, shutting down...
Aug 16 18:39:24 tegra-ubuntu pulseaudio[1189]: W: [pulseaudio] sink.c: Default and alternate sample rates are the same.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping nvcamera daemon...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Argus daemon...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Modem Manager...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Unattended Upgrades Shutdown...
Aug 16 18:39:24 tegra-ubuntu pulseaudio[1189]: W: [pulseaudio] module.c: After module unload, module 'module-null-sink' was still loaded!
Aug 16 18:39:24 tegra-ubuntu systemd[1182]: Stopped Sound Service.
Aug 16 18:39:24 tegra-ubuntu systemd[1182]: Reached target Shutdown.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Make remote CUPS printers available locally...
Aug 16 18:39:24 tegra-ubuntu systemd[1182]: Starting Exit the Session...
Aug 16 18:39:24 tegra-ubuntu systemd[1182]: Stopped target Basic System.
Aug 16 18:39:24 tegra-ubuntu systemd[1182]: Stopped target Paths.
Aug 16 18:39:24 tegra-ubuntu systemd[1182]: Stopped target Timers.
Aug 16 18:39:24 tegra-ubuntu systemd[1182]: Stopped target Sockets.
Aug 16 18:39:24 tegra-ubuntu systemd[1182]: Received SIGRTMIN+24 from PID 2812 (kill).
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Regular background program processing daemon...
Aug 16 18:39:24 tegra-ubuntu NetworkManager[788]: <info>  [1502908764.7563] ModemManager disappeared from bus
Aug 16 18:39:24 tegra-ubuntu ModemManager[774]: <info>  ModemManager is shut down
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping OpenBSD Secure Shell server...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopped target Login Prompts.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Getty on tty1...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping LSB: Speech Dispatcher...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping LSB: automatic crash report generation...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Serial Getty on ttyS0...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Hostname Service...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Authenticate and Authorize Users to Run Privileged Tasks...
Aug 16 18:39:24 tegra-ubuntu dbus[775]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Accounts Service...
Aug 16 18:39:24 tegra-ubuntu ofonod[802]: ofonod[802]: Terminating
Aug 16 18:39:24 tegra-ubuntu ofonod[802]: Terminating
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping oFono Mobile telephony stack...
Aug 16 18:39:24 tegra-ubuntu ofonod[802]: ofonod[802]: Exit
Aug 16 18:39:24 tegra-ubuntu ofonod[802]: Exit
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping Session c2 of user nvidia.
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping crash report submission daemon...
Aug 16 18:39:24 tegra-ubuntu org.gnome.zeitgeist.SimpleIndexer[1958]: ** (zeitgeist-fts:2659): WARNING **: zeitgeist-fts.vala:252: The connection is closed
Aug 16 18:39:24 tegra-ubuntu org.gnome.zeitgeist.Engine[1958]: (zeitgeist-daemon:2652): GLib-GIO-WARNING **: Error releasing name org.gnome.zeitgeist.Engine: The connection is closed
Aug 16 18:39:24 tegra-ubuntu org.gnome.zeitgeist.Engine[1958]: #033[31m[18:39:24.914718 WARNING]#033[0m zeitgeist-daemon.vala:449: The connection is closed
Aug 16 18:39:24 tegra-ubuntu systemd[1]: Stopping System Logging Service...
Aug 16 18:39:24 tegra-ubuntu rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="738" x-info="http://www.rsyslog.com"] exiting on signal 15.
Aug 16 18:39:28 tegra-ubuntu rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="747" x-info="http://www.rsyslog.com"] start
Aug 16 18:39:28 tegra-ubuntu rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Aug 16 18:39:28 tegra-ubuntu rsyslogd: rsyslogd's groupid changed to 115
Aug 16 18:39:28 tegra-ubuntu rsyslogd: rsyslogd's userid changed to 108
Aug 16 18:39:28 tegra-ubuntu systemd-modules-load[217]: Inserted module 'bluedroid_pm'
Aug 16 18:39:28 tegra-ubuntu systemd-modules-load[217]: Module 'nvhost_vi' is builtin
Aug 16 18:39:28 tegra-ubuntu loadkeys[214]: Loading /etc/console-setup/cached.kmap.gz
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Create list of required static device nodes for the current kernel.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Remount Root and Kernel File Systems.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Set console keymap.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Booting Linux on physical CPU 0x100
Aug 16 18:39:28 tegra-ubuntu rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Initializing cgroup subsys cpuset
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Load Kernel Modules.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Initializing cgroup subsys cpu
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Initializing cgroup subsys cpuacct
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started LVM2 metadata daemon.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Linux version 4.4.15-koi (root@tegra-ubuntu) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #1 SMP PREEMPT Wed Jul 12 23:03:10 UTC 2017
Aug 16 18:39:28 tegra-ubuntu rsyslogd-2007: action 'action 9' suspended, next retry is Wed Aug 16 18:39:58 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Apply Kernel Variables...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Boot CPU: AArch64 Processor [411fd073]
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] earlycon: Early serial console at MMIO32 0x3100000 (options '')
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] bootconsole [uart0] enabled
Aug 16 18:39:28 tegra-ubuntu systemd-sysctl[227]: Couldn't write '1' to 'kernel/yama/ptrace_scope', ignoring: No such file or directory
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Reserved memory: initialized node vpr-carveout, compatible id nvidia,vpr-carveout
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Reserved memory: initialized node ramoops_carveout, compatible id nvidia,ramoops
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] cma: Reserved 64 MiB at 0x00000000f2000000
Aug 16 18:39:28 tegra-ubuntu systemd-sysctl[227]: Couldn't write '1' to 'net/ipv4/tcp_syncookies', ignoring: No such file or directory
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] On node 0 totalpages: 2051584
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]   DMA zone: 7488 pages used for memmap
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]   DMA zone: 0 pages reserved
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Mounting Configuration File System...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]   DMA zone: 479232 pages, LIFO batch:31
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]   Normal zone: 24576 pages used for memmap
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]   Normal zone: 1572352 pages, LIFO batch:31
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting udev Coldplug all Devices...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] psci: probing for conduit method from DT.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] psci: PSCIv1.0 detected in firmware.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] psci: Using standard PSCI v0.2 function IDs
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Load/Save Random Seed...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] psci: MIGRATE_INFO_TYPE not supported.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] PERCPU: Embedded 17 pages/cpu @ffffffc1ffd13000 s31000 r8192 d30440 u69632
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Create Static Device Nodes in /dev...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] pcpu-alloc: s31000 r8192 d30440 u69632 alloc=17*4096
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Flush Journal to Persistent Storage...
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Mounted Configuration File System.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Apply Kernel Variables.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 2019520
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Load/Save Random Seed.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Kernel command line: fbcon=map:0 net.ifnames=0 console=tty0 OS=l4t console=ttyS0,115200n8 memtype=0 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x03100000 gpt tegraid=18.1.2.0.0 tegra_keep_boot_clocks maxcpus=6 android.kerneltype=normal androidboot.serialno=0335115020673 vpr_resize root=/dev/mmcblk0p1 rw rootwait
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Create Static Device Nodes in /dev.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Memory: 7286652K/8206336K available (10348K kernel code, 1660K rwdata, 5408K rodata, 1116K init, 679K bss, 166020K reserved, 753664K cma-reserved)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Virtual kernel memory layout:
Aug 16 18:39:28 tegra-ubuntu lvm[221]:   /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]     vmalloc : 0xffffff8000000000 - 0xffffffbdbfff0000   (   246 GB)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]     vmemmap : 0xffffffbdc0000000 - 0xffffffbfc0000000   (     8 GB maximum)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]               0xffffffbdc2000000 - 0xffffffbdca000000   (   128 MB actual)
Aug 16 18:39:28 tegra-ubuntu lvm[221]:   /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]     fixed   : 0xffffffbffa7fd000 - 0xffffffbffac00000   (  4108 KB)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]     PCI I/O : 0xffffffbffae00000 - 0xffffffbffbe00000   (    16 MB)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]     modules : 0xffffffbffc000000 - 0xffffffc000000000   (    64 MB)
Aug 16 18:39:28 tegra-ubuntu lvm[221]:   /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]     memory  : 0xffffffc000000000 - 0xffffffc200000000   (  8192 MB)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]       .init : 0xffffffc000fe4000 - 0xffffffc0010fb000   (  1116 KB)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]       .text : 0xffffffc000080000 - 0xffffffc000fe4000   ( 15760 KB)
Aug 16 18:39:28 tegra-ubuntu lvm[221]:   /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000]       .data : 0xffffffc00111a000 - 0xffffffc0012b90b0   (  1661 KB)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Preemptible hierarchical RCU implementation.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] 	Build-time adjustment of leaf fanout to 64.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=6.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=6
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting udev Kernel Device Manager...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] NR_IRQS:64 nr_irqs:64 0
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] GIC: Using split EOI/Deactivate mode
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] Architected cp15 timer(s) running at 31.25MHz (phys).
Aug 16 18:39:28 tegra-ubuntu systemd-udevd[241]: Network interface NamePolicy= disabled on kernel command line, ignoring.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xe6a171046, max_idle_ns: 881590405314 ns
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.000002] sched_clock: 56 bits at 31MHz, resolution 32ns, wraps every 4398046511088ns
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.008779] tegra-id: chipid=21817.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Reached target Local File Systems (Pre).
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.012563] tegra-id: opt_subrevision=1.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.017137] Console: colour dummy device 80x25
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.022086] console [tty0] enabled
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.025618] kmemleak: Kernel memory leak detector disabled
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Reached target Local File Systems.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.031318] Calibrating delay loop (skipped), value calculated using timer frequency.. 62.50 BogoMIPS (lpj=125000)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.042070] pid_max: default: 32768 minimum: 301
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.046894] Security Framework initialized
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.051166] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.058307] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Clean up any mess left by 0dns-up...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.066240] Initializing cgroup subsys freezer
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.070862] Initializing cgroup subsys debug
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting LSB: AppArmor initialization...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.075417] CPU0 ipc=752
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.078054] CPU1 ipc=1024
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.080769] CPU2 ipc=1024
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Set console font and keymap...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.083489] CPU3 ipc=752
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.086120] CPU4 ipc=752
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.088746] CPU5 ipc=752
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.091403] ASID allocator initialised with 65536 entries
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started udev Kernel Device Manager.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.133765] CPU1: Booted secondary processor [4e0f0030]
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.145371] CPU2: Booted secondary processor [4e0f0030]
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Flush Journal to Persistent Storage.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.157176] CPU3: Booted secondary processor [411fd073]
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.169170] CPU4: Booted secondary processor [411fd073]
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.181164] CPU5: Booted secondary processor [411fd073]
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.181208] Brought up 6 CPUs
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.211425] SMP: Total of 6 processors activated.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started udev Coldplug all Devices.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.216313] CPU: All CPU(s) started at EL2
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Found device /dev/ttyS0.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.220935] devtmpfs: initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.240367] Initilizing CustomIPI irq domain
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Create Volatile Files and Directories...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.245003] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.266265] pinctrl core: initialized pinctrl subsystem
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Aug 16 18:39:28 tegra-ubuntu systemd-tmpfiles[300]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.272102] OS set in device tree is L4T.
Aug 16 18:39:28 tegra-ubuntu systemd-udevd[258]: Could not generate persistent MAC address for dummy0: No such file or directory
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.276800] regulator-dummy: no parameters
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.281328] Initializing plugin-manager
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.285401] Plugin module not found
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started LSB: AppArmor initialization.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.289430] node /plugin-manager/soc-prod-a02-fragment match with chip-id A02P
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.297348] node /plugin-manager/fragement@0 match with odm-data enable-tegra-wdt
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Clean up any mess left by 0dns-up.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.305746] node /plugin-manager/fragement@4 match with odm-data enable-tegra-wdt
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.314320] node /plugin-manager/fragment-sdwake-p3310-1000-300 match with board >=3310-1000-300
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.323876] node /plugin-manager/fragement-pmon-p3310-1000-300 match with board >=3310-1000-300
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.333208] node /plugin-manager/fragement-pmon-p3310-1000-800 match with board >=3310-1000-800
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.342535] node /plugin-manager/fragment-devslp@0 match with board >=3310-1000-200
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.350841] node /plugin-manager/fragment-500-pcie-config match with board >=3310-1000-500
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.359783] node /plugin-manager/fragment-500-e3325-pcie match with board >=3310-1000-500
Aug 16 18:39:28 tegra-ubuntu systemd-udevd[259]: Process '/lib/udev/hdparm' failed with exit code 5.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.368420] node /plugin-manager/fragment-p3310-c00-comm match with board >=3310-1000-800
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.377181] node /plugin-manager/fragment-p3310-c01 match with board >=3310-1000-900
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.385489] node /plugin-manager/fragment-p3310-c03 match with board >=3310-1000-B00
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.396140] Adding domain adsp-pd to PM domain ape-pd
Aug 16 18:39:28 tegra-ubuntu systemd-udevd[274]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.405091] NET: Registered protocol family 16
Aug 16 18:39:28 tegra-ubuntu systemd-udevd[267]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.411264] console [pstore-1] enabled
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.415214] pstore: Registered ramoops as persistent store backend
Aug 16 18:39:28 tegra-ubuntu systemd-udevd[260]: Process '/bin/rm /var/lib/alsa/asound.state' failed with exit code 1.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.421702] ramoops: attached 0x200000@0x100000000, ecc: 0/0
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.433783] cpuidle: using governor ladder
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.445779] cpuidle: using governor menu
Aug 16 18:39:28 tegra-ubuntu mtp-probe: checking bus 1, device 4: "/sys/devices/3530000.xhci/usb1/1-2/1-2.2"
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.451332] bpmp: waiting for handshake
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.455346] bpmp: handshake completed
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.459235] bpmp: synchronizing channels
Aug 16 18:39:28 tegra-ubuntu mtp-probe: checking bus 1, device 3: "/sys/devices/3530000.xhci/usb1/1-2/1-2.1"
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.463338] bpmp: channels synchronized
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.467372] bpmp: connect returned 0
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.471530] tegra186-pmc device create success
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.476180] scratch reg offset dts data not present
Aug 16 18:39:28 tegra-ubuntu mtp-probe: bus: 1, device: 3 was not an MTP device
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.481370] padctrl padctrl.0: Pad control driver tegra-pmc-padctrl registered
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.488906] PMC: configuring io pad defaults
Aug 16 18:39:28 tegra-ubuntu mtp-probe: bus: 1, device: 4 was not an MTP device
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.493400] T186 pmc padctrl driver initialized
Aug 16 18:39:28 tegra-ubuntu mtp-probe: checking bus 1, device 5: "/sys/devices/3530000.xhci/usb1/1-2/1-2.3"
Aug 16 18:39:28 tegra-ubuntu mtp-probe: bus: 1, device: 5 was not an MTP device
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Reached target Sound Card.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Raise network interfaces...
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Create Volatile Files and Directories.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Set console font and keymap.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Created slice system-getty.slice.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Load/Save RF Kill Switch Status...
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Network Time Synchronization...
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 16 18:39:28 tegra-ubuntu systemd-timesyncd[708]: System clock time unset or jumped backwards, restoring from recorded timestamp: Wed 2017-08-16 18:39:28 UTC
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Network Time Synchronization.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Time has been changed
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Reached target System Time Synchronized.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Reached target System Initialization.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.498130] ### PMC reset source: Power on reset
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Listening on CUPS Scheduler.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.502945] ### PMC reset level: L0
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.506584] ### PMC reset status reg: 0x0
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.511516] vdso: 2 pages (1 code @ ffffffc001121000, 1 data @ ffffffc001120000)
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Daily Cleanup of Temporary Directories.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.519278] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.527825] atomic_pool_init():526: DMA: preallocated 1024 KiB pool for atomic allocations
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.537986] tegra_powergate_init: DONE
Aug 16 18:39:28 tegra-ubuntu systemd[1]: apt-daily.timer: Adding 2h 3min 56.342929s random time.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.542056] DTS File Name: /usr/parker/linux4tegra/branches/27.1/Linux_for_Tegra_tx2/sources/kernel_source/kernel-4.4/arch/arm64/boot/dts/../../../../../../hardware/nvidia/platform/t18x/quill/kernel-dts/tegra186-tx2-cti-ASG001-base.dts
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.563794] DTB Build time: <unknown>
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.569023] Tegra reboot handler registered.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Daily apt activities.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Listening on RPCbind Server Activation Socket.
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started CUPS Scheduler.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.574437] Registering Tegra186 clocks (this may take a while)...done
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.582671] arm-smmu 12000000.iommu: probing hardware configuration...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.589510] arm-smmu 12000000.iommu: SMMUv2 with:
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Reached target Paths.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.594423] arm-smmu 12000000.iommu: 	stage 1 translation
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.600077] arm-smmu 12000000.iommu: 	stage 2 translation
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Listening on D-Bus System Message Bus Socket.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.605729] arm-smmu 12000000.iommu: 	nested translation
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.611307] arm-smmu 12000000.iommu: 	stream matching with 128 register groups, mask 0x7f80
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.620057] arm-smmu 12000000.iommu: SMMU address space size (0x800000) differs from mapped region size (0x1000000)!
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.631034] arm-smmu 12000000.iommu: 	64 context banks (0 stage-2 only)
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Listening on GPS (Global Positioning System) Daemon Sockets.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.637932] arm-smmu 12000000.iommu: 	Stage-1: 39-bit VA -> 48-bit IPA
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.644738] arm-smmu 12000000.iommu: 	Stage-2: 39-bit IPA -> 48-bit PA
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.681651] arm-smmu 12000000.iommu: registered 66 master devices
Aug 16 18:39:28 tegra-ubuntu systemd[1]: snapd.refresh.timer: Adding 3h 38min 51.410652s random time.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.691532] iommu: Adding device 3460000.sdhci to group 0
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.697701] iommu: Adding device 3400000.sdhci to group 1
Aug 16 18:39:28 tegra-ubuntu systemd[1]: snapd.refresh.timer: Adding 5min 22.969222s random time.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.705978] iommu: Adding device 3507000.ahci-sata to group 2
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.712340] iommu: Adding device 3160000.i2c to group 3
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Started Timer to automatically refresh installed snaps.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.718102] iommu: Adding device c240000.i2c to group 4
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.723794] iommu: Adding device 3180000.i2c to group 5
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Reached target Timers.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.729500] iommu: Adding device 3190000.i2c to group 6
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.735314] iommu: Adding device 31b0000.i2c to group 7
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.741054] iommu: Adding device 31c0000.i2c to group 8
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.746764] iommu: Adding device c250000.i2c to group 9
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting Socket activation for snappy daemon.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.752494] iommu: Adding device 31e0000.i2c to group 10
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.759799] iommu: Adding device 3210000.spi to group 11
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.765623] iommu: Adding device c260000.spi to group 12
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Listening on Socket activation for snappy daemon.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.771447] iommu: Adding device 3240000.spi to group 13
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.777627] iommu: Adding device 3100000.serial to group 14
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.783707] iommu: Adding device 3110000.serial to group 15
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.789803] iommu: Adding device c280000.serial to group 16
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Reached target Sockets.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.795871] iommu: Adding device 3130000.serial to group 17
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.802599] iommu: Adding device 2490000.ether_qos to group 18
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.809260] iommu: Adding device b000000.rtcpu to group 19
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.815697] Wake73 for irq=42
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Reached target Basic System.
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.819085] iommu: Adding device smmu_test to group 20
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.824889] mc: mapped MMIO address: 0xffffff8000560000 -> 0x2c10000
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.831578] mc: mapped MMIO address: 0xffffff8000640000 -> 0x2c20000
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.838243] mc: mapped MMIO address: 0xffffff8000660000 -> 0x2c30000
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting System Logging Service...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.844903] mc: mapped MMIO address: 0xffffff8000fa0000 -> 0x2c40000
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.851581] mc: mapped MMIO address: 0xffffff8000fc0000 -> 0x2c50000
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.858229] mc-err: Set intmask: 0xf3140
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.862537] dram-ecc: DRAM ECC disabled-MC_ECC_CONTROL:0x0000000c
Aug 16 18:39:28 tegra-ubuntu systemd[1]: Starting NVIDIA specific script...
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.869394] Wake76 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.872578] Wake77 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.875759] Wake78 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.878936] Wake79 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.882117] Wake80 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.885303] Wake81 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.888484] Wake82 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.891794] iommu: Adding device 3530000.xhci to group 21
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.897722] iommu: Adding device 3550000.xudc to group 22
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.904042] tegra186-aowake c370000.pmc: WAKE_AOWAKE_CTRL_0 = 3
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.910232] tegra186-aowake c370000.pmc: WAKE_AOWAKE_CNTRL_24(PMU_INT) = 320
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.917989] iommu: Adding device 13e10000.host1x to group 23
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.924137] iommu: Adding device 13e10000.host1x:ctx0 to group 24
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.930692] iommu: Adding device 13e10000.host1x:ctx1 to group 25
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.937268] iommu: Adding device 13e10000.host1x:ctx2 to group 26
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.943844] iommu: Adding device 13e10000.host1x:ctx3 to group 27
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.950427] iommu: Adding device 13e10000.host1x:ctx4 to group 28
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.956991] iommu: Adding device 13e10000.host1x:ctx5 to group 29
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.963552] iommu: Adding device 13e10000.host1x:ctx6 to group 30
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.970118] iommu: Adding device 13e10000.host1x:ctx7 to group 31
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.976839] iommu: Adding device 150c0000.nvcsi to group 32
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.983190] iommu: Adding device 15700000.vi to group 33
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.988996] iommu: Adding device 15600000.isp to group 34
Aug 16 18:39:28 tegra-ubuntu kernel: [    0.994934] iommu: Adding device 15210000.nvdisplay to group 35
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.001298] iommu: Adding device 15340000.vic to group 36
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.007108] iommu: Adding device 154c0000.nvenc to group 37
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.013101] iommu: Adding device 15480000.nvdec to group 38
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.019166] iommu: Adding device 15380000.nvjpg to group 39
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.025159] iommu: Adding device 15500000.tsec to group 40
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.031115] iommu: Adding device 15100000.tsecb to group 41
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.037522] iommu: Adding device 15810000.se to group 42
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.043266] iommu: Adding device 15820000.se to group 43
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.048987] iommu: Adding device 15830000.se to group 44
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.054709] iommu: Adding device 15840000.se to group 45
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.060663] iommu: Adding device 17000000.gp10b to group 46
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.067519] tegra-reset 5000000.clock: registered 193 resets.
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.074681] iommu: Adding device d000000.bpmp to group 47
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.080565] bpmp: ping status is 0
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.084275] bpmp d000000.bpmp: firmware tag is c11dd04ae487c849cc552f8f702ed830
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.093988] iommu: Adding device 2600000.dma to group 48
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.100181] GPIO line 461 (cam0-rst) hogged as output/low
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.105864] GPIO line 456 (cam0-pwdn) hogged as output/low
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.111636] GPIO line 424 (wifi-enable) hogged as output/high
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.117671] GPIO line 445 (sdmmc-wake-input) hogged as input
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.123618] GPIO line 446 (sdmmc-wake-output) hogged as output/low
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.130170] gpiochip_add_data: registered GPIOs 320 to 511 on device: tegra-gpio
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.139522] GPIO line 315 (wifi-wake-ap) hogged as input
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.145170] gpiochip_add_data: registered GPIOs 256 to 319 on device: tegra-gpio-aon
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.154002] iommu: Adding device 10003000.pcie-controller to group 49
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.160930] iommu: Adding device sound to group 50
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.167269] iommu: Adding device 3510000.hda to group 51
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.173712] iommu: Adding device adsp_audio to group 52
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.180373] iommu: Adding device 2993000.adsp to group 53
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.192035] iommu: Adding device c160000.aon to group 54
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.199723] vdd-ac-bat: 5000 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.204912] vdd-1v8-ap: 1800 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.209162] gpio tegra-gpio-aon wake30 for gpio=60(FF:4)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.214982] gpio tegra-gpio-aon wake69 for gpio=59(FF:3)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.236079] SCSI subsystem initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.240189] libata version 3.00 loaded.
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.240349] usbcore: registered new interface driver usbfs
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.246157] usbcore: registered new interface driver hub
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.251813] usbcore: registered new device driver usb
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.259437] tegra-i2c 3160000.i2c: no acknowledge from address 0x74
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.266424] pca953x 0-0074: failed reading register
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.271599] pca953x: probe of 0-0074 failed with error -121
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.277652] tegra-i2c 3160000.i2c: no acknowledge from address 0x77
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.284622] pca953x 0-0077: failed reading register
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.289802] pca953x: probe of 0-0077 failed with error -121
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.295811] tps65132 0-003e: No active discharge gpio for regulator tps65132-outp
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.303785] tegra-i2c 3160000.i2c: no acknowledge from address 0x3e
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.310886] tegra-i2c 3160000.i2c: no acknowledge from address 0x3e
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.317856] outp: 4000 <--> 6000 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.321645] tps65132 0-003e: No active discharge gpio for regulator tps65132-outn
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.329634] tegra-i2c 3160000.i2c: no acknowledge from address 0x3e
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.336677] tegra-i2c 3160000.i2c: no acknowledge from address 0x3e
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.343660] outn: 4000 <--> 6000 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.357695] media: Linux media interface: v0.10
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.362508] Linux video capture interface: v2.00
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.371058] pps_core: LinuxPPS API ver. 1 registered
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.376261] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.385836] PTP clock support registered
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.391496] Tegra WDT setup timeout = 120 seconds.
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.396532] tegra_wdt_t18x 30c0000.watchdog: tegra_wdt_t18x_probe done
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.404767] max77620 4-003c: PMIC Version OTP:0x45 and ES:0x8
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.412608] GPIO line 253 (spmic_gpio_input_5) hogged as input
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.418912] GPIO line 254 (spmic_gpio_input_6) hogged as input
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.425103] gpiochip_add_data: registered GPIOs 248 to 255 on device: max77620-gpio
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.437929] vddio-ddr: at 1125 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.445781] avdd_dsi_csi: 1200 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.453779] vdd-1v8: 1800 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.461778] vdd-3v3-sys: 3300 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.466274] spmic-ldo0: at 1800 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.470694] spmic-ldo1: at 800 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.477781] vddio-3v3: 3300 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.481675] vddio-sdmmc1: 1800 <--> 3300 mV at 3300 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.489780] vdd-rtc: 1000 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.493623] avdd-ts-hv: 1800 <--> 3300 mV at 1800 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.501782] spmic-ldo6: at 1500 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.506146] vdd-pex-1v05: 1000 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.510261] dvdd-pex: 1000 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.513784] max77620 4-003c: max77620 probe successful
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.519449] Advanced Linux Sound Architecture Driver Initialized.
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.527285] en-vdd-sd: 3300 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.530878] vdd-usb0-5v: 5000 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.534550] vdd-usb1-5v: 5000 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.538521] vdd-3v3: 3300 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.541813] en-vdd-vcm-2v8: 2800 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.545750] vdd-sys-bl: 3300 mV 
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.550113] gpio tegra-gpio wake53 for gpio=159(X:5)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.557040] extcon-gpio-states external-connection:extcon@1: Cable state 1
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.564662] clocksource: Switched to clocksource arch_sys_counter
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.600392] nvmap_heap_init: nvmap_heap_init: created heap block cache
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.607466] dma_declare_coherent_resizable_cma_memory:288: resizable heap=vpr, base=0x00000000ae000000, size=0x2a000000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.616070] Wake76 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.616075] Wake77 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.616077] Wake78 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.616078] Wake79 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.616080] Wake80 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.616082] Wake81 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.616084] Wake82 for irq=199
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.617271] thermal thermal_zone0: Registering thermal zone thermal_zone0 for type BCPU-therm
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.617489] thermal thermal_zone1: Registering thermal zone thermal_zone1 for type MCPU-therm
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.617603] thermal thermal_zone2: Registering thermal zone thermal_zone2 for type GPU-therm
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.617673] thermal thermal_zone3: Registering thermal zone thermal_zone3 for type PLL-therm
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.617988] thermal thermal_zone4: Registering thermal zone thermal_zone4 for type AO-therm
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.618176] thermal thermal_zone5: Registering thermal zone thermal_zone5 for type Tboard_tegra
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.618335] thermal thermal_zone6: Registering thermal zone thermal_zone6 for type Tdiode_tegra
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.618496] thermal thermal_zone7: Registering thermal zone thermal_zone7 for type PMIC-Die
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.618522] isomgr_init(): iso emc max clk=1866000KHz
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.618525] isomgr_init(): max_iso_bw=26870400KB
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.618739] tegra186-pmc-iopower pmc-iopower: Rail iopower-sys is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.618796] tegra186-pmc-iopower pmc-iopower: Rail iopower-uart is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.618849] tegra186-pmc-iopower pmc-iopower: Rail iopower-conn is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.618901] tegra186-pmc-iopower pmc-iopower: Rail iopower-edp is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.618961] tegra186-pmc-iopower pmc-iopower: Rail iopower-pex-ctrl-audio is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619013] tegra186-pmc-iopower pmc-iopower: Rail iopower-ufs is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619077] tegra186-pmc-iopower pmc-iopower: Rail iopower-ddr0 is having fixed voltage 0
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619118] tegra186-pmc-iopower pmc-iopower: Rail iopower-ddr1 is having fixed voltage 0
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619160] tegra186-pmc-iopower pmc-iopower: Rail iopower-csi-dsi is having fixed voltage 1200000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619212] tegra186-pmc-iopower pmc-iopower: Rail iopower-cam is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619265] tegra186-pmc-iopower pmc-iopower: Rail iopower-sdmmc4 is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619352] tegra186-pmc-iopower pmc-iopower: Rail iopower-sdmmc1-hv is having voltages: 1800000:3300000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619421] tegra186-pmc-iopower pmc-iopower: Rail iopower-audio-hv is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619506] tegra186-pmc-iopower pmc-iopower: Rail iopower-dbg is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619560] tegra186-pmc-iopower pmc-iopower: Rail iopower-spi is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619612] tegra186-pmc-iopower pmc-iopower: Rail iopower-ao is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619658] tegra186-pmc-iopower pmc-iopower: Rail iopower-ao-hv is having fixed voltage 3300000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619713] tegra186-pmc-iopower pmc-iopower: Rail iopower-dmic-hv is having fixed voltage 1800000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619766] tegra186-pmc-iopower pmc-iopower: Rail iopower-sdmmc2-hv is having fixed voltage 3300000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619812] tegra186-pmc-iopower pmc-iopower: Rail iopower-sdmmc3-hv is having voltages: 1800000:3300000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.619821] tegra186-pmc-iopower pmc-iopower: NO_IO_POWER setting 0x00000000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.620093] NET: Registered protocol family 2
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.620764] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.621430] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.622188] TCP: Hash tables configured (established 65536 bind 65536)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.622232] UDP hash table entries: 4096 (order: 5, 131072 bytes)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.622379] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.622701] NET: Registered protocol family 1
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.623074] RPC: Registered named UNIX socket transport module.
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.623076] RPC: Registered udp transport module.
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.623079] RPC: Registered tcp transport module.
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.623081] RPC: Registered tcp NFSv4.1 backchannel transport module.
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.623118] PCI: CLS 0 bytes, default 128
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.638167] host1x 13e10000.host1x: initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.640933] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.641886] futex hash table entries: 2048 (order: 6, 262144 bytes)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.642022] audit: initializing netlink subsys (disabled)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.642055] audit: type=2000 audit(1.600:1): initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.649991] io scheduler noop registered (default)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.655398] Adding domain tsec-pd to PM domain host-pd
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.657551] tsec 15500000.tsec: initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.658883] tsec 15100000.tsecb: initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.659178] Adding domain nvdec-pd to PM domain host-pd
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.660870] nvdec 15480000.nvdec: initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.661294] Adding domain vic03-pd to PM domain host-pd
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.661312] Adding domain msenc-pd to PM domain host-pd
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.661328] Adding domain nvjpg-pd to PM domain host-pd
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.664428] falcon 15340000.vic: initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.665698] falcon 154c0000.nvenc: initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.666886] falcon 15380000.nvjpg: initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.667938] iommu_context_dev 13e10000.host1x:ctx0: initialized (streamid=56)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.668707] iommu_context_dev 13e10000.host1x:ctx1: initialized (streamid=57)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.669439] iommu_context_dev 13e10000.host1x:ctx2: initialized (streamid=58)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.670179] iommu_context_dev 13e10000.host1x:ctx3: initialized (streamid=59)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.670883] iommu_context_dev 13e10000.host1x:ctx4: initialized (streamid=60)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.671613] iommu_context_dev 13e10000.host1x:ctx5: initialized (streamid=61)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.672360] iommu_context_dev 13e10000.host1x:ctx6: initialized (streamid=62)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.673170] iommu_context_dev 13e10000.host1x:ctx7: initialized (streamid=63)
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.674606] tegradc 15210000.nvdisplay: Display dc.15210000 registered with id=0
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.674613] DC OR NODE connected to /host1x/sor1
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.674692] parse_tmds_config: No tmds-config node
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.674721] tegra_camera_platform tegra-camera-platform: tegra_camera_probe:camera_platform_driver probe
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.674765] tegradc 15210000.nvdisplay: DT parsed successfully
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.674913] misc tegra_camera_ctrl: tegra_camera_isomgr_register: some fields not in DT.
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.674921] misc tegra_camera_ctrl: tegra_camera_isomgr_register isp_iso_bw=0, vi_iso_bw=1500000, max_bw=1500000
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.681551] tegra_nvdisp_bandwidth_register_max_config: max config iso bw = 16727000 KB/s
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.681553] tegra_nvdisp_bandwidth_register_max_config: max config EMC floor = 665600000 Hz
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.681555] tegra_nvdisp_bandwidth_register_max_config: max config hubclk = 357620000 Hz
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.681584] tegradc 15210000.nvdisplay: vblank syncpt # 7 for dc 1
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.681588] tegradc 15210000.nvdisplay: vpulse3 syncpt # 8 for dc 1
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.683378] tegra-adma 2930000.adma: Tegra ADMA driver register 10 channels
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.683785] PD DISP0 index2 UP
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.683878] tegra-fuse-burn 3820000.efuse:efuse-burn: Fuse burn driver initialized
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.684191] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.684196] PD DISP1 index3 UP
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.684283] PD DISP2 index4 UP
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.686371] console [ttyS0] disabled
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.710848] PD DISP2 index4 DOWN
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.710938] PD DISP1 index3 DOWN
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.711018] PD DISP0 index2 DOWN
Aug 16 18:39:28 tegra-ubuntu kernel: [    1.712430] tegradc 15210000.nvdisplay: probed
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.267247] 3100000.serial: ttyS0 at MMIO 0x3100000 (irq = 36, base_baud = 25500000) is a Tegra
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.267296] cma: enabled page replacement for spfn=ae000, epfn=d8000
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.267307] dma_declare_coherent_resizable_cma_memory:335: resizable cma heap=vpr create successful
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.267307] nvmap_page_pool_init: Total RAM pages: 2010079
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.267312] nvmap_page_pool_init: nvmap page pool size: 251259 pages (981 MB)
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.267409] nvmap_background_zero_thread: PP zeroing thread starting.
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.267886] misc nvmap: created heap vpr base 0x00000000ae000000 size (688128KiB)
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.276599] Console: switching to colour frame buffer device 240x75
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.344854] tegradc 15210000.nvdisplay: fb registered
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.345075] gpio tegra-gpio wake21 for gpio=121(P:2)
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.345108] PD DISP0 index2 UP
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.345506] PD DISP1 index3 UP
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.345594] PD DISP2 index4 UP
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.352436]  rate get on hub 408000000
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.352759] Parent Clock set for DC plld2
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.354989]  dc clk 154128046
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.357955] tegradc 15210000.nvdisplay: Link compression not supported by the panel
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.357958]  rate get on compclk 154128046
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.373298] tegradc 15210000.nvdisplay: Window 3 assigned to head 1
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.389969] tegradc 15210000.nvdisplay: Window 4 assigned to head 1
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.406627] tegradc 15210000.nvdisplay: Window 5 assigned to head 1
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.468779] console [ttyS0] enabled
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.475977] bootconsole [uart0] disabled
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.485827] 3110000.serial: ttyTHS1 at MMIO 0x3110000 (irq = 37, base_baud = 0) is a TEGRA_UART
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.495631] c280000.serial: ttyTHS2 at MMIO 0xc280000 (irq = 38, base_baud = 0) is a TEGRA_UART
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.504679] serial-tegra 3130000.serial: RX in PIO mode
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.510890] 3130000.serial: ttyTHS3 at MMIO 0x3130000 (irq = 39, base_baud = 0) is a TEGRA_UART
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.521713] gpio tegra-gpio-aon wake35 for gpio=16(V:2)
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.527064] nct1008_nct72 7-004c: find device tree node, parsing dt
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.533450] nct1008_nct72 7-004c: starting parse dt
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.538501] nct1008_nct72 7-004c: success parsing dt
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.543668] nct1008_nct72 7-004c: success in enabling tmp451 VDD rail
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.548195] tegradc 15210000.nvdisplay: vrr_setup failed
Aug 16 18:39:28 tegra-ubuntu kernel: [    2.592846] tmp451: Enabled overheat logging at 104.00C

When the unit is intentionally shut down, how is it accomplished, e.g., via “sudo shutdown -h now”, or the GUI shutdown button? Direct hard power down by button would cause corruption similar to a failed power supply.

For the setup where the device failed, I typically use the GUI shutdown button.

When using SSH, I typically use “sudo poweroff,” but that was not the case here.

While this is true, the only “corruption” this should cause on an ext4 file system is that any data written but not flushed will be lost from within modified files.
ext4 uses journaling to make sure files don’t go missing when power failures happen, and the file system should not become corrupt from any instantaneous power failure event.

What can corrupt an ext4 file system is:

  1. Bad flash blocks. If a flash page fails catastrophically without the ECC being able to recover it, the flash controller can re-map this block to somewhere else if you re-write it, but the data in the block will be lost.

  2. Stray kernel memory pointer writes (driver bugs.) If you corrupt the data to be written to the file system, and then actually write that corrupted data, then the file system will become corrupt.

  3. Drivers or hardware that lie to the kernel. The kernel depends on ordered writes “taking effect” in order. If kernel writes block A, then block B, then block C, and the driver/hardware acknowledge the secure storage of each of these blocks in order, the kernel assumes that they committed in that order. If, for example, the flash controller re-orders blocks, and power fails, and it turns out B and C committed but A didn’t, the kernel will be confused and the file system may become corrupted.

  4. Bad disk or out of disk space when creating the initial file system image. Even if there’s a “failure” creating the file system image, the flashing toolkit may not discover this, and the corruption may lie latent in the file system image on disk until some particular event / write happens, at which point things start blowing up.

There’s not a lot you can do about 2. and 3. yourself (unless there is a bug in a driver that you’re developing yourself!) but you can easily investigate and fix 4. and perhaps also get some insight into 1. with some diagnostics. If the error happens multiple times, it’s less likely to be 1. unless the flash memory was damaged somewhere between fab line and your desk.

For #1, I was thinking to run “badblocks” in the default read only mode.

For #4, I ran “fsck.ext4 -nf system.img.raw” on my cloned image. It showed 0.3% non-contiguous files, but otherwise clean file system. Also, I’ll pay closer attention fsck results at boot next time.

Was this what you were thinking for investigating these issues?

Since the flash is always mounted on the Jetson, I can’t figure out a great way to run file system diagnostics. Everywhere I look says to run these types of things from the Live CD. Is there something obvious I’m missing for how to do this on a Jetson?

You can create an SD card for running fsck.ext4 from. I add an entry to extlinux.conf and then use serial console to select it at boot time. If you don’t have a serial console or you haven’t planned ahead and added the SD card alternate boot entry it gets more complicated. Something I suggest every Jetson owner do as an edit to their eMMC “/boot/extlinux/extlinux.conf” is copy the default entry “primary”, and make a duplicate below this with the following edits to the duplicate:

  • Rename LABEL to sdcard
  • Rename MENU LABEL to sdcard (or whatever you want).
  • Change "root=/dev/mmcblk0p1" to "root=/dev/mmcblk1p1".

If you have a USB hard drive (SATA) you might also add a similar entry with “/dev/mmcblk0p1” replaced by “/dev/sda1”.

With those in place you will still default to eMMC, but the entry will be there for alternate select via serial console should anything go wrong (it’s difficult to edit the file if the system won’t boot).

In a case where you have eMMC but did not make this edit you may have problems…but in a case where eMMC is corrupt and won’t mount it may be the boot loader continues looking for bootable devices and a rescue SD card will be detected anyway (or rescue USB hard drive).

Here’s some info for one way to deal with rescue (there are a lot of different ways to do this, the way which works depends on situation):
https://devtalk.nvidia.com/default/topic/1018963/jetson-tx2/jetson-tx2-doesn-t-startup-after-installing-tensor-flow/post/5188175/#5188175

The gist is that you copy the sample rootfs to the first partition of the rescue device via “sudo”, and that partition should be a native Linux type (“ext4” is guaranteed). If your host has some 64-bit extensions in mkfs.ext4 the extensions must be turned off (explained in the above URL…this is usually not required) during creation of an ext4 partition. Then you use “sudo” to name this partition as the alternate location of the “apply_binaries.sh” script (the “-r /where/ever/it/is/mounted” option). After you edit the SD card’s extlinux.conf to point at mmcblk1p1 you are ready to try.

I happen to do something similar with a clone or backup image instead of just the sample rootfs. It has my ssh keys in place, it has network setup in place…it just works without fuss. It also makes a backup image I can flash from if I lose the backup on my host.

Another rescue option is to clone the eMMC root partition (a very slow process), followed by repair of the partition on the PC host while the clone is covered by loopback (not difficult once you have the clone), and then flash again reusing the clone instead of a new system.img.raw (slow, but not as slow as a full flash).

Having a serial console is a “must” if you want to do efficient work when alternate boots are to be tested…or during rescue.

Yes, you can flash to an sdcard, using mmcblk1p1 as the target device.

Best way to create an sccard is likely to use a 32 GB or bigger sdcard, and clone the entire internal flash to the card:

dd if=/dev/mmcblk0 of=/dev/mmcblk1 bs=8M

Then, create a new entry in extlinux.conf to be able to boot from the SDCard; you’ll need to select it within seconds of boot on the serial console.

Separately, “badblocks” won’t help much, because once the flash controller sees a bad block, it will re-map it to a good spare block, but the data in that block will be lost if the ECC isn’t good enough. Re-scanning for “bad” blocks won’t find it, because it’s been replaced.

In fact, “badblocks” on flash media will needlessly stress the write cycle count of that media, so I wouldn’t recommend it.

I wonder if the flash controller has some insight/logs into its behavior, so you can tell whether bad things have happened in the past? I checked with smartmontools, but it doesn’t expose SMART counters that I can tell.

Thanks for the advice. I was able to re-flash the Jetson to get it running long enough to configure it to boot from an SSD. I ended using my host to copy my clone (system.img.raw) to the SSD using “cp -ax.” This was the simplest method for me. I cleaned the filesystem errors off of mmcblk0p1, but since I’m in the middle of a critical data collection and it is working on the SSD, I’m holding off further testing on the flash until probably next week sometime.

My current thinking is that there is something wrong with my sparse clone image. Before cloning the Jetson, I’d been using it for a while so I thought I’d clean up the unused flash by filling it with ones (assuming that is the default erased values)

tr '

tr ‘\0’ ‘\377’ < /dev/zero | dd bs=64K of=ones.file
rm ones.file

' '77' < /dev/zero | dd bs=64K of=ones.file
rm ones.file

It seemed that mksparse assumed the fill pattern was zeros so I had to manually create the sparse image

sudo ./mksparse -v --fillpattern=255 system.img.raw system.img

My best guess is that screwed something up because every Jetson I clone only works for a little while, but I can’t find any filesystem errors on the .raw file. I’ll try to post here if I ever get to the bottom of it.

Thanks again for your help.

Just so you don’t do more work than needed, you don’t need a sparse file to flash with. The original flash software used only the raw file named as system.img. It was later on (probably due to flash taking so long) that flash.sh started renaming system.img to system.img.raw, and then using mksparse. “system.img” will be flashed correctly regardless of whether it is raw or sparse. Skip the sparse file conversion and just flash (this takes a lot longer due to USB2 having more data to transfer, but it works). This started on the TK1, here’s a short blurb on it, including use of NULL bytes for the pattern:
http://elinux.org/Jetson/Cloning#About_the_Root_Partition_and_System.img

The default value for sparse files does not depend on the specific media (such as flash) default bit patterns.
It’s the file allocation information that makes the file “sparse” – it’s not just that they seek past the current write point, it’s that the file block map doesn’t even include blocks for certain ranges, and the kernel will then fill in zeros for those.

If you use a file system that does not support sparse files, then the sparse files won’t work. Make sure your host is installed on ext4 or a similar sparse-capable file system!

Finally got a chance to look into this further (it was working well booting from the SSD, so I left well enough alone for a while). @linuxdev, flashing with the raw file worked great… no flash errors… thank you!!!

@snarky, I’m not sure mksparse is actually taking the file allocation information into account (it would make a lot of sense if it did though). The reason I say that is because I tried running the following two commands today:

sudo ./mksparse -v system.img.raw system1.img
sudo ./mksparse -v --fillpattern=255 system.img.raw system2.img

system1.img was 28.9 GB and system2.img was 17.5 GB. If it was taking into account the file allocation information, those files should be the exact same size. Remember that I filled the empty flash with 0xFFs prior to reading the image off the device, so I’m not surprised that the fillpattern=255 command resulted in a smaller image. Any further thoughts?

Try “–fillpattern=0” as another comparison…I think this is what the flash script uses.

As you predict, I get the same results (28.9 GB) when I use either of these commands:

sudo ./mksparse -v system.img.raw system1.img
sudo ./mksparse -v --fillpattern=0 system.img.raw system3.img