From owner-freebsd-alpha Wed Mar 14 16:40:44 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 92A7D37B71D; Wed, 14 Mar 2001 16:40:42 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id TAA29224; Wed, 14 Mar 2001 19:40:42 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2F0eC609319; Wed, 14 Mar 2001 19:40:12 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15024.3948.98001.417245@grasshopper.cs.duke.edu> Date: Wed, 14 Mar 2001 19:40:12 -0500 (EST) To: John Baldwin Cc: alpha@FreeBSD.ORG Subject: Re: Deadlocks, whee! In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Baldwin writes: > Hi all, > > I managed to deadlock my alpha yesterday with a -j 4 buildworld. Previously it > would die when it trapped with a raised IPL as a blockable mtx_lock() of lockmgr > in trap(). I'm not sure if these two things are related or not. I'll try a > normal world without -j X today to see if it fairs better. Just FYI for those > running current that heavy load may deadlock right now. :( The machine is really deadlocked, or just one process is wedged and the buildworld stalled? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message