Guile 3.0.2 crashes with SIGBUS on x86_64 during 'guix pull'

Hello everyone,

on a freshly installed and reconfigured machine, I receive the following

error:

# guix pull: error: You found a bug: the program

'/gnu/store/kpxami25fi3mrxb37sfbbx2s366chpk5-compute-guix-derivation'

# failed to compute the derivation for Guix (version:

"790ada9168e0689c1c4607c61cdc1d2dbc327abf"; system: "x86_64-linux";

# host version: "398ec3c1e265a3f89ed07987f33b264db82e4080";

pull-version: 1).

I'm not entirely sure if, in this case, it is about RAM, as has been

mentioned in this thread: https://issues.guix.gnu.org/41710. I do have

24gb ram, but currently a small swap file, but that might be totally

unrelated.

If I can supply you with more information, please do not hesitate to

specify how I can aid fixing the issue.

Have a good day,

Olivier

Hello,

o.rojon@posteo.net skribis:

Is there more info above these lines?

I tried to reproduce it with:

guix time-machine --commit=398ec3c1e265a3f89ed07987f33b264db82e4080 \

-- time-machine --commit=790ada9168e0689c1c4607c61cdc1d2dbc327abf \

-- describe

but it works for me.

24 GiB is more than enough.

Is the problem reproducible if you try again now?

Thanks for reporting the issue,

Ludo’.

Hi,

I encountered a similar error message today, but it worked fine after

retrying. After digging around in /var/log/guix/drvs, I found these

lines in an appropriately-timestamped log file:

substitute: guix substitute: warning: ci.guix.gnu.org: connection failed: Connection timed out

@ build-started /gnu/store/klyq05c1q8jzwnwrlmvy4ma6m2h6hbk0-compute-guix-derivation.drv - x86_64-linux /var/log/guix/drvs/kl//yq05c1q8jzwnwrlmvy4ma6m2h6hbk0-compute-guix-derivation.drv.bz2 3907994

@ build-succeeded /gnu/store/klyq05c1q8jzwnwrlmvy4ma6m2h6hbk0-compute-guix-derivation.drv -

I do recall seeing the Connection timed out message, I'd even say it's

probably the reason why I decided to retry the pull without much

investigation.

Regards,

Jakub Kądziołka

Hej Ludo,

thanks for the quick reply!

I just tried to pull again and yielded the same result.

Actually, no, there is nothing above these lines. Yet, let me copy/paste

the whole command in/output. It is in german but I guess the steps are

so common by now that it shouldnt be a problem to understand :)

# user@computer ~$ guix pull

# Kanal „guix“ wird vom Git-Repository auf

„https://git.savannah.gnu.org/git/guix.git“aktualisiert …

# Von diesen Kanälen wird erstellt:

# guix https://git.savannah.gnu.org/git/guix.git 0713929

# guix pull: error: You found a bug: the program

'/gnu/store/kpxami25fi3mrxb37sfbbx2s366chpk5-compute-guix-derivation'

# failed to compute the derivation for Guix (version:

"0713929685d2fd1970df1b1ce238ee7bd6e892f8"; system: "x86_64-linux";

# host version: "398ec3c1e265a3f89ed07987f33b264db82e4080";

pull-version: 1).

# Please report it by email to <bug-guix@gnu.org>.

Also, now I am sure it has nothing to do with ram. Apart from the

already available ram, I resized my swapdevice.

Is there anything else I should test? One thing I could do is to

roll-back (I did a upgrade/reconfigure cycle after installation). Should

I do that and then pull again?

Greetings,

Olivier

On 04.06.2020 22:00, Ludovic Courtès wrote:

Just to follow up: a roll-back does NOT solve the issue.

What I have tried:

1) roll-back via guix system roll-back (to the generation that was

created upon system installation)

2) roll-back via guix package --roll-back (same)

3) (1) + (2) combined

4) boot into the generation created upon system installation.

In none of these cases was I able to run 'guix pull'.

Does it help for you to see my system configuration file? Because there

isnt much in there apart from very basic packages (ncdu, recutils, some

fonts, some icon packs) and a few services (GDM->SDDM login manager,

MATE desktop, TOR). Also note that before the re-installation, I have

not experienced problems with this configuration (MINUS mate desktop and

TOR).

On 04.06.2020 22:00, Ludovic Courtès wrote:

Hi,

o.rojon@posteo.net skribis:

Thanks for testing this.

Note that, if “which guix” returns ~/.config/guix/current/bin/guix, then

none of the rollbacks above can have any effect. What could make a

difference (but again, that would seem weird to me) is:

guix pull --roll-back

Are you passing extra options to guix-daemon, such as

‘--cache-failures’? Or did you enable offloading?

It could also be that a transient failure is causing a silent build

