JetPack3.1 creating problems with SD Card

I was able to flash Jetpack3.1 successfully on TX2 EMMC. After that I was creating a bootable SD Card for TX2.

For jetpack3.0 I followed this(https://www.youtube.com/watch?v=kVwG-Blz0zQ) link and was able to boot TX2 from SD Card rather than EMMC. But with JetPack3.1 it is not booting from SD Card after following the same procedure. It boots for 13 seconds, then says ‘Rebooting in 5 seconds’ and this cycle continues again and again.

It is booting successfully from EMMC.

Earlier in Jetpack3.0 extlinux file used to look different. Can this be an issue here?

Older Version:

TIMEOUT 30
DEFAULT sdcard

MENU TITLE p2771-0000 eMMC boot options

LABEL sdcard
MENU LABEL SD Card
LINUX /boot/Image
FDT /boot/dtb/tegra186-quill-p3310-1000-c03-00-base.dtb
APPEND 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/mmcblk1p1 rw rootwait

LABEL primary
MENU LABEL Internal EMMC
LINUX /boot/Image
APPEND 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

Current Version:
TIMEOUT 30
DEFAULT sdcard

MENU TITLE p2771-0000 eMMC boot options

LABEL sdcard
MENU LABEL SD Card
LINUX /boot/Image
APPEND ${cbootargs} root=/dev/mmcblk1p1 rw rootwait rootfstype=ext4

LABEL primary
MENU LABEL EMMC
LINUX /boot/Image
APPEND ${cbootargs} root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4

if I try the older version of extlinux it gets stuck while rebooting. Please Help

I haven’t installed this yet so I can’t check (probably in the next few days), but this appears to be something passed on from U-Boot:

${cbootargs}

If you were go into U-Boot console via a serial console there would likely be an environment variable or macro which places whatever cbootargs has in it with the kernel APPEND key/value pair. This would account for the different extlinux.conf where the actual equivalent APPEND might end up being the same between old and new. But…if you could get the Jetson to boot long enough to run this command you would see what the kernel thinks is its APPEND key/value pair:

cat /proc/cmdline

The same thing would exist in “/var/log/Xorg.0.log” if the Jetson made it to a boot stage which tried to run the X GUI. Since you are using an SD card, can you mount this on your PC host and look for the Xorg.0.log there and see if it gives the command line? Literally it will probably say “Kernel command line:…”. Perhaps what the kernel sees as its starting command line might shed some light on whether this is part of the issue.

Also, the same is true for other logs…if boot managed to at least start on the SD card, then the logs in the SD card’s “/var/log/” should be available from the host by mounting the SD card there. In particular, see if you can post the content of “/var/log/boot.log” and “kern.log”.

If boot did not succeed in reaching the SD card at all, then the only logs which will be there will be from whatever was in the system when the SD card was created…so possibly the logs won’t be of use other than proving boot never started on the SD card. If that’s the case, then the “${cbootargs}” probably needs to be examined.

There is one other “wild card” to check. There are some 64-bit extensions in ext4 file systems which are not compatible with the Jetson’s software. If your host uses those extensions, then you can expect a mysterious failure…and probably no fresh logs. On your host look at file “/etc/mke2fs.conf”. In the “ext4” block see if it has “metadata_csum” or “64bit” in it…if this is the case then it was the mkfs.ext4 which was incompatible and can easily be fixed.

Hi Linuxdev

Thanks for your help.

I understand very little of what you said. Hence few more questions.

  1. Could one of nvidia person try SD card boot and give instructions ? Jim’s video is what I have followed and that one seems old as format/contents of extlinux.conf seem to have changed from before.

  2. "If you were go into U-Boot console via a serial console "
    What are steps to go int U-Boot ? Do I need to connect serial cable and then boot ? What do I need to do to ‘intervene’ from host ?

  3. I think that boot did not reach SD card. How do we examine ${cbootargs} ?

Thanks,

Serial console is described here:
http://www.jetsonhacks.com/2017/03/24/serial-console-nvidia-jetson-tx2/

It’s basically an interactive terminal which works even in the boot loader, plus does not require any kind of video driver so most of the system can crash and burn while this still works. Hitting a key early on at the start of boot interrupts the boot loader and allows you to talk to its environment.

cbootargs is something you can examine from inside of the boot loader if you interrupt boot. The Xorg.0.log file should also have this information if Xorg attempted to start…you can view the content of this log using the SD card on your host PC so long as SD card started…if boot did not reach the SD card, then you are out of luck without the serial console.

The comments on 64bit extensions on your host are particularly easy to use, and finding “64bit” or “metadata_csum” in “/etc/mke2fs.conf” of your host PC for ext4 would guarantee the SD card won’t work…this is easy to fix if you know this is the case. One way to look:

cat /etc/mke2fs.conf | gawk '/ext4 /,/[}]/'

Thanks Linuxdev. I will try your suggestion and update.

Would like to check with Nvidia folks whether they have seen such issue during their SD card test(s) ?

Thanks

I am still curious if your host has any 64bit or metadata_csum showing up in:

cat /etc/mke2fs.conf | gawk '/ext4 /,/[}]/'

Some newer systems use this, and if they do, mkfs.ext4 is not able to write a valid file system without adding an option.

Hi Linuxdev,

  1. cat /etc/mke2fs.conf | gawk ‘/ext4 /,/[}]/’
    ext4 = {
    features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
    auto_64-bit_support = 1
    inode_size = 256
    }

  2. However, I do think (based on log that you asked me to examine) that boot did reach sd card.
    /var/log/Var.0.log

[ 16.713] Kernel command line: root=/dev/mmcblk0p1 rw rootwait console=ttyS0,115200n8 console=tty0 OS=l4t fbcon=map:0 net.ifnames=0 memtype=0 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x03100000 nvdumper_reserved=0x2772e0000 gpt tegraid=18.1.2.0.0 tegra_keep_boot_clocks maxcpus=6 androidboot.serialno=0321317103389 bl_prof_dataptr=0x10000@0x277240000 sdhci_tegra.en_boot_part_access=1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4

  1. Following us full log of Var.0.log
[    16.713] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[    16.713] X Protocol Version 11, Revision 0
[    16.713] Build Operating System: Linux 4.4.0-83-generic aarch64 Ubuntu
[    16.713] Current Operating System: Linux tegra-ubuntu 4.4.38-tegra #1 SMP PREEMPT Thu Jul 20 00:49:07 PDT 2017 aarch64
[    16.713] Kernel command line: root=/dev/mmcblk0p1 rw rootwait console=ttyS0,115200n8 console=tty0 OS=l4t fbcon=map:0 net.ifnames=0 memtype=0 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x03100000 nvdumper_reserved=0x2772e0000 gpt tegraid=18.1.2.0.0 tegra_keep_boot_clocks maxcpus=6 androidboot.serialno=0321317103389 bl_prof_dataptr=0x10000@0x277240000 sdhci_tegra.en_boot_part_access=1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4
[    16.713] Build Date: 17 July 2017  05:05:58PM
[    16.713] xorg-server 2:1.18.4-0ubuntu0.3 (For technical support please see http://www.ubuntu.com/support) 
[    16.713] Current version of pixman: 0.33.6
[    16.713] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    16.713] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    16.714] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 26 07:57:16 2017
[    16.715] (==) Using config file: "/etc/X11/xorg.conf"
[    16.715] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    16.718] (==) No Layout section.  Using the first Screen section.
[    16.718] (==) No screen section available. Using defaults.
[    16.718] (**) |-->Screen "Default Screen Section" (0)
[    16.718] (**) |   |-->Monitor "<default monitor>"
[    16.718] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[    16.718] (**) |   |-->Device "Tegra0"
[    16.718] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    16.718] (==) Automatically adding devices
[    16.718] (==) Automatically enabling devices
[    16.718] (==) Automatically adding GPU devices
[    16.718] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    16.720] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    16.720] 	Entry deleted from font path.
[    16.720] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[    16.720] 	Entry deleted from font path.
[    16.720] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    16.720] 	Entry deleted from font path.
[    16.720] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    16.720] 	Entry deleted from font path.
[    16.720] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    16.720] 	Entry deleted from font path.
[    16.720] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	built-ins
[    16.720] (==) ModulePath set to "/usr/lib/aarch64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[    16.720] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    16.720] (II) Loader magic: 0x5587d7fd80
[    16.720] (II) Module ABI versions:
[    16.720] 	X.Org ANSI C Emulation: 0.4
[    16.720] 	X.Org Video Driver: 20.0
[    16.720] 	X.Org XInput driver : 22.1
[    16.720] 	X.Org Server Extension : 9.0
[    16.721] (++) using VT number 7

