From owner-freebsd-smp Tue Jan 6 19:43:47 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA02271 for smp-outgoing; Tue, 6 Jan 1998 19:43:47 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from xoom.com (host074.xoom.com [207.90.142.74]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA02262; Tue, 6 Jan 1998 19:43:44 -0800 (PST) (envelope-from dpsmith@xoom.com) Received: from mail1.xoom.com (host074.xoom.com [207.90.142.74]) by xoom.com (8.8.8/8.8.8) with SMTP id TAA04703; Tue, 6 Jan 1998 19:42:42 -0800 (PST) Date: Tue, 6 Jan 1998 19:42:42 -0800 (PST) From: Dave Smith To: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Subject: Remote power cycle Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I want to remotely power cycle machines at our colocation because they tend to hang on reboots because of zombies or just hang. They are FreeBSD 3.0 and 2.2.5 boxes. Our colocation has a good power supply with a backup generator so an UPS is kind of redundant. I don't want to use a phone line to connect to a device which can power cycle machines. I would prefer to telnet into either a FreeBSD box which does nothing or the power cycling device if that is possible. Why? Because we will be moving from our current colocation to a new colocation in the next few weeks and it would be a waste of time and would probably take a few weeks to get the phone line installed. Granted telneting into a FreeBSD box which might itself hang is a single point of failure, but I can live with it. All help, ideas, suggestions would be much appreciated. I've looked around the archives and could only find some advice for a device which one dials into, to remotely power cycle machines. Dave. From owner-freebsd-smp Tue Jan 6 20:48:29 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA07368 for smp-outgoing; Tue, 6 Jan 1998 20:48:29 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from cs.utah.edu (cs.utah.edu [128.110.4.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA07328; Tue, 6 Jan 1998 20:48:16 -0800 (PST) (envelope-from vanmaren@fast.cs.utah.edu) Received: from fast.cs.utah.edu by cs.utah.edu (8.8.4/utah-2.21-cs) id VAA01303; Tue, 6 Jan 1998 21:48:11 -0700 (MST) Received: by fast.cs.utah.edu (8.6.10/utah-2.15-leaf) id VAA04209; Tue, 6 Jan 1998 21:48:10 -0700 Date: Tue, 6 Jan 1998 21:48:10 -0700 From: vanmaren@fast.cs.utah.edu (Kevin Van Maren) Message-Id: <199801070448.VAA04209@fast.cs.utah.edu> To: dpsmith@xoom.com, freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Remote power cycle Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I built a few power controllers out of relay cards, a serial interface, extension cords, and old disk/tape enclosures. However, I would recommend that you simply buy a `power board' from APC. I've never used one, but you can look at http://www.apcc.com/english/prods/acsry/mster/ for some infor on the APC MasterSwitch E515. It should cost somewhere around $450 for 8 ports. Kevin (BTW, why is this a SMP question?) From owner-freebsd-smp Tue Jan 6 21:03:17 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA09780 for smp-outgoing; Tue, 6 Jan 1998 21:03:17 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from news.quick.net (donegan@news.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA09770 for ; Tue, 6 Jan 1998 21:03:12 -0800 (PST) (envelope-from donegan@news.quick.net) Received: (from donegan@localhost) by news.quick.net (8.8.5/8.6.9) id VAA15724; Tue, 6 Jan 1998 21:03:09 -0800 (PST) Date: Tue, 6 Jan 1998 21:03:08 -0800 (PST) From: "Steven P. Donegan" To: freebsd-smp@freebsd.org Subject: Problem with Tyan IIID and P166's (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I mistakenly sent this to 'current'. Note what seems to me to be the key item is the MMX detection when the chips are not MMX. ---------- Forwarded message ---------- Date: Tue, 6 Jan 1998 16:08:07 -0800 (PST) From: Steven P. Donegan To: current@freebsd.org Subject: Problem with Tyan IIID and P166's Today I swapped my dual P100's for dual P166's (not MMX). All goes well until the 1st AP is launched and then it hangs. Put the 100's back and no problem. The only thing I noted is that the boot code seems to think the 166's have MMX capability - they don't. Any ideas? I'd really like to speed up a bit :-) (the 200's I had on order are back ordered and I just couldn't wait :-) TIA BTW - thanks to all of you who recommended the AH2940UW SCSI controller. It works like a charm. From owner-freebsd-smp Tue Jan 6 22:29:10 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA16448 for smp-outgoing; Tue, 6 Jan 1998 22:29:10 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA16441; Tue, 6 Jan 1998 22:29:04 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA07983; Tue, 6 Jan 1998 22:28:22 -0800 (PST) Message-Id: <199801070628.WAA07983@implode.root.com> To: Dave Smith cc: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Remote power cycle In-reply-to: Your message of "Tue, 06 Jan 1998 19:42:42 PST." From: David Greenman Reply-To: dg@root.com Date: Tue, 06 Jan 1998 22:28:22 -0800 Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I want to remotely power cycle machines at our colocation because >they tend to hang on reboots because of zombies or just hang. > >They are FreeBSD 3.0 and 2.2.5 boxes. Our colocation has a good power supply >with a backup generator so an UPS is kind of redundant. > >I don't want to use a phone line to connect to a device which can >power cycle machines. I would prefer to telnet into either a FreeBSD >box which does nothing or the power cycling device if that is >possible. > >Why? Because we will be moving from our current colocation to a new >colocation in the next few weeks and it would be a waste of time and >would probably take a few weeks to get the phone line installed. > >Granted telneting into a FreeBSD box which might itself hang >is a single point of failure, but I can live with it. > >All help, ideas, suggestions would be much appreciated. > >I've looked around the archives and could only find >some advice for a device which one dials into, to remotely >power cycle machines. I wrote this recently: ... For wcarchive, I use the BOOT_FORCE_COMCONSOLE make option. I run gettys on the vga virtual ttys so I can log in when I'm sitting in front of the machine, but the console is always on the serial port. The console serial port is connected to another PC (the "remote console" machine). I always have an rlogin/kermit session open on the console in an xterm here with the xterm configured to log all output to a logfile. When I need to use the console while physically in front of the machine, I just plug the serial cable into a laptop. The remote console machine also has an internal modem that I hacked to function as a reset switch whenever it goes off hook to dial - I use this to reset wcarchive if necessary. I have a watchdog process running on the remote console which pings wcarchive every minute or so, and if the pings start failing, wcarchive is automatically reset (I have a kermit dialout script for this :-)). ... It's never been necessary to power cycle the machine, and considering how much hardware is involved, that's a good thing. :-) -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-smp Tue Jan 6 23:07:08 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA18984 for smp-outgoing; Tue, 6 Jan 1998 23:07:08 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from xoom.com (host074.xoom.com [207.90.142.74]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA18977; Tue, 6 Jan 1998 23:07:04 -0800 (PST) (envelope-from dpsmith@xoom.com) Received: from mail1.xoom.com (host074.xoom.com [207.90.142.74]) by xoom.com (8.8.8/8.8.8) with SMTP id XAA06165; Tue, 6 Jan 1998 23:05:59 -0800 (PST) Date: Tue, 6 Jan 1998 23:05:59 -0800 (PST) From: Dave Smith To: David Greenman cc: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Remote power cycle In-Reply-To: <199801070628.WAA07983@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I wrote this recently: > > ... > For wcarchive, I use the BOOT_FORCE_COMCONSOLE make option. I run gettys In my kernel config files: On the FreeBSD 3.0 machines I do: device sio0 at isa? port "IO_COM1" tty flags 0x30 irq 4 vector siointr On the FreeBSD 2.2.5 machines I do: options COMCONSOLE These work for me. Once the kernel loads I see the boot messages which are something I need when I am installing new machines at our colocation with a laptop hooked up to the serial com1 port. > on the vga virtual ttys so I can log in when I'm sitting in front of the > machine, but the console is always on the serial port. The console serial > port is connected to another PC (the "remote console" machine). I always have > an rlogin/kermit session open on the console in an xterm here with the xterm > configured to log all output to a logfile. When I need to use the console > while physically in front of the machine, I just plug the serial cable into I am setting up a terminal server with 2 16-9pin port Digiboards and 1 db25 port. I am waiting for our hardware supplier to get all the pieces together for me so I can set it up. I hope it works. I scoured the list and it was either Digiboard (or whatever it is called, starts with Digi) or Cyclades. > a laptop. The remote console machine also has an internal modem that I hacked > to function as a reset switch whenever it goes off hook to dial - I use this > to reset wcarchive if necessary. I have a watchdog process running on the > remote console which pings wcarchive every minute or so, and if the pings > start failing, wcarchive is automatically reset (I have a kermit dialout > script for this :-)). > ... This I do not do, and I would like to know more about the watchdog process and how you do the auto reset. And how did you hack an internal modem to act as a reset switch? Pings would be difficult for me because of our configuration it looks like machines are up all the time. We use a product called BigIP from f5.com. It does fancy load-balancing like the Cisco LocalDirector. However some sort of ping to port 23 would work for me. > > It's never been necessary to power cycle the machine, and considering how > much hardware is involved, that's a good thing. :-) I know it is a bad thing. I could only think of a good swift power cycle when machines are not responding. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project > From owner-freebsd-smp Wed Jan 7 00:26:16 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA28034 for smp-outgoing; Wed, 7 Jan 1998 00:26:16 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA27984; Wed, 7 Jan 1998 00:26:04 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA02435; Wed, 7 Jan 1998 19:21:56 +1100 Date: Wed, 7 Jan 1998 19:21:56 +1100 From: Bruce Evans Message-Id: <199801070821.TAA02435@godzilla.zeta.org.au> To: dg@root.com, dpsmith@xoom.com Subject: Re: Remote power cycle Cc: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >... > For wcarchive, I use the BOOT_FORCE_COMCONSOLE make option. I run gettys This option doesn't exist in 2.2.5 or 3.0. You set flags on the desired serial console instead. See sio(4) in 3.0. The documentation is out of date in 2.2.5. Bruce From owner-freebsd-smp Wed Jan 7 00:47:35 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA02228 for smp-outgoing; Wed, 7 Jan 1998 00:47:35 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA02214; Wed, 7 Jan 1998 00:47:28 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA03138; Wed, 7 Jan 1998 19:44:00 +1100 Date: Wed, 7 Jan 1998 19:44:00 +1100 From: Bruce Evans Message-Id: <199801070844.TAA03138@godzilla.zeta.org.au> To: bde@zeta.org.au, dg@root.com, dpsmith@xoom.com Subject: Re: Remote power cycle Cc: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>... >> For wcarchive, I use the BOOT_FORCE_COMCONSOLE make option. I run gettys I wrote: >This option doesn't exist in 2.2.5 or 3.0. You set flags on the desired >serial console instead. See sio(4) in 3.0. The documentation is out of >date in 2.2.5. Oops, the serial console flags don't exist in 2.2.5. Only 2.2.5's /etc/make.conf is out of date. It "documents" the wrong BOOT* make options. 2.2.5's README.serial is anachronistic. It documents the 3.0 serial console flags which don't exist in 2.2.5. Bruce From owner-freebsd-smp Wed Jan 7 01:06:31 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA04076 for smp-outgoing; Wed, 7 Jan 1998 01:06:31 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA04061; Wed, 7 Jan 1998 01:06:25 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA03103; Wed, 7 Jan 1998 18:04:52 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id SAA09026; Wed, 7 Jan 1998 18:12:09 +0900 (JST) Message-Id: <199801070912.SAA09026@zodiac.mech.utsunomiya-u.ac.jp> To: Bruce Evans Cc: dg@root.com, dpsmith@xoom.com, freebsd-questions@freebsd.org, freebsd-smp@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Remote power cycle In-Reply-To: Your message of "Wed, 07 Jan 1998 19:21:56 +1100." <199801070821.TAA02435@godzilla.zeta.org.au> References: <199801070821.TAA02435@godzilla.zeta.org.au> Date: Wed, 07 Jan 1998 18:12:09 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>... >> For wcarchive, I use the BOOT_FORCE_COMCONSOLE make option. I run gettys > >This option doesn't exist in 2.2.5 or 3.0. You set flags on the desired >serial console instead. See sio(4) in 3.0. The documentation is out of >date in 2.2.5. > >Bruce BOOT_FORCE_COMCONSOLE doesn't exist in both 2.2.5 and 3.0. But, the serial console flags exist only in 3.0 yet. And yes, the documentation in 2.2.5 is VERY confusing ;-< Under 3.0 you do: 1. Put '-h' in /boot.config, 2. and set flags to 0x10 on the desired serial device. You may switch to the internal (video card) console, if you like, by toggling '-h' at "boot:" prompt. Or 1. Set flags to 0x20 on the desired serial device to force the serial console, regardless of the state of the -h option. Under 2.2.5 you do: 1. Put '-h' in /boot.config and COM0 will be the console. You may switch to the internal (video card) console, if you like, by toggling '-h' at "boot:" prompt. Or 1. Use options COMCONSOLE in your kernel configuration file to force COM0 to be the console, regardless of the state of the -h option. Kazu From owner-freebsd-smp Wed Jan 7 01:56:42 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA07223 for smp-outgoing; Wed, 7 Jan 1998 01:56:42 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA07215; Wed, 7 Jan 1998 01:56:39 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id BAA09833; Wed, 7 Jan 1998 01:55:53 -0800 (PST) Message-Id: <199801070955.BAA09833@implode.root.com> To: Bruce Evans cc: dpsmith@xoom.com, freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Remote power cycle In-reply-to: Your message of "Wed, 07 Jan 1998 19:21:56 +1100." <199801070821.TAA02435@godzilla.zeta.org.au> From: David Greenman Reply-To: dg@root.com Date: Wed, 07 Jan 1998 01:55:53 -0800 Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>... >> For wcarchive, I use the BOOT_FORCE_COMCONSOLE make option. I run gettys > >This option doesn't exist in 2.2.5 or 3.0. You set flags on the desired >serial console instead. See sio(4) in 3.0. The documentation is out of >date in 2.2.5. The "BOOT_FORCE_COMCONSOLE" option was an option to building the bootblocks, not a kernel option, so I don't see how sio() flags has anything to do with it. That said, the option went away in 2.2, and now this is done with BOOT_COMCONSOLE_PORT, I guess. I haven't rebuilt the bootblocks since 2.1, so I didn't notice the change. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-smp Wed Jan 7 08:42:07 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA13458 for smp-outgoing; Wed, 7 Jan 1998 08:42:07 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA13448; Wed, 7 Jan 1998 08:42:03 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id KAA06079; Wed, 7 Jan 1998 10:40:08 -0600 (CST) From: Kevin Day Message-Id: <199801071640.KAA06079@home.dragondata.com> Subject: Re: Remote power cycle In-Reply-To: <199801070955.BAA09833@implode.root.com> from David Greenman at "Jan 7, 98 01:55:53 am" To: dg@root.com Date: Wed, 7 Jan 1998 10:40:08 -0600 (CST) Cc: bde@zeta.org.au, dpsmith@xoom.com, freebsd-questions@freebsd.org, freebsd-smp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The "BOOT_FORCE_COMCONSOLE" option was an option to building the > bootblocks, not a kernel option, so I don't see how sio() flags has > anything to do with it. That said, the option went away in 2.2, and > now this is done with BOOT_COMCONSOLE_PORT, I guess. I haven't rebuilt > the bootblocks since 2.1, so I didn't notice the change. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project > I'm also using the serial console to monitor machines, and remotely reboot them when necessary. (I'm working on using X10 stuff to actually cycle power for me) However, for now, even when the serial console is still running, but the machine is mostly dead, I can never get reboot to work... It tells me some processess would not die, ps axl advised - then it locks up. I've even tried reboot -q or reboot -n and got nowhere. Is there a better way of recovering for this? Kevin From owner-freebsd-smp Thu Jan 8 02:20:49 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA29548 for smp-outgoing; Thu, 8 Jan 1998 02:20:49 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA29539; Thu, 8 Jan 1998 02:20:44 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA04517; Thu, 8 Jan 1998 21:19:07 +1100 Date: Thu, 8 Jan 1998 21:19:07 +1100 From: Bruce Evans Message-Id: <199801081019.VAA04517@godzilla.zeta.org.au> To: dg@root.com, toasty@home.dragondata.com Subject: Re: Remote power cycle Cc: bde@zeta.org.au, dpsmith@xoom.com, freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >However, for now, even when the serial console is still running, but the >machine is mostly dead, I can never get reboot to work... It tells me some >processess would not die, ps axl advised - then it locks up. > >I've even tried reboot -q or reboot -n and got nowhere. Is there a better >way of recovering for this? Kill the offending processes before rebooting, or unmount nfs file systems before rebooting. The hang seems to be caused by bugs in nfs. I use: sync umount -Af -t nfs reboot Bruce From owner-freebsd-smp Thu Jan 8 06:35:26 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA19677 for smp-outgoing; Thu, 8 Jan 1998 06:35:26 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from lt.irbs.com (lt.irbs.com [209.36.63.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA19661 for ; Thu, 8 Jan 1998 06:35:18 -0800 (PST) (envelope-from jc@lt.irbs.com) Received: (from jc@localhost) by lt.irbs.com (8.8.8/8.8.7) id JAA00389; Thu, 8 Jan 1998 09:34:45 -0500 (EST) (envelope-from jc) Message-ID: <19980108093445.36836@irbs.com> Date: Thu, 8 Jan 1998 09:34:45 -0500 From: John Capo To: freebsd-smp@freebsd.org Subject: SMP and 440LX Chipset Reply-To: jc@irbs.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can anyone confirm that a SMP kernel works with a 440LX chipset? I'm considering a Supermicro P6DLF. John Capo From owner-freebsd-smp Thu Jan 8 10:02:00 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA08322 for smp-outgoing; Thu, 8 Jan 1998 10:02:00 -0800 (PST) (envelope-from owner-freebsd-smp) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08316 for ; Thu, 8 Jan 1998 10:01:51 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id LAA07788; Thu, 8 Jan 1998 11:01:33 -0700 (MST) Message-Id: <199801081801.LAA07788@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: jc@irbs.com cc: freebsd-smp@freebsd.org Subject: Re: SMP and 440LX Chipset In-reply-to: Your message of "Thu, 08 Jan 1998 09:34:45 EST." <19980108093445.36836@irbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Jan 1998 11:01:32 -0700 Sender: owner-freebsd-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > Can anyone confirm that a SMP kernel works with a 440LX chipset? > > I'm considering a Supermicro P6DLF. I brought up SMP on an ASUS dual PII-300 last weekend with no problems! This board uses thew LX chipset. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD