What is the highest usable DRAM clock speed for you?
552
29.17%
7
564
0%
0
576
12.50%
3
588
8.33%
2
600
4.17%
1
612
8.33%
2
624
37.50%
9
24 vote(s)
* You voted for this item. [Show Results]

[Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes
#37
(05-23-2020, 09:46 PM)Djhg2000 Wrote: Anyway, just to confirm, did changing "/boot/boot.cmd" and running "mkimage -T script -A arm64 -C none -n pinephone -d /boot/boot.cmd /boot/boot.scr" suffice to get it up and running?

Yes

(05-23-2020, 09:46 PM)Djhg2000 Wrote: I'm not sure "memtest=256" has well defined behavior, there's only 17 patterns defined in the struct: https://github.com/torvalds/linux/blob/m...t.c#L9-L25 . However, the pattern selection is done through modulo of the number of available patterns here: https://github.com/torvalds/linux/blob/m...est.c#L110 .

So while "memtest=256" will work (evidently), the benefit of looping through the same patterns over and over is unlikely to find new errors. On the other hand, when the memory fails due to overclocking I think the results will be less consistent because some cells will appear to both pass and fail randomly. It's an interesting experiment but without persistence across reboots I don't think it will yield much of a benefit?

I think in line with the OP, memory instability, it is still a path worth walking. My overclocking days go back to getting 100MHz out of my Pentium 75 and yup the BraveHeart seems to be susceptible to thermal issues. I don't think we are dealing with "bad" memory, just as we degrade the environment it is in, it starts misbehaving. So running memtest for longer was my aim (and I can't read a line of C code Sad , in my day it was FORTRAN & Assembler) - in the old days systems that were over-overclocked usually took a while to get them to show measurable stress.

(05-23-2020, 09:46 PM)Djhg2000 Wrote: Oh and I almost forgot; put your phone in the freezer to make it boot, the lower temperatures should increase the stability enough to SSH in and disable memtest. From there you can power off and let it cool down again before you flash U-boot with 600 MHz DRAM Smile

Yeah had similar thought: Managed to get into ssh after a "cold" boot with memtest=256 and 624MHz memory.

Code:
$ ./mem.sh
No memtest output found in kernel log, wrong boot option?

but