[    16.721] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    16.721] (II) no primary bus or device found
[    16.721] (WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
[    16.721] (II) "glx" will be loaded by default.
[    16.721] (II) LoadModule: "extmod"
[    16.722] (II) Module "extmod" already built-in
[    16.722] (II) LoadModule: "glx"
[    16.725] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    16.827] (II) Module glx: vendor="NVIDIA Corporation"
[    16.827] 	compiled for 4.0.2, module version = 1.0.0
[    16.827] 	Module class: X.Org Server Extension
[    16.827] (II) NVIDIA GLX Module  28.1.0  Release Build  (integ_stage_rel)  (buildbrain@mobile-u64-553)  Thu Jul 20 00:50:32 PDT 2017
[    16.827] (II) LoadModule: "nvidia"
[    16.827] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    16.845] (II) Module nvidia: vendor="NVIDIA Corporation"
[    16.845] 	compiled for 4.0.2, module version = 1.0.0
[    16.845] 	Module class: X.Org Video Driver
[    16.845] (II) NVIDIA dlloader X Driver  28.1.0  Release Build  (integ_stage_rel)  (buildbrain@mobile-u64-553)  Thu Jul 20 00:51:56 PDT 2017
[    16.845] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    18.001] (WW) Falling back to old probe method for NVIDIA
[    18.001] (II) Loading sub module "fb"
[    18.001] (II) LoadModule: "fb"
[    18.002] (II) Loading /usr/lib/xorg/modules/libfb.so
[    18.004] (II) Module fb: vendor="X.Org Foundation"
[    18.004] 	compiled for 1.18.4, module version = 1.0.0
[    18.004] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    18.004] (II) Loading sub module "wfb"
[    18.004] (II) LoadModule: "wfb"
[    18.004] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    18.005] (II) Module wfb: vendor="X.Org Foundation"
[    18.005] 	compiled for 1.18.4, module version = 1.0.0
[    18.005] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    18.006] (II) Loading sub module "ramdac"
[    18.006] (II) LoadModule: "ramdac"
[    18.006] (II) Module "ramdac" already built-in
[    18.007] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    18.007] (II) NVIDIA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    18.007] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[    18.007] (==) NVIDIA(0): RGB weight 888
[    18.007] (==) NVIDIA(0): Default visual is TrueColor
[    18.007] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    18.007] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration" "true"
[    18.007] (**) NVIDIA(0): Enabling 2D acceleration
[    18.009] (--) NVIDIA(0): Valid display device(s) on GPU-0 at SoC
[    18.009] (--) NVIDIA(0):     DFP-0
[    18.009] (II) NVIDIA(0): NVIDIA GPU NVIDIA Tegra X2 (nvgpu) (GP10B) at SoC (GPU-0)
[    18.009] (--) NVIDIA(0): Memory: 8039124 kBytes
[    18.009] (--) NVIDIA(0): VideoBIOS: 
[    18.009] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): connected
[    18.009] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): External TMDS
[    18.009] (==) NVIDIA(0): 
[    18.009] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[    18.009] (==) NVIDIA(0):     will be used as the requested mode.
[    18.009] (==) NVIDIA(0): 
[    18.010] (II) NVIDIA(0): Validated MetaModes:
[    18.010] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select"
[    18.010] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[    18.012] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi" X config
[    18.012] (--) NVIDIA(0):     option
[    18.012] (--) Depth 24 pixmap format is 32 bpp
[    18.013] (II) NVIDIA: Reserving 49152.00 MB of virtual memory for indirect memory
[    18.013] (II) NVIDIA:     access.
[    18.018] (EE) NVIDIA(0): Failed to allocate NVIDIA Error Handler
[    18.018] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    18.018] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    18.018] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    18.018] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    18.018] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    18.018] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    18.018] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    18.018] (II) NVIDIA(0):     Config Options in the README.
[    18.064] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[    19.244] (==) NVIDIA(0): Disabling shared memory pixmaps
[    19.244] (==) NVIDIA(0): Backing store enabled
[    19.244] (==) NVIDIA(0): Silken mouse enabled
[    19.271] (==) NVIDIA(0): DPMS enabled
[    19.272] (II) Loading sub module "dri2"
[    19.272] (II) LoadModule: "dri2"
[    19.272] (II) Module "dri2" already built-in
[    19.272] (II) NVIDIA(0): [DRI2] Setup complete
[    19.272] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    19.309] (--) RandR disabled
[    19.334] (II) SELinux: Disabled on system
[    19.336] (II) Initializing extension GLX
[    19.336] (II) Indirect GLX disabled.
[    19.480] (II) config/udev: Adding input device tegra-hda HDMI/DP,pcm=3 (/dev/input/event0)
[    19.480] (II) No input driver specified, ignoring this device.
[    19.480] (II) This device may have been added with another device file.
[    19.481] (II) config/udev: Adding input device tegra-hda HDMI/DP,pcm=7 (/dev/input/event1)
[    19.481] (II) No input driver specified, ignoring this device.
[    19.481] (II) This device may have been added with another device file.
[    19.481] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event4)
[    19.481] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[    19.481] (II) LoadModule: "evdev"
[    19.482] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    19.485] (II) Module evdev: vendor="X.Org Foundation"
[    19.485] 	compiled for 1.18.1, module version = 2.10.1
[    19.485] 	Module class: X.Org XInput Driver
[    19.486] 	ABI class: X.Org XInput driver, version 22.1
[    19.486] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[    19.486] (**) Logitech USB Receiver: always reports core events
[    19.486] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event4"
[    19.486] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc534
[    19.486] (--) evdev: Logitech USB Receiver: Found keys
[    19.486] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[    19.486] (**) Option "config_info" "udev:/sys/devices/3530000.xhci/usb1/1-2/1-2:1.0/0003:046D:C534.0001/input/input4/event4"
[    19.486] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 6)
[    19.486] (**) Option "xkb_rules" "evdev"
[    19.486] (**) Option "xkb_model" "pc105"
[    19.486] (**) Option "xkb_layout" "us"
[    19.488] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event5)
[    19.488] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[    19.488] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[    19.488] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[    19.488] (**) Logitech USB Receiver: always reports core events
[    19.488] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event5"
[    19.488] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc534
[    19.489] (--) evdev: Logitech USB Receiver: Found 20 mouse buttons
[    19.489] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[    19.489] (--) evdev: Logitech USB Receiver: Found relative axes
[    19.489] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[    19.489] (--) evdev: Logitech USB Receiver: Found absolute axes
[    19.489] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
[    19.489] (--) evdev: Logitech USB Receiver: Found keys
[    19.489] (II) evdev: Logitech USB Receiver: Configuring as mouse
[    19.489] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[    19.489] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[    19.489] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[    19.489] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    19.489] (**) Option "config_info" "udev:/sys/devices/3530000.xhci/usb1/1-2/1-2:1.1/0003:046D:C534.0002/input/input5/event5"
[    19.489] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 7)
[    19.489] (**) Option "xkb_rules" "evdev"
[    19.489] (**) Option "xkb_model" "pc105"
[    19.489] (**) Option "xkb_layout" "us"
[    19.489] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[    19.489] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
[    19.490] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[    19.490] (**) Logitech USB Receiver: (accel) acceleration profile 0
[    19.490] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[    19.490] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[    19.491] (II) config/udev: Adding input device gpio-keys (/dev/input/event3)
[    19.491] (**) gpio-keys: Applying InputClass "evdev keyboard catchall"
[    19.491] (II) Using input driver 'evdev' for 'gpio-keys'
[    19.491] (**) gpio-keys: always reports core events
[    19.491] (**) evdev: gpio-keys: Device: "/dev/input/event3"
[    19.491] (--) evdev: gpio-keys: Vendor 0x1 Product 0x1
[    19.491] (--) evdev: gpio-keys: Found keys
[    19.491] (II) evdev: gpio-keys: Configuring as keyboard
[    19.491] (**) Option "config_info" "udev:/sys/devices/gpio-keys/input/input3/event3"
[    19.491] (II) XINPUT: Adding extended input device "gpio-keys" (type: KEYBOARD, id 8)
[    19.491] (**) Option "xkb_rules" "evdev"
[    19.492] (**) Option "xkb_model" "pc105"
[    19.492] (**) Option "xkb_layout" "us"
[    19.493] (II) config/udev: Adding input device tegra-snd-t186ref-mobile-rt565x Headphone Jack (/dev/input/event2)
[    19.494] (**) tegra-snd-t186ref-mobile-rt565x Headphone Jack: Applying InputClass "evdev keyboard catchall"
[    19.494] (II) Using input driver 'evdev' for 'tegra-snd-t186ref-mobile-rt565x Headphone Jack'
[    19.494] (**) tegra-snd-t186ref-mobile-rt565x Headphone Jack: always reports core events
[    19.494] (**) evdev: tegra-snd-t186ref-mobile-rt565x Headphone Jack: Device: "/dev/input/event2"
[    19.494] (--) evdev: tegra-snd-t186ref-mobile-rt565x Headphone Jack: Vendor 0 Product 0
[    19.494] (--) evdev: tegra-snd-t186ref-mobile-rt565x Headphone Jack: Found keys
[    19.494] (II) evdev: tegra-snd-t186ref-mobile-rt565x Headphone Jack: Configuring as keyboard
[    19.494] (**) Option "config_info" "udev:/sys/devices/sound/sound/card1/input2/event2"
[    19.494] (II) XINPUT: Adding extended input device "tegra-snd-t186ref-mobile-rt565x Headphone Jack" (type: KEYBOARD, id 9)
[    19.494] (**) Option "xkb_rules" "evdev"
[    19.494] (**) Option "xkb_model" "pc105"
[    19.494] (**) Option "xkb_layout" "us"
[    21.743] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): connected
[    21.743] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): External TMDS
[    22.100] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): connected
[    22.100] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): External TMDS
[    22.309] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[    23.066] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): connected
[    23.066] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): External TMDS
[   343.654] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[   343.687] (EE) NVIDIA(0): Failed to set the display configuration.
[   343.885] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): connected
[   343.885] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): External TMDS
[   343.896] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[   345.058] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[  4285.795] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[  4633.088] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[  5007.463] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[  5009.583] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): connected
[  5009.584] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): External TMDS
[  5009.586] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[  5010.834] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
  1. Also full log of kern.log

[code]
Jul 25 12:48:06 tegra-ubuntu kernel: [ 375.161521] PD DISP2 index4 DOWN
Jul 25 12:48:06 tegra-ubuntu kernel: [ 375.161690] PD DISP1 index3 DOWN
Jul 25 12:48:06 tegra-ubuntu kernel: [ 375.161769] PD DISP0 index2 DOWN
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.241726] PD DISP0 index2 UP
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.242577] PD DISP1 index3 UP
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.242664] PD DISP2 index4 UP
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.244249] Parent Clock set for DC plld2
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.245697] tegradc 15210000.nvdisplay: hdmi: pclk:148500K, set prod-setting:prod_c_150M
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.420874] PD DISP2 index4 DOWN
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.421033] PD DISP1 index3 DOWN
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.421111] PD DISP0 index2 DOWN
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.431616] PD DISP0 index2 UP
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.432447] PD DISP1 index3 UP
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.432524] PD DISP2 index4 UP
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.434018] Parent Clock set for DC plld2
Jul 25 12:48:10 tegra-ubuntu kernel: [ 379.435630] tegradc 15210000.nvdisplay: hdmi: pclk:148500K, set prod-setting:prod_c_150M
Jul 25 13:04:28 tegra-ubuntu kernel: [ 1357.265905] gk20a 17000000.gp10b: railgate is disabled.
Jul 25 13:06:50 tegra-ubuntu kernel: [ 1498.907680] compiz[1659]: unhandled level 2 translation fault (11) at 0x7f9696fd90, esr 0x92000006
Jul 25 13:06:50 tegra-ubuntu kernel: [ 1498.916828] pgd = ffffffc072617000
Jul 25 13:06:50 tegra-ubuntu kernel: [ 1498.920308] [7f9696fd90] *pgd=00000000f262d003, *pud=00000000f262d003, pmd=0000000000000000
Jul 25 13:06:50 tegra-ubuntu kernel: [ 1498.929229]
Jul 25 13:06:50 tegra-ubuntu kernel: [ 1498.930721] CPU: 5 PID: 1659 Comm: compiz Not tainted 4.4.38-tegra #1
Jul 25 13:06:50 tegra-ubuntu kernel: [ 1498.937340] Hardware name: quill (DT)
Jul 25 13:06:50 tegra-ubuntu kernel: [ 1498.941143] task: ffffffc1c3f6d780 ti: ffffffc1c0a94000 task.ti: ffffffc1c0a94000
Jul 25 13:06:50 tegra-ubuntu kernel: [ 1498.949804] PC is at 0x7f91ed6604
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Booting Linux on physical CPU 0x100
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpuset
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpu
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Initializing cgroup subsys cpuacct
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Linux version 4.4.38-tegra (buildbrain@mobile-u64-553) (gcc version 4.8.5 (GCC) ) #1 SMP PREEMPT Thu Jul 20 00:49:07 PDT 2017
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Boot CPU: AArch64 Processor [411fd073]
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] earlycon: Early serial console at MMIO32 0x3100000 (options ‘’)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] bootconsole [uart0] enabled
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Reserved memory: initialized node ramoops_carveout, compatible id nvidia,ramoops
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] cma: Reserved 64 MiB at 0x00000000fc000000
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] On node 0 totalpages: 2051072
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] DMA zone: 8192 pages used for memmap
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] DMA zone: 0 pages reserved
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] DMA zone: 519408 pages, LIFO batch:31
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Normal zone: 23933 pages used for memmap
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Normal zone: 1531664 pages, LIFO batch:31
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] psci: probing for conduit method from DT.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] psci: PSCIv1.0 detected in firmware.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] psci: Using standard PSCI v0.2 function IDs
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] PERCPU: Embedded 17 pages/cpu @ffffffc1f5cf3000 s31232 r8192 d30208 u69632
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] pcpu-alloc: s31232 r8192 d30208 u69632 alloc=17
4096
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2018947
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Kernel command line: root=/dev/mmcblk0p1 rw rootwait console=ttyS0,115200n8 console=tty0 OS=l4t fbcon=map:0 net.ifnames=0 memtype=0 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x03100000 nvdumper_reserved=0x2772e0000 gpt tegraid=18.1.2.0.0 tegra_keep_boot_clocks maxcpus=6 androidboot.serialno=0321317103389 bl_prof_dataptr=0x10000@0x277240000 sdhci_tegra.en_boot_part_access=1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Memory: 7972328K/8204288K available (10976K kernel code, 1817K rwdata, 5712K rodata, 1164K init, 682K bss, 166424K reserved, 65536K cma-reserved)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Virtual kernel memory layout:
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] vmalloc : 0xffffff8000000000 - 0xffffffbdbfff0000 ( 246 GB)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] vmemmap : 0xffffffbdc0000000 - 0xffffffbfc0000000 ( 8 GB maximum)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] 0xffffffbdc2000000 - 0xffffffbdc9d7c400 ( 125 MB actual)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] fixed : 0xffffffbffa7fd000 - 0xffffffbffac00000 ( 4108 KB)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] PCI I/O : 0xffffffbffae00000 - 0xffffffbffbe00000 ( 16 MB)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] memory : 0xffffffc000000000 - 0xffffffc1f5f10000 ( 8031 MB)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] .init : 0xffffffc0010cd000 - 0xffffffc0011f0000 ( 1164 KB)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] .text : 0xffffffc000080000 - 0xffffffc0010cd000 ( 16692 KB)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] .data : 0xffffffc001211000 - 0xffffffc0013d7430 ( 1818 KB)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Preemptible hierarchical RCU implementation.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Build-time adjustment of leaf fanout to 64.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=6.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=6
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] NR_IRQS:64 nr_irqs:64 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] GIC: Using split EOI/Deactivate mode
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] Architected cp15 timer(s) running at 31.25MHz (phys).
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xe6a171046, max_idle_ns: 881590405314 ns
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.000002] sched_clock: 56 bits at 31MHz, resolution 32ns, wraps every 4398046511088ns
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.009858] Console: colour dummy device 80x25
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.014517] console [tty0] enabled
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.018071] bootconsole [uart0] disabled
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022173] kmemleak: Kernel memory leak detector disabled
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022184] Calibrating delay loop (skipped), value calculated using timer frequency… 62.50 BogoMIPS (lpj=125000)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022196] pid_max: default: 32768 minimum: 301
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022239] Security Framework initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022268] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022277] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022627] Initializing cgroup subsys freezer
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022638] Initializing cgroup subsys debug
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022776] CPU0 ipc=752
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022785] CPU1 ipc=1024
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022792] CPU2 ipc=1024
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022801] CPU3 ipc=752
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022809] CPU4 ipc=752
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022818] CPU5 ipc=752
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.022848] ASID allocator initialised with 65536 entries
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.046207] tegra-id: chipid=21817.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.046219] tegra-id: opt_subrevision=1.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.046228] Tegra Revision: A02p SKU: 0xdc CPU Process: 0 SoC Process: 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.046840] DTS File Name: /dvs/git/dirty/git-master_linux/kernel/kernel-4.4/arch/arm64/boot/dts/…/…/…/…/…/…/hardware/nvidia/platform/t18x/quill/kernel-dts/tegra186-quill-p3310-1000-c03-00-base.dts
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.046859] DTB Build time: Jul 20 2017 00:50:45
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.062592] CPU1: Booted secondary processor [4e0f0030]
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.074077] CPU2: Booted secondary processor [4e0f0030]
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.085834] CPU3: Booted secondary processor [411fd073]
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.097812] CPU4: Booted secondary processor [411fd073]
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.109808] CPU5: Booted secondary processor [411fd073]
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.109869] Brought up 6 CPUs
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.109918] SMP: Total of 6 processors activated.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.109929] CPU: All CPU(s) started at EL2
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.110412] devtmpfs: initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.137355] Initilizing CustomIPI irq domain
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.137553] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.138402] pinctrl core: initialized pinctrl subsystem
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.138574] OS set in device tree is L4T.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.138770] regulator-dummy: no parameters
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.138871] Initializing plugin-manager
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.138923] Plugin module not found
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.139330] node /plugin-manager/soc-prod-a02-fragment match with chip-id A02P
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.139666] node /plugin-manager/fragement@0 match with odm-data enable-denver-wdt
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.140272] node /plugin-manager/fragement@4 match with odm-data enable-denver-wdt
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.141449] node /plugin-manager/fragment-sdwake-p3310-1000-300 match with board >=3310-1000-300
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.141802] node /plugin-manager/fragement-pmon-p3310-1000-300 match with board >=3310-1000-300
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.142051] node /plugin-manager/fragement-pmon-p3310-1000-800 match with board >=3310-1000-800
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.142268] node /plugin-manager/fragment-devslp@0 match with board >=3310-1000-200
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.142692] node /plugin-manager/fragment-500-pcie-config match with board >=3310-1000-500
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.143132] node /plugin-manager/fragment-500-xusb-config match with board >=3310-1000-500
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.143407] node /plugin-manager/fragment-500-e3325-pcie match with board >=3310-1000-500
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.143785] node /plugin-manager/fragment-p3310-c00-comm match with board >=3310-1000-800
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.144031] node /plugin-manager/fragment-p3310-c00-pmic match with board >=3310-1000-800
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.144250] node /plugin-manager/fragment-p3310-c01 match with board >=3310-1000-900
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.144509] node /plugin-manager/fragment-p3310-c03 match with board >=3310-1000-B00
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.146446] node /plugin-manager/fragment-p3310-c00-camera match with board >=3310-1000-800
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.147346] node /plugin-manager/fragment-imx274@0 match with board LPRD-002002
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.148937] Adding domain adsp-pd to PM domain ape-pd
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.151324] NET: Registered protocol family 16
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.151989] console [pstore-1] enabled
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.151999] pstore: Registered ramoops as persistent store backend
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.152012] ramoops: attached 0x200000@0x96080000, ecc: 0/0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.161353] cpuidle: using governor ladder
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.165833] cpuidle: using governor menu
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.166958] bpmp: waiting for handshake
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.166971] bpmp: handshake completed
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.167011] bpmp: synchronizing channels
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.167038] bpmp: channels synchronized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.167049] bpmp: mail init ok
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.167369] vdso: 2 pages (1 code @ ffffffc001219000, 1 data @ ffffffc001218000)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.167400] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.168340] atomic_pool_init():526: DMA: preallocated 1024 KiB pool for atomic allocations
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.169819] tegra_powergate_init: DONE
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.169848] DTS File Name: /dvs/git/dirty/git-master_linux/kernel/kernel-4.4/arch/arm64/boot/dts/…/…/…/…/…/…/hardware/nvidia/platform/t18x/quill/kernel-dts/tegra186-quill-p3310-1000-c03-00-base.dts
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.169874] DTB Build time: Jul 20 2017 00:50:45
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.170774] Tegra reboot handler registered.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.171826] Registering Tegra186 clocks (this may take a while)…done
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.173974] arm-smmu 12000000.iommu: probing hardware configuration…
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.173991] arm-smmu 12000000.iommu: SMMUv2 with:
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.174003] arm-smmu 12000000.iommu: stage 1 translation
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.174015] arm-smmu 12000000.iommu: stage 2 translation
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.174025] arm-smmu 12000000.iommu: nested translation
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.174038] arm-smmu 12000000.iommu: stream matching with 128 register groups, mask 0x7f80
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.174056] arm-smmu 12000000.iommu: SMMU address space size (0x800000) differs from mapped region size (0x1000000)!
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.174073] arm-smmu 12000000.iommu: 64 context banks (0 stage-2 only)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.174086] arm-smmu 12000000.iommu: Stage-1: 39-bit VA -> 48-bit IPA
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.174097] arm-smmu 12000000.iommu: Stage-2: 39-bit IPA -> 48-bit PA
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.223758] arm-smmu 12000000.iommu: registered 67 master devices
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.229100] iommu: Adding device 3460000.sdhci to group 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.229896] iommu: Adding device 3400000.sdhci to group 1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.233444] iommu: Adding device 3507000.ahci-sata to group 2
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.233905] iommu: Adding device 3160000.i2c to group 3
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.234316] iommu: Adding device c240000.i2c to group 4
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.234664] iommu: Adding device 3180000.i2c to group 5
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.235012] iommu: Adding device 3190000.i2c to group 6
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.235466] iommu: Adding device 31b0000.i2c to group 7
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.235842] iommu: Adding device 31c0000.i2c to group 8
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.236156] iommu: Adding device c250000.i2c to group 9
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.236516] iommu: Adding device 31e0000.i2c to group 10
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.238418] iommu: Adding device 3210000.spi to group 11
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.238767] iommu: Adding device c260000.spi to group 12
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.239089] iommu: Adding device 3240000.spi to group 13
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.239858] iommu: Adding device 3100000.serial to group 14
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.240196] iommu: Adding device 3110000.serial to group 15
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.240480] iommu: Adding device c280000.serial to group 16
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.240820] iommu: Adding device 3130000.serial to group 17
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.242047] iommu: Adding device 2490000.ether_qos to group 18
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.242877] iommu: Adding device b000000.rtcpu to group 19
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.243366] iommu: Adding device c1a0000.aon to group 20
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.244196] Wake73 for irq=42
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.244544] iommu: Adding device smmu_test to group 21
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.245020] mc: mapped MMIO address: 0xffffff8000560000 -> 0x2c10000
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.245078] mc: mapped MMIO address: 0xffffff8000640000 -> 0x2c20000
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.245115] mc: mapped MMIO address: 0xffffff8000660000 -> 0x2c30000
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.245148] mc: mapped MMIO address: 0xffffff8000fa0000 -> 0x2c40000
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.245180] mc: mapped MMIO address: 0xffffff8000fc0000 -> 0x2c50000
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.245212] mc-err: Set intmask: 0xf3140
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.245423] dram-ecc: DRAM ECC disabled-MC_ECC_CONTROL:0x0000000c
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.246184] Wake76 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.246204] Wake77 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.246222] Wake78 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.246249] Wake79 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.246266] Wake80 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.246282] Wake81 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.246299] Wake82 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.246433] iommu: Adding device 3530000.xhci to group 22
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.246797] iommu: Adding device 3550000.xudc to group 23
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.247551] tegra-pmc c360000.pmc: scratch reg offset dts data not present
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.247579] tegra-pmc: ### PMC reset source: Power on reset
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.247599] tegra-pmc: ### PMC reset level: L0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.247618] tegra-pmc: ### PMC reset status reg: 0x0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.247860] padctrl padctrl.0: Pad control driver tegra-pmc-padctrl registered
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.247912] tegra-pmc c360000.pmc: IO padctrl driver initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.248069] tegra186-aowake c370000.pmc: WAKE_AOWAKE_CTRL_0 = 3
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.248095] tegra186-aowake c370000.pmc: WAKE_AOWAKE_CNTRL_24(PMU_INT) = 320
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.248569] iommu: Adding device 13e10000.host1x to group 24
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.248800] iommu: Adding device 13e10000.host1x:ctx0 to group 25
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.249031] iommu: Adding device 13e10000.host1x:ctx1 to group 26
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.249256] iommu: Adding device 13e10000.host1x:ctx2 to group 27
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.249496] iommu: Adding device 13e10000.host1x:ctx3 to group 28
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.249731] iommu: Adding device 13e10000.host1x:ctx4 to group 29
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.249938] iommu: Adding device 13e10000.host1x:ctx5 to group 30
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.250152] iommu: Adding device 13e10000.host1x:ctx6 to group 31
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.250386] iommu: Adding device 13e10000.host1x:ctx7 to group 32
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.250869] iommu: Adding device 150c0000.nvcsi to group 33
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.251388] iommu: Adding device 15700000.vi to group 34
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.251734] iommu: Adding device 15600000.isp to group 35
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.252045] iommu: Adding device 15210000.nvdisplay to group 36
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.252261] iommu: Adding device 15340000.vic to group 37
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.252453] iommu: Adding device 154c0000.nvenc to group 38
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.252641] iommu: Adding device 15480000.nvdec to group 39
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.253084] iommu: Adding device 15380000.nvjpg to group 40
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.253303] iommu: Adding device 15500000.tsec to group 41
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.253525] iommu: Adding device 15100000.tsecb to group 42
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.254225] iommu: Adding device 15810000.se to group 43
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.254422] iommu: Adding device 15820000.se to group 44
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.254655] iommu: Adding device 15830000.se to group 45
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.254841] iommu: Adding device 15840000.se to group 46
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.255331] iommu: Adding device 17000000.gp10b to group 47
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.256691] tegra-reset 5000000.clock: registered 193 resets.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.258848] iommu: Adding device d000000.bpmp to group 48
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.259063] bpmp: ping status is 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.259238] bpmp d000000.bpmp: firmware tag is 0705d30e2bb4ef1fcf63b70c5fc3deef
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.259605] bpmp d000000.bpmp: probe ok
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.262093] iommu: Adding device 2600000.dma to group 49
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.262962] GPIO line 461 (cam0-rst) hogged as output/high
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.263013] GPIO line 424 (wifi-enable) hogged as output/high
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.263059] GPIO line 445 (sdmmc-wake-input) hogged as input
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.263125] GPIO line 446 (sdmmc-wake-output) hogged as output/low
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.263224] gpiochip_add_data: registered GPIOs 320 to 511 on device: tegra-gpio
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.265066] GPIO line 315 (wifi-wake-ap) hogged as input
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.265166] gpiochip_add_data: registered GPIOs 256 to 319 on device: tegra-gpio-aon
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.266047] iommu: Adding device 10003000.pcie-controller to group 50
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.266316] iommu: Adding device sound to group 51
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.268108] iommu: Adding device 3510000.hda to group 52
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.269234] iommu: Adding device adsp_audio to group 53
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.270643] iommu: Adding device 2993000.adsp to group 54
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.280517] vdd-ac-bat: 5000 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.282830] vdd-1v8-ap: 1800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.283992] gpio tegra-gpio-aon wake30 for gpio=60(FF:4)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.284341] gpio tegra-gpio-aon wake69 for gpio=59(FF:3)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.300667] SCSI subsystem initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.300893] libata version 3.00 loaded.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.301061] usbcore: registered new interface driver usbfs
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.301118] usbcore: registered new interface driver hub
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.301226] usbcore: registered new device driver usb
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.305161] GPIO line 241 (touch-rail-1) hogged as output/high
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.305607] GPIO line 242 (touch-rail-2) hogged as output/high
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.305719] gpiochip_add_data: registered GPIOs 240 to 255 on device: tca9539
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.307082] GPIO line 228 (lcd-bias-en-rail) hogged as output/high
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.307169] gpiochip_add_data: registered GPIOs 224 to 239 on device: tca9539
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.319485] media: Linux media interface: v0.10
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.319552] Linux video capture interface: v2.00
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.323383] pps_core: LinuxPPS API ver. 1 registered
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.323428] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.323475] PTP clock support registered
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.324361] tegra_wdt_t18x 30c0000.watchdog: Tegra WDT init timeout = 120 sec
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.324402] tegra_wdt_t18x 30c0000.watchdog: Registered successfully
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.325865] max77620 4-003c: PMIC Version OTP:0x45 and ES:0x8
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.327812] GPIO line 221 (spmic_gpio_input_5) hogged as input
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.328003] GPIO line 222 (spmic_gpio_input_6) hogged as input
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.328096] gpiochip_add_data: registered GPIOs 216 to 223 on device: max77620-gpio
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.334769] vddio-ddr: at 1125 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.338611] avdd_dsi_csi: 1200 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.342608] vdd-1v8: 1800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.346609] vdd-3v3-sys: 3300 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.347698] spmic-ldo0: at 1800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.348468] spmic-ldo1: at 800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.354606] vddio-3v3: 3300 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.355214] vddio-sdmmc1: 1800 <–> 3300 mV at 3300 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.357349] vdd-rtc: at 800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.358034] avdd-ts-hv: 1800 <–> 3300 mV at 1800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.361347] spmic-ldo6: at 1500 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.365346] vdd-pex-1v05: 1000 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.365892] dvdd-pex: 1000 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.366161] max77620 4-003c: max77620 probe successful
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.366401] Advanced Linux Sound Architecture Driver Initialized.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.367351] en-vdd-sd: 3300 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.367976] en-vdd-cam: 1800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.369839] vdd-hdmi: 5000 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.370025] vdd-usb0-5v: 5000 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.370191] vdd-usb1-5v: 5000 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.373837] en-vdd-ts-1v8: 1800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.377836] en-vdd-ts-hv-3v3: 3300 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.378350] en-vdd-disp-3v3: 3300 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.378856] en-mdm-pwr-3v7: 3700 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.379381] en-vdd-disp-1v8: 1800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.379900] en-vdd-cam-hv-2v8: 2800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.380419] en-vdd-cam-1v2: 1200 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.380938] vdd-fan: 5000 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.381044] vdd-3v3: 3300 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.381768] dis-vdd-1v2: 1200 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.381900] en-vdd-vcm-2v8: 2800 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.382421] vdd-usb2-5v: 5000 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.382527] vdd-sys-bl: 3300 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.383050] en-vdd-sys: 1200 mV
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.384760] gpio tegra-gpio wake53 for gpio=159(X:7)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.386437] extcon-gpio-states external-connection:extcon@1: Cable state 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.386793] clocksource: Switched to clocksource arch_sys_counter
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.405803] nvmap_heap_init: nvmap_heap_init: created heap block cache
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.406120] nvmap: nvmap_override_cache_ops() set roc flush ops to replace cache ops by set/ways
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.406592] nvmap_page_pool_init: Total RAM pages: 2009466
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.406608] nvmap_page_pool_init: nvmap page pool size: 251183 pages (981 MB)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.406832] nvmap_background_zero_thread: PP zeroing thread starting.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.411260] Wake76 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.411272] Wake77 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.411282] Wake78 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.411291] Wake79 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.411299] Wake80 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.411307] Wake81 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.411315] Wake82 for irq=199
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.412320] pca954x 2-0070: pca954x_probe: forcing device bus number, start 30.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.412338] pca954x 2-0070: device detect skipped.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.412417] regulator_get() failed for (2-0070,vcc-pullup), -19
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.412429] pca954x 2-0070: vcc-pullup regulator not found
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.412624] i2c i2c-2: Added multiplexed i2c bus 30
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.412690] i2c i2c-2: Added multiplexed i2c bus 31
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.412755] i2c i2c-2: Added multiplexed i2c bus 32
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.412819] i2c i2c-2: Added multiplexed i2c bus 33
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.412832] pca954x 2-0070: registered 4 multiplexed busses for I2C switch pca9546
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.413144] thermal thermal_zone0: Registering thermal zone thermal_zone0 for type BCPU-therm
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.413338] thermal thermal_zone1: Registering thermal zone thermal_zone1 for type MCPU-therm
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.413450] thermal thermal_zone2: Registering thermal zone thermal_zone2 for type GPU-therm
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.413527] thermal thermal_zone3: Registering thermal zone thermal_zone3 for type PLL-therm
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.413920] thermal thermal_zone4: Registering thermal zone thermal_zone4 for type AO-therm
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.414059] thermal thermal_zone5: Registering thermal zone thermal_zone5 for type Tboard_tegra
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.414203] thermal thermal_zone6: Registering thermal zone thermal_zone6 for type Tdiode_tegra
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.414352] thermal thermal_zone7: Registering thermal zone thermal_zone7 for type PMIC-Die
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.414646] isomgr_init(): iso emc max clk=1866000KHz
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.414657] isomgr_init(): max_iso_bw=26870400KB
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.414734] NET: Registered protocol family 2
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.415072] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.415292] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.415583] TCP: Hash tables configured (established 65536 bind 65536)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.415637] UDP hash table entries: 4096 (order: 5, 131072 bytes)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.415688] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.415840] NET: Registered protocol family 1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.416079] RPC: Registered named UNIX socket transport module.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.416093] RPC: Registered udp transport module.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.416104] RPC: Registered tcp transport module.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.416115] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.416136] PCI: CLS 0 bytes, default 128
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.416240] Trying to unpack rootfs image as initramfs…
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.430109] host1x 13e10000.host1x: initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.430928] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.432957] futex hash table entries: 2048 (order: 6, 262144 bytes)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.433050] audit: initializing netlink subsys (disabled)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.433093] audit: type=2000 audit(0.420:1): initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.439532] io scheduler noop registered (default)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.442416] tegra-pwm 3280000.pwm: PWM clk can sleep in ops
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.443641] tegra-pwm 3290000.pwm: PWM clk can sleep in ops
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.444709] tegra-pwm 32a0000.pwm: PWM clk can sleep in ops
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.445758] tegra-pwm c340000.pwm: PWM clk can sleep in ops
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.449161] tsec 15500000.tsec: initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.450271] tsec 15100000.tsecb: initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.452605] nvdec 15480000.nvdec: initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.456184] falcon 15340000.vic: initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.457175] falcon 154c0000.nvenc: initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.458155] falcon 15380000.nvjpg: initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.458934] iommu_context_dev 13e10000.host1x:ctx0: initialized (streamid=56)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.459440] iommu_context_dev 13e10000.host1x:ctx1: initialized (streamid=57)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.459934] iommu_context_dev 13e10000.host1x:ctx2: initialized (streamid=58)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.460428] iommu_context_dev 13e10000.host1x:ctx3: initialized (streamid=59)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.460921] iommu_context_dev 13e10000.host1x:ctx4: initialized (streamid=60)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.461416] iommu_context_dev 13e10000.host1x:ctx5: initialized (streamid=61)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.461910] iommu_context_dev 13e10000.host1x:ctx6: initialized (streamid=62)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.462403] iommu_context_dev 13e10000.host1x:ctx7: initialized (streamid=63)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.464973] DC OR NODE connected to /host1x/sor1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.465120] tegra_camera_platform tegra-camera-platform: tegra_camera_probe:camera_platform_driver probe
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.465185] tegradc 15210000.nvdisplay: DT parsed successfully
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.465226] tegradc 15210000.nvdisplay: Display dc.ffffff8002320000 registered with id=0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.465229] misc tegra_camera_ctrl: tegra_camera_isomgr_register tpg_max_iso = 3916800KBs
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.465234] misc tegra_camera_ctrl: tegra_camera_isomgr_register isp_iso_bw=4687500, vi_iso_bw=1500000, max_bw=4687500
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.472964] tegra_nvdisp_bandwidth_register_max_config: max config iso bw = 16727000 KB/s
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.472983] tegra_nvdisp_bandwidth_register_max_config: max config EMC floor = 665600000 Hz
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.472998] tegra_nvdisp_bandwidth_register_max_config: max config hubclk = 357620000 Hz
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.473041] tegradc 15210000.nvdisplay: vblank syncpt # 7 for dc 1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.473055] tegradc 15210000.nvdisplay: vpulse3 syncpt # 8 for dc 1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.473281] tegra-adma 2930000.adma: Tegra ADMA driver register 10 channels
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.475353] tegra-fuse-burn 3820000.efuse:efuse-burn: Fuse burn driver initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.475593] tegradc 15210000.nvdisplay: hdmi: no prod_list_hdmi_board, use default range
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.475612] PD DISP0 index2 UP
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.475716] kfuse 3830000.kfuse: initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.476469] PD DISP1 index3 UP
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.476632] PD DISP2 index4 UP
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.476906] tegra-pmc-iopower pmc-iopower: NO_IOPOWER setting 0x0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.477330] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.479189] console [ttyS0] disabled
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.479240] 3100000.serial: ttyS0 at MMIO 0x3100000 (irq = 37, base_baud = 25500000) is a Tegra
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.502856] PD DISP2 index4 DOWN
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.503008] PD DISP1 index3 DOWN
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.503147] PD DISP0 index2 DOWN
Jul 25 18:26:39 tegra-ubuntu kernel: [ 0.505143] tegradc 15210000.nvdisplay: probed
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.600545] console [ttyS0] enabled
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.602417] 3110000.serial: ttyTHS1 at MMIO 0x3110000 (irq = 38, base_baud = 0) is a TEGRA_UART
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.603522] c280000.serial: ttyTHS2 at MMIO 0xc280000 (irq = 39, base_baud = 0) is a TEGRA_UART
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.603729] serial-tegra 3130000.serial: RX in PIO mode
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.604612] 3130000.serial: ttyTHS3 at MMIO 0x3130000 (irq = 40, base_baud = 0) is a TEGRA_UART
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.614448] brd: module loaded
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.614611] Console: switching to colour frame buffer device 240x67
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.618546] loop: module loaded
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.618771] gpio tegra-gpio-aon wake35 for gpio=16(V:0)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.618856] nct1008_nct72 7-004c: find device tree node, parsing dt
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.618861] nct1008_nct72 7-004c: starting parse dt
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.618943] nct1008_nct72 7-004c: success parsing dt
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.619075] nct1008_nct72 7-004c: success in enabling tmp451 VDD rail
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.688053] tmp451: Enabled overheat logging at 104.00C
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.688116] gpio tegra-gpio-aon wake35 for gpio=16(V:0)
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.688145] nct1008_nct72 7-004c: nct1008_probe: initialized
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.690491] THERMAL EST: found 3 subdevs
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.690502] THERMAL EST num_resources: 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.690504] [THERMAL EST subdev 0]
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.690508] [THERMAL EST subdev 1]
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.690511] [THERMAL EST subdev 2]
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.690731] thermal thermal_zone8: Registering thermal zone thermal_zone8 for type thermal-fan-est
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.690733] THERMAL EST: thz register success.
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.690831] THERMAL EST: end of probe, return err: 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691028] tegra_profiler: Branch: Dev
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691029] tegra_profiler: Version: 1.109
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691031] tegra_profiler: Samples version: 37
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691032] tegra_profiler: IO version: 21
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691035] armv8_pmu: imp: 0x41, idcode: 0x1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691037] armv8_pmu: [0] arch: AA64 PmuV3 ARM CORTEX-A57, type: 5, ver: 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691039] armv8_pmu: imp: 0x4e, idcode: 0x1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691041] armv8_pmu: [1] arch: AA64 PmuV3 NVIDIA (Denver), type: 6, ver: 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691043] armv8_pmu: imp: 0x4e, idcode: 0x1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691045] armv8_pmu: [2] arch: AA64 PmuV3 NVIDIA (Denver), type: 6, ver: 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691047] armv8_pmu: imp: 0x41, idcode: 0x1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691048] armv8_pmu: [3] arch: AA64 PmuV3 ARM CORTEX-A57, type: 5, ver: 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691050] armv8_pmu: imp: 0x41, idcode: 0x1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691052] armv8_pmu: [4] arch: AA64 PmuV3 ARM CORTEX-A57, type: 5, ver: 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691053] armv8_pmu: imp: 0x41, idcode: 0x1
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691055] armv8_pmu: [5] arch: AA64 PmuV3 ARM CORTEX-A57, type: 5, ver: 0
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691181] tegra_profiler: auth: init
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.691935] gk20a 17000000.gp10b: failed to allocate secure buffer -12
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.693996] tegra-ahci 3507000.ahci-sata: AHCI 0001.0301 32 slots 2 ports 3 Gbps 0x1 impl platform mode
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.694003] tegra-ahci 3507000.ahci-sata: flags: 64bit ncq sntf pm led pmp pio slum part deso sadm apst
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.694619] scsi host0: tegra_ahci
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.694839] scsi host1: tegra_ahci
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.694951] ata1: SATA max UDMA/133 mmio [mem 0x03507000-0x03508fff] port 0x100 irq 25
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.694952] ata2: DUMMY
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.695653] spi-tegra114 3210000.spi: Static pin configuration used
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.696010] spi-tegra114 c260000.spi: Static pin configuration used
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.696334] spi-tegra114 3240000.spi: Static pin configuration used
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.696938] tun: Universal TUN/TAP device driver, 1.6
Jul 25 18:26:39 tegra-ubuntu kernel: [ 2.696940] tun: © 1999-2004 Max Krasnyansky maxk@qualcomm.com
Jul 25 18:26:39 tegra-ubuntu kerne

