problem with common lisp

problem with common lisp

[Adam Kandur via]

hi everyone! 
recently i started getting this error when i try to build any sbcl package:
--------------------------------------------------------------------------------------------------------
starting phase `build'
Invoking sbcl: "/gnu/store/48v5srksa9nkp4hh527l6rb08pigy1bw-sbcl-2.0.9/bin/sbcl" "--non-interactive" "--eval" "(require :asdf)" "--eval" "(asdf:load-asd (truename \"/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497/share/common-lisp/sbcl-source/deploy/deploy.asd\") :name \"deploy\")" "--eval" "(asdf:operate (quote asdf:compile-bundle-op) \"deploy\")" 
This is SBCL 2.0.9, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
fatal error encountered in SBCL pid 15 tid 15:
Unhandled SIGILL at 0x52000e9d.

Error opening /dev/tty: No such device or address
Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb> command "/gnu/store/48v5srksa9nkp4hh527l6rb08pigy1bw-sbcl-2.0.9/bin/sbcl" "--non-interactive" "--eval" "(require :asdf)" "--eval" "(asdf:load-asd (truename \"/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497/share/common-lisp/sbcl-source/deploy/deploy.asd\") :name \"deploy\")" "--eval" "(asdf:operate (quote asdf:compile-bundle-op) \"deploy\")" failed with status 1
--------------------------------------------------------------------------------------------------------
dont understand what went wrong, package definitions are unchanged

Re: problem with common lisp

[zimoun]

Dear,

On Wed, 21 Oct 2020 at 22:31, Adam Kandur via <help-guix@gnu.org> wrote:

> recently i started getting this error when i try to build any sbcl
> package:

Recently, I have also built couple of ’sbcl’ packages and I have not
noticed an issue.  I should have miss something…

> --------------------------------------------------------------------------------------------------------
[..]
> ldb> command "/gnu/store/48v5srksa9nkp4hh527l6rb08pigy1bw-sbcl-2.0.9/bin/sbcl" "--non-interactive" "--eval" "(require :asdf)" "--eval" "(asdf:load-asd (truename \"/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497/share/common-lisp/sbcl-source/deploy/deploy.asd\") :name \"deploy\")" "--eval" "(asdf:operate (quote asdf:compile-bundle-op) \"deploy\")" failed with status 1
> --------------------------------------------------------------------------------------------------------

> dont understand what went wrong, package definitions are unchanged

This “sbcl-deploy” package is not in the Guix tree, right?  Do I miss
something?

Moreover, what do you mean by “package definitions are unchanged”?
Other said, what was the Guix version where it worked (guix pull -l) and
what is the current Guix version which breaks your flow (guix describe)?


All the best,
simon

Re: problem with common lisp

[zimoun]

Please keep help-guix CC. :-)

On Wed, 21 Oct 2020 at 23:53, Adam Kandur <rndd@tuta.io> wrote:

> hi, i mean that my packages for common lisp are same as one week ago when everything worked. also i had same issues with packages from guix channel.
> don't know about guix-deploy

I understand.

First, since the package you are building is yours, more information
is required to be able to find what is wrong.  Idem about your
channel.


The questions in my previous email are:

 1. could you provide the last version of Guix where it "worked"?
 2. could you provide the current version of Guix where it is "broken"?

The #1 means that you have to:

  a) "guix pull -l | grep guix".  This will display all the previous
versions of Guix you had (hoping that you have not deleted by running
"guix gc" with some well-chosen options).
From these versions (hashes), you can run:

   guix time-machine --commit=<hash> -- build -L paht/to/your/local/pkg sbcl-foo

and see which worked and which not.  The easiest is to go
anti-chronological (start by your current Guix version and go
backward).

  b) "guix describe" and probably attach the recipe of your broken
package.  For example it seems that one of your package is named
"sbcl-deploy" since you have one item in the store named
"/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497"
and this package is not in "master", AFAICT.


All the best,
simon

Re: problem with common lisp

[Guillaume Le Vaillant]

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


Adam Kandur via <help-guix@gnu.org> skribis:

> hi everyone! 
> recently i started getting this error when i try to build any sbcl package:
> --------------------------------------------------------------------------------------------------------
> starting phase `build'
> Invoking sbcl: "/gnu/store/48v5srksa9nkp4hh527l6rb08pigy1bw-sbcl-2.0.9/bin/sbcl" "--non-interactive" "--eval" "(require :asdf)" "--eval" "(asdf:load-asd (truename \"/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497/share/common-lisp/sbcl-source/deploy/deploy.asd\") :name \"deploy\")" "--eval" "(asdf:operate (quote asdf:compile-bundle-op) \"deploy\")" 
> This is SBCL 2.0.9, an implementation of ANSI Common Lisp.
> More information about SBCL is available at <http://www.sbcl.org/>.
>
> SBCL is free software, provided as is, with absolutely no warranty.
> It is mostly in the public domain; some portions are provided under
> BSD-style licenses.  See the CREDITS and COPYING files in the
> distribution for more information.
> fatal error encountered in SBCL pid 15 tid 15:
> Unhandled SIGILL at 0x52000e9d.
>
> Error opening /dev/tty: No such device or address
> Welcome to LDB, a low-level debugger for the Lisp runtime environment.
> ldb> command "/gnu/store/48v5srksa9nkp4hh527l6rb08pigy1bw-sbcl-2.0.9/bin/sbcl" "--non-interactive" "--eval" "(require :asdf)" "--eval" "(asdf:load-asd (truename \"/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497/share/common-lisp/sbcl-source/deploy/deploy.asd\") :name \"deploy\")" "--eval" "(asdf:operate (quote asdf:compile-bundle-op) \"deploy\")" failed with status 1
> --------------------------------------------------------------------------------------------------------
> dont understand what went wrong, package definitions are unchanged

