From owner-freebsd-smp Sun Jun 21 01:03:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19115 for freebsd-smp-outgoing; Sun, 21 Jun 1998 01:03:40 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19099; Sun, 21 Jun 1998 01:03:31 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id KAA20182; Sun, 21 Jun 1998 10:02:42 +0200 (CEST) (envelope-from sos) Message-Id: <199806210802.KAA20182@sos.freebsd.dk> Subject: Re: TYAN 1668 anyone ?? In-Reply-To: <23915.898404196@time.cdrom.com> from "Jordan K. Hubbard" at "Jun 20, 98 09:43:16 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 21 Jun 1998 10:02:42 +0200 (CEST) Cc: sos@FreeBSD.ORG, kedar@asacomputers.com, smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Jordan K. Hubbard who wrote: > > Hmm, I doubt it, I use only prime quality RAM here (because of exactly > > that reason), and the same RAM works just fine in a 1662 board, which > > is just as picky... > > Actually, and just to note it for the audience, it's easily possible > to create memory failures using "prime quality" RAM that has been > tested on a different motherboard. Mixing RAM from different > manufacturers, using RAM of the wrong speed or at the wrong voltage > (in motherboards which allow that degree of configuration), all would > be possible while meeting the above criteria and all have been > reported to us as the causes of mysterious hangs, crashes, resets, you > name it. Once the RAM was simply swapped or the misconfiguration > issues dealt with, the system has become a rock of gibraltar in each > case. I'm using several 1668 mobos myself, and they work very nicely > with Matrox cards (yep, there's another variable for you! ;) Well, I'm using ONLY Hyundai 32M/60ns SIMMs here they are of prime quality, so I'm sure its not memory related... Now, I've been running one of these monsters (1668) with the old Diamond Viper PRO card (remember that Jordan?), and it hasn't had a hicup for 36 hours !! The only problem is that I only have an Xinside 1.3 server that supports that card (remember the 1.1.5.1+ days anyone :) ). I'll try to get ahold of another more modern videocard that is NOT S3 based, it seems the 1668 has severe problems with that.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sun Jun 21 15:03:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08883 for freebsd-smp-outgoing; Sun, 21 Jun 1998 15:03:32 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles145.castles.com [208.214.165.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08877; Sun, 21 Jun 1998 15:03:30 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA01389; Sun, 21 Jun 1998 13:58:38 -0700 (PDT) Message-Id: <199806212058.NAA01389@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sos@FreeBSD.ORG cc: jkh@time.cdrom.com (Jordan K. Hubbard), kedar@asacomputers.com, smp@FreeBSD.ORG Subject: Re: TYAN 1668 anyone ?? In-reply-to: Your message of "Sun, 21 Jun 1998 10:02:42 +0200." <199806210802.KAA20182@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sun, 21 Jun 1998 13:58:37 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id PAA08878 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Well, I'm using ONLY Hyundai 32M/60ns SIMMs here they are of prime > quality, so I'm sure its not memory related... Hyundai memory parts are not "prime quality" by any stretch of the imagination. You're welcome to ask about my experiences with their parts offline, but basically there is no one vendor you can point at and say "their parts are all prime quality". -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sun Jun 21 15:43:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16615 for freebsd-smp-outgoing; Sun, 21 Jun 1998 15:43:01 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16608; Sun, 21 Jun 1998 15:42:47 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id AAA01080; Mon, 22 Jun 1998 00:41:55 +0200 (CEST) (envelope-from sos) Message-Id: <199806212241.AAA01080@sos.freebsd.dk> Subject: Re: TYAN 1668 anyone ?? In-Reply-To: <199806212058.NAA01389@antipodes.cdrom.com> from Mike Smith at "Jun 21, 98 01:58:37 pm" To: mike@smith.net.au (Mike Smith) Date: Mon, 22 Jun 1998 00:41:55 +0200 (CEST) Cc: sos@FreeBSD.ORG, jkh@time.cdrom.com, kedar@asacomputers.com, smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Mike Smith who wrote: > > > > Well, I'm using ONLY Hyundai 32M/60ns SIMMs here they are of prime > > quality, so I'm sure its not memory related... > > Hyundai memory parts are not "prime quality" by any stretch of the > imagination. You're welcome to ask about my experiences with their > parts offline, but basically there is no one vendor you can point at > and say "their parts are all prime quality". We are not talking about the same memory then, thats for sure. We have run tests on these suckers and they are amoung the better parts available. Granted they also market their rejects and THOSE I would not touch.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sun Jun 21 17:07:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00439 for freebsd-smp-outgoing; Sun, 21 Jun 1998 17:07:11 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mail1.its.rpi.edu (root@mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00391 for ; Sun, 21 Jun 1998 17:06:50 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id UAA47866; Sun, 21 Jun 1998 20:06:44 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199806201647.LAA10688@base486.home.org> Date: Sun, 21 Jun 1998 20:10:31 -0400 To: Dave Bodenstab , freebsd-smp@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Equium 6200M successfull install Cc: darrylo@sr.hp.com Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:47 AM -0500 6/20/98, Dave Bodenstab wrote: > I have successfully installed the 5/20 snap on a dual-ppro > Toshiba Equium 6200m (pr440fx mb). I had to upgrade the > firmware on the Micropolis disks, but that's all. That's encouraging to hear! I have a second PPro to install in one of my Toshiba 6200M's, but I haven't done it yet (almost did it this past weekend). > Previously, Darryl Okahata had noted: > >> It appears that a BIOS upgrade may be necessary (one newer than >> that available from Toshiba). > Since I'm now new to SMP, a few questions: > > 1. I got the BIOS upgrade from the intel support site, but when I > tried it, it gave me an error about a failure to initialize the > flash memory and the upgrade aborted. Anyone have a clue about > this? Both I and a friend of mine bought some of these Toshibas. As near as we can tell, all of the machines require that you change a jumper on the motherboard to do a BIOS upgrade. It's the "Flash Mode Recover" jumper (J12B1-B). All the documentation that we've read indicates that you'd only need to use this jumper in emergency situations (such as if you've really screwed up a previous attempt to upgrade the BIOS). However, we have had to use this on all the BIOS upgrades we have done. This means you end up having to do the upgrade "blind". You flip the jumper on, boot up off the floppy which has the bios upgrade, wait until the floppy light goes out and you hear two "beeps", turn the machine off, flip the jumper back, and then boot up normally. You then follow the remaining instructions (such as going thru the BIOS settings to make sure they're what you want them to be). It is a little disconcerting, but it has worked every time. And if anyone is dual-booting into WinNT, you may find that WindowsNT dies with the blue screen of death immediately on bootup. If this happens to you, it might mean that you have turned off the APM support in the BIOS as part of the upgrade. --- Garance Alistair Drosehn = gad@eclipse.its.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 Sun Jun 21 22:19:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15944 for freebsd-smp-outgoing; Sun, 21 Jun 1998 22:19:44 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles314.castles.com [208.214.167.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15901; Sun, 21 Jun 1998 22:19:35 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA02759; Sun, 21 Jun 1998 18:53:22 -0700 (PDT) Message-Id: <199806220153.SAA02759@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sos@FreeBSD.ORG cc: mike@smith.net.au (Mike Smith), jkh@time.cdrom.com, kedar@asacomputers.com, smp@FreeBSD.ORG Subject: Re: TYAN 1668 anyone ?? In-reply-to: Your message of "Mon, 22 Jun 1998 00:41:55 +0200." <199806212241.AAA01080@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sun, 21 Jun 1998 18:53:22 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id WAA15918 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In reply to Mike Smith who wrote: > > > > > > Well, I'm using ONLY Hyundai 32M/60ns SIMMs here they are of prime > > > quality, so I'm sure its not memory related... > > > > Hyundai memory parts are not "prime quality" by any stretch of the > > imagination. You're welcome to ask about my experiences with their > > parts offline, but basically there is no one vendor you can point at > > and say "their parts are all prime quality". > > We are not talking about the same memory then, thats for sure. I guess not. We were looking at banded parts from various brokers, and comparing their real performance against the documentation. > We have run tests on these suckers and they are amoung the > better parts available. Granted they also market their rejects > and THOSE I would not touch.... The hard part appears to be guaranteeing that you're getting the right parts from one batch to the next, and this is what I was getting at - when you go to an assembled-memory broker, you have no easy way of being sure that the modules you buy are assembled from non-reject parts. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mon Jun 22 01:15:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16141 for freebsd-smp-outgoing; Mon, 22 Jun 1998 01:15:37 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16032; Mon, 22 Jun 1998 01:14:59 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id KAA01948; Mon, 22 Jun 1998 10:13:59 +0200 (CEST) (envelope-from sos) Message-Id: <199806220813.KAA01948@sos.freebsd.dk> Subject: Re: TYAN 1668 anyone ?? In-Reply-To: <199806220153.SAA02759@antipodes.cdrom.com> from Mike Smith at "Jun 21, 98 06:53:22 pm" To: mike@smith.net.au (Mike Smith) Date: Mon, 22 Jun 1998 10:13:59 +0200 (CEST) Cc: sos@FreeBSD.ORG, mike@smith.net.au, jkh@time.cdrom.com, kedar@asacomputers.com, smp@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Mike Smith who wrote: > > In reply to Mike Smith who wrote: > > > > > > > > Well, I'm using ONLY Hyundai 32M/60ns SIMMs here they are of prime > > > > quality, so I'm sure its not memory related... > > > > > > Hyundai memory parts are not "prime quality" by any stretch of the > > > imagination. You're welcome to ask about my experiences with their > > > parts offline, but basically there is no one vendor you can point at > > > and say "their parts are all prime quality". > > > > We are not talking about the same memory then, thats for sure. > > I guess not. We were looking at banded parts from various brokers, and > comparing their real performance against the documentation. Ahh, keep away from brokers :), buy ONLY from an established importer or something like that. I buy Hyundai memory from the Danish importer and I'm sure I get the real thing each time, modules made from chips from the same run, on thier own SIMM PCB's mounted & tested at Hyundai... > The hard part appears to be guaranteeing that you're getting the right > parts from one batch to the next, and this is what I was getting at - > when you go to an assembled-memory broker, you have no easy way of being > sure that the modules you buy are assembled from non-reject parts. Again dont buy from the "grey" market, buy directly from the source, it might be a bit more expensive, but you KNOW what you get then... I've yet to see a single bad Hyundai module here.. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Jun 22 04:11:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12564 for freebsd-smp-outgoing; Mon, 22 Jun 1998 04:11:42 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12546; Mon, 22 Jun 1998 04:11:37 -0700 (PDT) (envelope-from bkogawa@primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id EAA13660; Mon, 22 Jun 1998 04:11:38 -0700 (MST) Received: from ip196.sjc.primenet.com(206.165.96.196), claiming to be "foo.primenet.com" via SMTP by smtp04.primenet.com, id smtpd013623; Mon Jun 22 04:11:28 1998 Received: (from bkogawa@localhost) by foo.primenet.com (8.8.8/8.8.6) id DAA02653; Mon, 22 Jun 1998 03:40:13 -0700 (PDT) Date: Mon, 22 Jun 1998 03:40:13 -0700 (PDT) Message-Id: <199806221040.DAA02653@foo.primenet.com> To: tjohnson@verio.net Subject: Re: TYAN 1668 anyone ?? Newsgroups: localhost.freebsd.hackers References: From: "Bryan K. Ogawa" Cc: smp@FreeBSD.ORG, FreeBSD hackers , "'Chuck Robey'" X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In localhost.freebsd.hackers you write: >This message is in MIME format. Since your mail reader does not understand >this format, some or all of this message may not be legible. >------ =_NextPart_000_01BD9B90.E8266C30 >Content-Type: text/plain; > charset="iso-8859-1" >Content-Transfer-Encoding: quoted-printable >I got a few lockups when I had dram refresh queue and I think the other >option is fast dram leadoff turned on in chipset options of my = >bios.(awd >5.01) The bios defaults turns them on I think. Turning them off fixed >my lockup problems. They would happen to me when I had heavy disk >access and I moved the mouse and noticed the pc locked up. >I have a Tyan 1668 For the record, I just had this exact same problem while trying to diagnose a hang on my 430HX SuperMicro board. The symptoms happened with a 4M Trident card, but are not so bad with my Matrox Millenium -- essentially any mouse motion (PS/2 or Serial mouse) will cause a hang given enough time. One thing I've noticed is that the power on the MB seems dodgy -- I have a lot of SCSI devices and I am getting rather nasty hangs during boot with 5 SCSI devices. I was able to get rid of the hangs by disabling the internal cache on the chips -- obviously not a solution, but perhaps a clue? This also seems to be related to a hang that I get with Netscape periodically with both the Matrox and the Trident card -- the results are the same (everything dies, not even pings of the machine work). For the record, the board in question is a SuperMicro P55T2S -- a Pentium board with 430HX chipset. My other 430TX board with a K6 doesn't have the problem, btw. >-----Original Message----- >From: Chuck Robey [mailto:chuckr@glue.umd.edu] >Sent: Friday, June 19, 1998 7:56 AM >To: S=F8ren Schmidt >Cc: smp@FreeBSD.ORG; FreeBSD hackers >Subject: Re: TYAN 1668 anyone ?? >On Fri, 19 Jun 1998, S=F8ren Schmidt wrote: >>=20 >> I have this most odd problem with at least 3 of these boards >> (TYAN 1668 dual P6). >>=20 >> The problem is that those boards can lock up totally given a set >> of specific events: >>=20 >> Run in a high res graphics mode, that uses linear addressing. >> Use the mouse together with disk activity. >>=20 >> This can be done in either X, win95 or winNT with the same sad >> result, a total lockup of the system. >>=20 >> If I use the mouse in a textmode, or in a graphics mode that >> uses banking, the problem doesn't appear. >>=20 >> We have tried anything here, we have the problem in 3 machines >> all of them have had their motherboards changed several times, >> we have tried different videocards, mouses, tried SCSI vs IDE, >> you name it, everytime with the same result. >>=20 >> They can all "make world" for days in an xterm, given that you >> dont touch the mouse, if you do move the mouse and hit a bottom >> that will hang the machin solid in 80% of the cases. >>=20 >> I have a TYAN 1662 board which is allmost the same just AT instead >> of ATX, and it doesn't show this behavior, even with the same >> parts put into the machine.... >>=20 >> Any ideas, I'm totally at a loss here.... >I have a 1662 with 2 PPro 166/512's here, running with a Cirrus 5436 >card, doing 1024X1280. 64 megs memory, and just as stable as a rock. >Done many hundreds of buildworlds, only once have I ever had a panic. >Using Option "linear" in my XF86Config file. >Toss a test at me if you want. I'm not using softupdates or CAM, tho, >and I only use a mouse in X. I often do the buildworlds while I'm >screwing around with something else, even netscape. I have 4 G of = >disk, >with 192M of swap. >>=20 >> >-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= >-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= >-=3D-=3D- >> S=F8ren Schmidt (sos@FreeBSD.org) FreeBSD >Core Team >> Even more code to hack -- will it ever end? >> .. >>=20 >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-smp" in the body of the message >>=20 >>=20 >----------------------------+-------------------------------------------= >---- >Chuck Robey | Interests include any kind of voice or >data=20 >chuckr@glue.umd.edu | communications topic, C programming, and >Unix. >213 Lakeside Drive Apt T-1 | >Greenbelt, MD 20770 | I run Journey2 and picnic >(FreeBSD-current) >(301) 220-2114 | and jaunt (NetBSD). >----------------------------+-------------------------------------------= >---- >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-smp" in the body of the message >------ =_NextPart_000_01BD9B90.E8266C30 >Content-Type: application/octet-stream; > name="Tony Johnson.vcf" >Content-Disposition: attachment; > filename="Tony Johnson.vcf" >BEGIN:VCARD >VERSION:2.1 >N:Johnson;Greg >FN:Tony Johnson >EMAIL;PREF;INTERNET:tjohnson@gulfsouth.verio.net >REV:19980326T195655Z >END:VCARD >------ =_NextPart_000_01BD9B90.E8266C30-- >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message -- bryan k ogawa http://www.primenet.com/~bkogawa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Jun 22 09:04:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23681 for freebsd-smp-outgoing; Mon, 22 Jun 1998 09:04:05 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from base486.home.org (imdave@imdave.pr.mcs.net [205.164.3.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23625 for ; Mon, 22 Jun 1998 09:03:59 -0700 (PDT) (envelope-from imdave@mcs.net) Received: (from imdave@localhost) by base486.home.org (8.8.8/8.8.8) id LAA01618; Mon, 22 Jun 1998 11:02:26 -0500 (CDT) Date: Mon, 22 Jun 1998 11:02:26 -0500 (CDT) From: Dave Bodenstab Message-Id: <199806221602.LAA01618@base486.home.org> To: drosih@rpi.edu, freebsd-smp@FreeBSD.ORG, imdave@mcs.net Subject: Re: Equium 6200M successfull install Cc: darrylo@sr.hp.com Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Garance A Drosihn > > And if anyone is dual-booting into WinNT, you may find that > WindowsNT dies with the blue screen of death immediately on > bootup. If this happens to you, it might mean that you have > turned off the APM support in the BIOS as part of the upgrade. The Toshiba web site: http://www.csd.toshiba.com/tais/csd/support/techsupport.html contains some info about upgrading NT for a 2nd CPU. Among other things, it requires one to uninstall Toshiba's APM software. >From your description above, I suspect that one would also need to uninstall the APM software before turning off APM in the BIOS. Dave Bodenstab imdave@mcs.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Jun 22 14:19:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23567 for freebsd-smp-outgoing; Mon, 22 Jun 1998 14:19:01 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mail.sltic.com (www.sltic.com [207.51.206.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA23424 for ; Mon, 22 Jun 1998 14:18:10 -0700 (PDT) (envelope-from info@sltic.com) From: info@sltic.com Received: from slartibartfast [207.51.206.46] by mail.sltic.com (SMTPD32-4.02) id AB9CCDFB00BC; Mon, 22 Jun 1998 16:24:44 CST6CDT Message-Id: <3.0.1.32.19980622162311.06530bb0@sltic.com> X-Sender: info@sltic.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Mon, 22 Jun 1998 16:23:11 -0500 To: freebsd-smp@FreeBSD.ORG Subject: boot freezes at npx0 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying the 3.0-980620-SNAP and after recomiling for SMP, the boot will freeze after these lines: npx0 on motherboard npx0: INT 16 interface Has anyone seen this or have a fix for this problem? Or should I go back to an earlier snap, if so what is the most recent release you feel is good? This box is an HP Netserver LS2 w/ 2 P100s, 96meg ram, dual adaptec aic7870s. Thanks, Bruce info@sltic.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 23 03:54:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17234 for freebsd-smp-outgoing; Tue, 23 Jun 1998 03:54:40 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from ers.online.sh.cn ([202.96.211.193]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA17204 for ; Tue, 23 Jun 1998 03:54:30 -0700 (PDT) (envelope-from paulk@ether.online.sh.cn) Received: from jinbo (202.120.100.126) by ers.online.sh.cn (EMWAC SMTPRS 0.81) with SMTP id ; Tue, 23 Jun 1998 18:48:30 +0800 Message-ID: <000c01bd9e94$477a7cc0$c201a8c0@jinbo.ecust.edu.cn> Reply-To: "Paul King" From: "Paul King" To: Subject: When will 3.0 release avaliable? Date: Tue, 23 Jun 1998 18:47:10 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3007.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3007.0 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When will 3.0 release avaliable? does it support Compaq SMART Array and Netflex? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 23 05:47:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06471 for freebsd-smp-outgoing; Tue, 23 Jun 1998 05:47:51 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from j51.com (root@gorplex.j51.com [209.94.121.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA06464; Tue, 23 Jun 1998 05:47:48 -0700 (PDT) (envelope-from yubyub@j51.com) Received: from tcpc54.tcam.com (tcpc54.tcam.com [198.115.45.103]) by j51.com (8.8.8/8.8.5) with SMTP id IAA28847; Tue, 23 Jun 1998 08:49:13 -0400 (EDT) Date: Tue, 23 Jun 1998 08:46:58 -0400 (Eastern Daylight Time) From: Yubyub Bird To: Søren Schmidt cc: Cyrus Rahman , smp@FreeBSD.ORG Subject: Re: S3 video cards In-Reply-To: <199806200913.LAA05181@sos.freebsd.dk> Message-ID: X-X-Sender: yubyub@j51.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id FAA06465 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 20 Jun 1998, Søren Schmidt wrote: > Hmm, I'm not so sure about your findings, I run a S3ViRGE/DX 4M cards in > my other box (also a TYAN but the 1662 AT formfactor board) with 256M > memory and I've NEVER seen it fail. > The exact same S3 board fails horribly in the 1668 (ATX form factor) > even with 32M memory, so it doesn't fit you description.... > > BTW the machine has now been up for 24+hours with the P9100 card, so the > video card has something to do with the problem... Similar but opposite experience here. I had an older P5 60Mhz mboard which I ran an S3ViRGE in (4M), and ran solid as rock for months straight. A few months ago I upgraded to the TYAN 1662 AT mboard, and the card started showing snow and garbage. I figured it may have something to do with bus speeds, tolerances, or something. I replaced the video with an S3 864, and that fixed it - haven't thought a wink about it for months. -yubyub@j51.com "I had to laugh like hell." - Vonnegut To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 23 06:02:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09467 for freebsd-smp-outgoing; Tue, 23 Jun 1998 06:02:19 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09432 for ; Tue, 23 Jun 1998 06:02:13 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id IAA08470; Tue, 23 Jun 1998 08:55:53 -0400 (EDT) Date: Tue, 23 Jun 1998 09:02:00 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: info@sltic.com cc: freebsd-smp@FreeBSD.ORG Subject: Re: boot freezes at npx0 In-Reply-To: <3.0.1.32.19980622162311.06530bb0@sltic.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 Mon, 22 Jun 1998 info@sltic.com wrote: > I'm trying the 3.0-980620-SNAP and after recomiling for > SMP, the boot will freeze after these lines: > > npx0 on motherboard > npx0: INT 16 interface > > Has anyone seen this or have a fix for this problem? Or should I > go back to an earlier snap, if so what is the most recent release > you feel is good? This box is an HP Netserver LS2 w/ 2 P100s, 96meg > ram, dual adaptec aic7870s. Not on current I havent, but I have a client with a 2.2.6-stable box that I had installed fresh, made a new custom kernel, and that kernel works but EVERY kernel after that RSFUSES to boot locking ujp at npx0. The first custom kernl i built works with npx0 just fine but EVERY kernel after that I have built FAILS and hangs at npx0 It's the most bizarra thing ive ever seen. Chris -- "Linux... The choice of a GNUtered generation." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 23 08:07:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00822 for freebsd-smp-outgoing; Tue, 23 Jun 1998 08:07:44 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00786 for ; Tue, 23 Jun 1998 08:07:31 -0700 (PDT) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id LAA01859; Tue, 23 Jun 1998 11:06:47 -0400 (EDT) (envelope-from adrian@lorax.ubergeeks.com) Date: Tue, 23 Jun 1998 11:06:47 -0400 (EDT) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Paul King cc: freebsd-smp@FreeBSD.ORG Subject: Re: When will 3.0 release avaliable? In-Reply-To: <000c01bd9e94$477a7cc0$c201a8c0@jinbo.ecust.edu.cn> 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 Tue, 23 Jun 1998, Paul King wrote: > When will 3.0 release avaliable? does it support Compaq SMART Array and > Netflex? Last week at USENIX 10/15/98 was used as the target release date for 3.0. I don't know the answer to your second question. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 23 19:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04479 for freebsd-smp-outgoing; Tue, 23 Jun 1998 19:43:32 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from gorillanet.gorilla.net (gorillanet.gorilla.net [208.128.8.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA04436 for ; Tue, 23 Jun 1998 19:43:15 -0700 (PDT) (envelope-from tom@gorilla.net) Received: from [208.143.84.52] by gorillanet.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id oa328264 for ; Tue, 23 Jun 1998 21:42:23 -0500 Received: (from tom@localhost) by gorilla.net (8.8.8/8.8.8) id VAA01507; Tue, 23 Jun 1998 21:41:49 -0500 (CDT) (envelope-from tom) Message-ID: <19980623214148.00185@TOJ.org> Date: Tue, 23 Jun 1998 21:41:49 -0500 From: Tom Jackson To: freebsd-smp@FreeBSD.ORG Subject: Running RC5 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, Is anyone successfully running this client normally. ie. running just *one* instance of the client and numcpu=2 and achieve about 2X the normal crack rate. Mine appears to crack at about 1/2 rate. A single PII-266 cracks at about 745 kkeys/s. Mine completes a block at 377 kkeys/s. Anybody have any thoughts on this? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 23 20:18:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10026 for freebsd-smp-outgoing; Tue, 23 Jun 1998 20:18:56 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from jsackett.slip.rtd.com (jsackett.slip.rtd.com [198.102.68.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10012 for ; Tue, 23 Jun 1998 20:18:51 -0700 (PDT) (envelope-from jsackett@jsackett.slip.rtd.com) Received: from jsackett.slip.rtd.com (jsackett.slip.rtd.com [198.102.68.45]) by jsackett.slip.rtd.com (8.8.8/8.8.8) with ESMTP id UAA00817; Tue, 23 Jun 1998 20:18:31 -0700 (MST) (envelope-from jsackett@jsackett.slip.rtd.com) Message-ID: <35907007.F537C820@jsackett.slip.rtd.com> Date: Tue, 23 Jun 1998 20:18:31 -0700 From: "John L. Sackett III" Reply-To: jsackett@rtd.com Organization: Sackett Enterprises X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-980520-SNAP i386) MIME-Version: 1.0 To: Tom Jackson , "freebsd-smp@freebsd.org" Subject: Re: Running RC5 References: <19980623214148.00185@TOJ.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tom Jackson wrote: > Hi all, > > Is anyone successfully running this client normally. ie. > running just *one* instance of the client and numcpu=2 > and achieve about 2X the normal crack rate. > > Mine appears to crack at about 1/2 rate. A single PII-266 > cracks at about 745 kkeys/s. Mine completes a block at > 377 kkeys/s. Anybody have any thoughts on this? > > Tom > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message set your client to 1 in the number of cpu's and run 2 processes, that's what I do. the two processes run and slice back and forth between the processors. I noticed the mt client with processors set to 2 just occupies the time of one processor. I did not notice a problem with duplication of keys, either. I also run them not very nice. John Sackett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jun 23 21:10:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19589 for freebsd-smp-outgoing; Tue, 23 Jun 1998 21:10:27 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA19487 for ; Tue, 23 Jun 1998 21:09:41 -0700 (PDT) (envelope-from seth@pengar.com) Received: from ([192.168.0.2]) [166.70.7.197] by mail.xmission.com with esmtp (Exim 1.82 #2) id 0yogsK-0004ML-00; Tue, 23 Jun 1998 22:09:36 -0600 X-Sender: seth-pc@hobbiton.shire.net Message-Id: In-Reply-To: <19980623214148.00185@TOJ.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 23 Jun 1998 22:12:34 +0100 To: Tom Jackson , freebsd-smp@FreeBSD.ORG From: Seth Leigh Subject: Re: Running RC5 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Hi all, > >Is anyone successfully running this client normally. ie. >running just *one* instance of the client and numcpu=2 >and achieve about 2X the normal crack rate. To my understanding, this can't currently be done in FreeBSD, because there is currently no type of threading that has support from the kernel for multiple threads. Without this support, the threads can't be scheduled to different processors (or be scheduled preemptively, or only block the calling thread for blocking io and other calls, etc.). I currently run two independent rc5 clients on my dual PPro 200, and each of these clients does about 526 kKeys/sec, for a total of 1052 kKeys/sec combined. Not bad at all. This is with X running, with a whole bunch of other processes (different xterms, top, etc), most of which aren't using up any significant cpu time. The absolute fastest speed I have seen on this machine was 537 kKeys/s per processor, without X, and with nothing else running. I don't have anything against running two rc5 clients. If I didn't have to I wouldn't, but it is not a problem to do it. I also run the rc5 client in an xterm rlogined into my other FreeBSD machine, which uses a Cyrix P166+ cpu. That machine does around 309 kKeys/sec. Between these two machines I get something like 450 blocks a day. Plus I have several machines at work running rc5, so I do about 1200-1500 blocks per day total. Anyways, if you absolutely have to have kernel supported threads on your machine, you'll have to go with Linux for the time being. Their LinuxThreads implementation uses one process per thread, so their threads are independently schedulable. Seth > >Mine appears to crack at about 1/2 rate. A single PII-266 >cracks at about 745 kkeys/s. Mine completes a block at >377 kkeys/s. Anybody have any thoughts on this? > >Tom > >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 Thu Jun 25 11:28:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27769 for freebsd-smp-outgoing; Thu, 25 Jun 1998 11:28:56 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from tomservo.ee.calpoly.edu (root@tomservo.ee.calpoly.edu [129.65.26.123]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27722 for ; Thu, 25 Jun 1998 11:28:33 -0700 (PDT) (envelope-from kwayman@tomservo.ee.calpoly.edu) Received: (from kwayman@localhost) by tomservo.ee.calpoly.edu (8.8.5/ELEE) id LAA10249 for freebsd-smp@FreeBSD.ORG; Thu, 25 Jun 1998 11:29:38 -0700 (PDT) From: Kyle Wayman Message-Id: <199806251829.LAA10249@tomservo.ee.calpoly.edu> Subject: Advice on SMP To: freebsd-smp@FreeBSD.ORG Date: Thu, 25 Jun 1998 11:29:37 -0700 (PDT) X-Mailer: ELM [version 2.4 PL25] 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 admin a system with about 800 users, about 3-400 moderately active. We got a new server, a dual pentium pro 200. Our old server was running FreeBSD, so it was nice to just stay with this OS so that we would be sure that all our services would continue to work on the new machine. Well, now we (my boss mostly) are anxious to get the new server up to its full potential. I want to try FreeBSD SMP but I want to know how likely it will work well enough for our needs and how hard it would be to go back to a UP system if it doesn't work out. Any help/comments would be appreciated. ----------------------------------------------------------------- = Kyle Wayman kwayman@ee.calpoly.edu = = System Administrator office: 805-756-1390 = = EE Department, Cal Poly, SLO page: 805-542-5777 = ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 25 13:37:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22277 for freebsd-smp-outgoing; Thu, 25 Jun 1998 13:37:47 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22241 for ; Thu, 25 Jun 1998 13:37:16 -0700 (PDT) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id QAA10788; Thu, 25 Jun 1998 16:39:25 -0400 (EDT) Date: Thu, 25 Jun 1998 16:39:25 -0400 (EDT) From: Mike To: Kyle Wayman cc: freebsd-smp@FreeBSD.ORG Subject: Re: Advice on SMP In-Reply-To: <199806251829.LAA10249@tomservo.ee.calpoly.edu> 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 Thu, 25 Jun 1998, Kyle Wayman wrote: > the new server up to its full potential. I want to try FreeBSD SMP > but I want to know how likely it will work well enough for our needs This depends largely upon the unique components from machine to machine, but we're running a fairly-recent 3.0-CURRENT snap with a SMP kernel and have encountered no problems. We're running dual P5 200's and dual P6 400's. Other than the CPU's, both setups are almost identical (Super Micro mb, WD Enterprise UW2 drives, Exabyte SCSI TBU, 2x128MB DIMMs, 3Com 100MB, Matrox Millenium). We're currently supporting ~10,000 users. We distribute DNS, mail, radius, ftp and http tasks across these boxes on a 24x7 basis. -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 25 17:13:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29708 for freebsd-smp-outgoing; Thu, 25 Jun 1998 17:13:28 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from compound.east.sun.com (port13.prairietech.net [208.141.230.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29568 for ; Thu, 25 Jun 1998 17:12:18 -0700 (PDT) (envelope-from alk@compound.east.sun.com) Received: (from alk@localhost) by compound.east.sun.com (8.8.8/8.7.3) id TAA01837; Thu, 25 Jun 1998 19:12:26 -0500 (CDT) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 25 Jun 1998 19:12:25 -0500 (CDT) X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: mike@seidata.com Cc: kwayman@tomservo.ee.calpoly.edu, freebsd-smp@FreeBSD.ORG Subject: Re: Advice on SMP References: <199806251829.LAA10249@tomservo.ee.calpoly.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13714.59139.307830.755598@compound.east> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoth Mike on Thu, 25 June: : we're running a fairly-recent 3.0-CURRENT snap with a SMP kernel... : We're currently supporting ~10,000 users. We distribute DNS, : mail, radius, ftp and http tasks across these boxes on a 24x7 basis. This kind of stability in a snap is more the exception than the rule, so perhaps you could be kind enough to report the specific version? Others may wish to try it, as a presumed local optimum. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 25 20:16:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22647 for freebsd-smp-outgoing; Thu, 25 Jun 1998 20:16:47 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from penelope (root@alex-va-n013c109.moon.jic.com [208.135.210.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22638 for ; Thu, 25 Jun 1998 20:16:42 -0700 (PDT) (envelope-from mbriggs@switchboard.net) Received: from penelope (really [192.168.1.1]) by penelope.ml.org via in.smtpd with smtp (ident mbriggs using rfc1413) id (Debian Smail3.2.0.101) for ; Thu, 25 Jun 1998 23:05:12 -0400 (EDT) Date: Fri, 26 Jun 1998 03:05:00 +0000 (GMT) From: "Matthew R. Briggs" X-Sender: mbriggs@penelope To: Kyle Wayman cc: freebsd-smp@FreeBSD.ORG Subject: Re: Advice on SMP In-Reply-To: <199806251829.LAA10249@tomservo.ee.calpoly.edu> 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 Kyle, I have read of people using SMP PPro systems in production environments, and doubtless they will speak up, but I just wanted to mention that I have had (and am still having) a great deal of trouble with a dual-PII system and SMP-FreeBSD. The machine locks up easily and quite predictably under load and I/O, most frequently with a "Supervisor write, page not present" kernel panic. John Dyson was working on some patches that made SMP much more workable for me (yet still not bulletproof), but he recently left the FreeBSD project, and his patches no longer apply cleanly. Best of luck...I'm no kernel hacker, but I think I may have to become one if I want to get this fixed! Matt Briggs mbriggs@switchboard.net On Thu, 25 Jun 1998, Kyle Wayman wrote: > I admin a system with about 800 users, about 3-400 moderately active. > We got a new server, a dual pentium pro 200. Our old server was > running FreeBSD, so it was nice to just stay with this OS so that > we would be sure that all our services would continue to work on > the new machine. Well, now we (my boss mostly) are anxious to get > the new server up to its full potential. I want to try FreeBSD SMP > but I want to know how likely it will work well enough for our needs > and how hard it would be to go back to a UP system if it doesn't > work out. Any help/comments would be appreciated. > > > ----------------------------------------------------------------- > = Kyle Wayman kwayman@ee.calpoly.edu = > = System Administrator office: 805-756-1390 = > = EE Department, Cal Poly, SLO page: 805-542-5777 = > ----------------------------------------------------------------- > > 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 26 00:54:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28122 for freebsd-smp-outgoing; Fri, 26 Jun 1998 00:54:42 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28108 for ; Fri, 26 Jun 1998 00:54:38 -0700 (PDT) (envelope-from fullermd@shell.futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id CAA04424; Fri, 26 Jun 1998 02:54:26 -0500 (CDT) Message-ID: <19980626025425.18638@futuresouth.com> Date: Fri, 26 Jun 1998 02:54:25 -0500 From: "Matthew D. Fuller" To: Mike Cc: Kyle Wayman , freebsd-smp@FreeBSD.ORG Subject: Re: Advice on SMP References: <199806251829.LAA10249@tomservo.ee.calpoly.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Mike on Thu, Jun 25, 1998 at 04:39:25PM -0400 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jun 25, 1998 at 04:39:25PM -0400, Mike woke me up to tell me: > On Thu, 25 Jun 1998, Kyle Wayman wrote: > > > the new server up to its full potential. I want to try FreeBSD SMP > > but I want to know how likely it will work well enough for our needs > > This depends largely upon the unique components from machine to machine, > but we're running a fairly-recent 3.0-CURRENT snap with a SMP kernel and > have encountered no problems. We're running dual P5 200's and dual P6 > 400's. P6 400's? Where do you get Pentium Pro 400's from? ;) *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 26 05:10:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26444 for freebsd-smp-outgoing; Fri, 26 Jun 1998 05:10:31 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26418 for ; Fri, 26 Jun 1998 05:10:20 -0700 (PDT) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id IAA07142; Fri, 26 Jun 1998 08:12:34 -0400 (EDT) Date: Fri, 26 Jun 1998 08:12:34 -0400 (EDT) From: Mike To: Tony Kimball cc: kwayman@tomservo.ee.calpoly.edu, freebsd-smp@FreeBSD.ORG Subject: Re: Advice on SMP In-Reply-To: <13714.59139.307830.755598@compound.east> 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 Thu, 25 Jun 1998, Tony Kimball wrote: > This kind of stability in a snap is more the exception than the rule, > so perhaps you could be kind enough to report the specific version? > Others may wish to try it, as a presumed local optimum. Yeah... doncha love getting 'lucky' on production machines? ;) Ahh, we've got mirrored REL boxes ready to come up if we run into any problems on CURRENT (my boss won't go for *total* reckless abandon ;). Maybe this will be helpful... ---8< snip >8--- Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-980520-SNAP #0: Thu Jun 4 16:01:09 EST 1998 root@ns2.seidata.com:/usr/src/sys/compile/SMP-SEI-NS1 Timecounter "i8254" frequency 1193182 Hz cost 3188 ns CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183fbff,MMX,> real memory = 268435456 (262144K bytes) avail memory = 258691072 (252628K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x01 int d irq 255 on pci0.7.2 chip4: rev 0x02 on pci0.7.3 Freeing (NOT implemented) redirected ISA irq 0. Freeing (NOT implemented) redirected ISA irq 0. Freeing (NOT implemented) redirected ISA irq 10. ahc0: rev 0x01 int a irq 16 on pci0.15.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd0 at scbus0 target 1 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 8683MB (17783204 512 byte sectors) sd1 at scbus0 target 2 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 8683MB (17783204 512 byte sectors) st0 at scbus0 target 6 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access density code 0x29, 512-byte blocks, write-enabled Freeing (NOT implemented) redirected ISA irq 15. vx0: <3COM 3C905 Fast Etherlink XL PCI> rev 0x00 int a irq 18 on pci0.18.0 mii[*mii*]: disable 'auto select' with DOS util! address 00:60:08:bd:1b:64 Probing for devices on PCI bus 1: Freeing (NOT implemented) redirected ISA irq 11. vga0: rev 0x01 int a irq 17 on pci1.0.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 ep0 not found at 0x300 npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 changing root device to sd0s1a SMP: AP CPU #1 Launched! ---8< snip >8--- Here's the exact config I'm currently running... ---8< snip >8--- # # SMP-GENERIC -- Smp machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: SMP-GENERIC,v 1.12 1998/04/29 06:58:43 max Exp $ machine "i386" # SMP does NOT support 386/486 CPUs. #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident GENERIC maxusers 100 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional, these are the defaults: #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs # Lets always enable the kernel debugger for SMP. options DDB # SMP shouldn't need x87 emulation, disable by default. #options MATH_EMULATE #Support for x87 emulation options QUOTA options INET #InterNETworking options FFS #Berkeley Fast Filesystem #options NFS #Network Filesystem #options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers #options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 controller isa0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 #tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device wcd0 #IDE CD-ROM # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. #controller ncr0 #controller amd0 #controller ahb0 controller ahc0 #controller isp0 #controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 device sd0 #device od0 #See LINT for possible `od' options. device st0 device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options PCVT_FREEBSD=210 # pcvt running on FreeBSD >= 2.0.5 #options XSERVER # include code for XFree86 #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # #device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? #device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr #device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr #device lpt0 at isa? port? tty irq 7 vector lptintr #device lpt1 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr #device psm0 at isa? disable port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device de0 #device fxp0 device vx0 #device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr #device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr #device ie1 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr device ep0 at isa? port 0x300 net irq 10 vector epintr #device ex0 at isa? port? net irq? vector exintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr pseudo-device loop pseudo-device ether #pseudo-device sl 1 # iijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device vn 1 pseudo-device tun 1 pseudo-device pty 30 pseudo-device gzip # Exec gzipped a.out's pseudo-device speaker # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. #options KTRACE #kernel tracing options SYSVSHM options SYSVSEM options SYSVMSG ---8< snip >8--- Hope this is helpful... FreeBSD is amazing. :) -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jun 26 05:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28557 for freebsd-smp-outgoing; Fri, 26 Jun 1998 05:31:02 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28542 for ; Fri, 26 Jun 1998 05:30:54 -0700 (PDT) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id IAA09479; Fri, 26 Jun 1998 08:33:13 -0400 (EDT) Date: Fri, 26 Jun 1998 08:33:13 -0400 (EDT) From: Mike To: "Matthew D. Fuller" cc: Kyle Wayman , freebsd-smp@FreeBSD.ORG Subject: Re: Advice on SMP In-Reply-To: <19980626025425.18638@futuresouth.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, 26 Jun 1998, Matthew D. Fuller wrote: > P6 400's? > Where do you get Pentium Pro 400's from? ;) Foo-pah. Let's make that P2 400's and P6 200's. :) -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message