From owner-freebsd-current Sat Aug 21 19:37:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6C3C714FD9 for ; Sat, 21 Aug 1999 19:37:13 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA75666; Sat, 21 Aug 1999 19:35:32 -0700 (PDT) (envelope-from dillon) Date: Sat, 21 Aug 1999 19:35:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199908220235.TAA75666@apollo.backplane.com> To: Luoqi Chen Cc: freebsd-current@FreeBSD.ORG, roberto@keltia.freenix.fr Subject: Re: Panic with NFSv3 on a CURRENT/SMP system References: <199908220230.WAA08616@lor.watermarkgroup.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> I'm generating a core dump. Please note that as tara is my test machine, I use :> "INVARIANT" & "INVARIANT_SUPPORT". Should I remove them ? :> :> It seems that from my reading of the code, the panic would not had happened :> without INVARIANT. :> :It is these options that caused the panic, you either remove them from the :kernel proper, or compile the kld with them. : :-lq No mix and match, eh? I don't use kld's at all any more - at least not on the development kernel (CURRENT). Too many changes to system structures almost guarentee crashes when kld's are used. I run all my kernels with INVARIANTS and INVARIANT_SUPPORT, and all modules are built into the kernel. That works for me. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message