The TX2 Can't work when I plugged the hdmi to power on

The TX2 Can’t work when I plugged the hdmi to power on. I unplug the hdmi and power on, it return to normal,and then I plug the hdmi it also normal.Please help me to resolve this problem, thank you so much.

To make your problem more easier to understand, only hotplug the cable would hit this issue.

When you hit such issue, it is common to share below information

  1. Which release are you using?
  2. Are you using a nvidia devkit?
  3. Please paste the error log from dmesg to us. Please check your forum post after you send it out to make sure the log is not missing.
  • Thank you very much.

    1. The release is L28.3.2
    2. The carrier board is designed by myself.
    3. I cat the something when the power on unormal.
    Jan 17 09:02:14 jetson-0422518026124 systemd[1]: Starting System Logging Service...
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/siri.c:ofono_siri_driver_register() driver: 0x563f88, name: hfpmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/network.c:ofono_netreg_driver_register() driver: 0x563c60, name: dunmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_driver_register() driver: 0x563ca8, name: dunmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x563ac8, name: stemodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x563be0, name: stemodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x563b68, name: stemodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x563888, name: ifxmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/audio-settings.c:ofono_audio_settings_driver_register() driver: 0x563938, name: ifxmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x563960, name: ifxmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x5639d0, name: ifxmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/stk.c:ofono_stk_driver_register() driver: 0x563a20, name: ifxmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/ctm.c:ofono_ctm_driver_register() driver: 0x563a60, name: ifxmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x5637a8, name: hsomodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x5637e8, name: hsomodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/location-reporting.c:ofono_location_reporting_driver_register() driver: 0x563728, name: telitmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x563618, name: mbmmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/stk.c:ofono_stk_driver_register() driver: 0x563658, name: mbmmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/location-reporting.c:ofono_location_reporting_driver_register() driver: 0x563698, name: mbmmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x5634e8, name: calypsomodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/stk.c:ofono_stk_driver_register() driver: 0x563588, name: calypsomodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/ussd.c:ofono_ussd_driver_register() driver: 0x5632f8, name: huaweimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x563320, name: huaweimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/audio-settings.c:ofono_audio_settings_driver_register() driver: 0x5633c0, name: huaweimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x563428, name: huaweimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x5633e8, name: huaweimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/cdma-netreg.c:ofono_cdma_netreg_driver_register() driver: 0x563488, name: huaweimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x563208, name: iceramodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x563258, name: iceramodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x563158, name: ztemodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x5630d8, name: swmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x563048, name: nwmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x562d38, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_devinfo_driver_register() driver: 0x562e68, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-barring.c:ofono_call_barring_driver_register() driver: 0x562dd8, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-forwarding.c:ofono_call_forwarding_driver_register() driver: 0x5628e8, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-meter.c:ofono_call_meter_driver_register() driver: 0x562968, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-settings.c:ofono_call_settings_driver_register() driver: 0x562780, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/phonebook.c:ofono_phonebook_driver_register() driver: 0x562e38, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/ussd.c:ofono_ussd_driver_register() driver: 0x562cf0, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sms.c:ofono_sms_driver_register() driver: 0x562860, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sim.c:ofono_sim_driver_register() driver: 0x562b70, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sim.c:ofono_sim_driver_register() driver: 0x562c00, name: atmodem-noef
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/stk.c:ofono_stk_driver_register() driver: 0x562ca0, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/network.c:ofono_netreg_driver_register() driver: 0x562a30, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/cbs.c:ofono_cbs_driver_register() driver: 0x5628b0, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-volume.c:ofono_call_volume_driver_register() driver: 0x562ec0, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_driver_register() driver: 0x562f20, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x562f50, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sim-auth.c:ofono_sim_auth_driver_register() driver: 0x562f90, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gnss.c:ofono_gnss_driver_register() driver: 0x562fd0, name: atmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_modem_driver_register() driver: 0x562390, name: gobi
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_devinfo_driver_register() driver: 0x562018, name: qmimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/network.c:ofono_netreg_driver_register() driver: 0x5620e0, name: qmimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x562050, name: qmimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sim.c:ofono_sim_driver_register() driver: 0x562128, name: qmimodem-legacy
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sim.c:ofono_sim_driver_register() driver: 0x5621b8, name: qmimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sms.c:ofono_sms_driver_register() driver: 0x562248, name: qmimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/ussd.c:ofono_ussd_driver_register() driver: 0x562288, name: qmimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_driver_register() driver: 0x5622b0, name: qmimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x5622e0, name: qmimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x562310, name: qmimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/location-reporting.c:ofono_location_reporting_driver_register() driver: 0x562360, name: qmimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_modem_driver_register() driver: 0x561f40, name: u8500
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_devinfo_driver_register() driver: 0x561f08, name: u8500
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_modem_driver_register() driver: 0x561e70, name: n900
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_modem_driver_register() driver: 0x561dd8, name: isiusb
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_devinfo_driver_register() driver: 0x561930, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/phonebook.c:ofono_phonebook_driver_register() driver: 0x561910, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/network.c:ofono_netreg_driver_register() driver: 0x561968, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x5619b0, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sms.c:ofono_sms_driver_register() driver: 0x561a40, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/cbs.c:ofono_cbs_driver_register() driver: 0x561a80, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sim.c:ofono_sim_driver_register() driver: 0x561aa8, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/ussd.c:ofono_ussd_driver_register() driver: 0x561b38, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-forwarding.c:ofono_call_forwarding_driver_register() driver: 0x561b60, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-settings.c:ofono_call_settings_driver_register() driver: 0x561ba0, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-barring.c:ofono_call_barring_driver_register() driver: 0x561c00, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-meter.c:ofono_call_meter_driver_register() driver: 0x561c30, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x561c80, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_driver_register() driver: 0x561cd0, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x561d00, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/audio-settings.c:ofono_audio_settings_driver_register() driver: 0x561d30, name: isimodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sim.c:ofono_sim_driver_register() driver: 0x561d48, name: wgmodem2.5
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: drivers/qcommsimmodem/qcom_msim_modem.c:qcom_msim_modem_init()
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x561880, name: qcommsimmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: drivers/rilmodem/rilmodem.c:rilmodem_init()
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_devinfo_driver_register() driver: 0x561458, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: drivers/rilmodem/sim.c:ril_sim_init()
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sim.c:ofono_sim_driver_register() driver: 0x5615f8, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x5614d8, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: drivers/rilmodem/sms.c:ril_sms_init()
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/sms.c:ofono_sms_driver_register() driver: 0x561688, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/network.c:ofono_netreg_driver_register() driver: 0x561490, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-volume.c:ofono_call_volume_driver_register() driver: 0x561568, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_driver_register() driver: 0x561598, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0x5615c8, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/ussd.c:ofono_ussd_driver_register() driver: 0x5616c8, name: rilmodem[code]
    

    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-settings.c:ofono_call_settings_driver_register() driver: 0x5616f0, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-forwarding.c:ofono_call_forwarding_driver_register() driver: 0x561750, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x561790, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/call-barring.c:ofono_call_barring_driver_register() driver: 0x5617e0, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/phonebook.c:ofono_phonebook_driver_register() driver: 0x561820, name: rilmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: drivers/mtkmodem/mtkmodem.c:mtkmodem_init()
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0x561308, name: mtkmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/gprs.c:ofono_gprs_driver_register() driver: 0x561398, name: mtkmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0x5613c8, name: mtkmodem
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_modem_driver_register() driver: 0x5611e0, name: qcom_msim
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_modem_driver_register() driver: 0x561148, name: infineon
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: src/modem.c:ofono_modem_driver_register() driver: 0x5610b0, name: mtk
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udevng.c:udev_start()
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udevng.c:enumerate_devices()
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: Failed to create system keep alive wakelock
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: Failed to create system keep alive wakelock
    Jan 17 09:02:14 jetson-0422518026124 anacron[464]: Anacron 2.3 started on 2020-01-17
    Jan 17 09:02:14 jetson-0422518026124 anacron[464]: Normal exit (0 jobs run)
    Jan 17 09:02:14 jetson-0422518026124 dnsmasq[469]: dnsmasq: syntax check OK.
    Jan 17 09:02:14 jetson-0422518026124 systemd[1]: Started Regular background program processing daemon.
    Jan 17 09:02:14 jetson-0422518026124 systemd[1]: Started crash report submission daemon.
    Jan 17 09:02:14 jetson-0422518026124 systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down…
    Jan 17 09:02:14 jetson-0422518026124 systemd[1]: Started NVIDIA specific first-boot script.
    Jan 17 09:02:14 jetson-0422518026124 systemd[1]: Started Permit User Sessions.
    Jan 17 09:02:14 jetson-0422518026124 systemd[1]: Started LSB: Set up cgroupfs mounts…
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 systemd[1]: Started System Logging Service.
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty add
    Jan 17 09:02:14 jetson-0422518026124 ofonod[441]: plugins/udev.c:udev_event() subsystem tty finished[/code]

    1. I cat the something when the power on unormal.

    This is not what we need. We don’t need syslog. Moreover, your syslog does not have any kernel info.

    1. If your system is still alive after hotplug, please use command “dmesg” and share us the kernel log.

    2. If your system is dead after hotplug, please try to dump the serial console log and share the last message spew from uart.
      https://www.jetsonhacks.com/2017/03/24/serial-console-nvidia-jetson-tx2/

    Jan 17 09:20:22 jetson-0422518026124 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="449" x-info="http://www.rsyslog.com"] start
    Jan 17 09:20:22 jetson-0422518026124 systemd-modules-load[276]: Inserted module 'bluedroid_pm'
    Jan 17 09:20:22 jetson-0422518026124 systemd-modules-load[276]: Module 'nvhost_vi' is builtin
    Jan 17 09:20:22 jetson-0422518026124 systemd[1]: Started Remount Root and Kernel File Systems.
    Jan 17 09:20:22 jetson-0422518026124 systemd[1]: Started Create list of required static device nodes for the current kernel.
    Jan 17 09:20:22 jetson-0422518026124 rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
    Jan 17 09:20:22 jetson-0422518026124 rsyslogd: rsyslogd's groupid changed to 115
    Jan 17 09:20:22 jetson-0422518026124 rsyslogd: rsyslogd's userid changed to 108
    Jan 17 09:20:22 jetson-0422518026124 systemd[1]: Started Load Kernel Modules.
    Jan 17 09:20:22 jetson-0422518026124 systemd[1]: Started LVM2 metadata daemon.
    Jan 17 09:20:22 jetson-0422518026124 systemd[1]: Mounting Configuration File System...
    Jan 17 09:20:22 jetson-0422518026124 systemd[1]: Starting Apply Kernel Variables...
    Jan 17 09:20:22 jetson-0422518026124 systemd[1]: Starting Create Static Device Nodes in /dev...
    Jan 17 09:20:22 jetson-0422518026124 systemd[1]: Starting Load/Save Random Seed...
    Jan 17 09:20:22 jetson-0422518026124 systemd-sysctl[288]: Couldn't write '1' to 'net/ipv4/tcp_syncookies', ignoring: No such file or directory
    Jan 17 09:20:22 jetson-0422518026124 systemd-sysctl[288]: Couldn't write '1' to 'kernel/yama/ptrace_scope', ignoring: No such file or directory
    Jan 17 09:20:22 jetson-0422518026124 systemd[1]: Starting udev Coldplug all Devices...
    

    That it is not kernel log… This is also syslog…

    There isn’t uart on my board ,are there any way to find the problem, thank you so much.
    And when it dead it will reboot after.

    If there is no uart, then it is not possible to debug such issue.

    You could try different hdmi cable and monitors to see if every monitor would hit this issue.
    If every HDMI monitor hits this issue, then it is a hardware issue and you will need to review your hardware design then.

    It’s ok in L28.3.1, I used the same device tree on L28.3.2,it occur this problem.
    Thank you so much to help me find the problem…Although I can’t find it.
    Thank you.

    Are these conflicts between “sor” and USB0 ‘otg’,I found the problem when I set the usb0 otg.
    Thank you very much.

    And I found this

    [   45.548679] tegradc 15200000.nvdisplay: Invalid out_w + out_x (1280) > hActive (1024)
                    OR/AND out_h + out_y (720) > vActive (600)
                    for WIN 0
    

    This probably would be a lot of work, and perhaps still not show enough logging, but if you are motivated you might clone the filesystem after a failure and provide a copy of “/var/log/kern.log”.

    Keep in mind that so long as you don’t fully boot the system after a failure, then it doesn’t matter which carrier board you clone from (I don’t know if clone will work from your carrier board or not).

    If you wanted to do this, then here is what I would suggest:

    1. Boot the unit until it fails.
    2. Use the "magic sysrq" keys to make sure the eMMC is in sync and flushed (don't do this unless you need to) and the filesystem unmounted (any corruption would be contained in a clone and recent disk activity would be lost...this helps prevent ext4 journal replay issues):
      1. Press ALT+SYSRQ+s twice.
      2. Press ALT+SYSRQ+u once.
      3. Power off. Do not power on after this unless it is into recovery mode.
    3. Clone (unfortunately the instructions vary depending on release, and in one case there is a bug fix to flash.sh...if you have an error post it here since this might be the version of flash.sh needing a patch...or see the URL https://devtalk.nvidia.com/default/topic/1000105/jetson-tx2/tx2-cloning/post/5111893/#5111893 for the patch if needed). Notes:
      1. TX2 in recovery mode and micro-B USB cable connected.
      2. Make sure you have a lot of space...one file will be about 30GB (clone.img.raw), another two to four GB (clone.img).
      3. sudo ./flash.sh -r -k APP -G clone.img jetson-tx2 mmcblk0p1
      4. The "clone.img" can be discarded. This file works for flashing, but cannot be examined or manipulated.
      5. The file you can loopback mount is the "clone.img.raw". This file can be used for flashing or manipulating or examining content. The down side is the very large file size and increased time required even doing a copy of the file.
    4. Mount the "clone.img.raw" version on the host PC (read-only is good).
    5. I will assume you created or are otherwise mounting at "/mnt", but this could be any directory you created.
    6. sudo mount -o loop,ro ./clone.img.raw /mnt
    7. cd /mnt/var/log
    8. cp kern.log /where/ever/you/want/to/save/it/
    9. Attach that file (may need to rename with ".txt" to one of your existing posts.
    10. sudo umount /mnt
    11. You could save other files from "/var/log/" if you want to, or just keep the whole image, or delete the image (at nearly 30GB this might be too much space to keep around).

    Having a serial UART console is superior though since it includes more logging and logging from before Linux runs.

    Thank you. I try it. I found the problem may be… a kernel bug? Because I found the problem on my 1024*600 hdmi monitor and the others monitors is normal.

    Only HDMI auto configuration is allowed, which in turn means only EDID modes (modes from query of the monitor over i2c…something VGA lacks) are supported. Among those there is a “mode pool” of supported modes within the driver itself, and of the modes reported to the driver, only the compatible subset of EDID modes are supported. It is quite possible that an odd layout from a 1024*600 HDMI monitor may not produce any modes supported by the available modes (an empty final mode pool).

    This would definitely cause display to not work, but should not provide a crash.

    As a suggestion, if you can now boot with a different monitor, or even no monitor at all, and monitor via serial console (which can log for you), then use the “hot plug” properties of HDMI…meaning you can un plug or plug in your HDMI cable at any time and this should be detected. If you are fully booted, either with a different monitor or no monitor at all, then unplug of the working monitor would provide some output. Following this you would want to see what shows up in “dmesg --follow” over serial console as the monitor with failing case is connected.

    Should you be able to get this to not crash from late plugin, then this is good debug information. Any logging during plugin would be valuable. Should it turn out that the unit itself is working, and there is only an issue with the one monitor, then this can probably be debugged instead of doing an RMA.

    Note: If you can boot without that monitor and can get further debugging logs, then it would be important to know what release this is from “head -n 1 /etc/nv_tegra_release”. You may also want to run the command “sha1sum -c /etc/nv_tegra_release” and verify if all files list “ok” or not. If all files are not “ok”, then there may be a corrupted or altered or missing driver (which could cause similar problems).