Re: Boot code broken in some way in recent current (Was: Panic at boot)

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 08/23/04

  • Next message: John Baldwin: "Re: net80211+atheros changes" 
    To: freebsd-current@FreeBSD.org
Date: Mon, 23 Aug 2004 13:27:11 -0400

    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. 

    -- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
  • Next message: John Baldwin: "Re: net80211+atheros changes"

    Relevant Pages