Date: Wed, 9 Jun 2004 10:25:03 -0400 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-current@FreeBSD.org Cc: freebsd-amd64@FreeBSD.org Subject: Re: continuing troubles with AMD64 Message-ID: <200406091025.03741.jhb@FreeBSD.org> In-Reply-To: <200406081617.29485@misha-mx.virtual-estates.net> References: <200406081617.29485@misha-mx.virtual-estates.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 08 June 2004 04:17 pm, Mikhail Teterin wrote: > The good part: the Mar 1st -current kernel works fine. > > The bad: > 1) Any newer kernels don't see the system drive, presumably, > abecause ttempts to allocate IRQs for the all of the > aata-controllers fail. > > 2) Yesterday's kernel panics with: > > madt_probe_cpus_handler: CPU ID 129 too high > > Indeed, 129 is greater than NLAPICS, which is 32, but the > Mar 1st kernel works. 129 is not a valid local APIC ID. (x86 only supports APIC IDs from 0 to 15). Do you have acpidump -t output available? (Namely, the APIC table). -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406091025.03741.jhb>