From owner-freebsd-smp Tue Jun 6 4: 1:53 2000 Delivered-To: freebsd-smp@freebsd.org Received: from internal.mail.demon.net (internal.mail.demon.net [193.195.224.3]) by hub.freebsd.org (Postfix) with ESMTP id 6A65337BFEC for ; Tue, 6 Jun 2000 04:01:26 -0700 (PDT) (envelope-from jguard@demon.net) Received: from gti.noc.demon.net (gti.noc.demon.net [195.11.55.101]) by internal.mail.demon.net with ESMTP id MAA21441; Tue, 6 Jun 2000 12:01:15 +0100 (BST) Received: (from jguard@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id MAA22553 for freebsd-smp@freebsd.org; Tue, 6 Jun 2000 12:01:09 +0100 (BST) Date: Tue, 6 Jun 2000 12:01:09 +0100 From: James Guard To: freebsd-smp@freebsd.org Subject: Re: Problem with SMP on Compaq DL360 Message-ID: <20000606120108.B29775@demon.net> References: <20000601164834.A25084@demon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000601164834.A25084@demon.net>; from jguard@demon.net on Thu, Jun 01, 2000 at 04:48:34PM +0100 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi again, I have found (with help from another reader of this list) the "Advanced Settings" in the Compaq setup. I have tried the APIC setting as Full-Table, Full-Table-mapped and disabled with no luck. We would really like :o) to get SMP working on these boxes and we are willing to assist in the development of support for this box. This could include our time, and making a box available via network for testing/deveopment etc. Is there anything else we can provide to help with this or sponsering the work required. Thanks again, James -- James Guard System Administrator Interactive Services Demon Internet, Demon@THUS http://www.games.demon.net/ http://www.demon.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 6 10: 6:45 2000 Delivered-To: freebsd-smp@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id D315737BA3A; Tue, 6 Jun 2000 10:06:25 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb43.imasy.or.jp [202.227.24.171]) by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.04) with ESMTP id e56H6GP29636; Wed, 7 Jun 2000 02:06:16 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: freebsd-current@freebsd.org Cc: freebsd-smp@freebsd.org, msmith@freebsd.org, jlemon@flugsvamp.com, sumitani@bd2.hnes.nec.co.jp Subject: SMP + APM = panic -> fixed! X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000607020615U.iwasaki@jp.FreeBSD.org> Date: Wed, 07 Jun 2000 02:06:15 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 27 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, We're having this problem for long time (from the old 4.0-CURRENT days), but Mr. SUMITANI discovered a bug and fixed it. The problem was that we got worng gdt pointer for the current cpu, then panic... The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! Please test this and I'll commit & MFC this if we have no problem with this fix. I love to have APM enabled SMP system with 4.1-RELEASE. Index: bios.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/bios.c,v retrieving revision 1.32 diff -u -r1.32 bios.c --- bios.c 2000/05/17 19:44:16 1.32 +++ bios.c 2000/06/06 16:47:46 @@ -262,7 +262,7 @@ union descriptor *p_gdt; #ifdef SMP - p_gdt = &gdt[cpuid]; + p_gdt = &gdt[cpuid * NGDT]; #else p_gdt = gdt; #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 6 10:14:11 2000 Delivered-To: freebsd-smp@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 1FF2C37B69B; Tue, 6 Jun 2000 10:13:59 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id MAA05724; Tue, 6 Jun 2000 12:18:43 -0500 (CDT) (envelope-from jlemon) Date: Tue, 6 Jun 2000 12:18:43 -0500 From: Jonathan Lemon To: Mitsuru IWASAKI Cc: freebsd-current@freebsd.org, freebsd-smp@freebsd.org, msmith@freebsd.org, jlemon@flugsvamp.com, sumitani@bd2.hnes.nec.co.jp Subject: Re: SMP + APM = panic -> fixed! Message-ID: <20000606121843.A4129@prism.flugsvamp.com> References: <20000607020615U.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000607020615U.iwasaki@jp.FreeBSD.org> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jun 07, 2000 at 02:06:15AM +0900, Mitsuru IWASAKI wrote: > > We're having this problem for long time (from the old 4.0-CURRENT > days), but Mr. SUMITANI discovered a bug and fixed it. > The problem was that we got worng gdt pointer for the current cpu, > then panic... > The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! > Please test this and I'll commit & MFC this if we have no problem with > this fix. I don't have an SMP + APM system around at the moment, but the fix does look correct to me, go ahead and commit it. Thanks for tracking this down! -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 6 10:41:50 2000 Delivered-To: freebsd-smp@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 7165337B567; Tue, 6 Jun 2000 10:41:45 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb43.imasy.or.jp [202.227.24.171]) by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.04) with ESMTP id e56HfgP40167; Wed, 7 Jun 2000 02:41:42 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: jlemon@flugsvamp.com Cc: iwasaki@jp.FreeBSD.org, freebsd-current@freebsd.org, freebsd-smp@freebsd.org, msmith@freebsd.org, sumitani@bd2.hnes.nec.co.jp Subject: Re: SMP + APM = panic -> fixed! In-Reply-To: <20000606121843.A4129@prism.flugsvamp.com> References: <20000607020615U.iwasaki@jp.FreeBSD.org> <20000606121843.A4129@prism.flugsvamp.com> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000607024141K.iwasaki@jp.FreeBSD.org> Date: Wed, 07 Jun 2000 02:41:41 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 11 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Please test this and I'll commit & MFC this if we have no problem with > > this fix. > > I don't have an SMP + APM system around at the moment, but the > fix does look correct to me, go ahead and commit it. Thanks for > tracking this down! Thank you for reviewing this. I'm going to comit tomorrow night (JST), then MFC on early next week if no problems are reported. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 6 20:22:56 2000 Delivered-To: freebsd-smp@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 9D29B37BBA1; Tue, 6 Jun 2000 20:22:43 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12zWPu-000Hru-00; Wed, 07 Jun 2000 10:22:06 +0700 Date: Wed, 7 Jun 2000 10:22:06 +0700 (ALMST) From: Boris Popov To: Mitsuru IWASAKI Cc: freebsd-current@freebsd.org, freebsd-smp@freebsd.org, msmith@freebsd.org, jlemon@flugsvamp.com, sumitani@bd2.hnes.nec.co.jp Subject: Re: SMP + APM = panic -> fixed! In-Reply-To: <20000607020615U.iwasaki@jp.FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 7 Jun 2000, Mitsuru IWASAKI wrote: > We're having this problem for long time (from the old 4.0-CURRENT > days), but Mr. SUMITANI discovered a bug and fixed it. > The problem was that we got worng gdt pointer for the current cpu, > then panic... > The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! Yes, this fixes panic and even 'halt -p' works as expected. 'zzz' command works too, but machine never come back from the suspend mode (looks like interrupt controller programmed incorrectly or something like this). -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 0:24:46 2000 Delivered-To: freebsd-smp@freebsd.org Received: from bart.esiee.fr (bart.esiee.fr [147.215.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 9EA2B37B6AE for ; Wed, 7 Jun 2000 00:24:43 -0700 (PDT) (envelope-from bonnetf@bart.esiee.fr) Received: (from bonnetf@localhost) by bart.esiee.fr (8.10.1/8.10.1) id e577Oee02380 for freebsd-smp@freebsd.org; Wed, 7 Jun 2000 09:24:40 +0200 (MEST) From: Frank Bonnet Message-Id: <200006070724.e577Oee02380@bart.esiee.fr> Subject: HP Netserver LC II anyone ? To: freebsd-smp@freebsd.org Date: Wed, 07 Jun 2000 9:24:40 MEST X-Mailer: Elm [revision: 212.5] Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I have a HP Netserver LC II that I plan to convert to a Bi Processor machine. Actually it runs in single proc mode but the motherboard is dual cpu ready. It is 300 Mhz pentium II based. Before jumping to dual proc I would like to have some feedback of eventual users with such configuration. any infos welcome. Thanks a lot. -- Frank Bonnet Groupe ESIEE Paris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 0:55:58 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 68DC637BEFB for ; Wed, 7 Jun 2000 00:55:48 -0700 (PDT) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id JAA05337; Wed, 7 Jun 2000 09:54:23 +0200 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id JAA01097; Wed, 7 Jun 2000 09:54:15 +0200 (MET DST) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C12568F7.002B8987 ; Wed, 7 Jun 2000 09:55:32 +0200 X-Lotus-FromDomain: ALCATEL To: Frank Bonnet Cc: freebsd-smp@FreeBSD.ORG Message-ID: Date: Wed, 7 Jun 2000 09:55:18 +0200 Subject: Re: HP Netserver LC II anyone ? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, SMP with FreeBSD runs very well (not as good as could be, due to the present design, but this is changing). One difficult point with many SMP motherboards is that you need two "compatible" processors to get SMP running. This usually means you have to buy your processors from the same fabrication batch. We have here investigated swapping Pentium-II-266 processors with a colleague to build an SMP machine from two UP machines, but we have not tried as the two processors have two different steppings. In summary : beware of getting a second processor (it may be easier to buy two new celerons and run them on "Slotkets") TfH Frank Bonnet on 07/06/2000 11:24:40 To: freebsd-smp@FreeBSD.ORG cc: (bcc: Thierry HERBELOT/FR/ALCATEL) Subject: HP Netserver LC II anyone ? Hi I have a HP Netserver LC II that I plan to convert to a Bi Processor machine. Actually it runs in single proc mode but the motherboard is dual cpu ready. It is 300 Mhz pentium II based. Before jumping to dual proc I would like to have some feedback of eventual users with such configuration. any infos welcome. Thanks a lot. -- Frank Bonnet Groupe ESIEE Paris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 4:46:11 2000 Delivered-To: freebsd-smp@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 3136337B657 for ; Wed, 7 Jun 2000 04:46:09 -0700 (PDT) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id HAA10915; Wed, 7 Jun 2000 07:53:32 -0400 (EDT) From: Brian Hechinger Message-Id: <200006071153.HAA10915@entropy.tmok.com> Subject: Re: HP Netserver LC II anyone ? In-Reply-To: from "Thierry.Herbelot@alcatel.fr" at "Jun 7, 2000 9:55:18 am" To: Thierry.Herbelot@alcatel.fr Date: Wed, 7 Jun 2000 07:53:32 -0400 (EDT) Cc: bonnetf@bart.esiee.fr, freebsd-smp@FreeBSD.ORG Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thierry.Herbelot@alcatel.fr drunkenly mumbled... > > One difficult point with many SMP motherboards is that you need two "compatible" > processors to get SMP running. This usually means you have to buy your processors > from the same fabrication batch. > > We have here investigated swapping Pentium-II-266 processors with a colleague > to build an SMP machine from two UP machines, but we have not tried as the two > processors have two different steppings. > > In summary : beware of getting a second processor (it may be easier to buy two > new celerons and run them on "Slotkets") or worst case, any cpu supplier should be willing to find you a CPU with a specific stepping if you ask. just mentioning this since i'm not a big fan of the sloket hokeyness. i know that certain intel motherboards don't work well with the slotkey adapters, so be careful. -brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 9:53:45 2000 Delivered-To: freebsd-smp@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id DC4CB37BB75; Wed, 7 Jun 2000 09:53:27 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn49.imasy.or.jp [202.227.24.241]) by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.04) with ESMTP id e57GrMP05053; Thu, 8 Jun 2000 01:53:22 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: bp@butya.kz Cc: iwasaki@jp.FreeBSD.org, freebsd-current@freebsd.org, freebsd-smp@freebsd.org, msmith@freebsd.org, jlemon@flugsvamp.com, sumitani@bd2.hnes.nec.co.jp Subject: Re: SMP + APM = panic -> fixed! In-Reply-To: References: <20000607020615U.iwasaki@jp.FreeBSD.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000608015319J.iwasaki@jp.FreeBSD.org> Date: Thu, 08 Jun 2000 01:53:19 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 17 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > On Wed, 7 Jun 2000, Mitsuru IWASAKI wrote: > > > We're having this problem for long time (from the old 4.0-CURRENT > > days), but Mr. SUMITANI discovered a bug and fixed it. > > The problem was that we got worng gdt pointer for the current cpu, > > then panic... > > The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! > > Yes, this fixes panic and even 'halt -p' works as expected. 'zzz' OK, I think many people will be happy with poweroff on SMP system, so I'd like to commit this first. Then I'll track it down and try to fix later in order to support suspend/resume SMP system. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 10:55:50 2000 Delivered-To: freebsd-smp@freebsd.org Received: from paperboy.sixforty.co.uk (paperboy.sixforty.co.uk [195.10.242.11]) by hub.freebsd.org (Postfix) with ESMTP id AB30F37B51D for ; Wed, 7 Jun 2000 10:55:46 -0700 (PDT) (envelope-from l.farr@epcdirect.co.uk) Received: from bka (daisy.sixforty.co.uk [195.10.242.200]) by paperboy.sixforty.co.uk (8.9.3/8.9.3) with SMTP id SAA65819 for ; Wed, 7 Jun 2000 18:55:44 +0100 (BST) (envelope-from l.farr@epcdirect.co.uk) Reply-To: From: "Lawrence Farr" To: Subject: HP Vectra XU Date: Wed, 7 Jun 2000 18:57:36 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a HP Vectra XU, Dual PPro 200, 256Mb RAM, Internal Adaptec, that ran quite happily on a 4.0-CURRENT from mid January if I remember rightly. Upgraded to STABLE and it died on boot. Boots single processor OK, dual it wont. Blanked it, and put 4.0-RELEASE on there, same again. Single OK, Dual I get: (snip) avail memory = 257159168 (251132K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Then stops. Any ideas anyone? Lawrence Farr EPC Direct Limited mailto:l.farr@epcdirect.co.uk T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 14:32:29 2000 Delivered-To: freebsd-smp@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 23FCF37B676 for ; Wed, 7 Jun 2000 14:31:54 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by home.dragondata.com (8.9.2/8.9.2) with ESMTP id QAA28428 for ; Wed, 7 Jun 2000 16:31:50 -0500 (CDT) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id QAA73380 for freebsd-smp@freebsd.org; Wed, 7 Jun 2000 16:31:45 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200006072131.QAA73380@celery.dragondata.com> Subject: Tyan Thunder 2400/i840 SMP no good To: freebsd-smp@freebsd.org Date: Wed, 7 Jun 2000 16:31:45 -0500 (CDT) X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to get SMP working on my Tyan Thunder 2400 motherboard. When I recompile the kernel with SMP support and reboot I get as far as 'Testing 8254 interrupt delivery' and it hangs. The console is still responsive, though. Any ideas? Here's my config and mptable: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-RELEASE #0: Mon Mar 20 22:50:22 GMT 2000 root@monster.cdrom.com:/usr/src/sys/compile/GENERIC Calibrating clock(s) ... TSC clock: 498255304 Hz, i8254 clock: 1192983 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium III/Pentium III Xeon (498.34-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387fbff real memory = 268435456 (262144K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00377000 - 0x0fff7fff, 264769536 bytes (64641 pages) avail memory = 256942080 (250920K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fdb60 bios32: Entry = 0xfdb70 (c00fdb70) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xdb91 pnpbios: Found PnP BIOS data at 0xc00f5910 pnpbios: Entry = f0000:53a4 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=1a218086) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=1a218086) pcib0: on motherboard found-> vendor=0x8086, dev=0x1a21, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base f8000000, size 26 found-> vendor=0x8086, dev=0x1a23, revid=0x01 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=4 secondarybus=4 found-> vendor=0x8086, dev=0x1a24, revid=0x01 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=3 secondarybus=2 found-> vendor=0x8086, dev=0x2418, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x2410, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x2411, revid=0x02 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000ffa0, size 4 found-> vendor=0x8086, dev=0x2412, revid=0x02 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=11 map[20]: type 1, range 32, base 0000ef80, size 5 found-> vendor=0x8086, dev=0x2413, revid=0x02 class=0c-05-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=b, irq=9 map[20]: type 1, range 32, base 0000efa0, size 4 found-> vendor=0x8086, dev=0x2415, revid=0x02 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=b, irq=9 map[10]: type 1, range 32, base 0000e800, size 8 map[14]: type 1, range 32, base 0000ef00, size 6 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x1002, dev=0x5246, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f0000000, size 26 map[14]: type 1, range 32, base 0000d800, size 8 map[18]: type 1, range 32, base ff9fc000, size 14 pci4: on pcib1 pci4: (vendor=0x1002, dev=0x5246) at 0.0 irq 11 pcib2: at device 2.0 on pci0 found-> vendor=0x8086, dev=0x1360, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=3 secondarybus=3 pci2: on pcib2 pcib3: at device 31.0 on pci2 found-> vendor=0x8086, dev=0x1161, revid=0x01 class=08-00-20, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base ff7df000, size 12 found-> vendor=0x1000, dev=0x000b, revid=0x05 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 0000b400, size 8 map[14]: type 1, range 64, base ff7e8000, size 10 map[1c]: type 1, range 64, base ff7e0000, size 13 found-> vendor=0x1000, dev=0x000b, revid=0x05 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=10 map[10]: type 1, range 32, base 0000b800, size 8 map[14]: type 1, range 64, base ff7f8000, size 10 map[1c]: type 1, range 64, base ff7f0000, size 13 pci3: on pcib3 pci3: (vendor=0x8086, dev=0x1161) at 0.0 sym0: <896> port 0xb400-0xb4ff mem 0xff7e0000-0xff7e1fff,0xff7e8000-0xff7e83ff irq 10 at device 9.0 on pci3 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: handling phase mismatch from SCRIPTS. sym0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/4e/a0/01/00/24 sym0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/4e/80/01/08/24 sym0: Delay (GEN=11): 256 msec, 34720 KHz sym0: Delay (GEN=11): 264 msec, 33667 KHz sym0: Delay (GEN=11): 265 msec, 33540 KHz sym0: enabling clock multiplier sym0: Downloading SCSI SCRIPTS. sym1: <896> port 0xb800-0xb8ff mem 0xff7f0000-0xff7f1fff,0xff7f8000-0xff7f83ff irq 10 at device 9.1 on pci3 sym1: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: handling phase mismatch from SCRIPTS. sym1: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/4e/a0/01/00/24 sym1: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/4e/80/01/08/24 using shared irq10. sym1: enabling clock multiplier sym1: Downloading SCSI SCRIPTS. pcib4: at device 30.0 on pci0 found-> vendor=0x8086, dev=0x1229, revid=0x08 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base ff6fe000, size 12 map[14]: type 1, range 32, base 0000af00, size 6 map[18]: type 1, range 32, base ff500000, size 20 pci1: on pcib4 fxp0: port 0xaf00-0xaf3f mem 0xff500000-0xff5fffff,0xff6fe000-0xff6fefff irq 11 at device 8.0 on pci1 fxp0: Ethernet address 00:e0:81:10:cd:19 fxp0: supplying EUI64: 00:e0:81:ff:fe:10:cd:19 bpf: fxp0 attached isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=03 status0=7f status1=50 ata0: mask=03 status0=7f status1=10 ata0: devices = 0x8 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0x0 ata1: probe allocation failed pci0: (vendor=0x8086, dev=0x2412) at 31.2 irq 11 pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 9 chip1: port 0xef00-0xef3f,0xe800-0xe8ff irq 9 at device 31.5 on pci0 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 devclass_alloc_unit: ata0 already exists, using next available unit number devclass_alloc_unit: ata1 already exists, using next available unit number isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ata3: iobase=0x0170 altiobase=0x0376 bmaddr=0x0000 ata3: mask=03 status0=00 status1=00 ata3: mask=03 status0=00 status1=00 ata3: devices = 0x0 ata3: probe allocation failed bt0: Failed Status Reg Test - 0 bt_isa_probe: Probe failed at 0x330 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x334 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x230 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x234 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x130 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x134 aha0: status reg test failed 0 aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic1: not probed (disabled) sio0: irq maps: 0x401 0x411 0x401 0x401 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x401 0x409 0x401 0x401 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0: parallel port found at 0x378 ppc0: ECP SPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached isa_probe_children: probing PnP devices BIOS Geometries: 0:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: sl0 attached bpf: ppp0 attached new masks: bio 40084040, tty 4003009a, net 4007089a bpf: lo0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: stf0 attached bpf: faith0 attached ata0-slave: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata0-slave: success setting up PIO4 mode on generic chip acd0: CDROM drive at ata0 as slave acd0: read 6890KB/s (6890KB/s), 120KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. sym0: enabling clock multiplier sym0: Downloading SCSI SCRIPTS. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. sym1: enabling clock multiplier sym1: Downloading SCSI SCRIPTS. Creating DISK da0 pass0 at sym0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number LP457945000019321NK3 pass0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled Mounting root from ufs:da0s1a da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number LP457945000019321NK3 da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da0s1: type 0xa5, start 63, end = 35551844, size 35551782 : OK start_init: trying /sbin/init fxp0: starting DAD for fe80:0001::02e0:81ff:fe10:cd19 fxp0: DAD complete for fe80:0001::02e0:81ff:fe10:cd19 - no duplicates found =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000fb160 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0x64 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f50e0 signature: 'PCMP' base table length: 364 version: 1.1 checksum: 0xa4 OEM ID: '_AMI_ ' Product ID: '840_CARMEL__' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 37 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 7 3 0x387fbff 1 0x11 AP, usable 6 7 3 0x387fbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 PCI 3 PCI 4 PCI 5 ISA -- I/O APICs: APIC ID Version State Address 2 0x20 usable 0xfec00000 3 0x20 usable 0xff7df000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 5 0 2 0 INT conforms conforms 5 1 2 1 INT conforms conforms 5 0 2 2 INT conforms conforms 5 3 2 3 INT conforms conforms 5 4 2 4 INT conforms conforms 5 5 2 5 INT conforms conforms 5 6 2 6 INT conforms conforms 5 7 2 7 INT active-hi edge 5 8 2 8 INT conforms conforms 5 9 2 9 INT conforms conforms 5 10 2 10 INT conforms conforms 5 11 2 11 INT conforms conforms 5 12 2 12 INT conforms conforms 5 13 2 13 INT conforms conforms 5 14 2 14 INT conforms conforms 5 15 2 15 INT active-lo level 0 31:A 2 16 INT active-lo level 4 0:A 2 16 INT active-lo level 0 31:D 2 19 INT active-lo level 0 31:B 2 17 INT active-lo level 0 31:B 2 17 INT active-lo level 1 8:A 2 16 SMI conforms conforms 5 0 2 23 INT active-lo level 3 9:A 3 8 INT active-lo level 3 9:B 3 9 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=6 # number of busses #options NAPIC=2 # number of IO APICs #options NINTR=25 # number of INTs =============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 16:54:42 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mass.cdrom.com (ether.cdrom.com [204.216.28.196]) by hub.freebsd.org (Postfix) with ESMTP id 9300437B56D for ; Wed, 7 Jun 2000 16:54:39 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA02054; Wed, 7 Jun 2000 16:57:46 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006072357.QAA02054@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kevin Day Cc: freebsd-smp@freebsd.org Subject: Re: Tyan Thunder 2400/i840 SMP no good In-reply-to: Your message of "Wed, 07 Jun 2000 16:31:45 CDT." <200006072131.QAA73380@celery.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Jun 2000 16:57:46 -0700 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I'm trying to get SMP working on my Tyan Thunder 2400 motherboard. When I > recompile the kernel with SMP support and reboot I get as far as 'Testing > 8254 interrupt delivery' and it hangs. The console is still responsive, > though. > > Any ideas? You need -stable or -current to run on the i840. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 18:21:14 2000 Delivered-To: freebsd-smp@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 2371B37B5AE; Wed, 7 Jun 2000 18:21:11 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by home.dragondata.com (8.9.2/8.9.2) with ESMTP id UAA05016; Wed, 7 Jun 2000 20:21:10 -0500 (CDT) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id UAA03661; Wed, 7 Jun 2000 20:21:09 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <200006080121.UAA03661@celery.dragondata.com> Subject: Re: Tyan Thunder 2400/i840 SMP no good To: msmith@freebsd.org (Mike Smith) Date: Wed, 7 Jun 2000 20:21:09 -0500 (CDT) Cc: toasty@dragondata.com (Kevin Day), freebsd-smp@freebsd.org In-Reply-To: <200006072357.QAA02054@mass.cdrom.com> from "Mike Smith" at Jun 07, 2000 04:57:46 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > > I'm trying to get SMP working on my Tyan Thunder 2400 motherboard. When I > > recompile the kernel with SMP support and reboot I get as far as 'Testing > > 8254 interrupt delivery' and it hangs. The console is still responsive, > > though. > > > > Any ideas? > > You need -stable or -current to run on the i840. > It wasn't until after I posted that I realized that I wasn't running -current. I am now, and I've gotten past the boot problems. However, I'm now seeing weird data corruption in RAM, spurious SIGBUS or SIGSEGV's, etc... I've replaced the RAM and CPUs and am still seeing it. I'm going to try a new ram vendor, as well as swapping motherboards next. Has anyone else experienced this on a similar system? I know the i840 is highly picky when it comes to SDRAM.... -- Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 18:28:50 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mass.cdrom.com (ether.cdrom.com [204.216.28.196]) by hub.freebsd.org (Postfix) with ESMTP id 78AC237B5AE for ; Wed, 7 Jun 2000 18:28:48 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA03748; Wed, 7 Jun 2000 18:31:59 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006080131.SAA03748@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kevin Day Cc: freebsd-smp@freebsd.org Subject: Re: Tyan Thunder 2400/i840 SMP no good In-reply-to: Your message of "Wed, 07 Jun 2000 20:21:09 CDT." <200006080121.UAA03661@celery.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Jun 2000 18:31:58 -0700 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > > > > > I'm trying to get SMP working on my Tyan Thunder 2400 motherboard. When I > > > recompile the kernel with SMP support and reboot I get as far as 'Testing > > > 8254 interrupt delivery' and it hangs. The console is still responsive, > > > though. > > > > > > Any ideas? > > > > You need -stable or -current to run on the i840. > > > > It wasn't until after I posted that I realized that I wasn't running > -current. I am now, and I've gotten past the boot problems. > > However, I'm now seeing weird data corruption in RAM, spurious SIGBUS or > SIGSEGV's, etc... I've replaced the RAM and CPUs and am still seeing it. I'm > going to try a new ram vendor, as well as swapping motherboards next. > > Has anyone else experienced this on a similar system? I know the i840 is > highly picky when it comes to SDRAM.... Yes. I've even see this with "high quality" SDRAM; the i840 board I'm currently using has some cheap and nasty 64MB DIMMs which work fine, but most of the "high quality" parts I've tried have failed miserably. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 18:56:37 2000 Delivered-To: freebsd-smp@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 231FD37B5AE for ; Wed, 7 Jun 2000 18:56:18 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id VAA86614 for ; Wed, 7 Jun 2000 21:56:57 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Wed, 7 Jun 2000 21:56:57 -0400 (EDT) From: Adam To: smp@freebsd.org Subject: Re: SMP + APM = panic -> fixed! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 7 Jun 2000, Boris Popov wrote: >On Wed, 7 Jun 2000, Mitsuru IWASAKI wrote: > >> We're having this problem for long time (from the old 4.0-CURRENT >> days), but Mr. SUMITANI discovered a bug and fixed it. >> The problem was that we got worng gdt pointer for the current cpu, >> then panic... >> The followings is a patch to fix the problem. Thanks a lot, SUMITANI-san! > > Yes, this fixes panic and even 'halt -p' works as expected. 'zzz' >command works too, but machine never come back from the suspend mode >(looks like interrupt controller programmed incorrectly or something >like this). My Abit BP6 with smp kernel suspends and resumes fine (with the power button) after this patch. Before it, apm -e enable would panic the machine. halt -p works also. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 22:53: 9 2000 Delivered-To: freebsd-smp@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 514AE37BF40; Wed, 7 Jun 2000 22:53:05 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id WAA15952; Wed, 7 Jun 2000 22:53:04 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200006080553.WAA15952@freeway.dcfinc.com> Subject: Re: Tyan Thunder 2400/i840 SMP no good In-Reply-To: <200006080131.SAA03748@mass.cdrom.com> from Mike Smith at "Jun 7, 0 06:31:58 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Wed, 7 Jun 2000 22:53:04 -0700 (MST) Cc: toasty@dragondata.com, freebsd-smp@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As I recall, Mike Smith wrote: >> It wasn't until after I posted that I realized that I wasn't running >> -current. I am now, and I've gotten past the boot problems. >> >> However, I'm now seeing weird data corruption in RAM, spurious SIGBUS or >> SIGSEGV's, etc... I've replaced the RAM and CPUs and am still seeing it. I'm >> going to try a new ram vendor, as well as swapping motherboards next. >> >> Has anyone else experienced this on a similar system? I know the i840 is >> highly picky when it comes to SDRAM.... > > Yes. I've even see this with "high quality" SDRAM; the i840 board I'm > currently using has some cheap and nasty 64MB DIMMs which work fine, but > most of the "high quality" parts I've tried have failed miserably. Does this seem like a problem to anyone besides me? Given the MoBo's sold at Fry's with the memory sold at Fry's will run Windows98 without falling over in a way that is not clearly Windows fault, then we (FreeBSD) will look bad if we can't run on the same hardware. We can get some slack by saying we trapped a problem that would have resulted in an undetected data corruption under WinDoz, but that only goes so far. Can we claim (with a straight face) that there is a legitimate reason FreeBSD is more picky about its hardware platform than Windows/NT Server? If it were not, these MoBo/memory configurations would be being shoved back up the of the vendors when the customers tried to run the software package that is on 90% of the Intel boxen out there and failed. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 23:19:19 2000 Delivered-To: freebsd-smp@freebsd.org Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73]) by hub.freebsd.org (Postfix) with ESMTP id 05A8537BA19 for ; Wed, 7 Jun 2000 23:19:16 -0700 (PDT) (envelope-from drew@chopper.Poohsticks.ORG) Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1]) by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id e586JDR01400; Thu, 8 Jun 2000 00:19:13 -0600 Message-Id: <200006080619.e586JDR01400@chopper.Poohsticks.ORG> To: chad@DCFinc.com Cc: freebsd-smp@FreeBSD.ORG Subject: Hardware and MS rant Was: Tyan Thunder 2400/i840 SMP no good In-reply-to: Your message of "Wed, 07 Jun 2000 22:53:04 PDT." <200006080553.WAA15952@freeway.dcfinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1396.960445153.1@chopper.Poohsticks.ORG> Date: Thu, 08 Jun 2000 00:19:13 -0600 From: Drew Eckhardt Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200006080553.WAA15952@freeway.dcfinc.com>, chad@DCFinc.com writes: >As I recall, Mike Smith wrote: >> Yes. I've even see this with "high quality" SDRAM; the i840 board I'm >> currently using has some cheap and nasty 64MB DIMMs which work fine, but >> most of the "high quality" parts I've tried have failed miserably. > >Does this seem like a problem to anyone besides me? Sure. >Given the MoBo's sold at Fry's with the memory sold at Fry's will run >Windows98 without falling over in a way that is not clearly Windows >fault, then we (FreeBSD) will look bad if we can't run on the same >hardware. Good. Joe Random Clueless Luser will be scared off by the reports he sees on free unix hardware compatability problems, stick to windows, and not burden us with questions that are answered in the FAQs . With a more intelligent user community, unix software will be written for functionality (like nvi, with infinite undo), and not crippled to make it drool proof (like Netscape, where regexes weren't included in the released versions because "they would confuse people"). >Can we claim (with a straight face) that there is a legitimate reason >FreeBSD is more picky about its hardware platform than Windows/NT >Server? Yes. 1. Hardware is thoroughly tested and tweaked to work with common Windows/NT applications because otherwise it won't sell. Since failures under FreeBSD, OpenBSD, NetBSD, RedHat, Caldera, SUSE, or the free unix du jour will have a negligible impact on sales but a substantial impact on time to market it doesn't get tested and problems not detected in testing are more likely. 2. Many free unix programs are more complicated than their commercial counterparts. This means they do a better job (compare the code generated by GCC 1.37 to that from the Microsoft compiler resold by SCO at the same time), at the expense of more complex memory access patterns that are more likely to trigger bugs (search your Usenet archives for signal 11 or SIGSEGV and gcc). >If it were not, these MoBo/memory configurations would be >being shoved back up the >of the vendors when >the customers tried to run the software package that is on 90% of >the Intel boxen out there and failed. The accepted practice when something fails under Windows is to 1. Reboot 2. Rerun the application 3. Reboot 4. Reinstall the application 5. Reboot 6. Rerun the application 7. Reboot 8. Install all of the service packs 9. Reboot 10. Rerun the application 11. Reboot 12. Reinstall Windows du jour 13. Reboot 14. Install the service packs 15. Reboot 16. Reinstall the application 17. Reboot 18. Rerun the application 19. Bang head against wall in frustration 20. Live with the problem People's expectations of personal computer (PC, Mac, TRS80, Commodore 64, etc) software aren't very high, and they manage when it fails. Common hardware + driver + applications configurations DO fail with great regularity under Windows, and beyond a quiet "Oh yeah, that happened to me too. Buy a different board" people do nothing constructive about the situation. For that matter, some make a sport out of it. "Sure, my over-clocked system won't run the Wazzyding benchmark, but it runs 3 frames per second faster under quake demo". (Yeah, I'm feeling cranky tonight). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Jun 7 23:58:44 2000 Delivered-To: freebsd-smp@freebsd.org Received: from frond.minions.com (adsl-63-192-211-186.dsl.snfc21.pacbell.net [63.192.211.186]) by hub.freebsd.org (Postfix) with ESMTP id 6C7E337BAC0 for ; Wed, 7 Jun 2000 23:58:41 -0700 (PDT) (envelope-from bifrost@minions.com) Received: from localhost.minions.com (localhost.minions.com [127.0.0.1]) by frond.minions.com (8.9.3/8.9.3) with ESMTP id XAA05117 for ; Wed, 7 Jun 2000 23:58:41 -0700 (PDT) (envelope-from bifrost@minions.com) Date: Wed, 7 Jun 2000 23:58:41 -0700 (PDT) From: Tom To: freebsd-smp@FreeBSD.ORG Subject: HP Netserver LPr Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a whole bunch of these, some with Linux (yech), some with Solaris X86 (whee!) and one with FreeBSD on it. FreeBSD and Solaris X86 run really nicely on them, Linux blows itself apart because the boards use NCR U2W chipsets on them and there is some kind of interaction and race condition which causes ext2 to hose itself on them at random intervals. Nothing new to Linux (Just re-install, just like Windows!). They have the same stepping, on both CPU's, and the boxes run perfect. I'd say the boxes aren't really cost effective at $17k a pop and you'd be *much* better off with a Telenet box (www.tesys.com) but if HP is what you've got around, its whats around :) --- Tom bifrost@minions.com "Where am I and why am I in this handbasket?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 8 0:43:20 2000 Delivered-To: freebsd-smp@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 838C437B9E1 for ; Thu, 8 Jun 2000 00:43:15 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id AAA16300; Thu, 8 Jun 2000 00:43:03 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200006080743.AAA16300@freeway.dcfinc.com> Subject: Re: HP Netserver LPr In-Reply-To: from Tom at "Jun 7, 0 11:58:41 pm" To: bifrost@frond.minions.com (Tom) Date: Thu, 8 Jun 2000 00:43:03 -0700 (MST) Cc: freebsd-smp@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As I recall, Tom wrote: > FreeBSD and Solaris X86 run really nicely on them, Linux blows > itself apart because the boards use NCR U2W chip sets on them and > there is some kind of interaction and race condition which causes > ext2 to hose itself on them at random intervals. We're using LPng (the LP Next Generation) on our FreeBSD printer servers. The driving factor was that our mainframes (Pyramid DC/OSx) croaked on the extremely verbose response we got from an NT print server status request (buffer overrun, the response for a detailed status request gives everything that happened since boot). We set up the Linux systems as prophylaxis for the Pyramids. Don't ask me why we didn't implement LPng on the Pyramids, or why the condoms weren't FreeBSD. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 8 10:58:19 2000 Delivered-To: freebsd-smp@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [206.168.13.65]) by hub.freebsd.org (Postfix) with ESMTP id 750A137B608 for ; Thu, 8 Jun 2000 10:58:12 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.9.3/8.9.3) with ESMTP id LAA32266; Thu, 8 Jun 2000 11:57:58 -0600 (MDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Message-Id: <200006081757.LAA32266@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: Drew Eckhardt Cc: chad@DCFinc.com, freebsd-smp@FreeBSD.ORG Subject: Re: Hardware and MS rant Was: Tyan Thunder 2400/i840 SMP no good In-reply-to: Your message of "Thu, 08 Jun 2000 00:19:13 MDT." <200006080619.e586JDR01400@chopper.Poohsticks.ORG> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Jun 2000 11:57:58 -0600 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > In message <200006080553.WAA15952@freeway.dcfinc.com>, chad@DCFinc.com writes: > >As I recall, Mike Smith wrote: > >> Yes. I've even see this with "high quality" SDRAM; the i840 board I'm > >> currently using has some cheap and nasty 64MB DIMMs which work fine, but > >> most of the "high quality" parts I've tried have failed miserably. > > > >Does this seem like a problem to anyone besides me? > > Sure. > ... Intel has pretty much given up on supporting sdram in 820/MTH MBs. They have announced a replacement program why you supossedly will get a new MB/RDRAM setup... See tom's hardware page for MANY articles on this mess: http://www5.tomshardware.com/mainboard/00q2/000512/index.html -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 8 11: 5: 2 2000 Delivered-To: freebsd-smp@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 318EE37C09F for ; Thu, 8 Jun 2000 11:04:54 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id NAA46864 for freebsd-smp@freebsd.org; Thu, 8 Jun 2000 13:05:25 -0500 (CDT) From: Joe Greco Message-Id: <200006081805.NAA46864@aurora.sol.net> Subject: Re: HP Vectra XU To: freebsd-smp@freebsd.org Date: Thu, 8 Jun 2000 13:05:25 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a HP Vectra XU, Dual PPro 200, 256Mb RAM, Internal Adaptec, > that ran quite happily on a 4.0-CURRENT from mid January if I remember > rightly. Upgraded to STABLE and it died on boot. Boots single processor > OK, dual it wont. Blanked it, and put 4.0-RELEASE on there, same again. > Single OK, Dual I get: > > (snip) > avail memory = 257159168 (251132K bytes) > Programming 16 pins in IOAPIC #0 > IOAPIC #0 intpin 2 -> irq 0 > > Then stops. Any ideas anyone? It's something HP specific. Last time I tackled this, back in the earlier 3.x releases, we tracked it down to the second CPU not starting. They said something was wrong with my hardware, which seemed odd since it booted 3.0R fine. One thing I also noticed was that it was actually much more likely to start if powered up, rather than reset/rebooted. -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 8 20:13: 0 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id B72A837B640 for ; Thu, 8 Jun 2000 20:12:57 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA01184; Thu, 8 Jun 2000 20:16:49 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006090316.UAA01184@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: chad@DCFinc.com Cc: freebsd-smp@FreeBSD.ORG Subject: Re: Tyan Thunder 2400/i840 SMP no good In-reply-to: Your message of "Wed, 07 Jun 2000 22:53:04 PDT." <200006080553.WAA15952@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Jun 2000 20:16:49 -0700 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> It wasn't until after I posted that I realized that I wasn't running > >> -current. I am now, and I've gotten past the boot problems. > >> > >> However, I'm now seeing weird data corruption in RAM, spurious SIGBUS or > >> SIGSEGV's, etc... I've replaced the RAM and CPUs and am still seeing it. I'm > >> going to try a new ram vendor, as well as swapping motherboards next. > >> > >> Has anyone else experienced this on a similar system? I know the i840 is > >> highly picky when it comes to SDRAM.... > > > > Yes. I've even see this with "high quality" SDRAM; the i840 board I'm > > currently using has some cheap and nasty 64MB DIMMs which work fine, but > > most of the "high quality" parts I've tried have failed miserably. > > Does this seem like a problem to anyone besides me? Yes. It seems like these boards/RAM have some serious issues. > Given the MoBo's sold at Fry's with the memory sold at Fry's will run > Windows98 without falling over in a way that is not clearly Windows > fault, then we (FreeBSD) will look bad if we can't run on the same > hardware. There is no way to determine what is or is not "clealy Windows' fault". If the hardware corrupts data, then there is NOTHING that can be done about it. End of story. > Can we claim (with a straight face) that there is a legitimate reason > FreeBSD is more picky about its hardware platform than Windows/NT > Server? It's not. > If it were not, these MoBo/memory configurations would be > being shoved back up the of the vendors when > the customers tried to run the software package that is on 90% of > the Intel boxen out there and failed. I would expect that if I were to go purchase memory certified for this board, it would work. On the other hand, I have on several occasions failed entirely to install any of several different Microsoft operating systems on this board; by your criteria I would assert that the board is entirely unsuited for sale as a product at all. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 8 21:36:45 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 2645137B621; Thu, 8 Jun 2000 21:36:42 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id AAA393348; Fri, 9 Jun 2000 00:36:38 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200006090316.UAA01184@mass.cdrom.com> References: <200006090316.UAA01184@mass.cdrom.com> Date: Fri, 9 Jun 2000 00:37:02 -0400 To: Mike Smith , chad@DCFinc.com From: Garance A Drosihn Subject: Re: Tyan Thunder 2400/i840 SMP no good Cc: freebsd-smp@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Given the MoBo's sold at Fry's with the memory sold at Fry's will run > > Windows98 without falling over in a way that is not clearly Windows > > fault, then we (FreeBSD) will look bad if we can't run on the same > > hardware. > >There is no way to determine what is or is not "clearly Windows' fault". > >If the hardware corrupts data, then there is NOTHING that can be done >about it. End of story. > > > Can we claim (with a straight face) that there is a legitimate reason > > FreeBSD is more picky about its hardware platform than Windows/NT > > Server? > >It's not. To expand on that, I have also heard of a lot of problems with these boards being very picky about the memory used -- and I heard it from people who WERE running windows on them. They just shrug and go out and buy more RAM until they get a set which works... I just bought a new machine for running Linux, and my windows-buddies steered me away from anything having to do with those chipsets/motherboards. Hardware problems really do effect everyone on all OS's. FreeBSD has no need to feel bad if it can not run on faulty hardware. This problem may not come up for people who buy a packaged system and never add memory to it, but it certainly is happening to people running Windows who add more RAM. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 8 23:46:40 2000 Delivered-To: freebsd-smp@freebsd.org Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by hub.freebsd.org (Postfix) with ESMTP id 267D337C211 for ; Thu, 8 Jun 2000 23:46:36 -0700 (PDT) (envelope-from Joachim.Strombergson@Ericsson.com) Received: from poem.emw.ericsson.se (poem.emw.ericsson.se [136.225.49.25]) by penguin.wise.edt.ericsson.se (8.10.1/8.10.1/WIREfire-1.9) with ESMTP id e596kXr16763 for ; Fri, 9 Jun 2000 08:46:33 +0200 (MET DST) Received: from Ericsson.com (balvenie.mo.emw.ericsson.se [136.225.229.97]) by poem.emw.ericsson.se (8.9.3/8.9.3) with ESMTP id IAA05104 for ; Fri, 9 Jun 2000 08:46:28 +0200 (MET DST) Message-ID: <394092B9.19DB13C3@Ericsson.com> Date: Fri, 09 Jun 2000 08:46:17 +0200 From: Joachim Strombergson Organization: Ericsson Microwave Systems AB X-Mailer: Mozilla 4.7C-EMW [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-smp Subject: FCPGA and the new Celerons in BP6 MB for SMP? Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! I'm since a year back a happy owner of a FreeBSD SMP system currently based on the ABIt BP6 MB equipped with two Celeron 366 PPGA processors. Then system running FreeBSD 4.0 is stable and able to take a great load, like EMACS and StarOffice at the same time... But the speed (SETI hours actually) isn't enough for my needs/wishes/geek-wants. After overcooking/overclocking them (yes, yes - I know it's a no, no) I've had a few hiccups in the system. I'm therefore resorting to more certified ways of getting better performance (can we ever have enough? ;-) I've tried to figure out if the BP6 or any other MB with PPGA sockets can use the new Celerons with FCPGA packaging. There are converters to connect a FCPGA to a Slot1 MB, but haven't seen anything related to PPGA. Is the PPGA a dead end? Also, are the new Celerons (566/600) SMP-able? I've asked around, but gotten highly different answers. Should I instead opt for the older 500 or 533 MHz non-coppermine based Celerons? So, anyone with real world experience on this? Is the truth out there? -- Med vänlig hälsning, Yours Joachim Strömbergson - Alltid i harmonisk svängning ---------------- Ericsson Microwave Systems AB ----------------- Joachim Strömbergson http://www.ericsson.se/microwave ASIC System on Silicon engineer, nice to CUTE animals. * Opinions above, expressed or implicit, are strictly personal * ------------- Spamfodder: regeringen@regeringen.se ------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 9 0:11:50 2000 Delivered-To: freebsd-smp@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id EC03E37BBA2 for ; Fri, 9 Jun 2000 00:11:41 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id DAA00304; Fri, 9 Jun 2000 03:11:26 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Fri, 9 Jun 2000 03:11:26 -0400 (EDT) From: Adam To: Joachim Strombergson Cc: freebsd-smp Subject: Re: FCPGA and the new Celerons in BP6 MB for SMP? In-Reply-To: <394092B9.19DB13C3@Ericsson.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org www.bp6.com and www.hardocp.com are your friends :) On Fri, 9 Jun 2000, Joachim Strombergson wrote: >Hi! > >I'm since a year back a happy owner of a FreeBSD SMP system currently >based on the ABIt BP6 MB equipped with two Celeron 366 PPGA processors. >Then system running FreeBSD 4.0 is stable and able to take a great load, >like EMACS and StarOffice at the same time... But the speed (SETI hours >actually) isn't enough for my needs/wishes/geek-wants. > >After overcooking/overclocking them (yes, yes - I know it's a no, no) >I've had a few hiccups in the system. I'm therefore resorting to more >certified ways of getting better performance (can we ever have enough? >;-) > >I've tried to figure out if the BP6 or any other MB with PPGA sockets >can use the new Celerons with FCPGA packaging. There are converters to >connect a FCPGA to a Slot1 MB, but haven't seen anything related to >PPGA. Is the PPGA a dead end? > >Also, are the new Celerons (566/600) SMP-able? I've asked around, but >gotten highly different answers. Should I instead opt for the older 500 >or 533 MHz non-coppermine based Celerons? > >So, anyone with real world experience on this? Is the truth out there? > >--=20 >Med v=E4nlig h=E4lsning, Yours > >Joachim Str=F6mbergson - Alltid i harmonisk sv=E4ngning >---------------- Ericsson Microwave Systems AB ----------------- >Joachim Str=F6mbergson http://www.ericsson.se/microwave > ASIC System on Silicon engineer, nice to CUTE animals. =20 >* Opinions above, expressed or implicit, are strictly personal * >------------- Spamfodder: regeringen@regeringen.se ------------- > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-smp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 9 0:53:41 2000 Delivered-To: freebsd-smp@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id EF47E37C276; Fri, 9 Jun 2000 00:53:36 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id AAA19330; Fri, 9 Jun 2000 00:53:36 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200006090753.AAA19330@freeway.dcfinc.com> Subject: Re: Tyan Thunder 2400/i840 SMP no good In-Reply-To: <200006090316.UAA01184@mass.cdrom.com> from Mike Smith at "Jun 8, 0 08:16:49 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Fri, 9 Jun 2000 00:53:35 -0700 (MST) Cc: freebsd-smp@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As I recall, Mike Smith wrote: > On the other hand, I have on several occasions failed entirely to > install any of several different Microsoft operating systems on this > board; by your criteria I would assert that the board is entirely > unsuited for sale as a product at all. Sounds reasonable to me. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 9 0:54: 6 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 89AA637B667 for ; Fri, 9 Jun 2000 00:53:59 -0700 (PDT) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id JAA00015; Fri, 9 Jun 2000 09:52:19 +0200 From: Thierry.Herbelot@alcatel.fr Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with SMTP id JAA28475; Fri, 9 Jun 2000 09:53:32 +0200 (MET DST) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id C12568F9.002B6151 ; Fri, 9 Jun 2000 09:53:49 +0200 X-Lotus-FromDomain: ALCATEL To: Joachim Strombergson Cc: freebsd-smp Message-ID: Date: Fri, 9 Jun 2000 09:53:43 +0200 Subject: Re: FCPGA and the new Celerons in BP6 MB for SMP? Mime-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=dlxKNejl8Mr8nbuaJrc61efrqEazquRz4tvQcCt1f4sl30weRYX0jElQ" Content-Disposition: inline Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --0__=dlxKNejl8Mr8nbuaJrc61efrqEazquRz4tvQcCt1f4sl30weRYX0jElQ Content-type: text/plain; charset=us-ascii Content-Disposition: inline Hello, I also own a BP6 (but with cel-333's), and I'm considering an upgrade. I have for now seen two ways : - buy a SMP board using a Via chipset (I know this seems crazy, SMP being a bit "picky" wrt to chipset), more specifically an MSI 6321 (if it supports FCPGA's) - keep my old BP6 as my only SMP machine, and buy a cheap but wonderfully fast "Duron" mono-processor (~$120 for 600-MHz) I'm afraid an upgrade of the BP6 itself will never happen (the powerleap adaptor supported only one FCPGA the last time I checked), and anyway, the Pentium-III chips are much too expensive for me. TfH Joachim Strombergson on 09/06/2000 08:46:17 To: freebsd-smp cc: (bcc: Thierry HERBELOT/FR/ALCATEL) Subject: FCPGA and the new Celerons in BP6 MB for SMP? --0__=dlxKNejl8Mr8nbuaJrc61efrqEazquRz4tvQcCt1f4sl30weRYX0jElQ Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-transfer-encoding: quoted-printable Hi! I'm since a year back a happy owner of a FreeBSD SMP system currently based on the ABIt BP6 MB equipped with two Celeron 366 PPGA processors.= Then system running FreeBSD 4.0 is stable and able to take a great load= , like EMACS and StarOffice at the same time... But the speed (SETI hours= actually) isn't enough for my needs/wishes/geek-wants. After overcooking/overclocking them (yes, yes - I know it's a no, no) I've had a few hiccups in the system. I'm therefore resorting to more certified ways of getting better performance (can we ever have enough? ;-) I've tried to figure out if the BP6 or any other MB with PPGA sockets can use the new Celerons with FCPGA packaging. There are converters to connect a FCPGA to a Slot1 MB, but haven't seen anything related to PPGA. Is the PPGA a dead end? Also, are the new Celerons (566/600) SMP-able? I've asked around, but gotten highly different answers. Should I instead opt for the older 500= or 533 MHz non-coppermine based Celerons? So, anyone with real world experience on this? Is the truth out there? -- Med v=E4nlig h=E4lsning, Yours Joachim Str=F6mbergson - Alltid i harmonisk sv=E4ngning ---------------- Ericsson Microwave Systems AB ----------------- Joachim Str=F6mbergson http://www.ericsson.se/microwave ASIC System on Silicon engineer, nice to CUTE animals. * Opinions above, expressed or implicit, are strictly personal * ------------- Spamfodder: regeringen@regeringen.se ------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message = --0__=dlxKNejl8Mr8nbuaJrc61efrqEazquRz4tvQcCt1f4sl30weRYX0jElQ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 9 5:24:39 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mail2.bna.bellsouth.net (mail2.bna.bellsouth.net [205.152.150.14]) by hub.freebsd.org (Postfix) with ESMTP id D74F037B544; Fri, 9 Jun 2000 05:24:36 -0700 (PDT) (envelope-from lauasanf@bellsouth.net) Received: from damage (host-209-214-118-105.bna.bellsouth.net [209.214.118.105]) by mail2.bna.bellsouth.net (3.3.5alt/0.75.2) with SMTP id IAA25158; Fri, 9 Jun 2000 08:24:32 -0400 (EDT) From: Laurence Sanford Reply-To: lauasanf@bellsouth.net To: chad@DCFinc.com, "Chad R. Larson" , msmith@FreeBSD.ORG (Mike Smith) Subject: Re: Tyan Thunder 2400/i840 SMP no good Date: Fri, 9 Jun 2000 06:26:19 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-smp@FreeBSD.ORG References: <200006090753.AAA19330@freeway.dcfinc.com> In-Reply-To: <200006090753.AAA19330@freeway.dcfinc.com> MIME-Version: 1.0 Message-Id: <00060906285302.28178@damage> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 09 Jun 2000, Chad R. Larson spoke unto us, and they said: > As I recall, Mike Smith wrote: > > On the other hand, I have on several occasions failed entirely to > > install any of several different Microsoft operating systems on this > > board; by your criteria I would assert that the board is entirely > > unsuited for sale as a product at all. > > Sounds reasonable to me. > > -crl I hate to interupt this party, but the blame here lies with the chipset, and not with the motherboard. I have two tyan TomCats (a 3.0 and 4.0) both running SMP that have been rock solid since day one, well over 4 years ago for the 3.0. Tyan makes an excellent board. It's not their fault the intel chipset spec is crap. Just my $.02. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Drew Sanford Email: lauasanf@bellsouth.net ICQ: 8690555 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "My mother said to me, if you become a soldier, you'll be a general, if you become a monk, you'll end up as the pope. Instead I became a painter and wound up as Picasso." -- Pablo Picasso To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 9 8:33: 2 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id A903B37C466 for ; Fri, 9 Jun 2000 08:32:58 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA03577; Fri, 9 Jun 2000 08:36:21 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006091536.IAA03577@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: lauasanf@bellsouth.net Cc: freebsd-smp@FreeBSD.ORG Subject: Re: Tyan Thunder 2400/i840 SMP no good In-reply-to: Your message of "Fri, 09 Jun 2000 06:26:19 CDT." <00060906285302.28178@damage> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Jun 2000 08:36:21 -0700 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I hate to interupt this party, but the blame here lies with the chipset, and > not with the motherboard. I have two tyan TomCats (a 3.0 and 4.0) both running > SMP that have been rock solid since day one, well over 4 years ago for the 3.0. > Tyan makes an excellent board. It's not their fault the intel chipset spec is > crap. Just my $.02. Gah. Soda wars over motherboard vendors. Sheesh. And this is a Supermicro board anyway. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 9 8:43: 3 2000 Delivered-To: freebsd-smp@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id AE01C37B9D9; Fri, 9 Jun 2000 08:42:56 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id RAA14873; Fri, 9 Jun 2000 17:42:50 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Fri, 9 Jun 2000 17:42:49 +0200 (EET) From: Narvi To: Mike Smith Cc: lauasanf@bellsouth.net, freebsd-smp@FreeBSD.ORG Subject: Re: Tyan Thunder 2400/i840 SMP no good In-Reply-To: <200006091536.IAA03577@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 9 Jun 2000, Mike Smith wrote: > > > > I hate to interupt this party, but the blame here lies with the chipset, and > > not with the motherboard. I have two tyan TomCats (a 3.0 and 4.0) both running > > SMP that have been rock solid since day one, well over 4 years ago for the 3.0. > > Tyan makes an excellent board. It's not their fault the intel chipset spec is > > crap. Just my $.02. > > Gah. Soda wars over motherboard vendors. Sheesh. > > And this is a Supermicro board anyway. > Heh. OK. What is a good board with roughly comparable stats? > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 9 9:47:48 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 4E73D37C433 for ; Fri, 9 Jun 2000 09:47:44 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA03808; Fri, 9 Jun 2000 09:51:23 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006091651.JAA03808@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Narvi Cc: freebsd-smp@FreeBSD.ORG Subject: Re: Tyan Thunder 2400/i840 SMP no good In-reply-to: Your message of "Fri, 09 Jun 2000 17:42:49 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Jun 2000 09:51:23 -0700 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Gah. Soda wars over motherboard vendors. Sheesh. > > > > And this is a Supermicro board anyway. > > Heh. > > OK. What is a good board with roughly comparable stats? That depends on what counts as "comparable". When the i840 is working properly (with RDRAM) there isn't really anything "comparable" when it comes to memory bandwidth. You can go upmarket a bit to systems based on the RCC chipset (Tyan have a board that's meant to be out soon using these parts), or down a bit to the i440GX-based boards from various vendors. For a 'workstation'-class system, it's still hard to beat the old 440BX. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 9 19:58:52 2000 Delivered-To: freebsd-smp@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [206.168.13.65]) by hub.freebsd.org (Postfix) with ESMTP id 81CB137BBBB for ; Fri, 9 Jun 2000 19:58:49 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.9.3/8.9.3) with ESMTP id UAA42543 for ; Fri, 9 Jun 2000 20:58:47 -0600 (MDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Message-Id: <200006100258.UAA42543@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: freebsd-smp@FreeBSD.ORG Subject: Re: Tyan Thunder 2400/i840 SMP no good In-reply-to: Your message of "Fri, 09 Jun 2000 09:51:23 PDT." <200006091651.JAA03808@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 09 Jun 2000 20:58:47 -0600 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > > > Gah. Soda wars over motherboard vendors. Sheesh. > > > > > > And this is a Supermicro board anyway. > > > > Heh. > > > > OK. What is a good board with roughly comparable stats? > > That depends on what counts as "comparable". When the i840 is working > properly (with RDRAM) there isn't really anything "comparable" when it > comes to memory bandwidth. http://www.tomshardware.com/mainboard/00q1/000308/index.html -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Jun 10 18:37:33 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 3BCA237B6E2 for ; Sat, 10 Jun 2000 18:37:27 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id VAA113324; Sat, 10 Jun 2000 21:37:17 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200006080743.AAA16300@freeway.dcfinc.com> References: <200006080743.AAA16300@freeway.dcfinc.com> Date: Sat, 10 Jun 2000 21:37:37 -0400 To: chad@DCFinc.com, bifrost@frond.minions.com (Tom) From: Garance A Drosihn Subject: Re: HP Netserver LPr Cc: freebsd-smp@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:43 AM -0700 6/8/00, Chad R. Larson wrote: >As I recall, Tom wrote: > > FreeBSD and Solaris X86 run really nicely on them, Linux blows > > itself apart because the boards use NCR U2W chip sets on them and > > there is some kind of interaction and race condition which causes > > ext2 to hose itself on them at random intervals. > >We're using LPng (the LP Next Generation) on our FreeBSD printer >servers. The driving factor was that our mainframes (Pyramid DC/OSx) >croaked on the extremely verbose response we got from an NT print server >status request (buffer overrun, the response for a detailed status >request gives everything that happened since boot). We set up the >Linux systems as prophylaxis for the Pyramids. Don't ask me why >we didn't implement LPng on the Pyramids, or why the condoms weren't >FreeBSD. This thread has me a little confused. I don't know what an 'HP Netserver LPr' is. The first message implies it is some sort of x86-based multi-processor box, but the second message implies it has something to do with printing (ie, 'lpr'). Is this a hardware topic, or a printing topic? and in the world of printing topics, I assume you mean 'LPRng' not 'LPng'? --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message