From owner-freebsd-current Mon Aug 19 12:48:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2F5E37B401 for ; Mon, 19 Aug 2002 12:48:48 -0700 (PDT) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F6F943E6E for ; Mon, 19 Aug 2002 12:48:47 -0700 (PDT) (envelope-from winter@jurai.net) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.5/8.12.2) with ESMTP id g7JJkkOw037922; Mon, 19 Aug 2002 15:46:46 -0400 (EDT) (envelope-from winter@jurai.net) Date: Mon, 19 Aug 2002 15:46:46 -0400 (EDT) From: "Matthew N. Dodd" To: Terry Lambert Cc: Freebsd-current@tcpipbitch.net, Mark Murray , Subject: Re: VM panic In-Reply-To: <3D6148FE.32C703BA@mindspring.com> Message-ID: <20020819154149.E788-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 19 Aug 2002, Terry Lambert wrote: > Yes. My ASUS Dual P90 machine has the same problem. I just thought it > was the MP Spec compliance level of the BIOS, and gave up running > -current. I guess it's not just me. 8-(. Its likely that we've got the same motherboard. Mine is a PCI/E-P54NP4 running 133s clocked at 120. I've also got a Tyan S1564D running a pair of 166MMX CPUs. It doesn't seem to be related to drivers or to the compiler. I haven't yet ruled out other parts of the toolchain. My last good build was 1 March 2002. Checking out a tree even as far back as mid-Feb doesn't yeild a good kernel though. I'm at a loss. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message