From owner-freebsd-current  Sun Aug 10 03:07:55 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id DAA14487
          for current-outgoing; Sun, 10 Aug 1997 03:07:55 -0700 (PDT)
Received: from groa.uct.ac.za (groa.uct.ac.za [137.158.128.7])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA14470;
          Sun, 10 Aug 1997 03:07:45 -0700 (PDT)
Received: from rv by groa.uct.ac.za with local (Exim 1.653 #1)
	id 0wxUu1-0005X3-00; Sun, 10 Aug 1997 12:07:13 +0200
Subject: Re: scsi time-out & lockup under smp
To: jwd@unx.sas.com
Date: Sun, 10 Aug 1997 12:07:12 +0200 (SAT)
Cc: freebsd-current@freebsd.org, freebsd-smp@freebsd.org
In-Reply-To: <199708091618.KAA06802@Ilsa.StevesCafe.com> from "Steve Passe" at Aug 9, 97 10:18:00 am
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Message-Id: <E0wxUu1-0005X3-00@groa.uct.ac.za>
From: Russell Vincent <rv@groa.uct.ac.za>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Steve Passe wrote:
> Has anyone tried undefining PEND_INTS to fix this yet?

Steve has gone off to sleep, so I thought I would get people
caught up on the status of this.

Last night I ran a machine with the latest kernel (the one with
Steve's latest '3 locks' fix) and PEND_INTS undefined. The machine
stayed up for 10 hours while doing its usual work of web
cache and newsfeeds along with a make world. That seems to
have fixed the problem.

I have now defined PEND_INTS again and am running more tests.
Nothing definite yet, but after a good hammering (_lots_ of
CPU and disk activity) the machine is still running fine.
I will know more within the next 12 hours, but it looks
like the '3 locks' fix has solved the problem.

Many thanks to Steve for helping out.

 -Russell