GNU bug report logs - #37867
bug on x86_64-linux AMD box

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37867 in the body.
You can then email your comments to 37867 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Leo Barge <puppetistas <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: bug on x86_64-linux AMD box
Date: Tue, 22 Oct 2019 05:48:09 -0700

I found a bug.

I immediately went looking for the full log but failed to find it at the 
reported location in /tmp.  My box is a $3000 AMD system that freezes 
once or twice a day -- to let you know -- so now it is a $3000 television.

-------------------------------------------------------------------------------------------------------------------------------

At hour 0437 on date 22 OCT 2019, a ten-hour long guix pull that I ran 
ended with the following message, in a summary of operation:


Full log written to 
/tmp/guix-build-glib-2.60.6.drv-0/build/meson-logs/testlog.txt
@ build-log 3297 65
command "meson" "test" "--no-suite" "flaky" failed with status 1
builder for 
`/gnu/store/r1vq08xbknz6710yxwzgf0qvca6vyqwg-glib-2.60.6.drv' failed 
with exit code 1
@ build-failed 
/gnu/store/r1vq08xbknz6710yxwzgf0qvca6vyqwg-glib-2.60.6.drv - 1 builder 
for `/gnu/store/r1vq08xbknz6710yxwzgf0qvca6vyqwg-glib-2.60.6.drv' failed 
with exit code 1
cannot build derivation 
`/gnu/store/clkn2mpdv8yahp16skpdi879fwryjl6y-texlive-bin-20180414.drv': 
1 dependencies couldn't be built
cannot build derivation 
`/gnu/store/kr6c8rvrs745pjzs4dg3448fns5dmm21-po4a-0.56.drv': 1 
dependencies couldn't be built
Backtrace:
In ./guix/monads.scm:
    482:9 19 (_ _)
In ./guix/gexp.scm:
   590:13 18 (_ _)
In ./guix/store.scm:
   1685:8 17 (_ _)
In ./guix/gexp.scm:
    839:2 16 (_ _)
    695:2 15 (_ _)
In ./guix/monads.scm:
    482:9 14 (_ _)
In ./guix/gexp.scm:
   590:13 13 (_ _)
In ./guix/store.scm:
   1685:8 12 (_ _)
In ./guix/gexp.scm:
    839:2 11 (_ _)
    695:2 10 (_ _)
In ./guix/monads.scm:
    482:9  9 (_ _)
In ./guix/gexp.scm:
   590:13  8 (_ _)
In ./guix/store.scm:
   1685:8  7 (_ _)
   1685:8  6 (_ _)
  1708:38  5 (_ #<store-connection 256.99 84cc3c0>)
In ./guix/packages.scm:
   948:16  4 (cache! #<weak-table 438/883> #<package po4a <at> 0.56 8079?> ?)
In ./guix/grafts.scm:
    323:4  3 (graft-derivation #<store-connection 256.99 84cc3c0> # # ?)
    172:4  2 (references-oracle #<store-connection 256.99 84cc3c0> #)
   182:20  1 (_ _ _)
In ./guix/store.scm:
  1215:15  0 (_ #<store-connection 256.99 84cc3c0> _ _)

./guix/store.scm:1215:15: Throw to key `srfi-34' with args `(#<condition 
&store-protocol-error [message: "build of 
`/gnu/store/kr6c8rvrs745pjzs4dg3448fns5dmm21-po4a-0.56.drv' failed" 
status: 100] 5dce210>)'.
guix pull: error: You found a bug: the program 
'/gnu/store/p5jy9sxbl93208sn6rp2487b8jydrwhm-compute-guix-derivation'
failed to compute the derivation for Guix (version: 
"f5d6c88d0f5e1556295c1a19c46ddfcb7a23107f"; system: "x86_64-linux";
host version: "f27c6c16be002d3c132cfc09c5911384be853f27"; pull-version: 1).
Please report it by email to <bug-guix <at> gnu.org>.


Leo

Communist Party

Ashland, Oregon

Message #8 received at 37867 <at> debbugs.gnu.org (full text, mbox):

From: "pelzflorian (Florian Pelz)" <pelzflorian <at> pelzflorian.de>
To: Leo Barge <puppetistas <at> gmail.com>
Cc: 37867 <at> debbugs.gnu.org
Subject: Re: bug#37867: bug on x86_64-linux AMD box
Date: Wed, 23 Oct 2019 13:53:36 +0200

On Tue, Oct 22, 2019 at 05:48:09AM -0700, Leo Barge wrote:
> 
> I found a bug.
> […]
> At hour 0437 on date 22 OCT 2019, a ten-hour long guix pull that I ran ended
> with the following message, in a summary of operation:
> 
> 
> Full log written to
> /tmp/guix-build-glib-2.60.6.drv-0/build/meson-logs/testlog.txt
> @ build-log 3297 65
> command "meson" "test" "--no-suite" "flaky" failed with status 1
> […]

Thank you for reporting.  This is strange.  Your guix version is
recent.  Glib builds fine for me though (on a Macbook using
“./pre-inst-env guix build glib --check --no-grafts”).



> I immediately went looking for the full log but failed to find it at the
> reported location in /tmp.

You would need to add -K to the guix pull command (“guix pull -K”) to
get the full log because the log is generated not by Guix itself and
Guix deletes build directories by default.

Regards,
Florian

Message #11 received at 37867 <at> debbugs.gnu.org (full text, mbox):

From: ison <ison <at> airmail.cc>
To: Leo Barge <puppetistas <at> gmail.com>
Cc: 37867 <at> debbugs.gnu.org
Subject: Re: bug#37867: bug on x86_64-linux AMD box
Date: Wed, 23 Oct 2019 23:03:20 -0600

There is a known issue with AMD causing lockups:
https://bugzilla.kernel.org/show_bug.cgi?id=196683

It sounds like you might have that if you get multiple freezes every day.
I was also experiencing this problem after building a new AMD machine and
that link helped me.
To summarize the solution seems to be upgrading your BIOS. Some people don't
have luck with that in which case there are also several workarounds given
which reduce the problem.
Incompatible ram could also cause such freezing.
It might also help to check in dmesg for errors.

Message #16 received at 37867-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Leo Barge <puppetistas <at> gmail.com>
Cc: 37867-done <at> debbugs.gnu.org
Subject: Re: bug#37867: bug on x86_64-linux AMD box
Date: Tue, 13 Oct 2020 00:10:23 -0400

Hello Leo,

Leo Barge <puppetistas <at> gmail.com> writes:

[...]

> Full log written to
> /tmp/guix-build-glib-2.60.6.drv-0/build/meson-logs/testlog.txt
> @ build-log 3297 65
> command "meson" "test" "--no-suite" "flaky" failed with status 1
> builder for
> `/gnu/store/r1vq08xbknz6710yxwzgf0qvca6vyqwg-glib-2.60.6.drv' failed 
> with exit code 1

The CI reports some failures for the current glib version on master
2.62.6 but only for the ARM architecture [0].

Since you've mentioned you are also having freezes, it could well be a
hardware issue.  I've had lots of such problem with the first Ryzen
generation processors, where some power saving features had to be
disabled to get them into stable operation.

As there's nothing actionable for us to do here, I'll close the issue.

Thank you for the report!

Maxim

[0]  http://ci.guix.gnu.org/search?query=glib-2.62.6+status%3Afailed

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.