Code:
$ dmesg
[    0.000000]   0x000000004950e080 - 0x0000000049511000 pattern 1111111111111111
[    0.000000]   0x000000004a000000 - 0x00000000b7bcd330 pattern 1111111111111111
[    0.000000]   0x00000000b7bcd361 - 0x00000000b7bcd368 pattern 1111111111111111
[    0.000000]   0x00000000b7bcd397 - 0x00000000b7bcd398 pattern 1111111111111111
[    0.000000]   0x00000000b7bfaffc - 0x00000000b7bfb000 pattern 1111111111111111
[    0.000000]   0x0000000040000000 - 0x0000000040080000 pattern aaaaaaaaaaaaaaaa
[    0.000000]   0x000000004106f000 - 0x0000000049505000 pattern aaaaaaaaaaaaaaaa
[    0.000000]   0x000000004950e080 - 0x0000000049511000 pattern aaaaaaaaaaaaaaaa
[    0.000000]   0x000000004a000000 - 0x00000000b7bcd330 pattern aaaaaaaaaaaaaaaa
[    0.000000]   0x00000000b7bcd361 - 0x00000000b7bcd368 pattern aaaaaaaaaaaaaaaa
[    0.000000]   0x00000000b7bcd397 - 0x00000000b7bcd398 pattern aaaaaaaaaaaaaaaa
[    0.000000]   0x00000000b7bfaffc - 0x00000000b7bfb000 pattern aaaaaaaaaaaaaaaa
[    0.000000]   0x0000000040000000 - 0x0000000040080000 pattern 5555555555555555
[    0.000000]   0x000000004106f000 - 0x0000000049505000 pattern 5555555555555555
[    0.000000]   0x000000004950e080 - 0x0000000049511000 pattern 5555555555555555
[    0.000000]   0x000000004a000000 - 0x00000000b7bcd330 pattern 5555555555555555
[    0.000000]   0x00000000b7bcd361 - 0x00000000b7bcd368 pattern 5555555555555555
[    0.000000]   0x00000000b7bcd397 - 0x00000000b7bcd398 pattern 5555555555555555
[    0.000000]   0x00000000b7bfaffc - 0x00000000b7bfb000 pattern 5555555555555555
... { overall several hundred lines removed from here }
[    0.000000]   0x00000000b7bcd397 - 0x00000000b7bcd398 pattern 5555555555555555
[    0.000000]   0x00000000b7bfaffc - 0x00000000b7bfb000 pattern 5555555555555555
[    0.000000]   0x0000000040000000 - 0x0000000040080000 pattern ffffffffffffffff
[    0.000000]   0x000000004106f000 - 0x0000000049505000 pattern ffffffffffffffff
[    0.000000]   0x000000004950e080 - 0x0000000049511000 pattern ffffffffffffffff
[    0.000000]   0x000000004a000000 - 0x00000000b7bcd330 pattern ffffffffffffffff
[    0.000000]   0x00000000b7bcd361 - 0x00000000b7bcd368 pattern ffffffffffffffff
[    0.000000]   0x00000000b7bcd397 - 0x00000000b7bcd398 pattern ffffffffffffffff
[    0.000000]   0x00000000b7bfaffc - 0x00000000b7bfb000 pattern ffffffffffffffff
[    0.000000]   0x0000000040000000 - 0x0000000040080000 pattern 0000000000000000
[    0.000000]   0x000000004106f000 - 0x0000000049505000 pattern 0000000000000000
[    0.000000]   0x000000004950e080 - 0x0000000049511000 pattern 0000000000000000
[    0.000000]   0x000000004a000000 - 0x00000000b7bcd330 pattern 0000000000000000
[    0.000000]   0x00000000b7bcd361 - 0x00000000b7bcd368 pattern 0000000000000000
[    0.000000]   0x00000000b7bcd397 - 0x00000000b7bcd398 pattern 0000000000000000
[    0.000000]   0x00000000b7bfaffc - 0x00000000b7bfb000 pattern 0000000000000000
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xb7bcb100-0xb7bccfff]
[    0.000000] Zone ranges:
... { etc then "normal" boot chit-chat }

Not sure what this means. Very different from the first "No errors found" log I posted earlier but certainly not particularly coherent!

OK - Just worked out my problem above is that memtest=256 caused the boot log to "overflow" and lose the initial verbage.

I changed memtest=85 (runs for approx 5 mins and sadly despite 624MHz no errors) and get "nice/clean/expected" results:


Code:
$ ./mem.sh
85 tests completed with these patterns:

4c494e5558726c7a
eeeeeeeeeeeeeeee
dddddddddddddddd
bbbbbbbbbbbbbbbb
7777777777777777
cccccccccccccccc
9999999999999999
6666666666666666
3333333333333333
8888888888888888
4444444444444444
2222222222222222
1111111111111111
aaaaaaaaaaaaaaaa
5555555555555555
ffffffffffffffff
0000000000000000
4c494e5558726c7a
eeeeeeeeeeeeeeee
dddddddddddddddd
bbbbbbbbbbbbbbbb
7777777777777777
cccccccccccccccc
9999999999999999
6666666666666666
3333333333333333
8888888888888888
4444444444444444
2222222222222222
1111111111111111
aaaaaaaaaaaaaaaa
5555555555555555
ffffffffffffffff
0000000000000000
4c494e5558726c7a
eeeeeeeeeeeeeeee
dddddddddddddddd
bbbbbbbbbbbbbbbb
7777777777777777
cccccccccccccccc
9999999999999999
6666666666666666
3333333333333333
8888888888888888
4444444444444444
2222222222222222
1111111111111111
aaaaaaaaaaaaaaaa
5555555555555555
ffffffffffffffff
0000000000000000
4c494e5558726c7a
eeeeeeeeeeeeeeee
dddddddddddddddd
bbbbbbbbbbbbbbbb
7777777777777777
cccccccccccccccc
9999999999999999
6666666666666666
3333333333333333
8888888888888888
4444444444444444
2222222222222222
1111111111111111
aaaaaaaaaaaaaaaa
5555555555555555
ffffffffffffffff
0000000000000000
4c494e5558726c7a
eeeeeeeeeeeeeeee
dddddddddddddddd
bbbbbbbbbbbbbbbb
7777777777777777
cccccccccccccccc
9999999999999999
6666666666666666
3333333333333333
8888888888888888
4444444444444444
2222222222222222
1111111111111111
aaaaaaaaaaaaaaaa
5555555555555555
ffffffffffffffff
0000000000000000

