From owner-freebsd-current Wed Jun 9 17:51:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id E102C15455 for ; Wed, 9 Jun 1999 17:51:55 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id UAA07384; Wed, 9 Jun 1999 20:51:54 -0400 (EDT) (envelope-from luoqi) Date: Wed, 9 Jun 1999 20:51:54 -0400 (EDT) From: Luoqi Chen Message-Id: <199906100051.UAA07384@lor.watermarkgroup.com> To: jbryant@unix.tfs.net Subject: Re: 4-way SMP broken ? Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Do you mean messages like these? > > FreeBSD/SMP: Multiprocessor motherboard > > cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 > > cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 > > io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec00000 > > By the time you see these messages, all cpus should have been booted up > > successfully, any crash immediately follows is not likely to be SMP related. > > It's helpful to pinpoint the crash if you could include the last few lines > > from a verbose boot. > > interesting. then why the delay in bringing up the AP? Note in the > dmesg output below, that the AP only comes up during th SCSI delay. I > have also added other comments to the following output. > The APs are up, but not fully initialized. Initializations that require holding of the giant lock are done near the end of the booting process, until then the APs are just spinning around the lock. Tor Egge tried once to move to an earlier time, but it didn't work well on some motherboards. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message