VIM3 - Just Stops

Jonathan_Pickard · March 23, 2022, 4:03am

I have a heat sink and a big fan-in an ITX case but my VIM3 x2 just keep “stopping”. I am running Manjaro 22.

Is it it over heating i can write a script to check that and publish here
Does manjaro just put the board in sleep mode
3.I have checked journalctl and nothing obvious. Will post below

Other than that great boards.

I am just using the boards to rsync, beets and scripts.

Jonathan_Pickard · March 23, 2022, 4:26am

Mar 23 12:10:48 khadasOne kernel: rc rc0: two consecutive events of type space
Mar 23 12:10:48 khadasOne dbus-daemon[380]: [system] Activating via systemd: service name=‘org.freedesktop.home1’ unit=‘dbus-org.freedesktop.home1.service’ requested by ‘:1.35’ (uid=0 pid=961 comm=“sshd: jdip [priv] “)
Mar 23 12:10:48 khadasOne dbus-daemon[380]: [system] Activation via systemd failed for unit ‘dbus-org.freedesktop.home1.service’: Unit dbus-org.freedesktop.home1.service not found.
Mar 23 12:10:48 khadasOne sshd[961]: pam_systemd_home(sshd:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 23 12:10:48 khadasOne audit[961]: USER_AUTH pid=961 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct=“jdip” exe=”/usr/bin/sshd” hostname=192.168.>
Mar 23 12:10:48 khadasOne kernel: audit: type=1100 audit(1647990648.450:112): pid=961 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:authentication grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct=“jdip” exe="/u>
Mar 23 12:10:48 khadasOne audit[961]: USER_ACCT pid=961 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct=“jdip” exe="/usr/bin/sshd" hostname=192.168.2.72 addr=19>
Mar 23 12:10:48 khadasOne sshd[961]: Accepted password for jdip from 192.168.2.72 port 37085 ssh2
Mar 23 12:10:48 khadasOne audit[961]: CRED_ACQ pid=961 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct=“jdip” exe="/usr/bin/sshd" hostname=192.168.2.72 add>
Mar 23 12:10:48 khadasOne audit[961]: SYSCALL arch=c00000b7 syscall=64 success=yes exit=4 a0=3 a1=fffff59c82a0 a2=4 a3=ffffaa0b2020 items=0 ppid=444 pid=961 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4 com>
Mar 23 12:10:48 khadasOne audit: PROCTITLE proctitle=737368643A206A646970205B707269765D
Mar 23 12:10:48 khadasOne sshd[961]: pam_unix(sshd:session): session opened for user jdip(uid=1000) by (uid=0)
Mar 23 12:10:48 khadasOne systemd-logind[386]: New session 4 of user jdip.
Mar 23 12:10:48 khadasOne systemd[1]: Started Session 4 of User jdip.
Mar 23 12:10:48 khadasOne audit[961]: USER_START pid=961 uid=0 auid=1000 ses=4 subj==unconfined msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env acct=“jdip”>
Mar 23 12:10:48 khadasOne sshd[961]: pam_env(sshd:session): deprecated reading of user environment enabled
Mar 23 12:10:48 khadasOne audit[965]: CRED_ACQ pid=965 uid=0 auid=1000 ses=4 subj==unconfined msg=‘op=PAM:setcred grantors=pam_shells,pam_faillock,pam_permit,pam_faillock acct=“jdip” exe="/usr/bin/sshd" hostname=192.168.2.72 addr=192.168.2.72 >
Mar 23 17:23:51 khadasOne systemd-timesyncd[372]: Initial synchronization to time server 172.106.167.46:123 (2.arch.pool.ntp.org).
Mar 23 17:23:51 khadasOne systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Mar 23 17:23:51 khadasOne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg=‘unit=systemd-hostnamed comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
Mar 23 17:23:51 khadasOne audit: BPF prog-id=0 op=UNLOAD
Mar 23 17:23:51 khadasOne audit: BPF prog-id=0 op=UNLOAD
Mar 23 17:23:51 khadasOne audit: BPF prog-id=0 op=UNLOAD
Mar 23 17:23:54 khadasOne nmbd[631]: [2022/03/23 17:23:54.754144, 0] …/…/source3/nmbd/nmbd_namequery.c:109(query_name_response)
Mar 23 17:23:54 khadasOne nmbd[631]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.2.61 for name WORKGROUP<1d>.
Mar 23 17:23:54 khadasOne nmbd[631]: This response was from IP 192.168.2.56, reporting an IP address of 192.168.2.56.
Mar 23 17:24:05 khadasOne dbus-daemon[380]: [system] Activating via systemd: service name=‘org.freedesktop.home1’ unit=‘dbus-org.freedesktop.home1.service’ requested by ‘:1.38’ (uid=0 pid=976 comm=“sudo jounrnalctrl “)
Mar 23 17:24:05 khadasOne dbus-daemon[380]: [system] Activation via systemd failed for unit ‘dbus-org.freedesktop.home1.service’: Unit dbus-org.freedesktop.home1.service not found.
Mar 23 17:24:05 khadasOne sudo[976]: pam_systemd_home(sudo:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 23 17:24:08 khadasOne systemd[1]: blueman-mechanism.service: Deactivated successfully.
Mar 23 17:24:08 khadasOne audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm=“systemd” exe=”/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Mar 23 17:24:08 khadasOne kernel: kauditd_printk_skb: 11 callbacks suppressed
Mar 23 17:24:08 khadasOne kernel: audit: type=1131 audit(1648009448.333:122): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=blueman-mechanism comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re>
Mar 23 17:24:08 khadasOne audit[976]: USER_AUTH pid=976 uid=1000 auid=1000 ses=4 subj==unconfined msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct=“jdip” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 re>
Mar 23 17:24:08 khadasOne audit[976]: USER_ACCT pid=976 uid=1000 auid=1000 ses=4 subj==unconfined msg=‘op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct=“jdip” exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success’
Mar 23 17:24:08 khadasOne kernel: audit: type=1100 audit(1648009448.773:123): pid=976 uid=1000 auid=1000 ses=4 subj==unconfined msg='op=PAM:authentication grantors=pam_faillock,pam_permit,pam_faillock acct=“jdip” exe="/usr/bin/sudo" hostname=?>
Mar 23 17:24:08 khadasOne kernel: audit: type=1101 audit(1648009448.773:124): pid=976 uid=1000 auid=1000 ses=4 subj==unconfined msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_time acct=“jdip” exe="/usr/bin/sudo" hostname=? addr=? term>
Mar 23 17:24:18 khadasOne dbus-daemon[380]: [system] Activating via systemd: service name=‘org.freedesktop.home1’ unit=‘dbus-org.freedesktop.home1.service’ requested by ‘:1.39’ (uid=0 pid=992 comm="sudo journalctrl ")

Jonathan_Pickard · March 23, 2022, 4:27am

restart at 17:23 - unplug/replug
running an ssh based lftp script. Lock up seem random.

I will do a CPU heat script too

Jonathan_Pickard · March 23, 2022, 5:41am

date and time is correctly set to NZ ntp server - all resolve to NZ server

Jonathan_Pickard · March 23, 2022, 7:29am

cpu-thermal 26.7°C
ddr-thermal 28.2°C
cpu-thermal 27.1°C
ddr-thermal 28.4°C
cpu-thermal 27.1°C
ddr-thermal 28.5°C
cpu-thermal 26.8°C
ddr-thermal 28.5°C
cpu-thermal 26.9°C
ddr-thermal 28.5°C

the scripts are running the temps are taken every 10 minutes - temps are low

Spikerguy · March 23, 2022, 8:58am

Is it better to look at dmesg and track what’s happening, if you’re saying it just stops then did you put a suspend timer? Suspend does not work and it put the device to sleep and then it crashes.

Check if you have put it to suspend on timer.
Also share uname -a

Kindly use code syntax on forum text editor when posting logs.

Yasir_Javed · March 23, 2022, 9:22am

Similar thing was happening on Wayland for me… If you’re running Wayland, try running x11 session .