From owner-freebsd-questions@FreeBSD.ORG Thu Apr 19 10:37:12 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6914D16A408 for ; Thu, 19 Apr 2007 10:37:12 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (mail.computinginnovations.com [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id 0E86A13C44B for ; Thu, 19 Apr 2007 10:37:11 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.13.8/8.12.11) with ESMTP id l3JAaJ45072149; Thu, 19 Apr 2007 05:36:22 -0500 (CDT) Message-Id: <6.0.0.22.2.20070419053028.02558e98@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Thu, 19 Apr 2007 05:35:34 -0500 To: "Murray Taylor" , "FreeBSD Mailing List" From: Derek Ragona In-Reply-To: <04E232FDCD9FBE43857F7066CAD3C0F12DF19B@svmailmel.bytecraft .internal> References: <04E232FDCD9FBE43857F7066CAD3C0F12DF19B@svmailmel.bytecraft.internal> Mime-Version: 1.0 X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: FW: IBM / FreeBSD - Install Update - Seems to be ACPI X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2007 10:37:12 -0000 At 11:32 PM 4/18/2007, Murray Taylor wrote: >In our initial posts, we stated that we seemed to be having issues >getting the machine to boot with the 4 processors, so to bypass this we >disabled ACPI on boot. This allowed us to get past the CPU error and >continue to boot. However down the track we noticed things like the >ethernet adapater not getting picked up, and the big problem - none of >the disks getting recognised. > >We have since tried a few things, one of which was removing all but one >of the CPU's. If we do this, and boot with ACPI enabled, all is totally >fine. All disks are found, and I receive no CPU panic error. > >So it appears to me that by disabling ACPI in an attempt to bypass the >QUAD CPU problem, we are causing another issue behind the scenes. > >The root of the problem now appears to be, that if we have anything over >1 CPU, directly after the kernel is loaded (when booting from the CD), >we receive the error message "panic: madt_probe_cpus_handler: CPU ID 38 >Too High". The moment a second CPU to the machine....it bombs out. Have you tried booting a custom kernel with SMP enabled from the hard drives? You might try that and install another CPU and see how the system reacts. Are these CPU's hyperthreaded too? Or just single core CPU's? I have had problems installing with some systems if hyperthreading was enabled. Post installation with a custom SMP enabled kernel built I could turn hyperthreading on or off and the system booted and ran fine. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support.