From owner-freebsd-stable Mon Nov 29 12:51:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id EAA74153A5 for ; Mon, 29 Nov 1999 12:51:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA87236; Mon, 29 Nov 1999 12:51:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: David Gilbert Cc: stable@FreeBSD.ORG Subject: Re: vinum crash... how to proceed. In-reply-to: Your message of "Mon, 29 Nov 1999 15:42:47 EST." <14402.58695.141814.462651@trooper.velocet.net> Date: Mon, 29 Nov 1999 12:51:36 -0800 Message-ID: <87232.943908696@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok... on my 8 drive vinum system, I can cause a crash with a simple > "du" in a directory which is a copy of a normal usr filesystem. My > problem is that the kernel dump (as follows) is less-than-helpful. > Why is the 5th frame on the stack 0x0? How do I find out what caused > the trap() call? Look at frame 3 - it's quite obvious. Your crash was caused by a page fault, and you can consider it as analgous to a signal 10 or signal 11 in usermode. The driver went wild and attempted to use an address which wasn't kosher for something. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message