[Problem] Jetson TK1 auto logout randrom


My Moniter is ASUS MX279.
and I use a USB 3.0 HUB
[CustomKernel] The Grinch 19.3.6 for Jetson TK1
AC7260 wireless card
sometime my jetson tk1 will auto logout…

the video [url]Jetson tk1 auto logout random - YouTube

TKS

“the randrom is random…”

Old topic. Several threads on this. Here’s the one I think with workaround, plus another older:
[url]https://devtalk.nvidia.com/default/topic/751354/embedded-systems/sudden-logout-problems-create-new-user-/[/url]

[url]https://devtalk.nvidia.com/default/topic/763285/embedded-systems/sudden-logouts-example-jetson-tk1-l4t-19-2/[/url]

I already read those topic but not solve my problem.

try add a new user and change cpu performance rule…etc

tks

Is there anything crash related at the end of the previous X log (/var/log/Xorg.0.log.old)?

Or in “dmesg”? Or maybe in ~/.xsession-errors?

Mmm,I will cat the log when I back.
TKs

dmesg
[ 17.843636] wlan0: associated
[ 17.843896] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 23.515866] rt5639 0-001c: one bit hp_amp_power on=1 hp_amp_power_count=0
[ 34.157531] rt5639 0-001c: one bit hp_amp_power on=0 hp_amp_power_count=1
[ 125.613017] systemd-hostnamed[2127]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[ 138.004079] init: failsafe main process (963) killed by TERM signal
[ 138.264260] init: plymouth-stop pre-start process (2273) terminated with status 1
[ 154.012155] vgaarb: this pci device is not a vga device
[ 154.513083] tegradc tegradc.1: nominal-pclk:148500000 parent:594000000 div:4.0 pclk:148500000 147015000~161865000
[ 154.809827] vgaarb: this pci device is not a vga device
[ 154.936517] vgaarb: this pci device is not a vga device
[ 155.874040] rt5639 0-001c: one bit hp_amp_power on=1 hp_amp_power_count=0
[ 171.695621] rt5639 0-001c: one bit hp_amp_power on=0 hp_amp_power_count=1

Xorg.0.log

