From owner-freebsd-current@FreeBSD.ORG Tue Aug 24 17:59:05 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 D7D1516A4CE for ; Tue, 24 Aug 2004 17:59:05 +0000 (GMT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15D3C43D1F for ; Tue, 24 Aug 2004 17:59:05 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i7OHuBac053367 for freebsd-current@FreeBSD.org.checked; (8.12.8/vak/2.1) Tue, 24 Aug 2004 21:56:11 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru with ESMTP id i7OHrCcR053142; (8.12.8/vak/2.1) Tue, 24 Aug 2004 21:53:12 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <412B80DC.5060404@cronyx.ru> Date: Tue, 24 Aug 2004 21:54:36 +0400 From: Roman Kurakin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <41261D1B.5000003@cronyx.ru> <412640B5.9090104@cronyx.ru> <20040821133304.D84878@carver.gumbysoft.com> <200408231327.11303.jhb@FreeBSD.org> In-Reply-To: <200408231327.11303.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.org Subject: Re: Boot code broken in some way in recent current (Was: Panic at boot) 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: Tue, 24 Aug 2004 17:59:06 -0000 John Baldwin wrote: >On Saturday 21 August 2004 04:35 pm, Doug White wrote: > > >>On Fri, 20 Aug 2004, Roman Kurakin wrote: >> >> >>> At first I have two SMP system (Dual) one that boots normaly and one >>>that >>>goes to panic (the older pc). >>> I've setup finaly serial console to that system, so here is more >>>detailed output: >>> >>>OK boot -Dhv >>>/boot/kernel/acpi.ko text=0x406a8 data=0x1bc4+0x110c >>>syms=[0x4+0x72d0+0x4+0x9754] >>> >>> >>Have you tried booting without enabling ACPI? The ACPI tables seem to >>think you have two APs and no BSP. >> >> > >ACPI tables have no concept at all of a BSP. We infer the BSP by checking the >APIC ID of the CPU we are currently executing on when enumerating CPUs. > > > >>Also check the BIOS and set the MPTable version to 1.4, and upgrade the >>BIOS itself if there is an update. >> >> > >Since it worked before the recent loader change, I doubt this will make a >difference. More likely is that the code picked a bad memory address to >install the AP trampoline into for some reason. > > > I constantly see effect of moving this problem to other place if I debugging problematic one. rik