Date: Mon, 20 Nov 2000 11:18:47 -0800 From: Jake Burkholder <jburkhol@home.com> To: John Hay <jhay@icomtek.csir.co.za> Cc: jhb@FreeBSD.ORG, smp@FreeBSD.ORG, cp@bsdi.com Subject: Re: cvs commit: src/sys/kern kern_timeout.c Message-ID: <20001120191847.74C17BA7A@io.yi.org> In-Reply-To: Message from John Hay <jhay@icomtek.csir.co.za> of "Sat, 20 Nov 2000 17:55:34 %2B0200." <200011201555.eAKFtYS92502@zibbi.icomtek.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > > > Here's a patch that seems to work ok here. It works on my UP box running > > > X and stuff, I don't notice any hung processes. It works on the SMP box, > > > I built a kernel over NFS and it seemed ok, except that I can't > > > get a kernel to boot using the serial console with WITNESS enabled. It > > > stops at the twiddle thing before the copyright is printed and just hangs. > > > This also happens without the patch and even with a UP kernel, so I don't > > > really know what's going on. Please try and let me know if you still > > > see the hung processes. > > > > > > > Well I have tried your patch and so far it looks good. I have finished > > a "make -j13 world" and a "make release NODOC=YES WORLD_FLAGS=-j4" with > > no problems on a dual 266MHz PII. > > It looks like I spoke too soon. After those 2 runs without problems, I > haven't been able to get a world or release to finish again. Always > some process that gets stuck somewhere with no error or anything. If I > kill it it dies and everything seems ok again. > > One thing that I have noticed the last few times is that there is always > a zombie process when this happens and it looks like it is the zombie's > parent that gets stuck. If I kill the parent, the zombie goes away and > the rest of the processes that was waiting for it to finish untangle > themselves. I noticed this too. I'm going to start another build world here to see if I can find anything else out. One problem is that moving the system calls out from under Giant and adding the context stealing light-weight interrupt threads will change things a lot. I suspect that some of these problems will just go away. > > I have also tried allproc2.diff, but it did not seem to make a difference. I didn't expect it to. Its not a bug fix, its just to get moving on making the proc layer mp safe, which so far hasn't been happening. Thanks, Jake 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?20001120191847.74C17BA7A>