Re: [PATCH] runqueue: Really fix sigchld handling

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Wed, 2014-03-19 at 14:30 -0700, Chris Larson wrote:
> 
> On Tue, Mar 18, 2014 at 3:58 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>         +                        bb.warn("Unknown process (%s) exited
>         unexpectedly (%s), shutting down..." % (pid, str(status)))
>         
> 
> 
> This says it's shutting down, but the commit message and code imply
> that it isn't for these. I'm guessing this message needs adjustment
> from a copy/paste? :)
> 
Yes, indeed.

This signal handler stuff has been a mess and that patch and others have
just been making things worse.

Basically there are bugs in python 2.7.3 which expose problems which are
addressed in 2.7.4 and onwards. The whole signal handler approach was
flawed due to the toxic mix with subprocess anyway.

I've pushed some further patches basically reverting the signal handler
and we've ended up polling. Hopefully this stops things hanging and gets
us back to some kind of stability, I think I do understand all the
facets of the issues we've been hitting finally.

Cheers,

Richard