Segfault with GCC in Armbian [Solved].
This is a followup post to to confirm that the Rock64 board that was experiencing segmentation faults with the default 786 MHz memory clock on Armbian is now stable with the uboot-initialized 333 MHz setting. On a selection of computational benchmarks performance is about 77 percent of the original setting; for compilations with gcc more than 80 percent of the original performance is retained with the added advantage that the system doesn't crash and the compiler doesn't create segmentation faults. I understand, but did not verify, that setting the memory clocks to 333 MHz has a noticeable affect on video playback.
As far as I'm concerned this problem is solved and I'll try to mark it as such. Although one out of the two Rock64 single-board computers I have required this configuration change, based on posts appearing on this forum, my suspicion is a much less than 50 percent--perhaps closer to 10 or 20 percent--of systems in use actually exhibit this problem. Even so, I would favor a note on the wiki support page for the Rock64 explaining how to work around system instability by reducing the DDR RAM memory clock.
As far as I'm concerned this problem is solved and I'll try to mark it as such. Although one out of the two Rock64 single-board computers I have required this configuration change, based on posts appearing on this forum, my suspicion is a much less than 50 percent--perhaps closer to 10 or 20 percent--of systems in use actually exhibit this problem. Even so, I would favor a note on the wiki support page for the Rock64 explaining how to work around system instability by reducing the DDR RAM memory clock.