Tested memory region 0x0000000040000000 to 0x00000000b7bfb000 (1915MB)

0x0000000040000000 - 0x0000000040080000  GOOD
0x000000004106f000 - 0x0000000049505000  GOOD
0x000000004950e080 - 0x0000000049511000  GOOD
0x000000004a000000 - 0x00000000b7bcd330  GOOD
0x00000000b7bcd361 - 0x00000000b7bcd368  GOOD
0x00000000b7bcd397 - 0x00000000b7bcd398  GOOD
0x00000000b7bfaffc - 0x00000000b7bfb000  GOOD
0x0000000040000000 - 0x0000000040080000  GOOD
0x000000004106f000 - 0x0000000049505000  GOOD
0x000000004950e080 - 0x0000000049511000  GOOD
0x000000004a000000 - 0x00000000b7bcd330  GOOD
0x00000000b7bcd361 - 0x00000000b7bcd368  GOOD
0x00000000b7bcd397 - 0x00000000b7bcd398  GOOD
0x00000000b7bfaffc - 0x00000000b7bfb000  GOOD
0x0000000040000000 - 0x0000000040080000  GOOD
0x000000004106f000 - 0x0000000049505000  GOOD
0x000000004950e080 - 0x0000000049511000  GOOD
0x000000004a000000 - 0x00000000b7bcd330  GOOD
0x00000000b7bcd361 - 0x00000000b7bcd368  GOOD
0x00000000b7bcd397 - 0x00000000b7bcd398  GOOD
0x00000000b7bfaffc - 0x00000000b7bfb000  GOOD
0x0000000040000000 - 0x0000000040080000  GOOD
0x000000004106f000 - 0x0000000049505000  GOOD
0x000000004950e080 - 0x0000000049511000  GOOD
0x000000004a000000 - 0x00000000b7bcd330  GOOD
0x00000000b7bcd361 - 0x00000000b7bcd368  GOOD
0x00000000b7bcd397 - 0x00000000b7bcd398  GOOD
0x00000000b7bfaffc - 0x00000000b7bfb000  GOOD
0x0000000040000000 - 0x0000000040080000  GOOD
0x000000004106f000 - 0x0000000049505000  GOOD
0x000000004950e080 - 0x0000000049511000  GOOD
0x000000004a000000 - 0x00000000b7bcd330  GOOD
0x00000000b7bcd361 - 0x00000000b7bcd368  GOOD
0x00000000b7bcd397 - 0x00000000b7bcd398  GOOD
0x00000000b7bfaffc - 0x00000000b7bfb000  GOOD

No errors found


and


