From owner-freebsd-smp Sun Sep 29 17:06:31 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA02877 for smp-outgoing; Sun, 29 Sep 1996 17:06:31 -0700 (PDT) Received: from uruk.org (uruk.org [198.145.95.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA02823 for ; Sun, 29 Sep 1996 17:06:26 -0700 (PDT) From: erich@uruk.org Received: from loopback (loopback [127.0.0.1]) by uruk.org (8.7.4/8.7.3) with SMTP id RAA28992 for ; Sun, 29 Sep 1996 17:07:53 -0700 (PDT) Message-Id: <199609300007.RAA28992@uruk.org> X-Authentication-Warning: uruk.org: Host loopback [127.0.0.1] didn't use HELO protocol To: freebsd-smp@freebsd.org Subject: Re: Tyan S1562D Tomcat2 In-reply-to: Your message of "Mon, 30 Sep 1996 07:44:58 +0800." <199609292344.HAA04870@spinner.DIALix.COM> Date: Sun, 29 Sep 1996 17:07:52 -0700 Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [I didn't copy this to this list last time I sent it] Peter Wemm writes: > erich@uruk.org wrote: > > > I have 64MB and see something like this problem quite a bit once I turn > > on the second CPU (well, if I'm doing something big like a GCC compile). > > I'm not claiming it is exactly the same problem. > > > > Interestingly enough, it always seems particular problems are caused by > > "ln" (it gets memory core dumps very often) and GCC's "enquire" simply > > locks the machine solid. > > Hmm. I have some old 386 motherboards that lock solid on enquire, I seem > to recall it was dismissed as "FERR->INT 13 linkage foulup".. My suspicion has been a floating-point error problem. > Perhaps enquire is triggering a floating point IRQ-13 on the second cpu > which is currently not being handled? The second cpu does not get any > IRQ's at all at present, and if IRQ-13 is being generated directly within > the cpu then that might explain it. Yikes!!! This is definitely a major problem. With the APIC hardware, the I/O APIC is handling PIC interrupts only. Anything that is directly handled via the CPU or local APIC will of course generate interrupts on the CPU in question. -- Erich Stefan Boleyn \_ E-mail (preferred): Mad Genius wanna-be, CyberMuffin \__ (finger me for other stats) Web: http://www.uruk.org/~erich/ Motto: "I'll live forever or die trying" -- Erich Stefan Boleyn \_ E-mail (preferred): Mad Genius wanna-be, CyberMuffin \__ (finger me for other stats) Web: http://www.uruk.org/~erich/ Motto: "I'll live forever or die trying"