From owner-freebsd-alpha Sun Sep 27 02:11:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05610 for freebsd-alpha-outgoing; Sun, 27 Sep 1998 02:11:59 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05582; Sun, 27 Sep 1998 02:11:28 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA21890; Sun, 27 Sep 1998 10:11:35 +0100 (BST) Date: Sun, 27 Sep 1998 10:11:35 +0100 (BST) From: Doug Rabson To: Gary Palmer cc: "Justin T. Gibbs" , alpha@FreeBSD.ORG Subject: Re: Possible problem with wait syscall handling... In-Reply-To: <29457.906852805@gjp.erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 26 Sep 1998, Gary Palmer wrote: > Doug Rabson wrote in message ID > : > > I thought you were seeing memory fault panics in execve? Were you having > > the hang effect too? > > Yep. A couple of times I couldn't get console back, and could ping the box, > and get a connection accepted, but then nothing. Its POSSIBLE that the execve > problem was causing this, because I didn't have remote gdb hooked up 'cos it > had been stable for so long. I don't think the execve problem could have caused that. The box would have been sitting in DDB after a panic and couldn't have responded to a ping. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message