I create similar dtb as yours, but didn’t delete the plugin-manager. Please try your dtb without deleting plugin-manager and jetpack4.4.1.
Tried that, no change in behaviour, device still doesn’t resume beyond lighting LED CR1.
We cannot reproduce your issue with the dtb modified and latest jetpack4.4.1
I was able to reproduce the problem on 4.4.1 but I had to take additional steps so that the serial debug console was actually disabled. Here’s the details:
With a fresh 4.4.1 install & the modified device-tree in place, I was able to observe this:
nvidia@nvidia-desktop:~$ dmesg | grep ttyS0
[ 0.000000] Kernel command line: root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=tty0 fbcon=map:0 net.ifnames=0 vi4_fops.dyndbg channel.dyndbg csi4_fops.dyndbg csi.dyndbg camera_common.dyndbg graph.dyndbg tc358840.dyndbg debug root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x3100000 nvdumper_reserved=0x2772e0000 gpt usbcore.old_scheme_first=1 tegraid=18.1.2.0.0 maxcpus=6 boot.slot_suffix= boot.ratchetvalues=0.2031647.1 bl_prof_dataptr=0x10000@0x275840000 sdhci_tegra.en_boot_part_access=1 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2
[ 0.930123] console [ttyS0] disabled
[ 0.930144] 3100000.serial: ttyS0 at MMIO 0x3100000 (irq = 36, base_baud = 25500000) is a Tegra
[ 0.930177] console [ttyS0] enabled
[ 1.973466] systemd-getty-generator[2084]: Automatically adding serial getty for /dev/ttyS0.
Note that the serial debug console is still enabled despite the device-tree change. For comparision, this is observed on the 4.2.1 Jetson:
nvidia@jetpack4dot2dot1:~$ dmesg | grep ttyS0
[ 1.022469] 3100000.serial: ttyS0 at MMIO 0x3100000 (irq = 36, base_baud = 25500000) is a Tegra
Sure ttyS0 is still there, but it’s not being used as a console.
You can further confirm that ttyS0 is not being used as a console (beyond looking at what’s coming out of the serial port!) by the following:
nvidia@jetpack4dot2dot1:~$ cat /proc/consoles
tty0 -WU (EC ) 4:1
pstore-1 -W- (E p a)
I know that you can enable/disable serial debug ports on the kernel cmdline, nvidia@jetpack4dot2dot1:~$ grep ttyS0 /proc/cmdline yielded no results.
For reference this is what /boot/extlinux/extlinux.conf looks lik on my fresh 4.2.1 install:
nvidia@jetpack4dot2dot1:~$ cat /boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet
# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
# sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot
# LABEL backup
# MENU LABEL backup kernel
# LINUX /boot/Image.backup
# INITRD /boot/initrd
# APPEND ${cbootargs}
So hopping back over to the fresh 4.4.1 install (with the modified device-tree) & looking at the same files:
nvidia@nvidia-desktop:~$ cat /boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND ${cbootargs} quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2
# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
# sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot
# LABEL backup
# MENU LABEL backup kernel
# LINUX /boot/Image.backup
# INITRD /boot/initrd
# APPEND ${cbootargs}
nvidia@nvidia-desktop:~$ grep ttyS0 /proc/cmdline
root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=tty0 fbcon=map:0 net.ifnames=0 vi4_fops.dyndbg channel.dyndbg csi4_fops.dyndbg csi.dyndbg camera_common.dyndbg graph.dyndbg tc358840.dyndbg debug root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x3100000 nvdumper_reserved=0x2772e0000 gpt usbcore.old_scheme_first=1 tegraid=18.1.2.0.0 maxcpus=6 boot.slot_suffix= boot.ratchetvalues=0.2031647.1 bl_prof_dataptr=0x10000@0x275840000 sdhci_tegra.en_boot_part_access=1 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2
nvidia@nvidia-desktop:~$ cat /proc/consoles
tty0 -WU (EC ) 4:1
ttyS0 -W- (E p a) 4:64
pstore-1 -W- (E p a)
We can see that a fresh 4.4.1 install enables ttyS0 as console via the kernel cmdline and of course you can see the debug console coming out of the serial port.
I edited /boot/extlinux/extlinx.conf to look like:
nvidia@nvidia-desktop:~$ cat /boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT primary
MENU TITLE L4T boot options
LABEL primary
MENU LABEL primary kernel
LINUX /boot/Image
INITRD /boot/initrd
APPEND root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=tty0 fbcon=map:0 net.ifnames=0 vi4_fops.dyndbg channel.dyndbg csi4_fops.dyndbg csi.dyndbg camera_common.dyndbg graph.dyndbg tc358840.dyndbg debug root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x3100000 nvdumper_reserved=0x2772e0000 gpt usbcore.old_scheme_first=1 tegraid=18.1.2.0.0 maxcpus=6 boot.slot_suffix= boot.ratchetvalues=0.2031647.1 bl_prof_dataptr=0x10000@0x275840000 sdhci_tegra.en_boot_part_access=1 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2
# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
# sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot
# LABEL backup
# MENU LABEL backup kernel
# LINUX /boot/Image.backup
# INITRD /boot/initrd
# APPEND ${cbootargs}
with the following results:
nvidia@nvidia-desktop:~$ cat /proc/consoles
tty0 -WU (EC ) 4:1
pstore-1 -W- (E p a)
nvidia@nvidia-desktop:~$ grep ttyS0 /proc/cmdline
nvidia@nvidia-desktop:~$ cat /proc/cmdline
root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=tty0 fbcon=map:0 net.ifnames=0 vi4_fops.dyndbg channel.dyndbg csi4_fops.dyndbg csi.dyndbg camera_common.dyndbg graph.dyndbg tc358840.dyndbg debug root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x3100000 nvdumper_reserved=0x2772e0000 gpt usbcore.old_scheme_first=1 tegraid=18.1.2.0.0 maxcpus=6 boot.slot_suffix= boot.ratchetvalues=0.2031647.1 bl_prof_dataptr=0x10000@0x275840000 sdhci_tegra.en_boot_part_access=1 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2
With no debug coming out of the serial port I once again performed a systemctl suspend, on providing the wake signal again LED CR1 lit & the lights on the ethernet sockets remained on but sadly, that was the only change. The device was non-responsive over ethernet, it did not respond to pings, the device was no longer accessible over USB OTG & just as before there was no activity on the HDMI display.
To help with testing I’m uploading the dtb I’m using.
tegra186-quill-p3310-1000-c03-00-base_sigheader.dtb.encrypt (233.6 KB)