From owner-freebsd-smp Mon Feb 14 14:15:49 2000 Delivered-To: freebsd-smp@freebsd.org Received: from milhouse.cnbinc.com (martin2.lnk.telstra.net [139.130.137.91]) by builder.freebsd.org (Postfix) with ESMTP id CE7B64CF3 for ; Mon, 14 Feb 2000 14:12:22 -0800 (PST) Received: from bender (bender.cnbinc.com [203.38.182.20]) by milhouse.cnbinc.com (8.9.3/8.9.3) with SMTP id IAA31174 for ; Tue, 15 Feb 2000 08:39:59 +1030 (CST) (envelope-from diskiller@cnbinc.com) Message-ID: <002d01bf7738$362c2580$14b626cb@bender.cnbinc.com> From: "Martin Minkus" To: Subject: Re: 4.0 SMP Problem? Date: Tue, 15 Feb 2000 08:39:49 +1030 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002A_01BF7790.3898D7C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_002A_01BF7790.3898D7C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > On Mon, 14 Feb 2000, Martin Minkus wrote: > > [...]> > > SMP alone, and softupdate alone, and everything else, is broken on = 4.0. > > I cvsup'd a few days ago, so it was a recent current. > > I don't know about softupdates, which I do not use. SMP alone is *not* > broken on 4.0. It never was, not even during the recent (x)install > and lib problems. When i boot, it says "Broken MP Table Detected" Then it uses a work around. (dmesg output, 3.4-Stable) Intel Pentium detected, installing workaround for F00F bug APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int = pin 2 APIC_IO: routing 8254 via 8259 on pin 0 changing root device to wd0s1a SMP: AP CPU #1 Launched! Perhaps that work around is broken on 4.0, which is what is causing me = the problems. I have NEVER had a problem with SMP on 3.x. I built a very simple 4.0 kernel with just the bare essentials. (ie, ad driver, and SMP) and it still panics and spontaneously reboots. -- diskiller@cnbinc.com Linux/FreeBSD hacker Please use PGP: http://www.diskiller.net/pgp.html ------=_NextPart_000_002A_01BF7790.3898D7C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
> On Mon, 14 Feb 2000, Martin Minkus = wrote:
>
> [...]>
> > SMP alone, and softupdate = alone,=20 and everything else, is broken on 4.0.
> > I cvsup'd a few days = ago, so=20 it was a recent current.
>
> I don't know about softupdates, = which I=20 do not use. SMP alone is *not*
> broken on 4.0. It never was, not = even=20 during the recent (x)install
> and lib problems.

When i = boot, it=20 says "Broken MP Table Detected"
Then it uses a work = around.

(dmesg=20 output, 3.4-Stable)

Intel Pentium detected, installing workaround = for=20 F00F bug
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: Broken = MP table=20 detected: 8254 is not connected to IO APIC int pin
2
APIC_IO: = routing 8254=20 via 8259 on pin 0
changing root device to wd0s1a
SMP: AP CPU #1=20 Launched!

Perhaps that work around is broken on 4.0, which is = what is=20 causing me the
problems. I have NEVER had a problem with SMP on = 3.x.

I=20 built a very simple 4.0 kernel with just the bare essentials. (ie, = ad
driver,=20 and SMP) and it still panics and spontaneously = reboots.

--
diskiller@cnbinc.com
Linux/Fr= eeBSD=20 hacker
 
Please use PGP: http://www.diskiller.net/pgp.h= tml
------=_NextPart_000_002A_01BF7790.3898D7C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message