From owner-freebsd-questions Thu Jul 18 21:27:10 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA25788 for questions-outgoing; Thu, 18 Jul 1996 21:27:10 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA25781 for ; Thu, 18 Jul 1996 21:27:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id VAA13633; Thu, 18 Jul 1996 21:27:03 -0700 (PDT) Message-Id: <199607190427.VAA13633@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Thor Clark cc: questions@freebsd.org Subject: Re: help -system hangs - the ongoing saga In-reply-to: Your message of "Thu, 18 Jul 1996 21:18:48 PDT." From: David Greenman Reply-To: davidg@root.com Date: Thu, 18 Jul 1996 21:27:03 -0700 Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Thu, 18 Jul 1996, David Greenman wrote: > >cool, upgrade time... >Until I do, are there any other known triggers/situations I can avoid? Of this particular problem? Not that I can think of. There are plenty of other bugs in 2.1, however. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project >Thanks >-Thor Clark > >> >many of the processes (including init) were waiting with >> > >> >lock_write f020e004 >> > >> >> This is likely fixed in 2.1.5. There was a bug that could be easily >> triggered with doing a pair of ps(8)'s at the wrong time and resulted >> in the above hang. >> >> -DG >> >> David Greenman >> Core-team/Principal Architect, The FreeBSD Project >>