From owner-freebsd-alpha Sat Sep 26 13:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12139 for freebsd-alpha-outgoing; Sat, 26 Sep 1998 13:03:57 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12133 for ; Sat, 26 Sep 1998 13:03:55 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id OAA06853 for ; Sat, 26 Sep 1998 14:03:48 -0600 (MDT) Message-Id: <199809262003.OAA06853@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: alpha@FreeBSD.ORG Subject: Possible problem with wait syscall handling... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Sep 1998 13:57:16 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ken started up a buildworld on our Miata last night, but perhaps 40 minutes later, the machine started locking up. Ping worked, but old network connections were frozen and new network connections blocked after the initial connection. When I came in today and dropped into DDB, I found that almost every process on the box was sleeping on "wait". I continued and broke back into DDB two or three more times and suddenly the machine un-froze. Very bizarre. Assuming I can reproduce this, anyone have any ideas where I should start poking around to determine the cause? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message