From owner-freebsd-smp Sat Aug 30 11:40:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA26916 for smp-outgoing; Sat, 30 Aug 1997 11:06:41 -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 LAA26911 for ; Sat, 30 Aug 1997 11:06:38 -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 MAA16417; Sat, 30 Aug 1997 12:03:17 -0600 (MDT) Message-Id: <199708301803.MAA16417@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 12:03:16 -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 ? It would be really nice, any one with ideas along that line please speak up (or go for it!). One idea I had was to use the local timer as a watchdog. set it for 10 seconds going into a simplelock. if your not out by then if fires a high priority interrupt that causes a panic. the SMP disable_intr() would have to be reworked a little, and there are probably other areas like ISRs that would ignore it, but it should help some of the time. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD