From owner-freebsd-smp Mon Apr 8 12:26:25 2002 Delivered-To: freebsd-smp@freebsd.org Received: from proton.hexanet.fr (proton.hexanet.fr [81.23.32.33]) by hub.freebsd.org (Postfix) with ESMTP id 8481637B416 for ; Mon, 8 Apr 2002 12:26:17 -0700 (PDT) Received: from hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.11.6/8.11.6) with SMTP id g38JQEJ04550; Mon, 8 Apr 2002 21:26:14 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Date: Mon, 8 Apr 2002 21:26:14 +0200 From: Christophe Prevotaux To: "Hartmann, O." Cc: freebsd-smp@freebsd.org Subject: Re: SMP with VIA chipset system lockups Message-Id: <20020408212614.21ae810f.c.prevotaux@hexanet.fr> In-Reply-To: <20020408170933.W17027-100000@klima.physik.uni-mainz.de> References: <20020408145322.2221d01f.c.prevotaux@hexanet.fr> <20020408170933.W17027-100000@klima.physik.uni-mainz.de> Organization: HEXANET Sarl X-Mailer: Sylpheed version 0.7.0 (GTK+ 1.2.10; i386--freebsd4.4) X-NCC-RegID: fr.hexanet Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Yes I just did the APM thing and everything seems to be working fine APM can be nice when starting a server with WOL and shutting down previously the other one with APM among other things On Mon, 8 Apr 2002 17:22:07 +0200 (CEST) "Hartmann, O." wrote: > On Mon, 8 Apr 2002, Christophe Prevotaux wrote: > > :>On Wed, 3 Apr 2002 21:50:55 +0000 > :>Josh Paetzel wrote: > :> > :>> On Tue, Apr 02, 2002 at 04:04:21PM +0200, Administrator IPA wrote: > :>> > On Wed, 27 Mar 2002, mikea wrote: > :>> > > :>> > > On Wed, Mar 27, 2002 at 06:45:49PM +0100, Christophe Prévotaux wrote: > :>> > > > I have a similar problem with a ASUS CUV4X-DLS > :>> > > > Dual CPU motherboard it is using VIA CHIPSET > :>> > > > as well and I have lockups , the system > :>> > > > freezes but I am still able to ping the machine > :>> > > > this is very strange , however nothing else works > :>> > > > > :>> > > > I have no problems running these machine in single > :>> > > > CPU mode but when I run SMP it does have freezing > :>> > > > problems > :> > :>> > > :>> > Hello out there. > :>> > > :>> > We have several SMP machines around here, one is a ASUS CUV4X-D based > :>> > system. This machine never have had any lockups as you described. > :>> > > :>> > Another system, a TYAN Thunder 2500/Slot 1 system with ServerWorks ServerSet III/HE > :>> > chipset had today its 'spontanous' reboot. > :>> > > :>> > With TYAN's mainboard I had a lot of trouble and it seems not to be only a issue of the > :>> > chipset itself! > :>> > TYAN Thunder and ASUS CUV4X-D have problems with IRQs, I guess, especially when using more > :>> > than one Intel EtherExpress (fxp) NIC. > :> > :> > :>Well I do have problems with the ASUS CUV4X-D and I am using the integrated > :>fxp ethernet interface , one DG500SX DLINK Gigabit Ethernet board and a PCA200E-SMF > :>ATM card in the same machine. Under Linux they worked absolutely flawlessly > :> > :>I am using > :> > :># To make an SMP kernel, the next two are needed > :>options SMP # Symmetric MultiProcessor Kernel > :>options APIC_IO # Symmetric (APIC) I/O > :> > :># The `hfa' driver provides support for the FORE Systems, Inc. > :># PCA-200E ATM PCI Adapter. > :># > :>options ATM_CORE #core ATM protocol family > :>options ATM_IP #IP over ATM support > :>options ATM_SIGPVC #SIGPVC signalling manager > :>options ATM_SPANS #SPANS signalling manager > :>options ATM_UNI #UNI signalling manager > :># > :> > :> > :>I also have APM enabled , but I am going to try with > :> > :>APM disable > :> > :>in my KERNCONF and see what happens > :> > Well, you found one possible solution for your own. I had especially > on the TYAN Thunder 2500 problems with APM enabled, but why use this > seneseless feature in an server environment? Our ASUS CUV4X-D had > also APM problems, I deselected it - and things were fine as before. > > Another issue is networking, NICs and IRQ with FreeBSD. I made the same > experiences like you with more than one NIC enabled and used in an > SMP system. While UP systems does obviously not have any problems with > more than one NIC (we have a bridging firewall with two NICs, fxp > type EtherExpress 10/100 Pro+, never saw any problem if the NICs are > placed in the right PCI slots on the ASUS A7V mobo), SMP machines does. > Especially those with newer chipsets. Our older SMP system, based > on two Intel PII/350 on a GigaByte and Bx440 chipset worked without > problems with two Intel NICs, but the TYAN Thunder 2500 did not. Our > ASUS does not have a built in NIC and it worked with FBSD 4.3 without > problems and in SMP mode using two NICs (activated and therefore up and > under heavy load!). > On Linux I never saw similar problems, but Linux has several other issues, > and especially performance impacts, which can be measured if both systems > are up and running stable. -- =============================================================== Christophe Prevotaux Email: c.prevotaux@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A.C Les Charmilles Tel: +33 (0)3 26 79 30 05 3 Allée Thierry Sabine Direct: +33 (0)3 26 79 08 02 BP202 Fax: +33 (0)3 26 79 30 06 51686 Reims Cedex 2 FRANCE HEXANET Network Operation Center =============================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message