From owner-freebsd-stable Fri Aug 9 13:30:22 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0572837B400 for ; Fri, 9 Aug 2002 13:30:14 -0700 (PDT) Received: from sdf.lonestar.org (sdf.lonestar.org [207.202.214.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97F6A43E8A for ; Fri, 9 Aug 2002 13:30:13 -0700 (PDT) (envelope-from bmiddaug@sdf.lonestar.org) Received: from localhost (localhost [[UNIX: localhost]]) by sdf.lonestar.org (8.11.6/8.11.6) id g79KSaJ12382; Fri, 9 Aug 2002 20:28:36 GMT Date: Fri, 9 Aug 2002 20:28:36 +0000 (UTC) From: "Bob M." X-X-Sender: bmiddaug@sdf.lonestar.org To: Greg Panula Cc: Mario Pranjic , Subject: Re: SMP kernel problem In-Reply-To: <3D53B52D.E9C4BD91@dolaninformation.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been struggling with the same thing as Mario for like a week now. I was getting a very similar error message on an Epox bxbs board, dual pIII 450's same exact stepping, revision, etc. I configured the kernel with two I686_CPU entries instead of one figuring that might be it. I get errors on boot that look very similar (lines about APIC and int 2 and routing being interrupted from 8254.....) I also get the "SMP: AP CPU #1 Launched! message at the end. I recompiled the kernel with and without different cards and devices figuring I had an interrupt request conflict somewhere and the symmetrical I/O piece SMP was failing. There were two times out of about 20 that I was able to boot, and at the beginning of dmesg, it id'd my processor only once, as usual, but then it would list cpu0 and cpu1 and I wouldn't get the "SMP: AP CPU #1 Launched! I'm new to FreeBSD, but I figured if I get one boot mesg that looks like it detects and launches both cpu's at the beginning and one that says #1 CPU launched and never mentions cpu0 something ain't right. Why would I get that? I couldn't find a utility to bring up both processors in my installation, I didn't load any extra ports or packages, just user/bin and sbin. At the time I was looking for something under like ps or tlist or something like that to run to see what was going on. I've since blown away that installation and a few subsequent to that in my ignorant efforts to get a boot message that was apparently a goof. So that's a week of my life I'll never get back. Time for a beer. Thanks for the insight Greg. > Mario Pranjic wrote: > > > > Hi! > > > > I just got a new machine: Intel Server Board (SDS2) with 2 Pentium III > > CPU's on 1.13 GHz and 2 GB of RAM. > > > > So I've installed FreeBSD 4.6-RELEASE. > > > > I compiled kernel and with these options: > > machine i386 > > cpu I686_CPU > > options SMP # Symmetric MultiProcessor Kernel > > options APIC_IO # Symmetric (APIC) I/O > > > > MATH_EMULATE is not enabled. > > > > So, after reboot I got the following: > > CPU: Pentium III/Pentium III Xeon/Celeron (1127.91-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 > > > > Features=0x383fbff > > real memory = 2147483648 (2097152K bytes) > > avail memory = 2086330368 (2037432K bytes) > > > > ... > > > > APIC_IO: Testing 8254 interrupt delivery > > APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 > > intpin 2 > > APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 > > SMP: AP CPU #1 Launched! > > > > Seems I have some problems with SMP here. Anyone ever built SMP kernel to > > help me out? > > > > Naw, not really a problem. FreeBSD worked around it. "SMP: AP CPU #1 > Launched" means the second cpu has been started and is available to the > kernel. I encounter the same message when I install&run fbsd on > dual-cpu compaq machines. > > Unfortunately I don't know enough about APIC & company to explain why > 8245 should be connected to IOAPIC #0 intpin 2. A google search will > probably turn up something useful... just haven't been concerned enough > to research it. > > If you launch 'top', you should see CPU0 & CPU1 making appearances in > the STATE column. Easy way to confirm the kernel is seeing&using both > CPUs. > > Cheers, > Greg > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- bmiddaugNOSPAM@sdf.lonestar.org (please remove NOSPAM to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message