kern.log seems like humongous 1.7MB file. I am not able to attach it here. Is there any other way to attach that file ?

Thanks

I just realized I had made a bad assumption. I had assumed the logs were filled in from a boot that failed, and not from a prior working boot (such as from when you copied your file system onto the SD rather than unpacking sample rootfs), so that is a weakness in the test. However, you could delete the Xorg.0.log and boot again and see if it filled in.

Of the given data, I see it detected your monitor, so if the log is valid, then boot would have had to be fairly close to login before any error at all showed up:

[    18.009] (--) NVIDIA(0): VideoBIOS: 
[    18.009] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): connected
[    18.009] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): External TMDS

Then it used the BenQ EDID to select 1920x1080 as its mode:

[    18.010] (II) NVIDIA(0): Validated MetaModes:
[    18.010] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select"
[    18.010] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080

Following this it shows you switched to text console (e.g., ctrl+alt+F2) and back to X11 several times:

[   343.896] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[   345.058] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[  4285.795] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[  4633.088] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[  5007.463] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[  5009.583] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): connected
[  5009.584] (--) NVIDIA(GPU-0): BenQ EW2750ZL (DFP-0): External TMDS
[  5009.586] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[  5010.834] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"

I’m not positive, but in the middle of that last excerpt it looks like you also unplugged and re-plugged the HDMI port and it worked so far as X was concerned.