[ 154.737] (==) Log file: “/var/log/Xorg.0.log”, Time: Mon Oct 27 17:47:15 2014
[ 154.737] (==) Using config file: “/etc/X11/xorg.conf”
[ 154.737] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 154.738] (==) No Layout section. Using the first Screen section.
[ 154.738] (==) No screen section available. Using defaults.
[ 154.738] () |–>Screen “Default Screen Section” (0)
[ 154.739] (
) | |–>Monitor “”
[ 154.739] (==) No device specified for screen “Default Screen Section”.
Using the first device section listed.
[ 154.739] (**) | |–>Device “Tegra0”
[ 154.739] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
[ 154.739] (==) Automatically adding devices
[ 154.739] (==) Automatically enabling devices
[ 154.739] (==) Automatically adding GPU devices
[ 154.739] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
[ 154.739] Entry deleted from font path.
[ 154.739] (WW) The directory “/usr/share/fonts/X11/100dpi/” does not exist.
[ 154.739] Entry deleted from font path.
[ 154.739] (WW) The directory “/usr/share/fonts/X11/75dpi/” does not exist.
[ 154.739] Entry deleted from font path.
[ 154.739] (WW) The directory “/usr/share/fonts/X11/100dpi” does not exist.
[ 154.739] Entry deleted from font path.
[ 154.739] (WW) The directory “/usr/share/fonts/X11/75dpi” does not exist.
[ 154.740] Entry deleted from font path.
[ 154.740] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[ 154.740] (==) ModulePath set to “/usr/lib/arm-linux-gnueabihf/xorg/extra-modules,/usr/lib/xo rg/extra-modules,/usr/lib/xorg/modules”
[ 154.740] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 154.740] (II) Loader magic: 0xb6783f18
[ 154.740] (II) Module ABI versions:
[ 154.740] X.Org ANSI C Emulation: 0.4
[ 154.740] X.Org Video Driver: 15.0
[ 154.740] X.Org XInput driver : 20.0
[ 154.740] X.Org Server Extension : 8.0
[ 154.741] Initializing built-in extension Generic Event Extension
[ 154.741] Initializing built-in extension SHAPE
[ 154.741] Initializing built-in extension MIT-SHM
[ 154.741] Initializing built-in extension XInputExtension
[ 154.741] Initializing built-in extension XTEST
[ 154.741] Initializing built-in extension BIG-REQUESTS
[ 154.741] Initializing built-in extension SYNC
[ 154.741] Initializing built-in extension XKEYBOARD
[ 154.741] Initializing built-in extension XC-MISC
[ 154.741] Initializing built-in extension SECURITY
[ 154.742] Initializing built-in extension XINERAMA
[ 154.742] Initializing built-in extension XFIXES
[ 154.742] Initializing built-in extension RENDER
[ 154.742] Initializing built-in extension RANDR
[ 154.742] Initializing built-in extension COMPOSITE
[ 154.742] Initializing built-in extension DAMAGE
[ 154.742] Initializing built-in extension MIT-SCREEN-SAVER
[ 154.742] Initializing built-in extension DOUBLE-BUFFER
[ 154.742] Initializing built-in extension RECORD
[ 154.742] Initializing built-in extension DPMS
[ 154.742] Initializing built-in extension Present
[ 154.742] Initializing built-in extension DRI3
[ 154.742] Initializing built-in extension X-Resource
[ 154.742] Initializing built-in extension XVideo
[ 154.742] Initializing built-in extension XVideo-MotionCompensation
[ 154.742] Initializing built-in extension SELinux
[ 154.742] Initializing built-in extension XFree86-VidModeExtension
[ 154.742] Initializing built-in extension XFree86-DGA
[ 154.742] Initializing built-in extension XFree86-DRI
[ 154.742] Initializing built-in extension DRI2
[ 154.742] (WW) “dri” will not be loaded unless you’ve specified it to be loaded elsewhere.
[ 154.742] (II) “glx” will be loaded by default.
[ 154.742] (WW) “xmir” is not to be loaded by default. Skipping.
[ 154.742] (II) LoadModule: “extmod”
[ 154.743] (II) Module “extmod” already built-in
[ 154.743] (II) LoadModule: “glx”
[ 154.743] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 154.781] (II) Module glx: vendor=“NVIDIA Corporation”
[ 154.781] compiled for 4.0.2, module version = 1.0.0
[ 154.781] Module class: X.Org Server Extension
[ 154.781] (II) NVIDIA GLX Module 19.3 Release Build (integ_stage_rel) (buildbrain@mobile- u64-532) Wed Jun 18 11:22:11 PDT 2014
[ 154.781] Loading extension GLX
[ 154.781] (II) LoadModule: “nvidia”
[ 154.782] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 154.783] (II) Module nvidia: vendor=“NVIDIA Corporation”
[ 154.783] compiled for 4.0.2, module version = 1.0.0
[ 154.783] Module class: X.Org Video Driver
[ 154.783] (II) NVIDIA dlloader X Driver 19.3 Release Build (integ_stage_rel) (buildbrain@ mobile-u64-532) Wed Jun 18 11:22:27 PDT 2014
[ 154.783] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 154.783] (++) using VT number 7

