Hello all,

After upgrading to the below release of skarnet packages, my system
is not booting anymore on MIPS. I am using buildroot and the 
provided there by √Čric Le Bihan.

The init usually stays blocked there:

  s6-rc: info: processing service fdholder: starting

with the following processes running:

  136 root     s6-rc -v 3 -u change services-all
  143 root     s6-fdholderd -1 -i data/rules
  146 root     s6-ipcserverd -1 -- s6-ipcserver-access -v0 -E -l0 -i data/rules 
-- s6-sudod -t 2000 -- /usr/libexec/s6-rc-oneshot-run -l
  173 root     s6-svlisten1 -u -- /run/s6-rc/scandir/klogd-log s6-svc -u -- 
  183 root     s6-ftrigrd
  296 root     s6-svlisten1 -U -- /run/s6-rc/scandir/fdholder s6-svc -u -- 
  297 root     s6-ftrigrd

and I regularly see the following message, even though not consistently:

  s6-ftrigrd: fatal: unable to flush asyncout: Broken pipe

When I build the very same system for x86 I do not see any issue, it is very 
stable, so I
suspect a cross-compilation issue. Since buildroot patches skalibs in order to 
system capabilities through build-time asserts instead of runtime tests, it is 
possible that
something goes wrong there. However I have adapted the patches to the new 
and so far I cannot identify any error in the detected system settings.

If anyone has any idea to help the investigation, it would be highly 
appreciated :).
Maybe for example a hint on what could cause s6-ftrigrd to get a broken pipe ?

From: supervision@list.skarnet.org <supervision@list.skarnet.org> on behalf of 
Jean Louis <bugs@gnu.support>
Sent: Tuesday, March 28, 2017 3:45 PM
To: Laurent Bercot
Cc: skaw...@list.skarnet.org; supervision@list.skarnet.org
Subject: Re: [announce] skarnet.org Spring 2017 release

By the way, I have upgraded, without control, I see it is working well
and fine on a reboot.

On Tue, Mar 28, 2017 at 12:27:28PM +0000, Laurent Bercot wrote:
> >  * s6-
> >     ----------
>  And obviously I forgot to mention the important change for users:
> s6-svstat can now print programmatically parsable output, via a new
> "-o field" option (and shortcuts for common fields). This feature was
> asked for a long time ago.
> --
>  Laurent

Reply via email to