The kern.log does not show any kind of error or exceptional event. It seems likely the logs were copied over from the process of creating an SD card root file system, but you would have to delete the kern.log or Xorg.0.log and boot again and see if they are empty…being empty would validate this as from a different boot.

Would you post the entire content of your ext4 section of “/etc/mke2fs.conf”? The gawk command should have produced output, but had none (perhaps gawk is not installed, in which case it would have had an error, or your mke2fs.conf has a different layout than mine).

Hi Linuxdev

Yes you are right, I did plug hdmi cable in/out, at Tx2 HDMI port. I tried our suggestion of wiping out *.log from /var/log of SD card and then boot again. Following are sequence of my steps.

1. I boot from eMMC
2. Insert card
3. cd /media/ubuntu/SDRoot/var/log
   sudo rm *log /var/log
4. Power down. THe card is still inserted in the slot.
5. Power up again, since card is in slot - it will boot from SD card. 
6. Due to the issue for this this thread was started, the SD card boot does not complete. I pull the power cable.
7. Eject SD card. Power up again
8. Now boot happens successfully from eMMC. After login screen, I push the SD card back in slot.
9.  cd /media/ubuntu/SDRoot/var/log
   ls -ltr *.log

I not see any kern.log or Xorg.0.log now.

Furthermore, following the contents of /etc/mke2fs.conf on the host from which new release of flashed.

