[Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes

[Djhg2000]

...
I couldn't get a log sample from a system with bad memory so the entire error handling section is made from reverse engineering of the Linux source code. If you have a kernel log from a system with bad memory I'd greatly appreciate if you could provide real error messages.

But how do I get memtest to execute on boot?

I added memtest=17 in /boot/boot.cmd

Code:

$ cat /boot/boot.cmd if test ${mmc_bootdev} -eq 0 ; then echo "Booting from SD"; setenv linux_mmcdev 0; else echo "Booting from eMMC"; setenv linux_mmcdev 2; fi; setenv bootargs console=ttyS0,115200 no_console_suspend panic=10 consoleblank=0 loglevel=7 root=/dev/mmcblk${linux_mmcdev}p1 ro splash memtest=17 plymouth.ignore-serial-consoles vt.global_cursor_default=0 ...

but clearly that isn't what is being used at boot

Code:

$ uname -a Linux DuklaPP 5.6-pinephone #5.6.0+pinephone6 SMP PREEMPT Fri May 15 23:20:03 CEST 2020 aarch64 GNU/Linux chris@DuklaPP:~$ grep -i memtest /boot/config-$(uname -r) CONFIG_MEMTEST=y chris@DuklaPP:~$ ./mem.sh No memtest output found in kernel log, wrong boot option? $ dmesg | grep Kernel [    0.000000] Kernel command line: console=ttyS0,115200 no_console_suspend panic=10 consoleblank=0 loglevel=7 root=/dev/mmcblk2p1 ro splash plymouth.ignore-serial-consoles vt.global_cursor_default=0 ...

I'm afraid you'll have to redirect that question to @devrtz , I haven't received my PinePhone yet so I've been testing what I can on my Debian system.

But I'll try my best to help out anyway; can you please check whether or not you have memtest support in your kernel? You should be able to do that by issuing "grep -i memtest /boot/config-$(uname -r)"  from a terminal. One of five things will happen:

1. It returns "CONFIG_MEMTEST=y"
   
2. It returns "CONFIG_MEMTEST=n"
   
3. It returns "#CONFIG_MEMTEST is not set"
   
4. It returns something like "grep: /boot/config-5.4.0: No such file or directory"
   
5. It doesn't return anything
   

If you get 1 the "memtest=17" cmdline gets lost somewhere, 2 or 3 it probably means memtest isn't enabled for your kernel. If you get 4 or 5 then we need to investigate more.