From owner-freebsd-scsi Mon Dec 4 19:59:59 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 4 19:59:57 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 90CDF37B401 for ; Mon, 4 Dec 2000 19:59:56 -0800 (PST) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA18092; Mon, 4 Dec 2000 22:59:39 -0500 (EST) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA14806; Mon, 4 Dec 2000 23:00:19 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA14798; Mon, 4 Dec 2000 23:00:19 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Mon, 4 Dec 2000 23:00:19 -0500 (EST) From: Kenneth Wayne Culver To: Greg Lehey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: kernel panics in 4.2 In-Reply-To: <20001205121028.D84692@echunga.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've been ignoring these messages so far, since you don't include any > information about the panics. Take a dump with a kernel with symbols, > and things might look different. I'm working on getting it to crash again. It appears that with DDB in the kernel, it's reluctant to panic. Anyway, I wanted to make sure that I didn't do something wrong, so I sent this message so that somebody might be able to tell me if I made any mistakes. It appears that I made no mistakes... so I'll have a dump, and a backtrace and anything else that is needed for debugging as soon as I can cause it to crash again. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message