*** Please note that this reply is generated by LLM automatically ***
The provided information does not directly relate to the question about the Jetson AGX Orin image. However, I can provide some general information about the Jetson AGX Orin and its related topics.
The Jetson AGX Orin is a high-performance AI computing module developed by NVIDIA. It is designed for various applications, including robotics, autonomous vehicles, and edge AI computing.
The provided context includes information about the Jetson Orin NX and Nano series modules, their thermal design guide, and some related topics such as disk encryption, partition layout, and containerization.
The question seems to be asking about a specific image related to the Jetson AGX Orin, but without more context, it is difficult to provide a comprehensive answer. If you could provide more information about the image, such as its purpose or where it is used, I may be able to provide a more detailed answer.
In general, the Jetson AGX Orin module is a powerful AI computing platform that can be used for various applications. It has a high-performance GPU, CPU, and memory, making it suitable for demanding AI workloads.
If you are looking for information about a specific image related to the Jetson AGX Orin, I would recommend checking the official NVIDIA documentation or forums for more information.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
“Session 10 logged out. Waiting for processes to exit.”
That usually means one or more processes are still attached to the user session after logout, so logind keeps the session around until they die. find the process that is keeping the session alive, then decide whether to kill it, move it out of the session, or change how it is launched.
See which sessions still exist and which one is stuck:
loginctl list-sessions
loginctl session-status 9
loginctl session-status 10
Then list the processes still belonging to the user and their session:
ps -eo pid,ppid,user,tty,stat,etimes,cmd | grep maxsense
loginctl show-session 9 -p Id -p Name -p User -p State -p Remote -p Leader -p Scope
loginctl show-session 10 -p Id -p Name -p User -p State -p Remote -p Leader -p Scope
If a session is stuck, look at the leader PID:
ps -fp <leader_pid>
pstree -aps <leader_pid>
If you find the offender, test by killing it:
kill -TERM $pid
sleep 2
kill -KILL $pid
Or kill the whole session cleanly:
loginctl terminate-session 9
loginctl terminate-session 10
journalctl -u systemd-logind -b --no-pager
A test is to create a fresh user and try GUI login with that user.
sudo adduser testlogin
sudo usermod -aG sudo testlogin
If testlogin works, the problem is almost certainly in maxsense’s home directory or user services.
If testlogin also fails, look harder at system graphics, BSP, display manager, kernel logs, and that CBB fault.
Your system date time looks to be about 2 months ahead of actual date
timedatectl status
sudo timedatectl set-time
set-time [TIME]
Set the system clock to the specified time. This will also update the RTC time accordingly.
The time may be specified in the format “2026-03-26 21:42:52”.
这个我也测试过依旧还是失败了
Jun 18 04:37:36 msad323m /usr/lib/gdm3/gdm-x-session[4309]: Unable to register display with display manager
Jun 18 04:37:36 msad323m /usr/lib/gdm3/gdm-x-session[4311]: (II) event2 - Logitech Wireless Mouse: device removed
Jun 18 04:37:36 msad323m /usr/lib/gdm3/gdm-x-session[4311]: (II) event1 - Logitech Wireless Keyboard PID:4023: device removed
Jun 18 04:37:37 msad323m /usr/lib/gdm3/gdm-x-session[4311]: (II) UnloadModule: “libinput”
Jun 18 04:37:37 msad323m /usr/lib/gdm3/gdm-x-session[4311]: (II) UnloadModule: “libinput”
Jun 18 04:37:37 msad323m /usr/lib/gdm3/gdm-x-session[4311]: (II) UnloadModule: “libinput”
Jun 18 04:37:37 msad323m /usr/lib/gdm3/gdm-x-session[4311]: (II) NVIDIA(GPU-0): Deleting GPU-0
Jun 18 04:37:37 msad323m /usr/lib/gdm3/gdm-x-session[4311]: (II) Server terminated successfully (0). Closing log file.
Jun 18 04:37:37 msad323m gdm-password][3148]: pam_unix(gdm-password:session): session closed for user maxsense
Jun 18 04:37:37 msad323m gdm3[2055]: GdmDisplay: Session never registered, failing
Jun 18 04:38:30 msad323m gdm-password][4555]: gkr-pam: unable to locate daemon control file
Jun 18 04:38:30 msad323m gdm-password][4555]: gkr-pam: stashed password to try later in open session
Jun 18 04:38:30 msad323m gdm-password][4555]: pam_unix(gdm-password:account): account maxsense has password changed in future
Jun 18 04:38:30 msad323m gdm-password][4555]: pam_unix(gdm-password:session): session opened for user maxsense by (uid=0)
Jun 18 04:40:00 msad323m gdm-password][4555]: pam_systemd(gdm-password:session): Failed to create session: Job 1890 for unit ‘session-9.scope’ failed with ‘dependency’
Jun 18 04:40:00 msad323m gdm-password][4555]: gkr-pam: unable to locate daemon control file
Jun 18 04:40:00 msad323m gdm-password][4555]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: _XSERVTransSocketUNIXCreateListener: …SocketCreateListener() failed
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: _XSERVTransMakeAllCOTSServerListeners: server already running
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) Log file renamed from “/var/log/Xorg.pid-5231.log” to “/var/log/Xorg.1.log”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: X.Org X Server 1.20.13
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: X Protocol Version 11, Revision 0
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Build Operating System: linux Ubuntu
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Current Operating System: Linux msad323m 5.10.120-tegra #5 SMP PREEMPT Thu May 15 15:20:10 CST 2025 aarch64
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Kernel command line: root=PARTUUID=0467a4a1-2cd6-4558-8b50-0085495d1b0a rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 console=tty0 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 console=tty0 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nospectre_bhb
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Build Date: 19 February 2025 01:54:27PM
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: xorg-server 2:1.20.13-1ubuntu1~20.04.19 (For technical support please see Enterprise open source support | Ubuntu)
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Current version of pixman: 0.38.4
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Before reporting problems, check http://wiki.x.org
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: to make sure that you have the latest version.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Markers: (–) probed, () from config file, (==) default setting,
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (++) from command line, (!!) notice, (II) informational,
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) Log file: “/var/log/Xorg.1.log”, Time: Tue Jun 18 04:40:00 2024
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) Using config file: “/etc/X11/xorg.conf”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) Using config directory: “/etc/X11/xorg.conf.d”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) Using system config directory “/usr/share/X11/xorg.conf.d”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) No Layout section. Using the first Screen section.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) No screen section available. Using defaults.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () |–>Screen “Default Screen Section” (0)
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () | |–>Monitor “”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) No device specified for screen “Default Screen Section”.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Using the first device section listed.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () | |–>Device “Tegra0”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) No monitor specified for screen “Default Screen Section”.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Using a default monitor configuration.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) Automatically adding devices
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) Automatically enabling devices
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) Automatically adding GPU devices
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) Automatically binding GPU devices
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) Max clients allowed: 256, resource mask: 0x1fffff
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Entry deleted from font path.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) The directory “/usr/share/fonts/X11/100dpi/” does not exist.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Entry deleted from font path.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) The directory “/usr/share/fonts/X11/75dpi/” does not exist.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Entry deleted from font path.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) The directory “/usr/share/fonts/X11/100dpi” does not exist.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Entry deleted from font path.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) The directory “/usr/share/fonts/X11/75dpi” does not exist.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Entry deleted from font path.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) FontPath set to:
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: /usr/share/fonts/X11/misc,
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: /usr/share/fonts/X11/Type1,
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: built-ins
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) ModulePath set to “/usr/lib/xorg/modules”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) The server relies on udev to provide the list of input devices.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: If no devices become available, reconfigure udev or disable AutoAddDevices.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loader magic: 0xaaaae917a010
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Module ABI versions:
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: X.Org ANSI C Emulation: 0.4
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: X.Org Video Driver: 24.1
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: X.Org XInput driver : 24.1
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: X.Org Server Extension : 10.0
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (++) using VT number 2
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (EE) systemd-logind: failed to get session: PID 5231 does not belong to any known session
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) no primary bus or device found
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) “dri” will not be loaded unless you’ve specified it to be loaded elsewhere.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) “glx” will be loaded by default.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) LoadModule: “extmod”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Module “extmod” already built-in
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) LoadModule: “glx”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Module glx: vendor=“X.Org Foundation”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: compiled for 1.20.13, module version = 1.0.0
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: ABI class: X.Org Server Extension, version 10.0
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) LoadModule: “nvidia”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Module nvidia: vendor=“NVIDIA Corporation”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: compiled for 1.6.99.901, module version = 1.0.0
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Module class: X.Org Video Driver
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA dlloader X Driver 35.4.1 Release Build (bugfix_main) (buildbrain@mobile-u64-6422-d7000) Tue Aug 1 12:40:10 PDT 2023
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) Falling back to old probe method for NVIDIA
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading sub module “fb”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) LoadModule: “fb”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading /usr/lib/xorg/modules/libfb.so
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Module fb: vendor=“X.Org Foundation”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: compiled for 1.20.13, module version = 1.0.0
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: ABI class: X.Org ANSI C Emulation, version 0.4
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading sub module “wfb”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) LoadModule: “wfb”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading /usr/lib/xorg/modules/libwfb.so
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Module wfb: vendor=“X.Org Foundation”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: compiled for 1.20.13, module version = 1.0.0
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: ABI class: X.Org ANSI C Emulation, version 0.4
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading sub module “ramdac”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) LoadModule: “ramdac”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Module “ramdac” already built-in
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): Creating default Display subsection in Screen section
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: “Default Screen Section” for depth/fbbpp 24/32
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0): RGB weight 888
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0): Default visual is TrueColor
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (DB) xf86MergeOutputClassOptions unsupported bus type 0
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () NVIDIA(0): Option “AllowEmptyInitialConfiguration” “true”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () NVIDIA(0): Enabling 2D acceleration
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading sub module “glxserver_nvidia”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) LoadModule: “glxserver_nvidia”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading /usr/lib/xorg/modules/extensions/libglxserver_nvidia.so
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Module glxserver_nvidia: vendor=“NVIDIA Corporation”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: compiled for 1.6.99.901, module version = 1.0.0
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Module class: X.Org Server Extension
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA GLX Module 35.4.1 Release Build (bugfix_main) (buildbrain@mobile-u64-6422-d7000) Tue Aug 1 12:38:45 PDT 2023
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA: The X server supports PRIME Render Offload.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(0): Valid display device(s) on GPU-0 at SoC
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(0): DFP-0
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(0): DFP-1
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) NVIDIA: No DRM device: No direct render devices found.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): NVIDIA GPU Orin (nvgpu) (GA10B) at SoC (GPU-0)
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(0): Memory: 31329640 kBytes
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(0): VideoBIOS:
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(GPU-0): DFP-0: disconnected
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(GPU-0): DFP-0: 2380.0 MHz maximum pixel clock
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(GPU-0):
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(GPU-0): Huawei Technologies Co., Ltd SSN-24 (DFP-1): connected
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(GPU-0): Huawei Technologies Co., Ltd SSN-24 (DFP-1): Internal TMDS
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(GPU-0): Huawei Technologies Co., Ltd SSN-24 (DFP-1): 165.0 MHz maximum pixel clock
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(GPU-0):
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0):
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0): No modes were requested; the default mode “nvidia-auto-select”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0): will be used as the requested mode.
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0):
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): Validated MetaModes:
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): “DFP-1:nvidia-auto-select”
Jun 18 04:40:00 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(0): DPI set to (92, 91); computed from “UseEdidDpi” X config
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (–) NVIDIA(0): option
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA: access.
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (WW) NVIDIA(GPU-0): Failed to enter interactive mode.
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (EE) NVIDIA(0): Failed to allocate NVIDIA Error Handler
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): may not be running or the “AcpidSocketPath” X
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): configuration option may not be set correctly. When the
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): details, please see the “ConnectToAcpid” and
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): “AcpidSocketPath” X configuration options in Appendix B: X
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): Config Options in the README.
Jun 18 04:40:01 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): Setting mode “DFP-1:nvidia-auto-select”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0): Disabling shared memory pixmaps
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0): Backing store enabled
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0): Silken mouse enabled
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (==) NVIDIA(0): DPMS enabled
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading sub module “dri2”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) LoadModule: “dri2”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Module “dri2” already built-in
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): [DRI2] Setup complete
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension Generic Event Extension
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension SHAPE
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension MIT-SHM
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XInputExtension
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XTEST
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension BIG-REQUESTS
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension SYNC
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XKEYBOARD
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XC-MISC
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension SECURITY
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XFIXES
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension RENDER
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension RANDR
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension COMPOSITE
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension DAMAGE
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension MIT-SCREEN-SAVER
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension DOUBLE-BUFFER
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension RECORD
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension DPMS
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension Present
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension DRI3
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension X-Resource
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XVideo
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XVideo-MotionCompensation
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension SELinux
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) SELinux: Disabled on system
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension GLX
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension GLX
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Indirect GLX disabled.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) GLX: Another vendor is already registered for screen 0
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XFree86-VidModeExtension
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XFree86-DGA
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XFree86-DRI
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension DRI2
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension NV-GLX
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension NV-CONTROL
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Initializing extension XINERAMA
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) config/udev: Adding input device NVIDIA Jetson AGX Orin HDA HDMI/DP,pcm=9 (/dev/input/event6)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) No input driver specified, ignoring this device.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) This device may have been added with another device file.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) config/udev: Adding input device NVIDIA Jetson AGX Orin HDA HDMI/DP,pcm=3 (/dev/input/event0)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) No input driver specified, ignoring this device.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) This device may have been added with another device file.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) config/udev: Adding input device NVIDIA Jetson AGX Orin HDA HDMI/DP,pcm=7 (/dev/input/event4)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) No input driver specified, ignoring this device.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) This device may have been added with another device file.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) config/udev: Adding input device NVIDIA Jetson AGX Orin HDA HDMI/DP,pcm=8 (/dev/input/event5)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) No input driver specified, ignoring this device.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) This device may have been added with another device file.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) config/udev: Adding input device Logitech Wireless Keyboard PID:4023 (/dev/input/event1)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Keyboard PID:4023: Applying InputClass “libinput keyboard catchall”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) LoadModule: “libinput”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Module libinput: vendor=“X.Org Foundation”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: compiled for 1.20.4, module version = 0.29.0
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: Module class: X.Org XInput Driver
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: ABI class: X.Org XInput driver, version 24.1
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Using input driver ‘libinput’ for ‘Logitech Wireless Keyboard PID:4023’
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Keyboard PID:4023: always reports core events
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “Device” “/dev/input/event1”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “_source” “server/udev”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event1 - Logitech Wireless Keyboard PID:4023: is tagged by udev as: Keyboard
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event1 - Logitech Wireless Keyboard PID:4023: device is a keyboard
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event1 - Logitech Wireless Keyboard PID:4023: device removed
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) libinput: Logitech Wireless Keyboard PID:4023: needs a virtual subdevice
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “config_info” “udev:/sys/devices/platform/3610000.xhci/usb1/1-2/1-2.1/1-2.1:1.1/0003:046D:C534.0002/0003:046D:4023.0003/input/input22/event1”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) XINPUT: Adding extended input device “Logitech Wireless Keyboard PID:4023” (type: MOUSE, id 6)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “AccelerationScheme” “none”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Keyboard PID:4023: (accel) selected scheme none/0
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Keyboard PID:4023: (accel) acceleration factor: 2.000
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Keyboard PID:4023: (accel) acceleration threshold: 4
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event1 - Logitech Wireless Keyboard PID:4023: is tagged by udev as: Keyboard
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event1 - Logitech Wireless Keyboard PID:4023: device is a keyboard
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) config/udev: Adding input device Logitech Wireless Mouse (/dev/input/event2)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Mouse: Applying InputClass “libinput pointer catchall”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Using input driver ‘libinput’ for ‘Logitech Wireless Mouse’
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Mouse: always reports core events
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “Device” “/dev/input/event2”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “_source” “server/udev”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event2 - Logitech Wireless Mouse: is tagged by udev as: Mouse
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event2 - Logitech Wireless Mouse: device is a pointer
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event2 - Logitech Wireless Mouse: device removed
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “config_info” “udev:/sys/devices/platform/3610000.xhci/usb1/1-2/1-2.1/1-2.1:1.1/0003:046D:C534.0002/0003:046D:4091.0004/input/input23/event2”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) XINPUT: Adding extended input device “Logitech Wireless Mouse” (type: MOUSE, id 7)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “AccelerationScheme” “none”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Mouse: (accel) selected scheme none/0
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Mouse: (accel) acceleration factor: 2.000
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Mouse: (accel) acceleration threshold: 4
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event2 - Logitech Wireless Mouse: is tagged by udev as: Mouse
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event2 - Logitech Wireless Mouse: device is a pointer
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) config/udev: Adding input device Logitech Wireless Mouse (/dev/input/mouse0)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) No input driver specified, ignoring this device.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) This device may have been added with another device file.
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Keyboard PID:4023: Applying InputClass “libinput keyboard catchall”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Using input driver ‘libinput’ for ‘Logitech Wireless Keyboard PID:4023’
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Logitech Wireless Keyboard PID:4023: always reports core events
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “Device” “/dev/input/event1”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “_source” “_driver/libinput”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) libinput: Logitech Wireless Keyboard PID:4023: is a virtual subdevice
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “config_info” “udev:/sys/devices/platform/3610000.xhci/usb1/1-2/1-2.1/1-2.1:1.1/0003:046D:C534.0002/0003:046D:4023.0003/input/input22/event1”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) XINPUT: Adding extended input device “Logitech Wireless Keyboard PID:4023” (type: KEYBOARD, id 8)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: () Option “xkb_model” “pc105”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (**) Option “xkb_layout” “us”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5241]: dbus-daemon[5241]: [session uid=1001 pid=5241] Activating service name=‘org.freedesktop.systemd1’ requested by ‘:1.0’ (uid=1001 pid=5229 comm=“/usr/lib/gdm3/gdm-x-session --run-script env GNOME” label=“kernel”)
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5241]: dbus-daemon[5241]: [session uid=1001 pid=5241] Activated service ‘org.freedesktop.systemd1’ failed: Process org.freedesktop.systemd1 exited with status 1
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5229]: Unable to register display with display manager
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event2 - Logitech Wireless Mouse: device removed
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) event1 - Logitech Wireless Keyboard PID:4023: device removed
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) UnloadModule: “libinput”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) UnloadModule: “libinput”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) UnloadModule: “libinput”
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) NVIDIA(GPU-0): Deleting GPU-0
Jun 18 04:40:02 msad323m /usr/lib/gdm3/gdm-x-session[5231]: (II) Server terminated successfully (0). Closing log file.
Jun 18 04:40:02 msad323m gdm-password][4555]: pam_unix(gdm-password:session): session closed for user maxsense
Jun 18 04:40:02 msad323m gdm3[2055]: GdmDisplay: Session never registered, failing
也许我再尝试使用hdmi的密码的时候，有关gdm的这个日志可以让你帮我定位一下问题吗？非常感谢
Fix the clock:
date
timedatectl status
sudo timedatectl set-ntp false
Change next line to your watch date time
sudo timedatectl set-time “2026-03-26 12:00:00”
Also inspect the password aging metadata:
sudo chage -l maxsense
sudo passwd -S maxsense
sudo chage -l testlogin
sudo passwd -S testlogin
Then clean up stale session/runtime state:
sudo systemctl stop gdm
loginctl list-sessions
sudo pkill -u maxsense
sudo pkill -u testlogin
sudo rm -rf /run/user/1000
sudo rm -rf /run/user/1001
sudo systemctl restart systemd-logind
sudo systemctl start gdm
Reboot after time fix, don’t just restart GDM.
sudo reboot
sudo pkill -u maxsense
我有尝试过杀掉这个进程并且把已经权限混乱的user给删除，但是在我杀死了这个进程后我的这个终端就会被关掉，导致我没有办法再去尝试输入后面的输入，我目前的话是使用debug口也会卡在输入密码后，只有使用以太网的ip使用ssh访问才能进入
From a TTY, log in as a different admin user and run this sequence. If there is no second admin user, create one from TTY first.
sudo systemctl stop gdm
loginctl list-sessions
loginctl terminate-user maxsense
loginctl terminate-user testlogin
sudo systemctl restart systemd-logind
sudo systemctl start gdm
What does this show?
date
timedatectl status
sudo chage -l maxsense
journalctl -b | grep -E ‘password changed in future|pam_systemd|session-[0-9]+.scope|org.freedesktop.systemd1|Session never registered’
我按照上面的步骤终止进程什么的都已经操作过了但是还是没能解决这个问题
sudo dmesg | grep -E “nvdisplay|tegra” and check the output to see why the display handler is failing to allocate.
cat /proc/bus/input/devices|grep -iC10 event5
Look for the block that mentions event5. This will tell you if the lagging device is a USB mouse, a keyboard, or a custom I2C touch controller.
watch -n 1 cat /proc/interrupts
Look for any interrupt counter that is increasing by thousands every second.
Fix the Device Tree IRQ: If you identify a specific GPIO or peripheral causing an interrupt storm, check its node in your Device Tree. A common mistake is setting an interrupt to be Level-Triggered (e.g., IRQ_TYPE_LEVEL_LOW) when it should be Edge-Triggered (IRQ_TYPE_EDGE_FALLING), causing the interrupt to fire continuously if the line stays low.
使用sudo DMESG |grep -E “nvdisplay|tegra”后的日志是这样的
[ 0.291286] nv-tegra-mc 2c10000.mc: No mssnvlink node
[ 1.613658] tegra_wdt_t18x 2190000.watchdog: Tegra WDT init timeout = 120 sec
[ 1.620842] tegra_wdt_t18x 2190000.watchdog: Registered successfully
[ 2.226547] tegra-pwm 3280000.pwm: PWM clk can sleep in ops
[ 2.232149] tegra-pwm 32a0000.pwm: PWM clk can sleep in ops
[ 2.237734] tegra-pwm 32c0000.pwm: PWM clk can sleep in ops
[ 2.243318] tegra-pwm 32f0000.pwm: PWM clk can sleep in ops
[ 2.293280] tegra_dc_assign_hw_data: no matching compatible node
[ 2.299304] tegradccommon module_init failed
[ 2.303582] tegradc module_init failed
[ 2.312501] tegra-pmc c360000.pmc: scratch reg offset dts data not present
[ 2.319397] tegra-pmc: ### PMC reset source: SYS_RESET_N
[ 2.324724] tegra-pmc: ### PMC reset level: L0
[ 2.329175] tegra-pmc: ### PMC reset status reg: 0x0
[ 4.188594] tegra_profiler: version: 1.151, samples/io: 51/30
[ 4.195156] tegra_profiler: auth: init
[ 4.348154] tegra-xusb 3610000.xhci: Adding to iommu group 0
[ 4.382014] tegra_rtc c2a0000.rtc: registered as rtc1
[ 4.387752] tegra_rtc c2a0000.rtc: Tegra internal Real Time Clock
[ 4.398866] tegra-i2c 3160000.i2c: Adding to iommu group 1
[ 4.405201] tegra-i2c c240000.i2c: Adding to iommu group 1
[ 4.411427] tegra-i2c 3180000.i2c: Adding to iommu group 1
[ 4.417649] tegra-i2c 3190000.i2c: Adding to iommu group 1
[ 4.423840] tegra-i2c 31c0000.i2c: Adding to iommu group 1
[ 4.430027] tegra-i2c c250000.i2c: Adding to iommu group 1
[ 4.436207] tegra-i2c 31e0000.i2c: Adding to iommu group 1
[ 4.442435] tegra-i2c 31b0000.i2c: Adding to iommu group 1
[ 4.493262] sdhci-tegra 3460000.sdhci: Adding to iommu group 2
[ 4.493642] sdhci-tegra 3400000.sdhci: Adding to iommu group 3
[ 4.494782] tegra-bpmp bpmp: firmware: 6969245516d6bf7e0f23-925eece486b
[ 5.730112] tegra-dce d800000.dce: Adding to iommu group 4
[ 5.747726] tegra234-aon c000000.aon: Adding to iommu group 5
[ 5.776110] tegra234-aon c000000.aon: init done
[ 5.776486] tegra23x-psc e860000.psc: Adding to iommu group 6
[ 5.788168] tegra23x-psc e860000.psc: ext_cfg base:(ptrval)
[ 5.804479] tegra23x-psc e860000.psc: init done
[ 5.818928] tegra186-cam-rtcpu bc00000.rtcpu: Adding to iommu group 7
[ 5.834836] tegra186-cam-rtcpu bc00000.rtcpu: Trace buffer configured at IOVA=0xbff00000
[ 5.874720] tegra-ivc-bus bc00000.rtcpu:ivc-bus: region 0: iova=0xbfec0000-0xbfee01ff size=131584
[ 5.884643] tegra-ivc-bus bc00000.rtcpu:ivc-bus:echo@0: echo: ver=0 grp=1 RX[16x64]=0x1000-0x1480 TX[16x64]=0x1480-0x1900
[ 5.896751] tegra-ivc-bus bc00000.rtcpu:ivc-bus:dbg@1: dbg: ver=0 grp=1 RX[1x448]=0x1900-0x1b40 TX[1x448]=0x1b40-0x1d80
[ 5.909301] tegra-ivc-bus bc00000.rtcpu:ivc-bus:dbg@2: dbg: ver=0 grp=1 RX[1x8192]=0x1d80-0x3e00 TX[1x8192]=0x3e00-0x5e80
[ 5.921771] tegra-ivc-bus bc00000.rtcpu:ivc-bus:ivccontrol@3: ivccontrol: ver=0 grp=1 RX[64x320]=0x5e80-0xaf00 TX[64x320]=0xaf00-0xff80
[ 5.935081] tegra-ivc-bus bc00000.rtcpu:ivc-bus:ivccapture@4: ivccapture: ver=0 grp=1 RX[512x64]=0xff80-0x18000 TX[512x64]=0x18000-0x20080
[ 5.948625] tegra-ivc-bus bc00000.rtcpu:ivc-bus:diag@5: diag: ver=0 grp=1 RX[1x64]=0x20080-0x20140 TX[1x64]=0x20140-0x20200
[ 5.962444] tegra186-cam-rtcpu bc00000.rtcpu: using cam RTCPU IRQ (120)
[ 5.970002] tegra186-cam-rtcpu bc00000.rtcpu: tegra_camrtc_mon_create is successful
[ 5.983067] tegra186-cam-rtcpu bc00000.rtcpu: firmware version cpu=rce cmd=6 sha1=8676d22a01443bdbc66581b7dde3b6d6828cc925
[ 5.997459] t19x_cache tegra-cache: probed
[ 6.121172] tegra_hv: get_hvd: not initialized yet
[ 6.266154] tegra194-pcie 14160000.pcie: Adding to iommu group 8
[ 6.280073] tegra194-pcie 14160000.pcie: Using GICv2m MSI allocator
[ 6.288183] tegra194-pcie 141a0000.pcie: Adding to iommu group 9
[ 6.301079] tegra194-pcie 141a0000.pcie: Using GICv2m MSI allocator
[ 6.309071] tegra194-pcie 141e0000.pcie: Adding to iommu group 10
[ 6.321996] tegra194-pcie 141e0000.pcie: Using GICv2m MSI allocator
[ 6.354342] tegra-soc-hwpm f100000.tegra_soc_hwpm: Adding to iommu group 11
[ 6.904413] tegra-aconnect aconnect@2a41000: Tegra ACONNECT bus registered
[ 6.930538] gpiochip0: registered GPIOs 348 to 511 on tegra234-gpio
[ 6.938780] gpiochip1: registered GPIOs 316 to 347 on tegra234-gpio-aon
[ 6.946463] tegra-pwm 3280000.pwm: PWM clk can sleep in ops
[ 6.953652] tegra-pwm 32a0000.pwm: PWM clk can sleep in ops
[ 6.960789] tegra-pwm 32c0000.pwm: PWM clk can sleep in ops
[ 6.967695] tegra-pwm 32f0000.pwm: PWM clk can sleep in ops
[ 6.976614] tegra194-isp5 14800000.isp: Adding to iommu group 36
[ 7.003448] tegra-camrtc-capture-vi tegra-capture-vi: subdev 13e40000.host1x:nvcsi@15a00000- bound
[ 7.013385] tegra-camrtc-capture-vi tegra-capture-vi: subdev 13e40000.host1x:nvcsi@15a00000- bound
[ 7.023318] tegra-camrtc-capture-vi tegra-capture-vi: subdev 13e40000.host1x:nvcsi@15a00000- bound
[ 7.033228] tegra-camrtc-capture-vi tegra-capture-vi: subdev 13e40000.host1x:nvcsi@15a00000- bound
[ 7.043126] tegra-camrtc-capture-vi tegra-capture-vi: subdev 13e40000.host1x:nvcsi@15a00000- bound
[ 7.053041] tegra-camrtc-capture-vi tegra-capture-vi: subdev 13e40000.host1x:nvcsi@15a00000- bound
[ 7.062923] tegra-camrtc-capture-vi tegra-capture-vi: subdev 13e40000.host1x:nvcsi@15a00000- bound
[ 7.072796] tegra-camrtc-capture-vi tegra-capture-vi: subdev 13e40000.host1x:nvcsi@15a00000- bound
[ 7.082826] tegra194-vi5 13e40000.host1x:vi0@15c00000: Adding to iommu group 37
[ 7.091541] tegra194-vi5 13e40000.host1x:vi1@14c00000: Adding to iommu group 38
[ 7.400615] tegra-gpcdma 2600000.gpcdma: Adding to iommu group 1
[ 7.409433] tegra-gpcdma 2600000.gpcdma: GPC DMA driver register 31 channels
[ 7.417596] tegra-fuse-burn efuse-burn: shutdown limit check disabled
[ 7.424825] tegra-fuse-burn efuse-burn: Fuse burn driver initialized
[ 7.432248] serial-tegra 3100000.serial: Adding to iommu group 1
[ 7.439096] serial-tegra 3100000.serial: failed to get rts gpio
[ 7.456246] serial-tegra 3110000.serial: Adding to iommu group 1
[ 7.463088] serial-tegra 3110000.serial: failed to get rts gpio
[ 7.480154] serial-tegra 3130000.serial: Adding to iommu group 1
[ 7.487002] serial-tegra 3130000.serial: failed to get rts gpio
[ 7.503955] serial-tegra 3140000.serial: Adding to iommu group 1
[ 7.510834] serial-tegra 3140000.serial: failed to get rts gpio
[ 7.544776] tegra-xusb 3610000.xhci: Firmware timestamp: 2023-02-10 03:48:10 UTC, Version: 80.05 release
[ 7.555217] tegra-xusb 3610000.xhci: xHCI Host Controller
[ 7.561472] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 1
[ 7.570755] tegra-xusb 3610000.xhci: hcc params 0x0180ff05 hci version 0x120 quirks 0x0000000000050810
[ 7.581040] tegra-xusb 3610000.xhci: irq 236, io mem 0x03610000
[ 7.611200] usb usb1: Manufacturer: Linux 5.10.120-tegra xhci-hcd
[ 7.633699] tegra-xusb 3610000.xhci: xHCI Host Controller
[ 7.639957] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 2
[ 7.648448] tegra-xusb 3610000.xhci: Host supports USB 3.1 Enhanced SuperSpeed
[ 7.679802] usb usb2: Manufacturer: Linux 5.10.120-tegra xhci-hcd
[ 7.831893] tegra23x-oc-event soctherm-oc-event: Finished tegra23x overcurrent event probing
[ 7.884503] tegra194-cpufreq e000000.ccplex: probed with ICC, cl:3
[ 7.886650] usb 1-2: new high-speed USB device number 2 using tegra-xusb
[ 7.893702] tegra194-pcie 14160000.pcie: Using GICv2m MSI allocator
[ 7.895803] sdhci-tegra 3400000.sdhci: Got CD GPIO
[ 7.904733] sdhci-tegra 3400000.sdhci: wakeup init done, cdirq 303
[ 7.930891] tegra194-pcie 14160000.pcie: host bridge /pcie@14160000 ranges:
[ 7.938672] tegra194-pcie 14160000.pcie: IO 0x0036100000..0x00361fffff → 0x0036100000
[ 7.947962] tegra194-pcie 14160000.pcie: MEM 0x2428000000..0x242fffffff → 0x0040000000
[ 7.957239] tegra194-pcie 14160000.pcie: MEM 0x2140000000..0x2427ffffff → 0x2140000000
[ 8.086497] tegra194-pcie 14160000.pcie: Link up
[ 8.103131] tegra194-pcie 14160000.pcie: PCI host bridge to bus 0004:00
[ 8.178725] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using tegra-xusb
[ 8.329271] tegra194-pcie 141a0000.pcie: Using GICv2m MSI allocator
[ 8.446500] usb 1-2.2: new full-speed USB device number 3 using tegra-xusb
[ 8.451070] tegra194-pcie 141a0000.pcie: host bridge /pcie@141a0000 ranges:
[ 8.462175] tegra194-pcie 141a0000.pcie: IO 0x003a100000..0x003a1fffff → 0x003a100000
[ 8.471524] tegra194-pcie 141a0000.pcie: MEM 0x2b28000000..0x2b2fffffff → 0x0040000000
[ 8.480876] tegra194-pcie 141a0000.pcie: MEM 0x2740000000..0x2b27ffffff → 0x2740000000
[ 9.578655] tegra194-pcie 141a0000.pcie: Phy link never came up
[ 9.585555] tegra194-pcie 141a0000.pcie: PCI host bridge to bus 0005:00
[ 9.709212] tegra194-pcie 141e0000.pcie: Using GICv2m MSI allocator
[ 10.084873] WARNING: CPU: 0 PID: 0 at drivers/soc/tegra/cbb/tegra234-cbb.c:577 tegra234_cbb_isr+0x130/0x170
[ 10.099314] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.120-tegra #5
[ 10.125843] pc : tegra234_cbb_isr+0x130/0x170
[ 10.130998] lr : tegra234_cbb_isr+0x10c/0x170
[ 10.234630] tegra234_cbb_isr+0x130/0x170
[ 10.315623] tegra194-pcie 141e0000.pcie: host bridge /pcie@141e0000 ranges:
[ 10.323289] tegra194-pcie 141e0000.pcie: IO 0x003e100000..0x003e1fffff → 0x003e100000
[ 10.332450] tegra194-pcie 141e0000.pcie: MEM 0x3228000000..0x322fffffff → 0x0040000000
[ 10.341616] tegra194-pcie 141e0000.pcie: MEM 0x2e40000000..0x3227ffffff → 0x2e40000000
[ 11.434651] tegra194-pcie 141e0000.pcie: Phy link never came up
[ 11.441255] tegra194-pcie 141e0000.pcie: PCI host bridge to bus 0007:00
[ 11.573024] tegra194-isp5 14800000.isp: initialized
[ 11.582709] tegra194-vi5 13e40000.host1x:vi0@15c00000: initialized
[ 11.598114] tegra194-vi5 13e40000.host1x:vi1@14c00000: initialized
[ 11.745317] tegra-se-nvhost 15810000.se: Adding to iommu group 51
[ 11.752476] tegra-se-nvhost 15810000.se: initialized
[ 11.768686] tegra-se-nvhost 15810000.se: tegra_se_probe: complete
[ 11.775634] tegra-se-nvhost 15820000.se: Adding to iommu group 52
[ 11.782741] tegra-se-nvhost 15820000.se: initialized
[ 11.791488] tegra-se-nvhost 15820000.se: tegra_se_probe: complete
[ 11.798401] tegra-se-nvhost 15840000.se: Adding to iommu group 53
[ 11.805501] tegra-se-nvhost 15840000.se: initialized
[ 11.812564] tegra-se-nvhost 15840000.se: tegra_se_probe: complete
[ 11.819936] tegra_actmon d230000.actmon: in actmon_register()…
[ 11.826793] tegra_actmon d230000.actmon: bwmgr_disable = 1
[ 11.833350] tegra_actmon d230000.actmon: initialization Completed for the device mc_all
[ 13.360564] tegra-carveouts tegra-carveouts: fsi :dma coherent mem declare 0x0000000838e00000,16777216
[ 13.370836] tegra-carveouts tegra-carveouts: assigned reserved memory node fsi-carveout
[ 13.370844] tegra-carveouts tegra-carveouts: vpr :dma coherent mem declare 0x0000000849800000,914358272
[ 13.390097] tegra-carveouts tegra-carveouts: assigned reserved memory node vpr-carveout
[ 13.997617] ar0233yuv 2-001f: tegracam sensor driver:ar02330_v2.0.6
[ 13.997880] spi-tegra114 3210000.spi: Adding to iommu group 1
[ 14.007486] platform 13800000.display:nvdisplay-niso: Adding to iommu group 55
[ 14.020075] spi-tegra114 3230000.spi: Adding to iommu group 1
[ 14.046718] tegra-adma 2930000.adma: Tegra210 ADMA driver registered 16 channels
[ 14.139422] tegra-i2c 31e0000.i2c: un-recovered arbitration lost
[ 14.298641] tegra-hda 3510000.hda: Adding to iommu group 57
[ 14.336652] tegra-asoc: sound: Adding to iommu group 56
[ 14.341692] tegra210-adsp aconnect@2a41000:adsp_audio: Adding to iommu group 56
[ 14.351886] tegra210_adsp_audio_probe: platform probe started
[ 14.370169] tegra210-adsp tegra210-adsp: Default param-type to BYTE for mp3-dec1
[ 14.377342] tegra-camrtc-capture-vi tegra-capture-vi: subdev ar0233yuv 2-001f bound
[ 14.398657] tegra210-adsp tegra210-adsp: Default param-type to BYTE for spkprot
[ 14.401910] ar0233yuv 2-0020: tegracam sensor driver:ar02331_v2.0.6
[ 14.413355] tegra210-adsp tegra210-adsp: Default param-type to BYTE for src
[ 14.413594] tegra210-adsp tegra210-adsp: Default param-type to BYTE for aac-dec1
[ 14.413817] tegra210-adsp tegra210-adsp: Default param-type to BYTE for aec
[ 14.414036] tegra210-adsp tegra210-adsp: Default param-type to BYTE for wire
[ 14.414039] tegra210-adsp tegra210-adsp: adma channel page address dt entry not found
[ 14.414041] tegra210-adsp tegra210-adsp: using adma channel page 0
[ 14.722924] tegra-camrtc-capture-vi tegra-capture-vi: subdev ar0233yuv 2-0020 bound
[ 14.754487] tegra210-adsp tegra210-adsp: Loaded app wire
[ 14.768464] tegra210-adsp tegra210-adsp: Loaded app apm
[ 14.774819] ar0233yuv 2-0021: tegracam sensor driver:ar02332_v2.0.6
[ 14.780389] tegra210-adsp tegra210-adsp: Loaded app adma
[ 14.794010] tegra210-adsp tegra210-adsp: Loaded app adma_tx
[ 14.862815] tegra210-adsp tegra210-adsp: Tegra210 ADSP driver successfully registered
[ 15.073682] tegra-camrtc-capture-vi tegra-capture-vi: subdev ar0233yuv 2-0021 bound
[ 15.096507] ar0233yuv 2-0022: tegracam sensor driver:ar02333_v2.0.6
[ 15.320595] tegra-camrtc-capture-vi tegra-capture-vi: subdev ar0233yuv 2-0022 bound
[ 15.343368] ar0233yuv 2-001b: tegracam sensor driver:ar02334_v2.0.6
[ 15.619126] tegra-camrtc-capture-vi tegra-capture-vi: subdev ar0233yuv 2-001b bound
[ 15.621070] ar0233yuv 2-001c: tegracam sensor driver:ar02335_v2.0.6
[ 15.828956] tegra-camrtc-capture-vi tegra-capture-vi: subdev ar0233yuv 2-001c bound
[ 15.830560] ar0233yuv 2-001d: tegracam sensor driver:ar02336_v2.0.6
[ 16.064980] tegra-camrtc-capture-vi tegra-capture-vi: subdev ar0233yuv 2-001d bound
[ 16.067141] ar0233yuv 2-001e: tegracam sensor driver:ar02337_v2.0.6
[ 16.271613] tegra-camrtc-capture-vi tegra-capture-vi: subdev ar0233yuv 2-001e bound
[ 203.525632] pwm-tegra-tachometer 39c0000.tachometer: Tachometer Overflow is detected
[ 969.953091] usb 1-2.3: new high-speed USB device number 4 using tegra-xusb
[ 970.705638] usb 1-2.3: reset high-speed USB device number 4 using tegra-xusb
[ 1485.093248] CPU: 7 PID: 2654 Comm: Xorg Tainted: G W OE 5.10.120-tegra #5
使用cat /proc/bus/input/devices|grep -iC10 event5是这样的回执
maxsense@msad323m:/boot/dtb$ cat /proc/bus/input/devices|grep -iC10 event5
B: REL=1040
B: ABS=100000000
B: MSC=10
B: LED=1fI: Bus=0003 Vendor=046d Product=4091 Version=0111
N: Name=“Logitech Wireless Mouse”
P: Phys=usb-3610000.xhci-2.2/input1:2
S: Sysfs=/devices/platform/3610000.xhci/usb1/1-2/1-2.2/1-2.2:1.1/0003:046D:C534.0002/0003:046D:4091.0004/input/input23
U: Uniq=4091-00-00-00-00
H: Handlers=mouse0 event5
B: PROP=0
B: EV=17
B: KEY=ffff0000 0 0 0 0
B: REL=1943
B: MSC=10
你能看出问题所在吗，非常感谢
If your other board is working I’d double check how you configured the second one. Check device tree that you modified made it into the second board
Why Xorg Failed (The Display Issue)
In your previous screenshot, Xorg threw (EE) NVIDIA(0): Failed to allocate NVIDIA Error Handler. Your dmesg log shows exactly why:
[ 2.293280] tegra_dc_assign_hw_data: no matching compatible node
[ 2.299304] tegradccommon module_init failed
[ 2.303582] tegradc module_init failed
That this means: tegradc is the Tegra Display Controller. The kernel tried to turn on the display pipeline, but your custom Device Tree is missing the proper display nodes (or they are configured incorrectly, so the driver rejects them as “no matching compatible node”). Because the kernel-level display driver failed to load, Xorg (the user-space display server) crashes when it tries to use it.
How to fix: If your board is meant to have a display, you need to port the nvdisplay, sor, and dpaux nodes from the Nvidia DevKit device tree into your custom device tree, making sure the regulators match your board’s schematics. If your board is headless, you need to disable the X11/gdm3 service so it stops trying to load a GUI.
The Root Cause of the Lag: The CBB Error
This is the most critical error in your log and is almost certainly what is causing your system to lag and drop mouse inputs:
[ 10.084873] WARNING: CPU: 0 PID: 0 at drivers/soc/tegra/cbb/tegra234-cbb.c:577 tegra234_cbb_isr+0x130/0x170
What this means: CBB is the Control Backbone. It is the main interconnect fabric inside the Orin SoC. A CBB error/ISR (Interrupt Service Routine) fires when the CPU tries to read or write to a hardware register that is invalid, unpowered, or doesn’t have its clock turned on.
Why it matters: When a CBB error occurs, the SoC often hangs for a fraction of a second while the interconnect times out, which completely starves the system of CPU time (causing your mouse lag). This can happen when a driver defined in your Device Tree tries to probe a peripheral (like an SPI bus, an I2C controller, or a PCIe lane) that isn’t physically wired or powered correctly on your custom board.
To make this board usable while you debug the hardware, disable the desktop environment temporarily. This will stop Xorg from crashing and looping.
You can do this by dropping into a TTY terminal or SSH and run:
sudo systemctl set-default multi-user.target
(You can revert this later with sudo systemctl set-default graphical.target)
请问我该如何使用另一块健康的模组来查看这个模组的设备树是否正常呢，因为我是使用的是双模组并且系统也是相对独立的
健康的模组也能检测到tegra_dc_assign_hw_data: no matching compatible node
[ 2.304761] tegradccommon module_init failed
[ 2.309031] tegradc module_init failed这个log，所以还会有其他的问题吗？
What do you mean about “Dual Orin System”?
How do you connect them? Is the issue specific to your custom carrier board?