failure somewhere, as Jakub suggests.

Thanks,

Ludo’.

PS: Please keep the bug address Cc’d.

Hi Ludo,

guix pull --roll-back did not solve the issue. The only thing I believe

to have changed is the "host version" portion of the error message.

'which guix' actually points to ~/.configu/guix/current/bin/guix. Should

this command yield a different value?

I have actually not done anything regarding either guix-daemon or

offloading. The only things I did after the fresh install were a

reconfigure and passing a manifest file to 'guix package -m'.

I may have misunderstood what Jakub wrote because I am unsure what a

transient failure is. The portion I believe to have understood

essentially says "try again later and it should work".

I found the logs of 'compute-guix-derivation', but I was unable to see

anything meaningful opening the .drv.bz2 file in emacs. Am I doing

something wrong?

I wont be on my guix machine for some days now but appreciate pointers.

:)

Olivier

On 05.06.2020 18:29, Ludovic Courtès wrote:

Hi,

o.rojon@posteo.net skribis:

OK, that’s expected.

No.

Yes, that’s the essence of it. :-)

Could you try this:

strace -s 500 -o log guix pull

and post the ‘log’ file, compressed, somewhere?

Thanks,

Ludo’.

Hi Ludo,

here is the log uploaded on mediafire:

http://www.mediafire.com/file/ldqoi68y88rzrn9/log.bz2/file(note that if

you can recommend another uploading service, feel free to!)

Since the log is in german, let me specify at least two of the recurrent

phrases in english:

"Datei oder Verzeichnis nicht gefunden" means "file or directory not

found"

"Die Ressource ist zur Zeit nicht verfügbar" means "Resource is

currently unavailable"

If there is other things that need be translated, dont hesitate to tell

me :)

Greetings,

Olivier

On 07.06.2020 21:47, Ludovic Courtès wrote:

Hi,

o.rojon@posteo.net skribis:

I don’t know, maybe you could run IPFS.

The log reads:

… which means the ‘compute-guix-derivation’ process crashed with SIGBUS.

Could you run:

ulimit -c unlimited

guix pull

That should fail again, but this time there should be a ‘core’ file in

the current directory (or ‘core.’ followed by digits).

Then you can run:

gdb --core=./core

and at the GDB prompt, type:

thread apply all bt

Could you let me know what that returns?

Thanks,

Ludo’.

Hej Ludo,

crazy, I wouldn't have thought it would go as deep as gdb as quickly ;-)

I followed the steps you mentioned, the results you find here:

https://www.mediafire.com/file/g5yz8f3pput8f3w/gdb-output/file . The

only part I omitted from the gdb output is the first lines mentioned the

license. (Will look at IPFS, maybe next time :))

If you need anything else, dont hesitate to specify. Also, should a

reinstall become necessary, that would be annoying but not the end of

the world. So if we hit a dead end thats fine by me.

Thanks a lot for your help. So far, I received only good from the guix

community :)

Greetings,

Olivier

On 09.06.2020 16:30, Ludovic Courtès wrote:

Hi Olivier,

o.rojon@posteo.net skribis:

Since it’s a small file, you can send it as an attachment.

GDB shows:

That means debugging info is lacking. To address that, could you run:

guix build $(guix gc --derivers /gnu/store/0m0vd873jp61lcm4xa3ljdgx381qa782-guile-3.0.2)

and then:

echo 'set debug-file-directory /gnu/store/9lg4gssswn2cwn54p6jjy6nld16ah795-guile-3.0.2-debug/lib/debug' >> ~/.gdbinit

At that point, you can try again to run:

gdb --core=./core

That will hopefully show more useful info.

Thanks in advance!

Ludo’.

retitle 41715 Guile 3.0.2 crashes with SIGBUS on x86_64 during 'guix pull'

quit

severity 41715 important

quit

Hej Ludo,

I see that some time has passed and I believe that the issue can be closed.

Long story short, my hdd has died and I bought a new one and

re-installed. I could imagine that the errors I was running into were

related to the impending hardware failure -- that's a speculation,

though. Anyway, following your suggestions brought me to the same point

I was at earlier (gdb didnt show anything useful).

Another possible source of error I have not mentioned before (I simply

forgot about it): after the fresh install, I swapped the swap and /home

partition using another OS (I have two hdds, each of which has a

different OS). I don't know if that could've been the problem and/or one

reason the hdd died.

Anyway, I'm thankful for your supportive attitude and your time.

Have a good day,

Olivier

Am 12.06.20 um 16:12 schrieb Ludovic Courtès:

Hi Olivier,

Olivier <o.rojon@posteo.net> skribis:

OK, too bad.

Do let us know if you experience a similar crash again.

Thank you,

Ludo’.

tags 41715 unreproducible

close 41715

quit