Unexpected Shutdowns

acema · June 22, 2021, 10:58am

I know there are already a lot of issues discussed with VIM3 and unexpected shutdowns/reboots. Neither of the suggested solutions work for me.

Problem:
My Vim3 Pro shutdowns after several hours (no reboot!). The probability increases if it’s busy. It restarts after pressing the last button of the row (Reset).

Current state of analysis:
I use Quickcharge 3 power supply that was shipped with my VIM3 Pro. I use a high quality USB-A - USB-C cable. Using other cables or connecting to a real PD capable power suppy which runs another VIM3 Pro without any issues(!) didn’t work. Switching from Debian Buster 5.9 rc-2(?) image (using the one from Krescue) to Manjaro hasn’t worked.
A SSD is connected via a hub that provides power and there is no keyboard connected.

Any support is highly appreciated. I already spent HOURS on it!

Best regards

hyphop · June 22, 2021, 12:02pm

can u provide more details - kernel logs , screenshots , status led indicators

did u confirm is real power-off state or / just kernel crush / stuck …
which can help us understand is hardware defect or other problem !!!

acema · June 22, 2021, 12:27pm

Thanks for you quick support!!!

ssh: can’t connect, no pongs (headless)
If it helps I’ll connect a monitor and look at the screen.

leds: all off

dmesg:
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.12.9-1-MANJARO-ARM (builduser@Manjaro-HC) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35) #1 SMP PREEMPT Tue Jun 8 21:04:14 UTC 2021
[ 0.000000] Machine model: Khadas VIM3
[ 0.000000] efi: UEFI not found.
[ 0.000000] OF: fdt: Reserved memory: failed to reserve memory for node ‘secmon@5000000’: base 0x0000000005000000, size 3 MiB
[ 0.000000] Reserved memory: created CMA memory pool at 0x00000000e4800000, size 256 MiB
[ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool

journalctl -r:
Jun 22 14:03:59 vim3-02 kernel: random: crng init done
Jun 22 14:03:59 vim3-02 kernel: audit: type=1334 audit(1621433477.030:4): prog-id=10 op=LOAD
Jun 22 14:03:59 vim3-02 kernel: audit: type=1130 audit(1621433477.000:3): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg=‘unit=systemd-udevd comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
– Boot 1f615df077454fc4abd58e3f7e3c2899 –
Jun 22 10:39:01 vim3-02 kernel: audit: type=1106 audit(1624351141.350:2379): pid=24681 uid=0 auid=0 ses=42 subj=kernel msg=‘op=PAM:session_close grantors=pam_loginuid,pam_env,pam_env,pam_permit,pam_unix,pam_limits acct=“root” exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success’
Jun 22 10:39:01 vim3-02 kernel: audit: type=1104 audit(1624351141.350:2378): pid=24681 uid=0 auid=0 ses=42 subj=kernel msg=‘op=PAM:setcred grantors=pam_permit acct=“root” exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success’
Jun 22 10:39:01 vim3-02 audit[24681]: USER_END pid=24681 uid=0 auid=0 ses=42 subj=kernel msg=‘op=PAM:session_close grantors=pam_loginuid,pam_env,pam_env,pam_permit,pam_unix,pam_limits acct=“root” exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success’
Jun 22 10:39:01 vim3-02 audit[24681]: CRED_DISP pid=24681 uid=0 auid=0 ses=42 subj=kernel msg=‘op=PAM:setcred grantors=pam_permit acct=“root” exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success’
Jun 22 10:39:01 vim3-02 audit[24681]: USER_START pid=24681 uid=0 auid=0 ses=42 subj=kernel msg=‘op=PAM:session_open grantors=pam_loginuid,pam_env,pam_env,pam_permit,pam_unix,pam_limits acct=“root” exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success’
Jun 22 10:39:01 vim3-02 kernel: audit: type=1105 audit(1624351141.090:2377): pid=24681 uid=0 auid=0 ses=42 subj=kernel msg=‘op=PAM:session_open grantors=pam_loginuid,pam_env,pam_env,pam_permit,pam_unix,pam_limits acct=“root” exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success’
Jun 22 10:39:01 vim3-02 kernel: audit: type=1327 audit(1624351141.090:2376): proctitle="/usr/sbin/CRON"
Jun 22 10:39:01 vim3-02 audit: PROCTITLE proctitle="/usr/sbin/CRON"
Jun 22 10:39:01 vim3-02 audit[24681]: SYSCALL arch=c00000b7 syscall=64 success=yes exit=1 a0=6 a1=ffffe2b194e0 a2=1 a3=ffff99055010 items=0 ppid=16092 pid=24681 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=42 comm=“cron” exe="/usr/sbin/cron" subj=kernel key=(null)

(nothing special)

Gouwa · June 22, 2021, 3:43pm

Does your power adapter comes with 5V 3A and above specs?

We will suggest go with USBC PSU with 12V output.

acema · June 22, 2021, 4:52pm

It supports

5V, 3A
9V, 2A
12V, 1,5A

It was shipped with the VIM3. I just bought a 12V/2,5A PD power supply. Let’s see…

birty · June 22, 2021, 8:46pm

Has it got enough cooling?

acema · June 24, 2021, 6:48am

The CPU is at about 45° C. And just in case it has a fan and heat pipe. But I am not sure Manjaro can control the fan. The Vim3 shuts down even on short peaks - and even over night without any real load.

zonggestsu · June 24, 2021, 12:18pm

Does it shut down as such when running other OS like Ubuntu or android?

acema · June 24, 2021, 1:01pm

It runs some “home critical” applications that’s why I can’t install another OS temporarily. Currently I run Arch (Manjaro) and before Debian Buster (from Fenix) which also was unstable in this way.

sac27 · June 24, 2021, 2:16pm

Been having same issue myself lately while testing khadas vim3 pro as a chia node. I believe at least in my case the issue is actually with the usb3 port.

I swapped the ssd to the other usb port 2.0 i think and so far its been a few days non stop and no oh its switched off. For testing purposes i actually tried my 2.4g dongle for wireless keyboard and mouse and had the same issue it was randomly off when i checked on it. So my advise would be have nothing plugged into the usb3 port to see if its that causeing the issue.

Just incase anyone asks i use a oneplus dash charger which is rated 5v 4amp and a decent cable and that has worked flawlessly with khadas vim3 for like over a year on and off actually mining on 4 cores although i never really had anything plugged in as i ssh in.

Gouwa · June 25, 2021, 3:54pm

Yep, I think it makes sense to do a A/B test with another OS just in case it’s not the OS issue

acema · June 25, 2021, 5:20pm

Not sure if it is related to this problem but now initialisation of usb fails. The ssd light turn on 1s and neither the ssd nor the keyboard is identified. No chance to use Krescue.

And now I am using a powerful PD supply supporting 12v, 2.5a.

acema · June 27, 2021, 1:49pm

I got my new PD power supply with 12V, 2.5A. And I get different result depending on which power supply I use.

Works the one provided with the VIM3: 12V, 1.5A

Keyboard works
VIM3 boots but only without the SSD
Start of Android fails
can boot into Kresue and keyboard works

Power supply from laptop/desktop; ? V/? A

Keyboard and SSD lights up. But upon start of the kernel lights turn off.
VIM3 hangs at USB initialisation with SSD connected
VIM3 hangs with yelllow/red vertical stripes without SSD
white led flashes
can boot into Kresue and keyboard works

Power supply from USB-C PD: 12V/2.5A

Keyboard and SSD show no lights
VIM3 starts even with SSD
VIM3 hangs with yelllow/red vertical stripes without SSD
white led flashes
can boot into Krescue but keyboard doesn’t work

Maybe I am wrong, just guessing… The USB-C PD power supply provides sufficient power for VIM3 and SSD. But there is a problem with USB initialization depending on power negotiation. That’s the reason why it even start with connected SSD. The provided power supply with QC 3.0 works partly because power negotation works but it doesn’t prove enough power.

BTW, I already use a SSD with only 5V, 1A from Intel.

Looks like I need a combination of a low power SSD with a power supply whose power negotation with VIM3 works.
And this special power supply should provided 12V with >1.5A…