From owner-freebsd-scsi Fri Feb 4 6:20:22 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by builder.freebsd.org (Postfix) with ESMTP id 7E478413B; Fri, 4 Feb 2000 06:20:14 -0800 (PST) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id HAA06152; Fri, 4 Feb 2000 07:20:54 -0700 (MST) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <200002041420.HAA06152@caspian.plutotech.com> X-Mailer: exmh version 2.1.0 09/18/1999 To: toyonaga@msd.ts.fujitsu.co.jp Cc: "Justin T. Gibbs" , scsi@FreeBSD.org, toyonaga@rr.iij4u.or.jp Subject: Re: First attempt with new adw driver In-reply-to: Your message of "Fri, 04 Feb 2000 20:29:03 +0900." <200002041129.UAA86251@mail.msd.ts.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Feb 2000 07:20:54 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >I have DDB option in kernel but at this moment no crash dump is extracted >since"panic" ddb command has no effect (because of limited RAM/swap?, >dumpdev is set to /dev/ad0s1b). Even without the dump, you should be able to get a stack trace and the program counter at the time the panic occurred. This will be very important in determining why the system broke. For instance, it might be interested to see if you can reproduce the panic without softupdates and/or ccd. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message