From owner-freebsd-scsi  Tue Apr 22 19:59:14 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA28852
          for freebsd-scsi-outgoing; Tue, 22 Apr 1997 19:59:14 -0700 (PDT)
Received: from main.gbdata.com (USR2-1.detnet.com [207.113.12.44])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28041;
          Tue, 22 Apr 1997 19:48:00 -0700 (PDT)
Received: (from gclarkii@localhost)
	by main.gbdata.com (8.8.5/8.8.5) id VAA02748;
	Tue, 22 Apr 1997 21:47:54 -0500 (CDT)
From: Gary Clark II <gclarkii@main.gbdata.com>
Message-Id: <199704230247.VAA02748@main.gbdata.com>
Subject: Re: Freezes/Reboots with -current ahc driver
To: smp@csn.net (Steve Passe)
Date: Tue, 22 Apr 1997 21:47:54 -0500 (CDT)
Cc: kmitch@weenix.guru.org, scsi@freebsd.org, smp@freebsd.org
In-Reply-To: <199704230232.UAA20177@Ilsa.StevesCafe.com> from Steve Passe at "Apr 22, 97 08:32:24 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Steve Passe wrote:
> Hi,
> 
> > > > I just upgraded my 2.2-STABLE system (from around April 1) to 3.0-current
> > > > (as of April 21) to gain use of the SMP stuff.
> > > > 
> > > > Now, I am experiancing system freezes and reboots during the
> > > > nightly backup.  No error messages ever appear from what I can tell.
> > > > ...
> > 
> > I don't belive that this is a SMP problem.  I'm running the same current
> > here and am seeing random reboots (not panics) 1-4 times a day.
> > I'm running on a 486DX4-100, 24MB and NO SMP.
> 
Ohhhh.....  Then there are other problems in the latest current.  I may
have to downgrade to what I was running then (pre-lite snap).
I can't run DDB here due to the fact that I have a SUN 19" monitor and no
way to see regular VGA output...:(

> For the record, after DDB was added to the SMP kernel we demonstrated that the
> problem in this case is SMP, specifically the apicIPI() related deadlock.
> So this proves that my cheap bandaid doesn't solve the problem...
> I've got my thinking cap on, but for now I've suggested the user switch to
> a NON APIC_IO kernel.
> 
> --
> Steve Passe	| powered by
> smp@csn.net	|            Symmetric MultiProcessor FreeBSD
> 
Gary


-- 
Gary Clark II   (N5VMF) |    I speak only for myself and "maybe" my company 
gclarkii@GBData.COM     |          Member of the FreeBSD Doc Team 
  Providing Internet and ISP startups - http://WWW.GBData.com for information
       FreeBSD FAQ at ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/FAQ.latin1