[defaults]
	base_features = sparse_super,large_file,filetype,resize_inode,dir_index,ext_attr
	default_mntopts = acl,user_xattr
	enable_periodic_fsck = 0
	blocksize = 4096
	inode_size = 256
	inode_ratio = 16384

[fs_types]
	ext3 = {
		features = has_journal
	}
	ext4 = {
		features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
		auto_64-bit_support = 1
		inode_size = 256
	}
	ext4dev = {
		features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
		inode_size = 256
		options = test_fs=1
	}
	small = {
		blocksize = 1024
		inode_size = 128
		inode_ratio = 4096
	}
	floppy = {
		blocksize = 1024
		inode_size = 128
		inode_ratio = 8192
	}
	big = {
		inode_ratio = 32768
	}
	huge = {
		inode_ratio = 65536
	}
	news = {
		inode_ratio = 4096
	}
	largefile = {
		inode_ratio = 1048576
		blocksize = -1
	}
	largefile4 = {
		inode_ratio = 4194304
		blocksize = -1
	}
	hurd = {
	     blocksize = 4096
	     inode_size = 128
	}

Thanks,

The host’s mke2fs.conf shows all options are compatible and the ext4 creation should be valid, so this is not the issue. Knowing more about what goes on during the failed SD card boot by means of monitoring the serial console would be an extremely useful bit (no pun intended, but I should have thought of it:) of added information. Have you been able to get any serial console output yet?

Thanks Linuxdev, we are arranging serial console cable, (which is not shipped with Tx2). I will update again after we try from serial console.

Thanks,

hello dumbogeorge,

here’s external wiki page to share the steps to boot from sd card.
http://elinux.org/Boot_from_sd

Hi Linuxdev,

I am attaching the log of the serial console currently while booting from SD Card. You will be able to see that after every ~13 seconds it reboots and this process goes on indefinitely.

Hi Jerry Chang,
I will try the commands mentioned in your wiki link and try booting from SD Card again.

Thanks.
serialConsoleLog.txt (94.1 KB)

It simply can’t read the SD card (mmcblk1p1 is the first partition of the SD card…be sure you have a GPT partition on the SD card, e.g., “sudo gdisk -l /dev/mmcblk1”…or whichever device this is on your host’s SD card reader):

VFS: Cannot open root device "mmcblk1p1" or unknown-block(179,33): error -30

The missing rootfs causes a kernel failure, which reboots the system…and then it once more cannot read the rootfs, so it keeps going. Either (1), there is a failure to read the SD card at all, or (2) the first partition of type GPT does not exist, or (3) the file system on the partition is not readable. Based on the ext4 information given above it is unlikely to be (3). Odds of (2) are probably higher than being unable to read the card at all, but both are significant odds.

