GNU bug report logs

#77115 [shepherd] Attempt to suspend fiber within continuation barrier

PackageSource(s)Maintainer(s)
guix PTS Buildd Popcon
Reply or subscribe to this bug. View this bug as an mbox, status mbox, or maintainer mbox

Report forwarded to bug-guix@gnu.org:
bug#77115; Package guix. (Wed, 19 Mar 2025 11:53:02 GMT) (full text, mbox, link).


Acknowledgement sent to Maxim Cournoyer <maxim.cournoyer@gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix@gnu.org. (Wed, 19 Mar 2025 11:53:02 GMT) (full text, mbox, link).


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

From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: bug-guix <bug-guix@gnu.org>
Subject: [shepherd] Attempt to suspend fiber within continuation barrier
Date: Wed, 19 Mar 2025 20:52:21 +0900
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@gnu.org:
bug#77115; Package guix. (Wed, 19 Mar 2025 16:43:02 GMT) (full text, mbox, link).


Message #8 received at 77115@debbugs.gnu.org (full text, mbox, reply):

From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 77115@debbugs.gnu.org
Subject: Re: bug#77115: [shepherd] Attempt to suspend fiber within continuation barrier
Date: Thu, 20 Mar 2025 01:41:53 +0900
[Message part 1 (text/plain, inline)]
tag 77115 + important
quit

Hi,

Maxim Cournoyer <maxim.cournoyer@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@gnu.org:
bug#77115; Package guix. (Wed, 19 Mar 2025 16:43:02 GMT) (full text, mbox, link).


Message #11 received at 77115@debbugs.gnu.org (full text, mbox, reply):

From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 77115@debbugs.gnu.org, GNU Debbugs <control@debbugs.gnu.org>
Subject: Re: bug#77115: [shepherd] Attempt to suspend fiber within continuation barrier
Date: Thu, 20 Mar 2025 01:42:06 +0900
[Message part 1 (text/plain, inline)]
tag 77115 + important
quit

Hi,

Maxim Cournoyer <maxim.cournoyer@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@gnu.org:
bug#77115; Package guix. (Wed, 19 Mar 2025 18:14:02 GMT) (full text, mbox, link).


Message #14 received at 77115@debbugs.gnu.org (full text, mbox, reply):

From: Ludovic Courtès <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 77115@debbugs.gnu.org
Subject: Re: bug#77115: [shepherd] Attempt to suspend fiber within continuation barrier
Date: Wed, 19 Mar 2025 19:13:13 +0100
Hi,

Maxim Cournoyer <maxim.cournoyer@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@gmail.com> to control@debbugs.gnu.org. (Thu, 20 Mar 2025 03:13:02 GMT) (full text, mbox, link).


Reply sent to Maxim Cournoyer <maxim.cournoyer@gmail.com>:
You have taken responsibility. (Thu, 10 Apr 2025 14:26:02 GMT) (full text, mbox, link).


Notification sent to Maxim Cournoyer <maxim.cournoyer@gmail.com>:
bug acknowledged by developer. (Thu, 10 Apr 2025 14:26:03 GMT) (full text, mbox, link).


Message #21 received at 77115-done@debbugs.gnu.org (full text, mbox, reply):

From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ludovic Courtès <ludo@gnu.org>
Cc: 77115-done@debbugs.gnu.org
Subject: Re: bug#77115: [shepherd] Attempt to suspend fiber within continuation barrier
Date: Thu, 10 Apr 2025 23:24:50 +0900
Hi Ludovic,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi,
>
> Maxim Cournoyer <maxim.cournoyer@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




Send a report that this bug log contains spam.


debbugs.gnu.org maintainers <help-debbugs@gnu.org>. Last modified: Tue Apr 15 18:37:53 2025; Machine Name: wallace-server

GNU bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.