From owner-freebsd-scsi Thu Oct 1 08:58:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12270 for freebsd-scsi-outgoing; Thu, 1 Oct 1998 08:58:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12248 for ; Thu, 1 Oct 1998 08:58:10 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id JAA27451; Thu, 1 Oct 1998 09:51:23 -0600 (MDT) Date: Thu, 1 Oct 1998 09:51:23 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199810011551.JAA27451@narnia.plutotech.com> To: shimon@simon-shapiro.org cc: scsi@FreeBSD.ORG Subject: Re: DPT_RESET - Do We Still Need It? Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > The problem manifested itself by shutting the kernel down (including calls > to all registered at_shutdown functions), then proceeding to do massive I/O > to the (already shutdown) disk subsystem. This was during kernel panics > that resulted in kernel dumps. I corrected this by adding the SHUTDOWN_FINAL at_shutdown state. This hook class is called only after a system dump, if any, is performed. I needed this for the adaptec originally, but the CAM dpt driver uses it now too. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message