guix boot stop

  • Open
  • quality assurance status badge
Details
5 participants
  • Douglas Linford
  • Julien Lepiller
  • Leo Famulari
  • Ludovic Courtès
  • Tobias Geerinckx-Rice
Owner
unassigned
Submitted by
Douglas Linford
Severity
normal
D
D
Douglas Linford wrote on 27 Oct 2020 15:23
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
36A66CC3-7591-44DB-A061-26E39C82709D@getmailspring.com
Good day,
I am new to Guix, but not Linux, so I am familiar with Linux and it's structures.
Upon my initial install of Guix, the boot will start, but always hangs.
The last four lines in the boot messages are as follows...
populating /etc from /gnu/store/mfmgcsra291k3psl7mippy53fhqkf912-etc...

error in finalization thread: Success

[ 4.190744] udevd[217]: no sender credentials received, message ignored

[ 5.889796] Error: Driver 'pcspkr' is already registered, aborting...

And the boot process stops. It seems it would be a hardware issue.
My enclosed screenshot shows the /gnu/store folder.
And as you see, all modify times show a date of Dec 31 1969.
So, am I seeing a corrupted store, or maybe a corrupted install usb stick...or?Any thoughts or resolutions?

Respectfully,
Douglas Linford
Attachment: file
Attachment: Guix Store.png
J
J
Julien Lepiller wrote on 27 Oct 2020 17:25
C0CB3143-D9F9-4D78-A56D-C74A6FB178AE@lepiller.eu
Hi Douglas,

I think I've seen this before and the solution was to use the latest image, instead of the latest release because this issue was fixed after the last release. You can find more info on the latest installer at http://guix.gnu.org/en/download/latest/

Please tell us if it solves your issue or not!

Le 27 octobre 2020 10:23:07 GMT-04:00, Douglas Linford <drkrider@gmail.com> a écrit :
Toggle quote (21 lines)
>Good day,
>I am new to Guix, but not Linux, so I am familiar with Linux and it's
>structures.
>Upon my initial install of Guix, the boot will start, but always hangs.
>The last four lines in the boot messages are as follows...
>populating /etc from /gnu/store/mfmgcsra291k3psl7mippy53fhqkf912-etc...
>
>error in finalization thread: Success
>
>[ 4.190744] udevd[217]: no sender credentials received, message ignored
>
>[ 5.889796] Error: Driver 'pcspkr' is already registered, aborting...
>
>And the boot process stops. It seems it would be a hardware issue.
>My enclosed screenshot shows the /gnu/store folder.
>And as you see, all modify times show a date of Dec 31 1969.
>So, am I seeing a corrupted store, or maybe a corrupted install usb
>stick...or?Any thoughts or resolutions?
>
>Respectfully,
>Douglas Linford
Attachment: file
D
D
Douglas Linford wrote on 27 Oct 2020 19:13
(name . Julien Lepiller)(address . julien@lepiller.eu)(address . 44257@debbugs.gnu.org)
CAB3EbL4p0+AXP2YdrHaS8ubLGKcyP+CkEx9TH3YMmwS6SZGY=A@mail.gmail.com
Thanks, I'll check it out.

Douglas

On Tue, Oct 27, 2020, 12:25 PM Julien Lepiller <julien@lepiller.eu> wrote:

Toggle quote (39 lines)
> Hi Douglas,
>
> I think I've seen this before and the solution was to use the latest
> image, instead of the latest release because this issue was fixed after the
> last release. You can find more info on the latest installer at
> http://guix.gnu.org/en/download/latest/
>
> Please tell us if it solves your issue or not!
>
> Le 27 octobre 2020 10:23:07 GMT-04:00, Douglas Linford <drkrider@gmail.com>
> a écrit :
>>
>> Good day,
>> I am new to Guix, but not Linux, so I am familiar with Linux and it's
>> structures.
>> Upon my initial install of Guix, the boot will start, but always hangs.
>> The last four lines in the boot messages are as follows...
>>
>> 1. populating /etc from
>> /gnu/store/mfmgcsra291k3psl7mippy53fhqkf912-etc...
>> 2. error in finalization thread: Success
>> 3. [ 4.190744] udevd[217]: no sender credentials received, message
>> ignored
>> 4. [ 5.889796] Error: Driver 'pcspkr' is already registered,
>> aborting...
>>
>> And the boot process stops. It seems it would be a hardware issue.
>> My enclosed screenshot shows the /gnu/store folder.
>> And as you see, all modify times show a date of Dec 31 1969.
>> So, am I seeing a corrupted store, or maybe a corrupted install usb
>> stick...or?Any thoughts or resolutions?
>>
>> Respectfully,
>> Douglas Linford
>>
>>
>> [image: Sent from Mailspring]
>
>
Attachment: file
L
L
Ludovic Courtès wrote on 28 Oct 2020 15:21
(name . Julien Lepiller)(address . julien@lepiller.eu)
87k0va2zyv.fsf@gnu.org
Hi,

