From owner-freebsd-smp Thu Jun 8 11: 5: 2 2000 Delivered-To: freebsd-smp@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 318EE37C09F for ; Thu, 8 Jun 2000 11:04:54 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id NAA46864 for freebsd-smp@freebsd.org; Thu, 8 Jun 2000 13:05:25 -0500 (CDT) From: Joe Greco Message-Id: <200006081805.NAA46864@aurora.sol.net> Subject: Re: HP Vectra XU To: freebsd-smp@freebsd.org Date: Thu, 8 Jun 2000 13:05:25 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (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 > I have a HP Vectra XU, Dual PPro 200, 256Mb RAM, Internal Adaptec, > that ran quite happily on a 4.0-CURRENT from mid January if I remember > rightly. Upgraded to STABLE and it died on boot. Boots single processor > OK, dual it wont. Blanked it, and put 4.0-RELEASE on there, same again. > Single OK, Dual I get: > > (snip) > avail memory = 257159168 (251132K bytes) > Programming 16 pins in IOAPIC #0 > IOAPIC #0 intpin 2 -> irq 0 > > Then stops. Any ideas anyone? It's something HP specific. Last time I tackled this, back in the earlier 3.x releases, we tracked it down to the second CPU not starting. They said something was wrong with my hardware, which seemed odd since it booted 3.0R fine. One thing I also noticed was that it was actually much more likely to start if powered up, rather than reset/rebooted. -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message