unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Adam Kandur via <help-guix@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: problem with common lisp
Date: Sat, 24 Oct 2020 18:43:25 +0200 (CEST)	[thread overview]
Message-ID: <MKQUZiU--3-2@tuta.io> (raw)
In-Reply-To: <87d017k2ds.fsf@yamatai>

[-- Attachment #1: Type: text/plain, Size: 634 bytes --]

Hi! thank you for this question. dont have to much knowledge about cpu. i attached lscpu output. if you find something interesting in it, let me know, please



Oct 24, 2020, 16:35 by glv@posteo.net:

>
> Adam Kandur via <help-guix@gnu.org> skribis:
>
>> hi, i realized that i have this problem with sbcl itself, if i install sbcl in my main profile (without any of my packages, only sbcl from guix channel) i still got this error:
>>
>> fatal error encountered in SBCL pid 1954 tid 1954:
>> Unhandled SIGILL at 0x52000e9d.
>>
>
> Out of curiosity, what does the "lscpu" command return on your machine
> (the flags in particular)?
>


[-- Attachment #2: lscpu --]
[-- Type: application/octet-stream, Size: 2259 bytes --]

Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   39 bits physical, 48 bits virtual
CPU(s):                          4
On-line CPU(s) list:             0-3
Thread(s) per core:              1
Core(s) per socket:              4
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           92
Model name:                      Intel(R) Pentium(R) CPU N4200 @ 1.10GHz
Stepping:                        9
CPU MHz:                         2435.789
CPU max MHz:                     2500.0000
CPU min MHz:                     800.0000
BogoMIPS:                        2188.80
Virtualization:                  VT-x
L1d cache:                       96 KiB
L1i cache:                       128 KiB
L2 cache:                        2 MiB
NUMA node0 CPU(s):               0-3
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch cpuid_fault cat_l2 ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust smep erms mpx rdt_a rdseed smap clflushopt intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts md_clear arch_capabilities

  reply	other threads:[~2020-10-24 16:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 20:31 problem with common lisp Adam Kandur via
2020-10-21 21:44 ` zimoun
     [not found]   ` <MKC8lw5--3-2@tuta.io>
2020-10-21 22:51     ` zimoun
2020-10-24 15:59       ` Adam Kandur via
2020-10-24 16:35         ` Guillaume Le Vaillant
2020-10-24 16:43           ` Adam Kandur via [this message]
2020-10-24 17:02             ` Guillaume Le Vaillant
2020-10-22  8:27 ` Guillaume Le Vaillant
     [not found]   ` <MKFC0qb----2@tuta.io>
2020-10-22 12:28     ` Guillaume Le Vaillant

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=MKQUZiU--3-2@tuta.io \
    --to=help-guix@gnu.org \
    --cc=glv@posteo.net \
    --cc=rndd@tuta.io \
    /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.
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).