Date: Wed, 1 Aug 2001 13:11:11 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: John Baldwin <jhb@FreeBSD.org>, smp@FreeBSD.org Subject: Re: kaboom... Message-ID: <Pine.BSF.4.21.0108011308540.19703-100000@beppo> In-Reply-To: <20010729155402.V44279-100000@wonky.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Has there been anything further on this? Leaving this serious amount breakage
at the top of the tree for more than a week is really bad. I think I'm going
to roll this out if nothing happens in a couple of days.
On Sun, 29 Jul 2001, Matthew Jacob wrote:
>
> Ah. Sorry for the noise then.
>
> On Sun, 29 Jul 2001, Ian Dowse wrote:
>
> > In message <20010729153617.C44279-100000@wonky.feral.com>, Matthew Jacob writes
> > :
> > >Happened again once. It may be if I do 2 make -j 8 kernel builds I get this.
> > >The panic is somewhere in exit1 where marked:
> >
> > > if ((p->p_pptr->p_procsig->ps_flag & PS_NOCLDWAIT)
> > > || p->p_pptr->p_sigacts->ps_sigact[_SIG_IDX(SIGCHLD)] == SIG_IGN)
> >
> > Yeah, see my post to -current on friday ("SIGCHLD changes causing..").
> > Matt Dillon is apparently looking into this, but I was able to find
> > out that this is caused when the parent process is swapped out. It
> > is ok to check p_procsig->ps_flag, but p_sigacts is in the struct
> > user area that is inaccessible when the process is swapped out.
> >
> > Backing out kern_sig.c r1.125 and kern_exit.c r1.131 should fix it.
> >
> > Ian
> >
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0108011308540.19703-100000>