Code:
$ dmesg
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.6-pinephone (mobian@mobian) (gcc version 9.3.0 (Debian 9.3.0-11)) #5.6.0+pinephone6 SMP PREEMPT Fri May 15 23:20:03 CEST 2020
[    0.000000] Machine model: PinePhone
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000b8000000, size 128 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] early_memtest: # of tests: 85
[    0.000000]   0x0000000040000000 - 0x0000000040080000 pattern 4c494e5558726c7a
[    0.000000]   0x000000004106f000 - 0x0000000049505000 pattern 4c494e5558726c7a
[    0.000000]   0x000000004950e080 - 0x0000000049511000 pattern 4c494e5558726c7a
[    0.000000]   0x000000004a000000 - 0x00000000b7bcd330 pattern 4c494e5558726c7a
[    0.000000]   0x00000000b7bcd361 - 0x00000000b7bcd368 pattern 4c494e5558726c7a
[    0.000000]   0x00000000b7bcd397 - 0x00000000b7bcd398 pattern 4c494e5558726c7a
[    0.000000]   0x00000000b7bfaffc - 0x00000000b7bfb000 pattern 4c494e5558726c7a
[    0.000000]   0x0000000040000000 - 0x0000000040080000 pattern eeeeeeeeeeeeeeee
[    0.000000]   0x000000004106f000 - 0x0000000049505000 pattern eeeeeeeeeeeeeeee
[    0.000000]   0x000000004950e080 - 0x0000000049511000 pattern eeeeeeeeeeeeeeee
[    0.000000]   0x000000004a000000 - 0x00000000b7bcd330 pattern eeeeeeeeeeeeeeee
[    0.000000]   0x00000000b7bcd361 - 0x00000000b7bcd368 pattern eeeeeeeeeeeeeeee
[    0.000000]   0x00000000b7bcd397 - 0x00000000b7bcd398 pattern eeeeeeeeeeeeeeee
[    0.000000]   0x00000000b7bfaffc - 0x00000000b7bfb000 pattern eeeeeeeeeeeeeeee
[    0.000000]   0x0000000040000000 - 0x0000000040080000 pattern dddddddddddddddd
[    0.000000]   0x000000004106f000 - 0x0000000049505000 pattern dddddddddddddddd
[    0.000000]   0x000000004950e080 - 0x0000000049511000 pattern dddddddddddddddd
[    0.000000]   0x000000004a000000 - 0x00000000b7bcd330 pattern dddddddddddddddd
[    0.000000]   0x00000000b7bcd361 - 0x00000000b7bcd368 pattern dddddddddddddddd
[    0.000000]   0x00000000b7bcd397 - 0x00000000b7bcd398 pattern dddddddddddddddd
[    0.000000]   0x00000000b7bfaffc - 0x00000000b7bfb000 pattern dddddddddddddddd
[    0.000000]   0x0000000040000000 - 0x0000000040080000 pattern bbbbbbbbbbbbbbbb
[    0.000000]   0x000000004106f000 - 0x0000000049505000 pattern bbbbbbbbbbbbbbbb
[    0.000000]   0x000000004950e080 - 0x0000000049511000 pattern bbbbbbbbbbbbbbbb
[    0.000000]   0x000000004a000000 - 0x00000000b7bcd330 pattern bbbbbbbbbbbbbbbb
[    0.000000]   0x00000000b7bcd361 - 0x00000000b7bcd368 pattern bbbbbbbbbbbbbbbb
[    0.000000]   0x00000000b7bcd397 - 0x00000000b7bcd398 pattern bbbbbbbbbbbbbbbb
[    0.000000]   0x00000000b7bfaffc - 0x00000000b7bfb000 pattern bbbbbbbbbbbbbbbb

etc
  • ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Arch (6.2 kernel, Openbox desktop) for general purpose daily PC.
  • PinePhone Pro Explorer Edition, daily driver, rk2aw & U-boot on SPI, Arch/SXMO & Arch/phosh on eMMC
  • PinePhone BraveHeart now v1.2b 3/32Gb, Tow-boot with Arch/SXMO on eMMC
  Reply


Messages In This Thread
RE: [Volunteer needed]Too high DRAM clock speed MAY be causing you random crashes/freezes - by dukla2000 - 05-24-2020, 03:37 AM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Phone powers off with high user demands car46999 7 591 04-11-2024, 09:17 AM
Last Post: zetabeta
  Help needed: Jump drive not working UsnR2 5 4,951 07-09-2021, 03:22 PM
Last Post: UsnR2
  Endless crashes on Pine64 received today luciphercolors 4 5,562 11-24-2020, 06:09 PM
Last Post: rocket2nfinity
  Does the PinePhone have a hardware random number generator? LibrePhoneUser 4 6,314 11-12-2020, 07:47 PM
Last Post: megous
  Only enable modem when needed with kill switches sokolgeo 2 4,094 09-20-2020, 04:40 AM
Last Post: sokolgeo
Sad Crashes in every OS - Hardware-issue? rakor 4 6,123 06-22-2020, 09:20 AM
Last Post: Nooblife

Forum Jump:


Users browsing this thread: 3 Guest(s)