[ 154.783] (WW) Falling back to old probe method for NVIDIA
[ 154.783] (II) Loading sub module “fb”
[ 154.784] (II) LoadModule: “fb”
[ 154.784] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 154.784] (II) Module fb: vendor=“X.Org Foundation”
[ 154.784] compiled for 1.15.1, module version = 1.0.0
[ 154.784] ABI class: X.Org ANSI C Emulation, version 0.4
[ 154.785] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 154.785] (II) Loading sub module “wfb”
[ 154.785] (II) LoadModule: “wfb”
[ 154.785] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 154.785] (II) Module wfb: vendor=“X.Org Foundation”
[ 154.785] compiled for 1.15.1, module version = 1.0.0
[ 154.785] ABI class: X.Org ANSI C Emulation, version 0.4
[ 154.785] (II) Loading sub module “ramdac”
[ 154.785] (II) LoadModule: “ramdac”
[ 154.786] (II) Module “ramdac” already built-in
[ 154.792] (II) NVIDIA(0): Creating default Display subsection in Screen section
“Default Screen Section” for depth/fbbpp 24/32
[ 154.792] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 154.792] (==) NVIDIA(0): RGB weight 888
[ 154.792] (==) NVIDIA(0): Default visual is TrueColor
[ 154.792] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 154.793] () NVIDIA(0): Enabling 2D acceleration
[ 154.910] (II) NVIDIA(0): NVIDIA GPU GK20A (GK20A) at SoC (GPU-0)
[ 154.910] (–) NVIDIA(0): Memory: 1048576 kBytes
[ 154.910] (–) NVIDIA(0): VideoBIOS:
[ 154.910] (–) NVIDIA(0): Valid display device(s) on GK20A at SoC
[ 154.910] (–) NVIDIA(0): DFP-0 (connected)
[ 154.910] (–) NVIDIA(0): DFP-1 (connected)
[ 154.910] (–) NVIDIA(0): DFP-0: Internal Single Link TMDS
[ 154.910] (–) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 154.910] (
) NVIDIA(0): Option “Ignore”
[ 154.910] () NVIDIA(0): Ignoring display device DFP-0
[ 154.910] (
) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 154.910] () NVIDIA(0): device DFP-1 (Using EDID frequencies has been enabled on
[ 154.910] (
) NVIDIA(0): all display devices.)
[ 154.910] (==) NVIDIA(0):
[ 154.910] (==) NVIDIA(0): No modes were requested; the default mode “nvidia-auto-select”
[ 154.910] (==) NVIDIA(0): will be used as the requested mode.
[ 154.911] (==) NVIDIA(0):
[ 154.911] (II) NVIDIA(0): Validated MetaModes:
[ 154.911] (II) NVIDIA(0): “DFP-1:nvidia-auto-select”
[ 154.911] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 154.912] (WW) NVIDIA(0): Unable to support custom viewPortOut 1920 x 1079 +0 +0
[ 154.912] (WW) NVIDIA(0): Unable to support custom viewPortOut 1728 x 1080 +96 +0
[ 154.912] (WW) NVIDIA(0): Unable to get display device DFP-1’s EDID; cannot compute DPI
[ 154.912] (WW) NVIDIA(0): from DFP-1’s EDID.
[ 154.912] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
[ 154.913] (–) Depth 24 pixmap format is 32 bpp
[ 154.919] (WW) NVIDIA(GPU-0): Failed to enter interactive mode.
[ 154.926] (EE) NVIDIA(0): Failed to allocate NVIDIA Error Handler
[ 154.926] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 154.926] (II) NVIDIA(0): may not be running or the “AcpidSocketPath” X
[ 154.926] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 154.926] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 154.926] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 154.926] (II) NVIDIA(0): details, please see the “ConnectToAcpid” and
[ 154.926] (II) NVIDIA(0): “AcpidSocketPath” X configuration options in Appendix B: X
[ 154.926] (II) NVIDIA(0): Config Options in the README.
[ 154.926] (II) NVIDIA(0): Setting mode “DFP-1:nvidia-auto-select”
[ 154.998] Loading extension NV-GLX
[ 155.005] (==) NVIDIA(0): Disabling shared memory pixmaps

those all my log

Did you update your board to latest Software packages ?

Yes,I already upgrade …

You may have to install package “read-edid” and/or “edid-decode” (not sure which repos these are in), but run these commands to test monitor query:

get-edid | parse-edid
get-edid | edid-decode

ubuntu@tegra-ubuntu:~$ get-edid | parse-edid
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
Permission denied opening i2c. Run as root!
I’m sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern pyrophobicman@gmail.com.
Partial Read… Try again

ubuntu@tegra-ubuntu:~$ get-edid | edid-decode
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
Permission denied opening i2c. Run as root!
I’m sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern pyrophobicman@gmail.com.
Extracted contents:
header: 00 00 00 00 00 00 00 00
serial number: 00 00 00 00 00 00 00 00 00 00
version: 00 00
basic params: 00 00 00 00 00
chroma info: 00 00 00 00 00 00 00 00 00 00
established: 00 00 00
standard: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 1: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 2: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 3: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 4: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
extensions: 00
checksum: 00

No header found
Manufacturer: @@@ Model 0 Serial Number 0
EDID version: 0.0
Analog display, Input voltage level: 0.7/0.3 V
Sync:
Image size is variable
Gamma: 1.00
Monochrome or grayscale display
Established timings supported:
Standard timings supported:
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Checksum: 0x0
EDID block does not conform at all!
Bad year of manufacture
Manufacturer name field contains garbage
TKS

You’ll need to use “sudo get-edid | …”. Without root authority (via sudo) the command won’t be allowed full information.

OK…

ubuntu@tegra-ubuntu:~$ sudo get-edid | edid-decode >> b.txt
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.

ubuntu@tegra-ubuntu:~$ sudo get-edid | parse-edid >>a.txt
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
Checksum Correct

謝謝

Is the Xorg.0.log the one after the crash? If you check the log when you are back in the login screen, then you are checking the new log and not the old one that might contain information about the crash.

I wonder what the following line in the dmesg means:

[ 138.004079] init: failsafe main process (963) killed by TERM signal

Is that just something being killed because of the “crash” or is that perhaps something happening just before…

This is only part of the answer…the part listed is correct, but redirect to a file is hiding the part which is really needed. All that can be known from the above is that there is a DDC channel working, with more required to see if the data is usable. What is in the files from the redirect?

I forget where I’ve seen this before on Jetson, but I do remember it isn’t an issue.

Yes, the log is cat when the random auto log out.


[ 154.XXXXXXX]↑↓