From owner-freebsd-current@FreeBSD.ORG Wed Jun 9 14:24:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86A9916A4CE for ; Wed, 9 Jun 2004 14:24:22 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B81943D2F for ; Wed, 9 Jun 2004 14:24:22 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6370 invoked from network); 9 Jun 2004 14:24:19 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 9 Jun 2004 14:24:19 -0000 Received: from 10.50.41.233 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i59EODVb018208; Wed, 9 Jun 2004 10:24:16 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Wed, 9 Jun 2004 10:25:03 -0400 User-Agent: KMail/1.6 References: <200406081617.29485@misha-mx.virtual-estates.net> In-Reply-To: <200406081617.29485@misha-mx.virtual-estates.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406091025.03741.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Mikhail Teterin cc: SCHA cc: freebsd-amd64@FreeBSD.org Subject: Re: continuing troubles with AMD64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jun 2004 14:24:22 -0000 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 <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org