Hi,

The "Unhandled SIGILL at 0x52000e9d" error looks like the one in [1].
You could try downgrading sbcl to 2.0.8 to see if the error disappears.

[1] https://www.reddit.com/r/sbcl/comments/j824cs/does_binary_209_require_some_fancy_x86/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

Re: problem with common lisp

[Guillaume Le Vaillant]

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


Adam Kandur <rndd@tuta.io> skribis:

> Hi, i built 2.0.8 and error disappeared. could you tell where in manual i can read about donwgrading packages

If SBCL is in your main profile, you could downgrade it with:

--8<---------------cut here---------------start------------->8---
guix package --roll-back
guix package --upgrade --do-not-upgrade=sbcl
--8<---------------cut here---------------end--------------->8---

Or you could create an environment with "guix time-machine":

--8<---------------cut here---------------start------------->8---
guix time-machine --commit 21e79225352a5e78aa329b6cd213eb553862c363 -- environment --ad-hoc sbcl
--8<---------------cut here---------------end--------------->8---

Here 21e79225352a5e78aa329b6cd213eb553862c363 is the commit just before
the patch upgrading SBCL to 2.0.9.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

Re: problem with common lisp

[Adam Kandur via]

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.

Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb> 


Oct 21, 2020, 22:51 by zimon.toutoune@gmail.com:

> Please keep help-guix CC. :-)
>
> On Wed, 21 Oct 2020 at 23:53, Adam Kandur <rndd@tuta.io> wrote:
>
>> hi, i mean that my packages for common lisp are same as one week ago when everything worked. also i had same issues with packages from guix channel.
>> don't know about guix-deploy
>>
>
> I understand.
>
> First, since the package you are building is yours, more information
> is required to be able to find what is wrong.  Idem about your
> channel.
>
>
> The questions in my previous email are:
>
>  1. could you provide the last version of Guix where it "worked"?
>  2. could you provide the current version of Guix where it is "broken"?
>
> The #1 means that you have to:
>
>  a) "guix pull -l | grep guix".  This will display all the previous
> versions of Guix you had (hoping that you have not deleted by running
> "guix gc" with some well-chosen options).
> From these versions (hashes), you can run:
>
>  guix time-machine --commit=<hash> -- build -L paht/to/your/local/pkg sbcl-foo
>
> and see which worked and which not.  The easiest is to go
> anti-chronological (start by your current Guix version and go
> backward).
>
>  b) "guix describe" and probably attach the recipe of your broken
> package.  For example it seems that one of your package is named
> "sbcl-deploy" since you have one item in the store named
> "/gnu/store/fgfag09f1amsk82bs6jmg9h4rv6hqb94-sbcl-deploy-0.0.0-1.59fd497"
> and this package is not in "master", AFAICT.
>
>
> All the best,
> simon
>

Re: problem with common lisp

[Guillaume Le Vaillant]

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


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: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

Re: problem with common lisp

[Adam Kandur via]

[-- 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

Re: problem with common lisp

[Guillaume Le Vaillant]

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


Adam Kandur <rndd@tuta.io> skribis:

> 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)?
>>

According to [1], there is a bug in SBCL 2.0.9 that causes an illegal
instruction error on CPUs that support the popcnt instruction but not
the AVX instructions. It it the case of your CPU.
This bug has been fixed in the master branch of SBCL's repository, so
the next version of SBCL (which will be released soon I think) should
work on your machine.

[1] https://www.reddit.com/r/sbcl/comments/j824cs/does_binary_209_require_some_fancy_x86/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]