From owner-freebsd-current Mon Feb 5 14:52:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id BBA0237B698 for ; Mon, 5 Feb 2001 14:52:13 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f15Mp9394918; Mon, 5 Feb 2001 14:51:10 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010204220704.C91447@rfx-216-196-73-168.users.reflex> Date: Mon, 05 Feb 2001 14:51:59 -0800 (PST) From: John Baldwin To: "Crist J. Clark" Subject: RE: Kernel Panic from Yesterday's CVSup Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Feb-01 Crist J. Clark wrote: > I don't recall reports of trouble with recent CURRENT, but my CVSup > from yesterday afternoon is panicing. Before I try too debug this, has > anyone been getting these or knows what I might be missing? > > Boot messages and the panic info are attached. Could you please turn on DDB, WITNESS, and INVARIANTS in your kernel and see if you can reproduce this? Also, compile the kernel with debug symbols. Then type 'trace' at the db> prompt when it does to get a backtrace of where it blew up. Thanks. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message