From owner-freebsd-current Fri Jan 22 20:32:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11256 for freebsd-current-outgoing; Fri, 22 Jan 1999 20:32:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11250 for ; Fri, 22 Jan 1999 20:32:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id UAA58243; Fri, 22 Jan 1999 20:30:28 -0800 (PST) (envelope-from dillon) Date: Fri, 22 Jan 1999 20:30:28 -0800 (PST) From: Matthew Dillon Message-Id: <199901230430.UAA58243@apollo.backplane.com> To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: panic: found dirty cache page 0xf046f1c0 References: <199901230400.MAA00394@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Peter Wemm wrote: :> Dual p5-90 w/ 48M ram, doing a major cvs update/merge (which mostly got :> lost): :> :> panic: found dirty cache page 0xf046f1c0 :... : :This is possibly a false alarm.. Something wierd was happening. I cleaned :out the kernel and reconfigured with NFS static (it was being loaded) and :it seems to boot OK. At least, I'm not getting console corruption (random :baud rate changes) and the SMP mutex being broken and both cpu's entering :the kernel at once..... I think I'll blame it on the 15 hour electrical :storm. :-] : :Cheers, :-Peter An old nfs module would almost certainly not work with the new kernel without at least a recompile. I'd definitely recommend keeping the major modules compiled in rather then dynamically loaded, just on principle. In fact, in all my time at BEST and all my time playing with FreeBSD, I have *never* used any dynamic module except for the linux compatibility thingy, and even that was only a fluke. If you can compile it in, compile it in. But, keep a watch on it. I didn't have an SMP box to test the new VM stuff on so it's possible there's something going on there. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message