Guix reboot stops with some errors

  • Open
  • quality assurance status badge
Details
3 participants
  • Bengt Richter
  • Ludovic Courtès
  • znavko
Owner
unassigned
Submitted by
znavko
Severity
normal
Z
Z
znavko wrote on 28 Nov 2020 19:46
(name . bug-guix)(address . bug-guix@gnu.org)
17867ebf9e3b0a5c9bc45447899600d9@disroot.org
Hello!
I have a trouble that I cannot solve and did not have such before.
When I reboot or power off my pc the process of shutdown stops with lines of 'call trace' (in attach).
It happened today after hundreds of tries of update with network errors (from guix server as I think)

I just added another disk to my system, it works fine.
But something happened.
Please where to dig?

Config is in attach.
Attachment: file
Attachment: photo5336907176846930169.jpg
Attachment: config-disks.config
Z
Z
znavko wrote on 28 Nov 2020 20:05
246d875e407fc247fc53d72877f98b98@disroot.org
I have deleted lines with disks in config and reconfigured but the error remains.

I switched to generation (system and packages by root) but an issue remains.

In Attach entire screen with trace.

What is that?
November 28, 2020 6:47 PM, "znavko--- via Bug reports for GNU Guix" <bug-guix@gnu.org (mailto:bug-guix@gnu.org?to=%22znavko---%20via%20Bug%20reports%20for%20GNU%20Guix%22%20<bug-guix@gnu.org>)> wrote:
Hello!
I have a trouble that I cannot solve and did not have such before.
When I reboot or power off my pc the process of shutdown stops with lines of 'call trace' (in attach).
It happened today after hundreds of tries of update with network errors (from guix server as I think)
https://lists.gnu.org/archive/html/help-guix/2020-11/msg00220.html(https://lists.gnu.org/archive/html/help-guix/2020-11/msg00220.html)

I just added another disk to my system, it works fine.
But something happened.
Please where to dig?

Config is in attach.
Attachment: file
Attachment: full.jpg
B
B
Bengt Richter wrote on 28 Nov 2020 21:31
(address . znavko@disroot.org)(address . 44927@debbugs.gnu.org)
20201128203137.GA11115@LionPure
Hi znavko,

On +2020-11-28 19:05:25 +0000, znavko--- via Bug reports for GNU Guix wrote:
Toggle quote (20 lines)
> I have deleted lines with disks in config and reconfigured but the error remains.
>
> I switched to generation (system and packages by root) but an issue remains.
>
> In Attach entire screen with trace.
>
> What is that?
> November 28, 2020 6:47 PM, "znavko--- via Bug reports for GNU Guix" <bug-guix@gnu.org (mailto:bug-guix@gnu.org?to=%22znavko---%20via%20Bug%20reports%20for%20GNU%20Guix%22%20<bug-guix@gnu.org>)> wrote:
> Hello!
> I have a trouble that I cannot solve and did not have such before.
> When I reboot or power off my pc the process of shutdown stops with lines of 'call trace' (in attach).
> It happened today after hundreds of tries of update with network errors (from guix server as I think)
> https://lists.gnu.org/archive/html/help-guix/2020-11/msg00220.html (https://lists.gnu.org/archive/html/help-guix/2020-11/msg00220.html)
>
> I just added another disk to my system, it works fine.
> But something happened.
> Please where to dig?
>
> Config is in attach.

Just a guess, from my experience with device busy messages:

Is there a process which has a current working directory on the device when you shut down?

(E.g., I think it could happen if you had cd'd there to look around, and forgotten to cd back out first.
Or perhaps there is a bug doing something similar?)

HTH
--
Regards,
Bengt Richter
L
L
Ludovic Courtès wrote on 3 Dec 2020 17:55
(address . znavko@disroot.org)(address . 44927@debbugs.gnu.org)
87r1o6de2c.fsf@gnu.org
Hi,

znavko@disroot.org skribis:

Toggle quote (6 lines)
> I have deleted lines with disks in config and reconfigured but the error remains.
>
> I switched to generation (system and packages by root) but an issue remains.
>
> In Attach entire screen with trace.

Since you’re on an EFI machine, could it have to do with

If that is the case, it would seem that the solution is to pull and
reconfigure to a kernel >= 5.9.12 (the default in current ‘master’).

HTH,
Ludo’.
?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 44927
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