Julien Lepiller <julien@lepiller.eu> skribis:

Toggle quote (4 lines)
> I think I've seen this before and the solution was to use the latest
> image, instead of the latest release because this issue was fixed
> after the last release.

I think the 1.1 ISO did install bootable systems in general though. :-)
Do you have a specific bug in mind?

Thanks,
Ludo’.
D
D
Douglas Linford wrote on 28 Oct 2020 15:55
(name . Ludovic Courtès)(address . ludo@gnu.org)
1563A7D9-9391-4DB8-9059-C416F0C44DF4@getmailspring.com
Good day,
I seem to have the boot issue resolved, (an issue with radeon, I put nomodeset in the grub load line), but the bug issue I was referring to is when I run the command: ls -l on the /gnu/store directory, all store folders have a date stamp of Dec 31, 1969.
It doesn't seem to effect anything, so maybe I should just ignore the dates.

Douglas
On Oct 28 2020, at 10:21 am, Ludovic Courtès <ludo@gnu.org> wrote:
Toggle quote (13 lines)
> Hi,
>
> Julien Lepiller <julien@lepiller.eu> skribis:
> > I think I've seen this before and the solution was to use the latest
> > image, instead of the latest release because this issue was fixed
> > after the last release.
>
> I think the 1.1 ISO did install bootable systems in general though. :-)
> Do you have a specific bug in mind?
>
> Thanks,
> Ludo’.
>
Attachment: file
L
L
Leo Famulari wrote on 28 Oct 2020 17:24
(name . Douglas Linford)(address . drkrider@gmail.com)
20201028162431.GB12095@jasmine.lan
The timestamps are reset to "zero" (the first date possible on Unix
systems) as part of Guix's efforts to build everything reproducibly.

On Wed, Oct 28, 2020 at 10:55:38AM -0400, Douglas Linford wrote:
Toggle quote (21 lines)
> Good day,
> I seem to have the boot issue resolved, (an issue with radeon, I put nomodeset in the grub load line), but the bug issue I was referring to is when I run the command: ls -l on the /gnu/store directory, all store folders have a date stamp of Dec 31, 1969.
> It doesn't seem to effect anything, so maybe I should just ignore the dates.
>
> Douglas
> Sent from Mailspring (https://link.getmailspring.com/link/1563A7D9-9391-4DB8-9059-C416F0C44DF4@getmailspring.com/0?redirect=https%3A%2F%2Fgetmailspring.com%2F&recipient=NDQyNTdAZGViYnVncy5nbnUub3Jn), the best free email app for work
> On Oct 28 2020, at 10:21 am, Ludovic Courtès <ludo@gnu.org> wrote:
> > Hi,
> >
> > Julien Lepiller <julien@lepiller.eu> skribis:
> > > I think I've seen this before and the solution was to use the latest
> > > image, instead of the latest release because this issue was fixed
> > > after the last release.
> >
> > I think the 1.1 ISO did install bootable systems in general though. :-)
> > Do you have a specific bug in mind?
> >
> > Thanks,
> > Ludo’.
> >
>
T
T
Tobias Geerinckx-Rice wrote on 28 Oct 2020 17:33
(name . Douglas Linford)(address . drkrider@gmail.com)
875z6uz4wz.fsf@nckx
Douglas,

Thanks for clarifying!

Douglas Linford ???
Toggle quote (6 lines)
> the bug issue I was referring to is when I run the command: ls
> -l on the /gnu/store directory, all store folders have a date
> stamp of Dec 31, 1969.
> It doesn't seem to effect anything, so maybe I should just
> ignore the dates.

It affects everything:

Since there's no bug I'm closing this issue, but don't hesitate to
send any further questions or (mis)adventures to help-guix@ or
bug-guix@.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCX5mdXA0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15q0IA/R3SPRMfwN/aaPF72wh4+2fAlWcYPnH9vlsKF+sW
YR3NAQDVRjx+2Ndh51/jpR2JfzNeEAIkIR4tFpYMzJG12unQBA==
=Epyk
-----END PGP SIGNATURE-----

D
D
Douglas Linford wrote on 28 Oct 2020 17:32
(name . Leo Famulari)(address . leo@famulari.name)
CAB3EbL5NBJ3P_X+Xe=H2X2qQFB4B2=n8UxX_vSjGwjHMAGWSQw@mail.gmail.com
Awesome, thanks!
How do I close my, "non" bug?

Douglas

On Wed, Oct 28, 2020, 12:24 PM Leo Famulari <leo@famulari.name> wrote:

Toggle quote (32 lines)
> The timestamps are reset to "zero" (the first date possible on Unix
> systems) as part of Guix's efforts to build everything reproducibly.
>
> On Wed, Oct 28, 2020 at 10:55:38AM -0400, Douglas Linford wrote:
> > Good day,
> > I seem to have the boot issue resolved, (an issue with radeon, I put
> nomodeset in the grub load line), but the bug issue I was referring to is
> when I run the command: ls -l on the /gnu/store directory, all store
> folders have a date stamp of Dec 31, 1969.
> > It doesn't seem to effect anything, so maybe I should just ignore the
> dates.
> >
> > Douglas
> > Sent from Mailspring (
> https://link.getmailspring.com/link/1563A7D9-9391-4DB8-9059-C416F0C44DF4@getmailspring.com/0?redirect=https%3A%2F%2Fgetmailspring.com%2F&recipient=NDQyNTdAZGViYnVncy5nbnUub3Jn),
> the best free email app for work
> > On Oct 28 2020, at 10:21 am, Ludovic Courtès <ludo@gnu.org> wrote:
> > > Hi,
> > >
> > > Julien Lepiller <julien@lepiller.eu> skribis:
> > > > I think I've seen this before and the solution was to use the latest
> > > > image, instead of the latest release because this issue was fixed
> > > > after the last release.
> > >
> > > I think the 1.1 ISO did install bootable systems in general though. :-)
> > > Do you have a specific bug in mind?
> > >
> > > Thanks,
> > > Ludo’.
> > >
> >
>
Attachment: file
D
D
Douglas Linford wrote on 28 Oct 2020 17:45
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)
296E87C0-08A8-405A-973A-A0B00140C158@getmailspring.com
Tobias,
Is there a more appropriate place to post issues so as not to fill up the bug reports with needless issues?

Douglas

On Oct 28 2020, at 12:33 pm, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
Toggle quote (19 lines)
> Douglas,
>
> Thanks for clarifying!
> Douglas Linford ???
> > the bug issue I was referring to is when I run the command: ls
> > -l on the /gnu/store directory, all store folders have a date
> > stamp of Dec 31, 1969.
> > It doesn't seem to effect anything, so maybe I should just
> > ignore the dates.
>
> It affects everything:
> <https://www.mail-archive.com/help-guix@gnu.org/msg10274.html>.
>
> Since there's no bug I'm closing this issue, but don't hesitate to
> send any further questions or (mis)adventures to help-guix@ or
> bug-guix@.
>
> Kind regards,
> T G-R
Attachment: file
L
L
Leo Famulari wrote on 28 Oct 2020 17:45
(name . Douglas Linford)(address . drkrider@gmail.com)
20201028164532.GA13614@jasmine.lan
On Wed, Oct 28, 2020 at 12:32:49PM -0400, Douglas Linford wrote:
Toggle quote (3 lines)
> Awesome, thanks!
> How do I close my, "non" bug?

You can send any message to <44257-done@debbugs.gnu.org>, or you can
send the message "close 44257" to <control@debbugs.gnu.org>.
T
T
Tobias Geerinckx-Rice wrote on 28 Oct 2020 18:11
(name . Douglas Linford)(address . drkrider@gmail.com)(name . 44257-done@debbugs.gnu.org)(address . 44257@debbugs.gnu.org)
87361yz35q.fsf@nckx
Douglas,

To augment Leo's answer, here's the full skinny:

Douglas Linford ???
Toggle quote (3 lines)
> Is there a more appropriate place to post issues so as not to
> fill up the bug reports with needless issues?

In our system, ‘issues’ are synonymous with ‘bugs’ (‘shortcomings
in the software’, which can include feature requests). But
opening a bug that turns out not to be one isn't the end of the
world! They are easiest to fix...

Questions or other ‘troubles’ that aren't (yet) obvious flaws are
always welcome at help-guix@gnu.org. For more technical design-
and code-related discussions there's guix-devel@gnu.org.

Oy vey, semantics,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCX5mmQQ0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15c2IA/im309qCPb9QLKbgKrOFSIakG6rKDHlhbznnyhxL
NrJNAQCYjXQuOVn0YJpCR49NTwEi1f1W5BuOn912PUiTBSlNCA==
=nBl2
-----END PGP SIGNATURE-----

T
T
Tobias Geerinckx-Rice wrote on 28 Oct 2020 18:31
(name . Leo Famulari)(address . leo@famulari.name)
87zh46xnnl.fsf@nckx
Well, since this is the Internet...

Leo Famulari ???
Toggle quote (5 lines)
> The timestamps are reset to "zero" (the first date possible on
> Unix
> systems) as part of Guix's efforts to build everything
> reproducibly.

The manual does claim as much (in (guix)Binary Installation) but
it's never been true:

$ stat -c %Y /gnu/store/arbitrary.file
1

0 is a valid value:

$ touch -d @0 /tmp/foo
$ stat -c %Y /tmp/foo
0

But (IIRC) it's a dangerous one to use in practice as too much
code assumes it never occurs in the wild, and use it to mean
something special for internal use. IIRRC GNU make was (once?)
one such culprit.

I shall patch the manual and make this an actionable bug after
all.

Thanks,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCX5mq/g0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15xEoBANd4dv1z6R80XK37XlN3fvKRAvrGYZpqZRKUHYbd
SA8tAQDkPX/k0mjTqOow390Uuna1ADefcgVrBVbU7vD19Zs0AA==
=mYxn
-----END PGP SIGNATURE-----

J
J
Julien Lepiller wrote on 28 Oct 2020 18:43
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 44257@debbugs.gnu.org)
8986DBB3-D092-4A2A-BAFC-F6DEA04EB6D8@lepiller.eu
Nothing specific, the description rang a bell anl I thought I already saw that and its solution, but I might have been wrong.

Le 28 octobre 2020 10:21:28 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
Toggle quote (14 lines)
>Hi,
>
>Julien Lepiller <julien@lepiller.eu> skribis:
>
>> I think I've seen this before and the solution was to use the latest
>> image, instead of the latest release because this issue was fixed
>> after the last release.
>
>I think the 1.1 ISO did install bootable systems in general though.
>:-)
>Do you have a specific bug in mind?
>
>Thanks,
>Ludo’.
Attachment: file
L
L
Leo Famulari wrote on 28 Oct 2020 19:00
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)
20201028180053.GA17454@jasmine.lan
On Wed, Oct 28, 2020 at 06:31:42PM +0100, Tobias Geerinckx-Rice wrote:
Toggle quote (12 lines)
> Well, since this is the Internet...
>
> Leo Famulari ???
> > The timestamps are reset to "zero" (the first date possible on Unix
> > systems) as part of Guix's efforts to build everything reproducibly.
>
> The manual does claim as much (in (guix)Binary Installation) but it's never
> been true:
>
> $ stat -c %Y /gnu/store/arbitrary.file
> 1

Right, I meant "zero", not 0. As you point out, it's not practical to
actually set the timestamps to zero seconds.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAl+ZsdEACgkQJkb6MLrK
fwh6yRAAglGVxnv8mgbI6eKX/Gh2EdxDwN39z09BAkgh7XqdDXb3rD9WShQvsIjb
1/8MGPrPGvfTS4V+4KzWG/sNEsdtQu237V2dLQQVI4oHHe65Q8ePpK1C4PiEXOMH
B4yI/c3rVmGcyvAcQG/7yLUFjY5bIstX6t9dj6lxcd10mcv6lQlJ7JP65MRoxHaI
5t00ofoPnybZ8k1ZgkOv28/E+6aRAEsNvqy6ZGeiSPlyJEBvq7yefDo2FAggpHQ2
dwNTCsg31hWhMT1bhAsfuAwPuFM/XLl1P8RRr72KlYNNTzmjRYwEk/wsgvM3s7ux
y+C3GHDNvEj+Nt7RoraV8aLJDMwyOu/+J1I/3M89XI9EtyeknzNQlpf0TE1glkHB
/IX1SU9qnbdzUROGhhj9qY4H3JE1nfF5dfam5bD1WxbJpCN/1PLE3YY4ePwh/ejp
5NiKrW+/nPuapYrhdC2IvfNoe3CRACSuykV0cOztCd7vM8BfTCySlvzLrOqONYqj
SY+xkWLQWxiQMh0yjmRAMgDTfBm4bch014vM5UFONaVUl/4CzWPMuGjNCQbkE+XR
0+oiAeOOBuFOPBkl3yoR/gTPO323LR3AQeRkp4St8bVq1+XHJozQwo3NKD58OxoE
g3nLjC6Z37MB1YM7x8U+K/DD8yU2GkDJceVnoBt1qRS9QsXxsug=
=f42B
-----END PGP SIGNATURE-----


T
T
Tobias Geerinckx-Rice wrote on 28 Oct 2020 19:28
(name . Leo Famulari)(address . leo@famulari.name)
87wnzaxl0e.fsf@nckx
Leo Famulari ???
Toggle quote (4 lines)
> Right, I meant "zero", not 0. As you point out, it's not
> practical to
> actually set the timestamps to zero seconds.

You've lost me but I think that's OK. The manual didn't & was
lovingly corrected in 83c60bb0622440afe98930820186ddfa1e6e8b2f.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCX5m4YQ0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15ANgBAKElWmytt6voJdhuLJEUrGXJDfb3cXxJpL6E3g5p
S5EiAQCGzW+H0pkkAEwNnyTDRjWPjedUAR2suAIvDGC5aaJXBw==
=gB8o
-----END PGP SIGNATURE-----

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 44257@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 44257
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch