From owner-freebsd-scsi Tue Apr 22 12:37:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA11737 for freebsd-scsi-outgoing; Tue, 22 Apr 1997 12:37:57 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA11694; Tue, 22 Apr 1997 12:37:49 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id NAA17103; Tue, 22 Apr 1997 13:36:25 -0600 (MDT) Message-Id: <199704221936.NAA17103@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Keith Mitchell cc: gibbs@freebsd.org, smp@freebsd.org, scsi@freebsd.org Subject: Re: Freezes/Reboots with -current ahc driver In-reply-to: Your message of "Tue, 22 Apr 1997 15:05:51 EDT." <199704221905.PAA02398@weenix.guru.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Apr 1997 13:36:25 -0600 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > > what backup tool are you using when it crashes? > > I am using amanda 2.3.0.4 as the backup program which in turn uses > dump. None of the drives are mounted via NFS. > > I do have APIC_IO turned on. > > After I turned on the comconsole and ddb stuff I found out that it was > panicing (it looks like in the SMP stuff). The controller card is a > 3940UW. I did have toi patch the mp_machdep.c file for the PCI-PCI > bridge. > > The panic message is: > > apicIPI is stuck > panic(cpu#0): > > boot() called on cpu#0 > > What should I look for in DDB?? you are hitting the known "APIC_IO/heavy IO deadlock" problem. I'll think more about a solution. In the meantime you could try a non_APIC_IO kernel, that should solve the problem for now... -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD