Date: Mon, 23 Apr 2007 14:29:57 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-hackers@freebsd.org Cc: Murray Taylor <MTaylor@bytecraft.com.au> Subject: Re: FW: IBM / FreeBSD - Install Update - Seems to be ACPI Message-ID: <200704231429.58036.jhb@freebsd.org> In-Reply-To: <04E232FDCD9FBE43857F7066CAD3C0F12DF19D@svmailmel.bytecraft.internal> References: <04E232FDCD9FBE43857F7066CAD3C0F12DF19D@svmailmel.bytecraft.internal>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 19 April 2007 12:33:08 am 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. Yes, ACPI enumerates Host-PCI bridges, and trying to enumerate them w/o ACPI is a bit of a guessing game. > 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. You can use 'set hint.apic.0.disabled=1' for now to keep ACPI and just disable SMP for now. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704231429.58036.jhb>