From owner-freebsd-questions@FreeBSD.ORG Fri Dec 26 16:32:41 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07C1116A4CE for ; Fri, 26 Dec 2003 16:32:41 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id E17E843D1F for ; Fri, 26 Dec 2003 16:32:39 -0800 (PST) (envelope-from fbsd-questions@trini0.org) Received: from hivemind.trini0.org (trini0.org[68.39.114.118]) by comcast.net (rwcrmhc13) with ESMTP id <200312270032390150066ur4e>; Sat, 27 Dec 2003 00:32:39 +0000 Received: from gladiator.trini0.org (gladiator.trini0.org [192.168.0.3]) by hivemind.trini0.org (Postfix) with ESMTP id 176332CC; Fri, 26 Dec 2003 19:32:39 -0500 (EST) From: Gerard Samuel To: Lowell Gilbert Date: Fri, 26 Dec 2003 19:32:38 -0500 User-Agent: KMail/1.5.4 References: <200312251313.48529.fbsd-questions@trini0.org> <200312261443.58940.fbsd-questions@trini0.org> <44wu8jiasc.fsf@be-well.ilk.org> In-Reply-To: <44wu8jiasc.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312261932.38765.fbsd-questions@trini0.org> cc: questions@freebsd.org Subject: Re: Moving from a single to dual CPU setup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Dec 2003 00:32:41 -0000 On Friday 26 December 2003 03:28 pm, Lowell Gilbert wrote: > Gerard Samuel writes: > > I did a bit of googling, and came up with an instance, that there may be > > a problem with FreeBSD 4.9/SMP/ACPI combo. > > Even though (well at least I believe) ACPI is off, Im having something > > similar to what this google search was saying. > > Maybe this weekend, Ill try backing down to 4.8 and see how she does > > there... > > The fact that it hangs at different places each time argues for a > hardware problem of some sort... The thought did cross my mind. At the time I was putting the box together, I was also mixing PC133 & PC100 memory to which I've come to realise that the board is picky about that (also found a reference via google that supports that notion). Currently Im only using the PC133 memory, and what Ill do is try booting up with the 2nd processor installed, and pay attention to see where it hangs (it was late the other night, and I don't remember if I was trying the 2nd cpu with the PC100 memory). Ill report back on my findings... Thanks