From owner-freebsd-alpha Sun Sep 27 06:46:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01768 for freebsd-alpha-outgoing; Sun, 27 Sep 1998 06:46:54 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01755 for ; Sun, 27 Sep 1998 06:46:50 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id JAA10922; Sun, 27 Sep 1998 09:46:34 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Doug Rabson cc: "Justin T. Gibbs" , alpha@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Possible problem with wait syscall handling... In-reply-to: Your message of "Sun, 27 Sep 1998 10:11:35 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Sep 1998 09:46:34 -0400 Message-ID: <10918.906903994@gjp.erols.com> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug Rabson wrote in message ID : > 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. Hrm. True. Although, as I said, I don't know what state the machine was in, as I had't kept the serial console up and remote gdb wasn't giving me anything useful. Its possible that the execve problem was something that started happening when I was pushing the machine to see why it was hanging. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message