From: Timotej Lazar <timotej.lazar@araneo.si>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Rock64 segfaults (was: Merging ‘staging’?)
Date: Fri, 15 Jul 2022 12:52:45 +0200 [thread overview]
Message-ID: <874jziejgi.fsf@araneo.si> (raw)
In-Reply-To: <20220609171930.q66ow7dxzgt4jcqt@pelzflorian.localdomain>
Hi,
sorry to hijack the thread – I found your post when debugging random
segfaults on the rock64, and just wanted to post a possible solution for
anyone having the same problem.
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> [2022-06-09 19:19:30+0200]:
> (The build of llvm@11 also needed a few retries because gcc randomly
> fails sometimes (once with a segfault). That is not a Guix bug
> though, I think, but peculiarities of the rock64.)
This seems to be a hardware issue that can be fixed by downclocking the
memory¹. Mainline u-boot has two variants of the rk3328-sdram-lpddr3
.dtsi file, so I just did
(define u-boot-rock64-rk3328/666
(package
(inherit u-boot-rock64-rk3328)
(arguments
(substitute-keyword-arguments (package-arguments u-boot-rock64-rk3328)
((#:phases phases)
`(modify-phases ,phases
(add-after 'unpack 'change-ddr-clock
(lambda _
(substitute* "arch/arm/dts/rk3328-rock64-u-boot.dtsi"
(("rk3328-sdram-lpddr3-1600.dtsi") "rk3328-sdram-lpddr3-666.dtsi"))))))))))
and used that for the bootloader:
(bootloader
(bootloader-configuration
(bootloader
(bootloader
(inherit u-boot-rock64-rk3328-bootloader)
(package u-boot-rock64-rk3328/666)))
…
With this I was able to compile both gcc and llvm several times; before,
compilation would reliably crash within an hour unless it was done using
a single core. I assume performance with the lower memory rate is
considerably worse, but I haven’t done any measurements.
It’s very nice that I can include this in my OS configuration and then
pretty much forget about it. Big thanks to all guix for a system where
making such changes is so simple!
Regards,
Timotej
¹ https://forum.armbian.com/topic/15082-rock64-focal-fossa-memory-frequency/
next prev parent reply other threads:[~2022-07-15 12:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 8:35 Release v1.4? zimoun
2022-06-03 16:41 ` Ludovic Courtès
2022-06-05 17:57 ` zimoun
2022-06-05 22:31 ` vidak
2022-06-06 15:39 ` Maxim Cournoyer
2022-06-06 21:17 ` Merging ‘staging’? Ludovic Courtès
2022-06-08 11:50 ` Efraim Flashner
2022-06-08 21:24 ` Ludovic Courtès
2022-06-10 7:57 ` Efraim Flashner
2022-06-11 9:53 ` Ludovic Courtès
2022-06-11 10:49 ` Tom Fitzhenry
2022-06-12 3:58 ` Efraim Flashner
2022-06-12 21:08 ` Ludovic Courtès
2022-06-13 7:03 ` Ludovic Courtès
2022-06-14 4:01 ` Thiago Jung Bauermann
2022-06-14 10:32 ` Release ? (was: Merging ‘staging’?) zimoun
2022-06-14 13:08 ` Efraim Flashner
2022-06-15 9:21 ` Release ? Ludovic Courtès
2022-06-09 17:19 ` Merging ‘staging’? pelzflorian (Florian Pelz)
2022-06-09 17:41 ` Efraim Flashner
2022-06-09 19:02 ` pelzflorian (Florian Pelz)
2022-06-10 6:07 ` pelzflorian (Florian Pelz)
2022-06-11 7:35 ` pelzflorian (Florian Pelz)
2022-07-15 10:52 ` Timotej Lazar [this message]
2022-06-12 4:54 ` Thiago Jung Bauermann
2022-06-12 21:06 ` Ludovic Courtès
2022-06-10 15:47 ` Release v1.4? Josselin Poiret
2022-06-15 8:54 ` Ludovic Courtès
2022-06-15 16:51 ` Gábor Boskovits
2022-06-16 8:59 ` Josselin Poiret
2022-06-17 15:31 ` Ludovic Courtès
2022-06-17 15:37 ` Brian Cully via Development of GNU Guix and the GNU System distribution.
2022-06-19 3:33 ` Further thoughts on Xorg "vs" Wayland etc -- was: " bokr
2022-06-19 18:16 ` Philip McGrath
2022-06-22 13:31 ` Ludovic Courtès
2022-06-28 9:02 ` Efraim Flashner
2022-06-17 15:45 ` Josselin Poiret
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jziejgi.fsf@araneo.si \
--to=timotej.lazar@araneo.si \
--cc=guix-devel@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).