While the SD card is present on the host PC you might try:

sudo lsblk /dev/mmcblk1
sudo lsblk /dev/mmcblk1p1

Hi Linuxdev

I am able to plug in SD card in host machine and read extlinux.conf

The outputs that you wanted are -

:~$ sudo lsblk /dev/mmcblk1
[sudo] password for pankajc: 
lsblk: /dev/mmcblk1: not a block device
:~$ sudo lsblk /dev/mmcblk1p1
lsblk: /dev/mmcblk1p1: not a block device
:~$

Thanks

Are you sure that mmcblk1 is the SD card when plugged in to the host? You might want to monitor dmesg as you plug in the SD card. On newer systems you can run “dmesg --follow”, but you may need to manually do something like “dmesg | tail -n 25” before and after the SD card plugin (then look for what got appended from SD card insert).

If “/dev/mmcblk1” does not exist, then you will get the message you got (instead of a useful error saying “no such file”). If you are sure this is your SD card, then also find the output of:

sudo gdisk -l /dev/mmcblk1
sudo gdisk -l /dev/mmcblkp1

Hi Linuxdev

  1. Before plugging in SD card in host system -
~$ dmesg | tail -n 25
[ 7288.736510] mmc0: tried to reset card
[ 7288.739653] EXT4-fs (mmcblk0p1): INFO: recovery required on readonly filesystem
[ 7288.739655] EXT4-fs (mmcblk0p1): write access unavailable, cannot proceed
[ 7322.011903] mmc0: card 0007 removed
[ 7345.101229] mmc0: new ultra high speed SDR104 SDXC card at address 0007
[ 7345.102283] mmcblk0: mmc0:0007 7YDLP 120 GiB 
[ 7345.103365]  mmcblk0: p1
[ 7345.287972] EXT4-fs (mmcblk0p1): recovery complete
[ 7345.287977] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[11212.591032] usb 1-3: USB disconnect, device number 4
[55305.091492] perf interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[69199.894438] usb 1-3: new full-speed USB device number 5 using xhci_hcd
[69200.080475] usb 1-3: New USB device found, idVendor=046d, idProduct=c534
[69200.080479] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[69200.080481] usb 1-3: Product: USB Receiver
[69200.080483] usb 1-3: Manufacturer: Logitech
[69200.082593] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C534.0005/input/input15
[69200.138743] hid-generic 0003:046D:C534.0005: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-3/input0
[69200.141132] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C534.0006/input/input16
[69200.194674] hid-generic 0003:046D:C534.0006: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-3/input1
[69828.804290] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
[69828.814434] mmc0: card 0007 removed
[69828.852418] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8.
[69828.852422] Aborting journal on device mmcblk0p1-8.
[69828.852425] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8.

After plugging in SD card -

dmesg | tail -n 25
[ 7345.102283] mmcblk0: mmc0:0007 7YDLP 120 GiB 
[ 7345.103365]  mmcblk0: p1
[ 7345.287972] EXT4-fs (mmcblk0p1): recovery complete
[ 7345.287977] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[11212.591032] usb 1-3: USB disconnect, device number 4
[55305.091492] perf interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[69199.894438] usb 1-3: new full-speed USB device number 5 using xhci_hcd
[69200.080475] usb 1-3: New USB device found, idVendor=046d, idProduct=c534
[69200.080479] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[69200.080481] usb 1-3: Product: USB Receiver
[69200.080483] usb 1-3: Manufacturer: Logitech
[69200.082593] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C534.0005/input/input15
[69200.138743] hid-generic 0003:046D:C534.0005: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-3/input0
[69200.141132] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C534.0006/input/input16
[69200.194674] hid-generic 0003:046D:C534.0006: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-3/input1
[69828.804290] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
[69828.814434] mmc0: card 0007 removed
[69828.852418] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8.
[69828.852422] Aborting journal on device mmcblk0p1-8.
[69828.852425] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8.
[69994.377678] mmc0: new ultra high speed SDR104 SDXC card at address 0007
[69994.378053] mmcblk0: mmc0:0007 7YDLP 120 GiB 
[69994.379453]  mmcblk0: p1
[69999.048738] EXT4-fs (mmcblk0p1): recovery complete
[69999.050509] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)

It seems SD card is getting added as mmc0. Thus I get nothing for last two commands you gave.

sudo gdisk -l /dev/mmcblk1
GPT fdisk (gdisk) version 1.0.1

Problem opening /dev/mmcblk1 for reading! Error is 2.
The specified file does not exist!

sudo gdisk -l /dev/mmcblkp1
GPT fdisk (gdisk) version 1.0.1

Problem opening /dev/mmcblkp1 for reading! Error is 2.
The specified file does not exist!

But with mmblk0 , I get following info

~$ sudo gdisk -l /dev/mmcblk0
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. 
***************************************************************


Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/mmcblk0: 250806272 sectors, 119.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): BAAA66D2-1566-4C04-8C2B-5FFBE3941269
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 250806238
Partitions will be aligned on 2048-sector boundaries
Total free space is 32734 sectors (16.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1           32768       250806271   119.6 GiB   8300  Linux filesystem

It seems it is getting named as mmcblk0, on my host. Will be still be named same way on Tx2 ?

Thanks,

I don’t know if this is related, but to start with you seem to have a USB problem, plus an error on your first mmc device (perhaps a wireless device simply isn’t close enough):

...
    [69200.082593] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C534.0005/input/input15
    [69200.138743] hid-generic 0003:046D:C534.0005: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-3/input0
    [69200.141132] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C534.0006/input/input16
    [69200.194674] hid-generic 0003:046D:C534.0006: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-3/input1
    [69828.804290] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
    [69828.814434] mmc0: card 0007 removed
    [69828.852418] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8.
    [69828.852422] Aborting journal on device mmcblk0p1-8.
    [69828.852425] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8.

…this makes me wonder about SD card readers which are USB, and any other SD card you may use with the host. Beware that you can’t just remove an SD card from a host if it is mounted…it needs umount first or it will corrupt.

Because there is no other SD card this card’s first partition becomes “mmc0blk1”. This is why “mmcblk1” is not valid, this must be adjusted to “mmcblk0” when the SD card is the first device (see “ls /dev/mmcblk*” for a list of what SD cards your system sees…on a running Jetson mmcblk0 is the eMMC, and anything after that would be SD card).

Summary:

  • mmcblk0 is the first flash device.
  • mmcblk0p1 is the first partition of the first flash device.
  • mmcblk1 is the second flash device.
  • mmcblk1p1 is the first partition of the second flash device.
  • On a Jetson eMMC is mmcblk0, thus SD card will be mmcblk1
  • On a Jetson the first partition of the SD card will be mmcblk1p1
  • On your host the first partition with no other flash devices connected will be mmcblk0p1

So those commands I mentioned earlier for testing the SD depend on adjusting for host or Jetson mount.
To safely remove the SD card when mmcblk0 has partition 1 mounted:

sudo umount /dev/mmcblk0p1

Thanks Linuxdev.

When I plug in SD card on Tx2 it gets named as mmcblk1.“sudo gdisk -l /dev/mmcblk1” command gives following output on Tx2. Could invalid GPT be any reason (as given by the output below ) ?

“You will need to delete this partition or resize it in another utility”

Which partition is being referred to by ‘this’ ? Any idea how to delete ‘this’ or resize it ?

Thanks,

ubuntu@tegra-ubuntu:~$ sudo gdisk -l /dev/mmcblk1
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. 
***************************************************************


Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/mmcblk1: 250806272 sectors, 119.6 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 30C2620F-79CE-454D-9197-C186D9060CDD
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 250806238
Partitions will be aligned on 2048-sector boundaries
Total free space is 32734 sectors (16.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1           32768       250806271   119.6 GiB   8300  Linux filesystem
ubuntu@tegra-ubuntu:~$