Date: Tue, 24 Aug 2004 21:54:36 +0400 From: Roman Kurakin <rik@cronyx.ru> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: Boot code broken in some way in recent current (Was: Panic at boot) Message-ID: <412B80DC.5060404@cronyx.ru> In-Reply-To: <200408231327.11303.jhb@FreeBSD.org> References: <41261D1B.5000003@cronyx.ru> <412640B5.9090104@cronyx.ru> <20040821133304.D84878@carver.gumbysoft.com> <200408231327.11303.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?412B80DC.5060404>