Date: Tue, 15 Feb 2000 08:39:49 +1030 From: "Martin Minkus" <diskiller@cnbinc.com> To: <freebsd-smp@freebsd.org> Subject: Re: 4.0 SMP Problem? Message-ID: <002d01bf7738$362c2580$14b626cb@bender.cnbinc.com>
next in thread | raw e-mail | index | archive | help
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 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Diso-8859-1" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>> On Mon, 14 Feb 2000, Martin Minkus = wrote:<BR>><BR>> [...]><BR>> > SMP alone, and softupdate = alone,=20 and everything else, is broken on 4.0.<BR>> > I cvsup'd a few days = ago, so=20 it was a recent current.<BR>><BR>> I don't know about softupdates, = which I=20 do not use. SMP alone is *not*<BR>> broken on 4.0. It never was, not = even=20 during the recent (x)install<BR>> and lib problems.<BR><BR>When i = boot, it=20 says "Broken MP Table Detected"<BR>Then it uses a work = around.<BR><BR>(dmesg=20 output, 3.4-Stable)<BR><BR>Intel Pentium detected, installing workaround = for=20 F00F bug<BR>APIC_IO: Testing 8254 interrupt delivery<BR>APIC_IO: Broken = MP table=20 detected: 8254 is not connected to IO APIC int pin<BR>2<BR>APIC_IO: = routing 8254=20 via 8259 on pin 0<BR>changing root device to wd0s1a<BR>SMP: AP CPU #1=20 Launched!<BR><BR>Perhaps that work around is broken on 4.0, which is = what is=20 causing me the<BR>problems. I have NEVER had a problem with SMP on = 3.x.<BR><BR>I=20 built a very simple 4.0 kernel with just the bare essentials. (ie, = ad<BR>driver,=20 and SMP) and it still panics and spontaneously = reboots.<BR><BR></FONT></DIV> <DIV><FONT face=3DArial size=3D2>--<BR><A=20 href=3D"mailto:diskiller@cnbinc.com">diskiller@cnbinc.com</A><BR>Linux/Fr= eeBSD=20 hacker</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>Please use PGP: <A=20 href=3D"http://www.diskiller.net/pgp.html">http://www.diskiller.net/pgp.h= tml</A></FONT></DIV></BODY></HTML> ------=_NextPart_000_002A_01BF7790.3898D7C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002d01bf7738$362c2580$14b626cb>