From: Maxime Devos <maximedevos@telenet.be>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: 54651@debbugs.gnu.org
Subject: bug#54651: Guix pull failing on ARM 32bit with "Please report the COMPLETE output above by email"
Date: Mon, 23 May 2022 20:27:18 +0200 [thread overview]
Message-ID: <bf9857a0c429ddda79d852b8f8e808c4bb82a877.camel@telenet.be> (raw)
In-Reply-To: <20220523193013.4ab258df@primarylaptop.localdomain>
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
Denis 'GNUtoo' Carikli schreef op ma 23-05-2022 om 19:30 [+0200]:
> And here I probably lack some knowledge but I was under the
> impression
> that swap was handled transparently by the kernel (through page
> tables,
> virtual memory, and so on), so applications should not notice the
> difference apart from the huge performance drop.
>
> Though one issue could be that maybe for some reason the process
> wants
> to use more than 3GiB of memory and at least i686 processes are
> limited
> to 4GiB if you use an x86_64 kernel and about 3GiB if you use an i686
> kernel. So maybe it's somehow similar for armv7h?
That's what I was referring to. Additionally, I've also seen ‘2GiB’
(as in: 2/2 split) mentioned somewhere, though I don't know if it
applies to arm and linux.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-23 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 12:15 bug#54651: Guix pull failing on ARM 32bit with "Please report the COMPLETE output above by email" Denis 'GNUtoo' Carikli
2022-04-05 15:02 ` Denis 'GNUtoo' Carikli
2022-05-18 13:47 ` Denis 'GNUtoo' Carikli
2022-05-23 13:40 ` Denis 'GNUtoo' Carikli
2022-05-23 14:10 ` Maxime Devos
2022-05-23 14:22 ` raingloom
2022-05-23 17:30 ` Denis 'GNUtoo' Carikli
2022-05-23 18:27 ` Maxime Devos [this message]
2022-05-23 19:08 ` Denis 'GNUtoo' Carikli
2022-05-23 22:18 ` Denis 'GNUtoo' Carikli
2022-05-24 8:34 ` Maxime Devos
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=bf9857a0c429ddda79d852b8f8e808c4bb82a877.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54651@debbugs.gnu.org \
--cc=GNUtoo@cyberdimension.org \
/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).