From owner-freebsd-smp Fri Sep 27 22:38:31 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA09224 for smp-outgoing; Fri, 27 Sep 1996 22:38:31 -0700 (PDT) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA09163 for ; Fri, 27 Sep 1996 22:38:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id XAA07782; Fri, 27 Sep 1996 23:38:16 -0600 Message-Id: <199609280538.XAA07782@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: "J.M. Chuang" cc: FreeBSD-smp@freefall.freebsd.org Subject: Re: Tyan S1662 Titan Pro In-reply-to: Your message of "Sat, 28 Sep 1996 00:04:15 -0300." <199609280304.AAA22972@bluenose.na.tuns.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Sep 1996 23:38:15 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, >The system was up for about an hour. The file systems were gradually >messed up and the shared library libc.so.3.0 was damaged. Eventually, >the system dies. There were a lots of coredumps and segmentation faults >from running utilities such as perl, tcsh,... how long/well does it run the standard (non SMP) kernel? >Processor > apic ID: 1, version: 17 > CPU is usable, CPU is the bootstrap processor >Processor > apic ID: 0, version: 17 > CPU is usable, CPU is NOT the bootstrap processor here we have reverse ordering of the APIC IDs so the changes in test2 (or manually changing constants in several places) are definately necessary. > local APIC address: 0xfee00000 > I/O APIC > apic ID: 2, version: 17 > APIC is usable > apic address: 0xfec00000 both APIC addresses are standard, so that doesn't come into play. the real question is whether my changes are causing you problems. can you run this system for a while with the GENERIC kernel and see what happens? also, carefully look thru your BIOS to see what cache options you have. on another system we had to change from "write-back' to 'write-thru' you might try running with cache turned off to see if that stabalizes the system. >sysctl -w kern_smp.active=2 when you do this do you see a message about "SECOND CPU LAUNCHED" on the console? -- Steve Passe | powered by smp@csn.net | FreeBSD