From owner-freebsd-smp Mon Oct 2 16:26:52 2000 Delivered-To: freebsd-smp@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 2FBDB37B503 for ; Mon, 2 Oct 2000 16:26:50 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.1/8.11.1) id e92NWan00373 for freebsd-smp@freebsd.org; Mon, 2 Oct 2000 16:32:36 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200010022332.e92NWan00373@troutmask.apl.washington.edu> Subject: witness code status? To: freebsd-smp@freebsd.org Date: Mon, 2 Oct 2000 16:32:36 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What's the current status of the integration of BSDi's witness code? If I include "options WITNESS" in my kernel config file, I get an immediate panic at boot. My sources are from today (01 Oct 00), and the system is currently running a MP kernel (built without the witness code). PS: Yes, I know there will be periods of instability, but you (the SMP developers) can't possibly have all combinations of MP hardware. PPS: "options USER_LDT" is currently broken for MP kernels. -- Steve panic: mutex_enter: MTX_DEF on MTX_SPIN mutex random harvest\ @/usr/src/sys/modules/randomdev/../../dev/randomdev/yarrow.c:515 cpuid = 1; lapic.id = 00000000 Debugger("panic') CPU1 stopping CPUs: 0x00000001 stopped Stopped at Debugger+0x38: movb $0,in_Debugger.684 db>trace Debugger(c0277da1) panic witness_enter _mtx_enter random_harvest_internal write_random random_write ufs_vnoperatespec vn_write dofilewrite write syscall2 Xint0x80_syscall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message