From owner-freebsd-alpha Sat Sep 26 16:24:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02203 for freebsd-alpha-outgoing; Sat, 26 Sep 1998 16:24:43 -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 QAA02175 for ; Sat, 26 Sep 1998 16:24:38 -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 AAA20074; Sun, 27 Sep 1998 00:24:40 +0100 (BST) Date: Sun, 27 Sep 1998 00:24:40 +0100 (BST) From: Doug Rabson To: "Justin T. Gibbs" cc: alpha@FreeBSD.ORG Subject: Re: Possible problem with wait syscall handling... In-Reply-To: <199809262003.OAA06853@pluto.plutotech.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, Justin T. Gibbs wrote: > 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? Thats an odd one. I haven't seen anything like that but it looks like a lost wakeup somewhere in vmio. I think Eivind just found one lurking in ufs_readwrite so maybe its fixable. -- 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