From: Giovanni Biscuolo <g@xelera.eu>
To: Efraim Flashner <efraim@flashner.co.il>,
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: Racket REPL not working
Date: Wed, 17 May 2023 13:11:53 +0200 [thread overview]
Message-ID: <874jobjjpi.fsf@xelera.eu> (raw)
In-Reply-To: <ZGJbbzIf6QEWXyGf@3900XT>
[-- Attachment #1: Type: text/plain, Size: 3439 bytes --]
Hello,
Efraim Flashner <efraim@flashner.co.il> writes:
[...]
> I was able to run 'guix shell racket -- racket --version' with it
> segfaulting. Same thing when I switched to using the same commit that
> you're using.
I'm using this Guix commit:
--8<---------------cut here---------------start------------->8---
Generation 149 May 08 2023 13:31:35 (current)
guix e118b92
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: e118b92cfe7a598b71dbbda2622b7551f4a72104
--8<---------------cut here---------------end--------------->8---
I'm on a foreign distro (Debian 11), I've tested racket in a
pure/not-pure guix shell and it is working, no segfaulting
> Can you paste the output of 'lscpu'? I suspect that there might be some
> optimizations being applied during build time and it's been optimized
> with features not available in your CPU.
This is my lscpu output:
--8<---------------cut here---------------start------------->8---
giovanni@roquette: lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 36 bits physical, 48 bits virtual
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 1
Core(s) per socket: 8
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 77
Model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz
Stepping: 8
CPU MHz: 1899.896
CPU max MHz: 2400,0000
CPU min MHz: 1200,0000
BogoMIPS: 4799.73
Virtualization: VT-x
L1d cache: 192 KiB
L1i cache: 256 KiB
L2 cache: 4 MiB
NUMA node0 CPU(s): 0-7
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Mitigation; Clear CPU buffers; SMT disabled
Vulnerability Meltdown: Mitigation; PTI
Vulnerability Spec store bypass: Not affected
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP disabled, RSB filling
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_pe
rfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popc
nt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch cpuid_fault epb pti ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm arat
md_clear
--8<---------------cut here---------------end--------------->8---
HTH! Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2023-05-17 11:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 21:56 Racket REPL not working Zelphir Kaltstahl
2023-05-15 0:20 ` Felix Lechner via
2023-05-15 21:55 ` Zelphir Kaltstahl
2023-05-15 16:18 ` Efraim Flashner
2023-05-15 21:58 ` Zelphir Kaltstahl
2023-05-17 11:11 ` Giovanni Biscuolo [this message]
2023-06-30 4:52 ` Chris Keschnat
2023-06-30 12:08 ` Philip McGrath
2023-07-01 11:41 ` Chris Keschnat
2023-07-02 2:31 ` Philip McGrath
2023-07-02 15:34 ` Philip McGrath
2023-07-02 16:12 ` Chris Keschnat
2023-07-02 19:57 ` Philip McGrath
2023-07-05 4:16 ` Chris Keschnat
2023-07-05 7:13 ` How to find what grafts have been applied? [Was: Racket REPL not working] Philip McGrath
2023-08-23 14:48 ` Racket REPL not working Simon Tournier
2023-08-23 17:54 ` Chris Keschnat
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jobjjpi.fsf@xelera.eu \
--to=g@xelera.eu \
--cc=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@posteo.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.