GNU bug report logs -
#77115
[shepherd] Attempt to suspend fiber within continuation barrier
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 77115 in the body.
You can then email your comments to 77115 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#77115
; Package
guix
.
(Wed, 19 Mar 2025 11:53:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 19 Mar 2025 11:53:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
Seen on Berlin:
--8<---------------cut here---------------start------------->8---
$ sudo herd schedule mcron 1000 | grep mumi
herd: error: exception caught while executing 'schedule' on service 'mcron':
Attempt to suspend fiber within continuation barrier
--8<---------------cut here---------------end--------------->8---
--
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77115
; Package
guix
.
(Wed, 19 Mar 2025 16:43:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 77115 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
tag 77115 + important
quit
Hi,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
> Hi,
>
> Seen on Berlin:
>
> $ sudo herd schedule mcron 1000 | grep mumi
> herd: error: exception caught while executing 'schedule' on service 'mcron':
> Attempt to suspend fiber within continuation barrier
Another data point; when using virt-manager (which uses libvirt+qemu) to
run my own operating system definition, it triggers a similar hang/crash
in Shepherd during the boot; see the screenshot below. I haven't yet
isolated which service causes it.
[Screenshot_guix-system-latest_2025-03-20_00:26:07.png (image/png, inline)]
[Message part 3 (text/plain, inline)]
--
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77115
; Package
guix
.
(Wed, 19 Mar 2025 16:43:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 77115 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
tag 77115 + important
quit
Hi,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
> Hi,
>
> Seen on Berlin:
>
> $ sudo herd schedule mcron 1000 | grep mumi
> herd: error: exception caught while executing 'schedule' on service 'mcron':
> Attempt to suspend fiber within continuation barrier
Another data point; when using virt-manager (which uses libvirt+qemu) to
run my own operating system definition, it triggers a similar hang/crash
in Shepherd during the boot; see the screenshot below. I haven't yet
isolated which service causes it.
[Screenshot_guix-system-latest_2025-03-20_00:26:07.png (image/png, inline)]
[Message part 3 (text/plain, inline)]
--
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#77115
; Package
guix
.
(Wed, 19 Mar 2025 18:14:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 77115 <at> debbugs.gnu.org (full text, mbox):
Hi,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
> $ sudo herd schedule mcron 1000 | grep mumi
> herd: error: exception caught while executing 'schedule' on service 'mcron':
> Attempt to suspend fiber within continuation barrier
(For the record, that’s Shepherd 1.0.1 currently running on berlin.)
Can you reproduce it in a VM? With 1.0.2 vs. 1.0.3?
On my laptop, which runs 1.0.3ish, I can’t seem to hit this:
--8<---------------cut here---------------start------------->8---
$ sudo herd schedule mcron 20000|wc -l
60000
--8<---------------cut here---------------end--------------->8---
> Another data point; when using virt-manager (which uses libvirt+qemu) to
> run my own operating system definition, it triggers a similar hang/crash
> in Shepherd during the boot; see the screenshot below. I haven't yet
> isolated which service causes it.
Do you have a reproducer for this one?
This looks a lot like what was fixed by
<https://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=f1a82845eaf8851af9a811e5a1d185b68b1c363f>,
which is in 1.0.3.
Thanks,
Ludo’.
Severity set to 'important' from 'normal'
Request was from
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
to
control <at> debbugs.gnu.org
.
(Thu, 20 Mar 2025 03:13:02 GMT)
Full text and
rfc822 format available.
Reply sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
You have taken responsibility.
(Thu, 10 Apr 2025 14:26:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
bug acknowledged by developer.
(Thu, 10 Apr 2025 14:26:03 GMT)
Full text and
rfc822 format available.
Message #21 received at 77115-done <at> debbugs.gnu.org (full text, mbox):
Hi Ludovic,
Ludovic Courtès <ludo <at> gnu.org> writes:
> Hi,
>
> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> skribis:
>
>> $ sudo herd schedule mcron 1000 | grep mumi
>> herd: error: exception caught while executing 'schedule' on service 'mcron':
>> Attempt to suspend fiber within continuation barrier
>
> (For the record, that’s Shepherd 1.0.1 currently running on berlin.)
>
> Can you reproduce it in a VM? With 1.0.2 vs. 1.0.3?
>
> On my laptop, which runs 1.0.3ish, I can’t seem to hit this:
>
> $ sudo herd schedule mcron 20000|wc -l
> 60000
>
>> Another data point; when using virt-manager (which uses libvirt+qemu) to
>> run my own operating system definition, it triggers a similar hang/crash
>> in Shepherd during the boot; see the screenshot below. I haven't yet
>> isolated which service causes it.
>
> Do you have a reproducer for this one?
>
> This looks a lot like what was fixed by
> <https://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=f1a82845eaf8851af9a811e5a1d185b68b1c363f>,
> which is in 1.0.3.
I stopped being able to reproduce it after some time, probably following
a reconfigure/reboot.
Closing, thanks for the follow-up on all things Shepherds!
--
Thanks,
Maxim
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 09 May 2025 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 42 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.