From owner-freebsd-smp Sat Aug 30 20:45:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA16247 for smp-outgoing; Sat, 30 Aug 1997 20:45:54 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA16241 for ; Sat, 30 Aug 1997 20:45:50 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id VAA18553; Sat, 30 Aug 1997 21:41:45 -0600 (MDT) Message-Id: <199708310341.VAA18553@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Poul-Henning Kamp cc: smp@FreeBSD.ORG Subject: Re: HEADS UP: another set of changes. In-reply-to: Your message of "Sat, 30 Aug 1997 16:13:00 +0200." <6664.872950380@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 Aug 1997 21:41:45 -0600 Sender: owner-freebsd-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > >We're at the point where deadlocks are going to become common. Bear with me > >and help as you can. When you hit one please record all the facts you can, > >and report them to smp@freebsd.org. Hopefully we will get thru this period > >before too long... > > I pressume that we want to instrument simplelock carefully in the > #ifdef DIAGNOSTIC case ? I just committed a debug version of simple_lock that will notice an attempt to recursively get a lock and panic. It will print the cpu id, the lock address and contents. This should put us in pretty good shape to deal with any simple_lock deadlocks that I have introduced in the last week or so. It is ON by default in the new smptests.h file. If you hit this panic do a "trace" and "show registers" command and post the data. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD