From owner-freebsd-smp Fri Sep 10 5:31:13 1999 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 3CBA314DB5; Fri, 10 Sep 1999 05:31:07 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb10.imasy.or.jp [202.227.24.138]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id VAA12112; Fri, 10 Sep 1999 21:30:45 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199909101230.VAA12112@tasogare.imasy.or.jp> To: stable@FreeBSD.ORG Cc: smp@FreeBSD.ORG, jkh@FreeBSD.org, iwasaki@jp.FreeBSD.ORG Subject: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 10 Sep 1999 21:33:53 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 68 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, If you have problems on 3.3-RC SMP system with APM enabled, please test the attached patch and give feedback to me ASAP. The problem I was reported is that a lot of userland programs get signal 11 and core dumped on startup. It seems my bad MCF (8/24) breaks extra GDT entries for SMP. The following patch was already tested among folks in Japan, I want fix this before 3.3-RELEASE. My I commit this for RELENG_3 if somebody reports `fixed!' ? Index: i386/apm/apm.c =================================================================== RCS file: /home/ncvs/src/sys/i386/apm/apm.c,v retrieving revision 1.77.2.6 diff -u -r1.77.2.6 apm.c --- apm.c 1999/08/29 16:04:32 1.77.2.6 +++ apm.c 1999/09/10 11:57:40 @@ -20,7 +20,6 @@ #include "opt_devfs.h" #include "opt_vm86.h" -#include "opt_smp.h" #include #include @@ -53,10 +52,6 @@ #include #endif -#ifdef SMP -#include -#endif - static int apm_display __P((int newstate)); static int apm_int __P((u_long *eax, u_long *ebx, u_long *ecx, u_long *edx)); static void apm_resume __P((void)); @@ -127,10 +122,6 @@ static void setup_apm_gdt(u_int code32_base, u_int code16_base, u_int data_base, u_int code32_limit, u_int code16_limit, u_int data_limit) { -#ifdef SMP - int x; -#endif - /* setup 32bit code segment */ gdt_segs[GAPMCODE32_SEL].ssd_base = code32_base; gdt_segs[GAPMCODE32_SEL].ssd_limit = code32_limit; @@ -147,14 +138,6 @@ ssdtosd(gdt_segs + GAPMCODE32_SEL, &gdt[GAPMCODE32_SEL].sd); ssdtosd(gdt_segs + GAPMCODE16_SEL, &gdt[GAPMCODE16_SEL].sd); ssdtosd(gdt_segs + GAPMDATA_SEL , &gdt[GAPMDATA_SEL ].sd); - -#ifdef SMP - for (x = 1; x < NCPU; x++) { - gdt[x * NGDT + GAPMCODE32_SEL].sd = gdt[GAPMCODE32_SEL].sd; - gdt[x * NGDT + GAPMCODE16_SEL].sd = gdt[GAPMCODE16_SEL].sd; - gdt[x * NGDT + GAPMDATA_SEL ].sd = gdt[GAPMDATA_SEL ].sd; - } -#endif } /* 48bit far pointer. Do not staticize - used from apm_setup.s */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 6:55:52 1999 Delivered-To: freebsd-smp@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id C039E14E72; Fri, 10 Sep 1999 06:55:39 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id JAA12917; Fri, 10 Sep 1999 09:54:29 -0400 (EDT) (envelope-from luoqi) Date: Fri, 10 Sep 1999 09:54:29 -0400 (EDT) From: Luoqi Chen Message-Id: <199909101354.JAA12917@lor.watermarkgroup.com> To: iwasaki@jp.FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX Cc: jkh@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmm, this change doesn't belong in -stable. I remember I committed it to the head of the branch, how does it end up in -stable? It should definitely be taken out. -lq > Hi, > > If you have problems on 3.3-RC SMP system with APM enabled, > please test the attached patch and give feedback to me ASAP. > > The problem I was reported is that a lot of userland programs get > signal 11 and core dumped on startup. It seems my bad MCF (8/24) > breaks extra GDT entries for SMP. > > The following patch was already tested among folks in Japan, I > want fix this before 3.3-RELEASE. > > > My I commit this for RELENG_3 if somebody reports `fixed!' ? > > > Index: i386/apm/apm.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/apm/apm.c,v > retrieving revision 1.77.2.6 > diff -u -r1.77.2.6 apm.c > --- apm.c 1999/08/29 16:04:32 1.77.2.6 > +++ apm.c 1999/09/10 11:57:40 > @@ -20,7 +20,6 @@ > > #include "opt_devfs.h" > #include "opt_vm86.h" > -#include "opt_smp.h" > > #include > #include > @@ -53,10 +52,6 @@ > #include > #endif > > -#ifdef SMP > -#include > -#endif > - > static int apm_display __P((int newstate)); > static int apm_int __P((u_long *eax, u_long *ebx, u_long *ecx, u_long *edx)); > static void apm_resume __P((void)); > @@ -127,10 +122,6 @@ > static void > setup_apm_gdt(u_int code32_base, u_int code16_base, u_int data_base, u_int code32_limit, u_int code16_limit, u_int data_limit) > { > -#ifdef SMP > - int x; > -#endif > - > /* setup 32bit code segment */ > gdt_segs[GAPMCODE32_SEL].ssd_base = code32_base; > gdt_segs[GAPMCODE32_SEL].ssd_limit = code32_limit; > @@ -147,14 +138,6 @@ > ssdtosd(gdt_segs + GAPMCODE32_SEL, &gdt[GAPMCODE32_SEL].sd); > ssdtosd(gdt_segs + GAPMCODE16_SEL, &gdt[GAPMCODE16_SEL].sd); > ssdtosd(gdt_segs + GAPMDATA_SEL , &gdt[GAPMDATA_SEL ].sd); > - > -#ifdef SMP > - for (x = 1; x < NCPU; x++) { > - gdt[x * NGDT + GAPMCODE32_SEL].sd = gdt[GAPMCODE32_SEL].sd; > - gdt[x * NGDT + GAPMCODE16_SEL].sd = gdt[GAPMCODE16_SEL].sd; > - gdt[x * NGDT + GAPMDATA_SEL ].sd = gdt[GAPMDATA_SEL ].sd; > - } > -#endif > } > > /* 48bit far pointer. Do not staticize - used from apm_setup.s */ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 7:33: 9 1999 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 E46AF14E7E; Fri, 10 Sep 1999 07:33:02 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb42.imasy.or.jp [202.227.24.170]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id XAA23905; Fri, 10 Sep 1999 23:32:45 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199909101432.XAA23905@tasogare.imasy.or.jp> To: luoqi@watermarkgroup.com Cc: iwasaki@jp.FreeBSD.ORG, stable@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX In-Reply-To: Your message of "Fri, 10 Sep 1999 09:54:29 -0400 (EDT)" <199909101354.JAA12917@lor.watermarkgroup.com> References: <199909101354.JAA12917@lor.watermarkgroup.com> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 10 Sep 1999 23:35:43 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 12 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > Hmm, this change doesn't belong in -stable. I remember I committed it > to the head of the branch, how does it end up in -stable? It should > definitely be taken out. Yes, it's my fault, I'm sorry for this. I brought this fix to STABLE in my MFC (1.77 -> 1.77.2.1), however there was nothing to fix on STABLE SMP actually... I'm going to back my change as soon as getting reports. # Maybe I need to have SMP system to test with my hack :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 7:53: 6 1999 Delivered-To: freebsd-smp@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 7988614E7E; Fri, 10 Sep 1999 07:52:51 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id F0BE61CA8; Fri, 10 Sep 1999 22:52:17 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen Cc: iwasaki@jp.FreeBSD.ORG, stable@FreeBSD.ORG, jkh@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX In-reply-to: Your message of "Fri, 10 Sep 1999 09:54:29 -0400." <199909101354.JAA12917@lor.watermarkgroup.com> Date: Fri, 10 Sep 1999 22:52:17 +0800 From: Peter Wemm Message-Id: <19990910145217.F0BE61CA8@overcee.netplex.com.au> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Luoqi Chen wrote: > Hmm, this change doesn't belong in -stable. I remember I committed it > to the head of the branch, how does it end up in -stable? It should > definitely be taken out. BTW; to quote Linux's Alan Cox on one thread over SMP vs APM problems and hacks that partially work under Linux: "APM will never be SMP safe, the problem is at the BIOS level not Linux" I've re-read the mpspec 1.4.6 stuff and I can't find a single mention of APM in it. IMHO, it's a pretty safe assumption that APM should not be called for anything more than things like ATX poweroff under SMP, and even that's probably best to defer until after all the AP's have been halted. Things like suspend, cpuclock slowdown, idle showdown etc are seriously bad for SMP systems as the cpu calling the bios will be the one affected. (eg: a suspend-to-disk will put the calling CPU into SMI mode and dump it's state to disk... the other poor cpu's context is going to be lost, and indeed the other cpu will continue running *during* the suspend-to-disk...) For stuff like this to work, we're going to need to do a lot of sync work to get the AP's sufficiently quiescent so no damage is done while the APM code is active, and so that we can reboot the AP's after a suspend-to-disk recovery. > -lq > > > Hi, > > > > If you have problems on 3.3-RC SMP system with APM enabled, > > please test the attached patch and give feedback to me ASAP. > > > > The problem I was reported is that a lot of userland programs get > > signal 11 and core dumped on startup. It seems my bad MCF (8/24) > > breaks extra GDT entries for SMP. > > > > The following patch was already tested among folks in Japan, I > > want fix this before 3.3-RELEASE. > > > > > > My I commit this for RELENG_3 if somebody reports `fixed!' ? > > > > > > Index: i386/apm/apm.c > > =================================================================== > > RCS file: /home/ncvs/src/sys/i386/apm/apm.c,v > > retrieving revision 1.77.2.6 > > diff -u -r1.77.2.6 apm.c > > --- apm.c 1999/08/29 16:04:32 1.77.2.6 > > +++ apm.c 1999/09/10 11:57:40 > > @@ -20,7 +20,6 @@ > > > > #include "opt_devfs.h" > > #include "opt_vm86.h" > > -#include "opt_smp.h" > > > > #include > > #include > > @@ -53,10 +52,6 @@ > > #include > > #endif > > > > -#ifdef SMP > > -#include > > -#endif > > - > > static int apm_display __P((int newstate)); > > static int apm_int __P((u_long *eax, u_long *ebx, u_long *ecx, u_long *edx )); > > static void apm_resume __P((void)); > > @@ -127,10 +122,6 @@ > > static void > > setup_apm_gdt(u_int code32_base, u_int code16_base, u_int data_base, u_int code32_limit, u_int code16_limit, u_int data_limit) > > { > > -#ifdef SMP > > - int x; > > -#endif > > - > > /* setup 32bit code segment */ > > gdt_segs[GAPMCODE32_SEL].ssd_base = code32_base; > > gdt_segs[GAPMCODE32_SEL].ssd_limit = code32_limit; > > @@ -147,14 +138,6 @@ > > ssdtosd(gdt_segs + GAPMCODE32_SEL, &gdt[GAPMCODE32_SEL].sd); > > ssdtosd(gdt_segs + GAPMCODE16_SEL, &gdt[GAPMCODE16_SEL].sd); > > ssdtosd(gdt_segs + GAPMDATA_SEL , &gdt[GAPMDATA_SEL ].sd); > > - > > -#ifdef SMP > > - for (x = 1; x < NCPU; x++) { > > - gdt[x * NGDT + GAPMCODE32_SEL].sd = gdt[GAPMCODE32_SEL].sd; > > - gdt[x * NGDT + GAPMCODE16_SEL].sd = gdt[GAPMCODE16_SEL].sd; > > - gdt[x * NGDT + GAPMDATA_SEL ].sd = gdt[GAPMDATA_SEL ].sd; > > - } > > -#endif > > } > > > > /* 48bit far pointer. Do not staticize - used from apm_setup.s */ > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 9:59: 8 1999 Delivered-To: freebsd-smp@freebsd.org Received: from garnet.sover.net (garnet.sover.net [209.198.87.53]) by hub.freebsd.org (Postfix) with ESMTP id EF3E114BCF; Fri, 10 Sep 1999 09:58:56 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc0a317.bf.sover.net [209.198.83.225]) by garnet.sover.net (8.9.3/8.9.3) with ESMTP id MAA08744; Fri, 10 Sep 1999 12:57:08 -0400 (EDT) Comments: SoVerNet Verification (on garnet.sover.net) nightfall.digitalspark.net from arc0a317.bf.sover.net [209.198.83.225] 209.198.83.225 Fri, 10 Sep 1999 12:57:08 -0400 (EDT) Date: Fri, 10 Sep 1999 13:00:47 +0000 (GMT) From: Adam Strohl To: Peter Wemm Cc: Luoqi Chen , iwasaki@jp.FreeBSD.ORG, stable@FreeBSD.ORG, jkh@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX In-Reply-To: <19990910145217.F0BE61CA8@overcee.netplex.com.au> 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 Hmmm, I was thinking (uh-oh): Actually, all you really need to do is get the ability to set a processes' affinity working. When you call something like suspend, etc, move everything off the AP(s) then preform the call. Basically like in BeOS disabling a CPU with the CPU tool. Of course this'd require losts of work, but it'd be work that was already needed. Let me know if that's the stupidest thing you've ever heard, it sounds reasonable to me, but I'm not a kernel developer ;'D - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - On Fri, 10 Sep 1999, Peter Wemm wrote: > Luoqi Chen wrote: > > Hmm, this change doesn't belong in -stable. I remember I committed it > > to the head of the branch, how does it end up in -stable? It should > > definitely be taken out. > > BTW; to quote Linux's Alan Cox on one thread over SMP vs APM problems > and hacks that partially work under Linux: > "APM will never be SMP safe, the problem is at the BIOS level not Linux" > > I've re-read the mpspec 1.4.6 stuff and I can't find a single mention of > APM in it. > > IMHO, it's a pretty safe assumption that APM should not be called for > anything more than things like ATX poweroff under SMP, and even that's > probably best to defer until after all the AP's have been halted. Things > like suspend, cpuclock slowdown, idle showdown etc are seriously bad for > SMP systems as the cpu calling the bios will be the one affected. (eg: a > suspend-to-disk will put the calling CPU into SMI mode and dump it's state > to disk... the other poor cpu's context is going to be lost, and indeed the > other cpu will continue running *during* the suspend-to-disk...) > > For stuff like this to work, we're going to need to do a lot of sync work > to get the AP's sufficiently quiescent so no damage is done while the APM > code is active, and so that we can reboot the AP's after a suspend-to-disk > recovery. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 10:26: 3 1999 Delivered-To: freebsd-smp@freebsd.org Received: from dingo.cdrom.com (castles529.castles.com [208.214.165.93]) by hub.freebsd.org (Postfix) with ESMTP id BC59E1529D; Fri, 10 Sep 1999 10:25:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id KAA03219; Fri, 10 Sep 1999 10:19:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909101719.KAA03219@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen Cc: iwasaki@jp.FreeBSD.ORG, stable@FreeBSD.ORG, jkh@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX In-reply-to: Your message of "Fri, 10 Sep 1999 09:54:29 EDT." <199909101354.JAA12917@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Sep 1999 10:19:22 -0700 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hmm, this change doesn't belong in -stable. I remember I committed it > to the head of the branch, how does it end up in -stable? It should > definitely be taken out. It was merged after a request for comment didn't elict any responses. Do you want to see the original patchset for the merge, in case something else undesired came in? -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Sep 10 12:18:17 1999 Delivered-To: freebsd-smp@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id E4732150CD; Fri, 10 Sep 1999 12:18:05 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id PAA17952; Fri, 10 Sep 1999 15:17:30 -0400 (EDT) (envelope-from luoqi) Date: Fri, 10 Sep 1999 15:17:30 -0400 (EDT) From: Luoqi Chen Message-Id: <199909101917.PAA17952@lor.watermarkgroup.com> To: luoqi@watermarkgroup.com, mike@smith.net.au Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX Cc: iwasaki@jp.FreeBSD.ORG, jkh@FreeBSD.ORG, smp@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Hmm, this change doesn't belong in -stable. I remember I committed it > > to the head of the branch, how does it end up in -stable? It should > > definitely be taken out. > > It was merged after a request for comment didn't elict any responses. > Do you want to see the original patchset for the merge, in case > something else undesired came in? > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com > I'm sorry I didn't see the message. I checked the cvs log, it was merged on 8/24. I wasn't following the mailing list for the two weeks prior to Labor day. I went through the diff, only this SMP related change should be taken out (well, I know nothing about other changes, I presume they are fine). -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 12:28: 3 1999 Delivered-To: freebsd-smp@freebsd.org Received: from c008.sfo.cp.net (c008-h008.c008.sfo.cp.net [209.228.14.197]) by hub.freebsd.org (Postfix) with SMTP id 9C77E1549F for ; Fri, 10 Sep 1999 12:27:55 -0700 (PDT) (envelope-from williamdwoods@etrademail.com) Received: (cpmta 26521 invoked from network); 10 Sep 1999 12:27:55 -0700 Date: 10 Sep 1999 12:27:54 -0700 Message-ID: <19990910192754.26520.cpmta@c008.sfo.cp.net> X-Sent: 10 Sep 1999 19:27:54 GMT Received: from [208.26.204.140] by mail.etrademail.com with HTTP; 10 Sep 1999 12:27:54 PDT Content-Type: text/plain Content-Disposition: inline Mime-Version: 1.0 To: freebsd-questions@freebsd.org From: wwoods@cybcon.com Cc: freebsd-smp@freebsd.org X-Mailer: Web Mail 3.1 Subject: CPU upgrade X-Sent-From: williamdwoods@etrademail.com Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am currently running a Dual PP200 system with 128meg memory and am looking to upgrade the processors. What would you reccomend in the ay of fairly inexpensive processors? I was looking at the AMD line, mabe a k6-350, what do you think. Are these the same socket and voltage set up? Also, what would I need to do after the CPU upgrade? Recompile the kernel, or? I would think I would be able to just drop in the new processors and boot up right? William William *************************************************************************** Our funds have Star Power. Explore our site and share your investment ideas and real-life experiences. Find the Transamerica Premier Fund that's right for you. Visit http://ad.doubleclick.net/clk;529412;3450872;h?http://www.transamericafunds. com/legal.html *************************************************************************** It's time for E*TRADE (SM) Get your free @etrademail.com address at http://www.etrade.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 12:31:56 1999 Delivered-To: freebsd-smp@freebsd.org Received: from synthcom.com (beacon.synthcom.com [198.145.98.253]) by hub.freebsd.org (Postfix) with ESMTP id 9B22814DE4; Fri, 10 Sep 1999 12:31:33 -0700 (PDT) (envelope-from neil@beacon.synthcom.com) Received: from beacon.synthcom.com (beacon.synthcom.com [198.145.98.253] (may be forged)) by synthcom.com (8.9.3/8.9.3) with ESMTP id MAA43504; Fri, 10 Sep 1999 12:44:12 -0700 (PDT) (envelope-from neil@beacon.synthcom.com) Date: Fri, 10 Sep 1999 12:44:12 -0700 (PDT) From: Neil Bradley Cc: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org Subject: Re: CPU upgrade In-Reply-To: <19990910192754.26520.cpmta@c008.sfo.cp.net> 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 am currently running a Dual PP200 system with 128meg memory and am > looking to upgrade the processors. What would you reccomend in the ay > of fairly inexpensive processors? I was looking at the AMD line, mabe > a k6-350, what do you think. Are these the same socket and voltage set > up? Nope. The K6/K6-2's are socket 7, the Pentium Pro is not (I even forgot the name of the socket). As long as you're not doing floating point, the K6 is quite the viable option. FP Performance on it sucks compared to the Pentium (I do a lot of 3d rendering so I have quite a bit of hardcore experience with the K6). > Also, what would I need to do after the CPU upgrade? Recompile the > kernel, or? I would think I would be able to just drop in the new > processors and boot up right? I didn't have to when I swapped motherboards and processors (from a PPro 200 to a K6-2/300). Seemed to work nicely, but your mileage may vary. -->Neil ------------------------------------------------------------------------------- Neil Bradley Synthcom home : http://www.synthcom.com Synthcom Systems, Inc. Play a song wrong once and it's a mistake. Play it ICQ # 29402898 wrong twice and it's Jazz. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 12:40:27 1999 Delivered-To: freebsd-smp@freebsd.org Received: from revolution.3-cities.com (revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (Postfix) with ESMTP id B91BC15447; Fri, 10 Sep 1999 12:40:06 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn1009.bossig.com [208.26.241.9]) by revolution.3-cities.com (8.9.3/8.9.3) with ESMTP id MAA02173; Fri, 10 Sep 1999 12:39:58 -0700 (PDT) Message-ID: <37D95E53.CB43F5F7@3-cities.com> Date: Fri, 10 Sep 1999 12:38:59 -0700 From: Kent Stewart Organization: BOSSig X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: wwoods@cybcon.com Cc: freebsd-questions@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: CPU upgrade References: <19990910192754.26520.cpmta@c008.sfo.cp.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org wwoods@cybcon.com wrote: > > I am currently running a Dual PP200 system with 128meg memory and am looking to upgrade the processors. What would you reccomend in the ay of fairly inexpensive processors? I was looking at the AMD line, mabe a k6-350, what do you think. Are these the same socket and voltage set up? The only cpu that is supported on SMP is the Intel's. The other thing to remember is payback decreases around 3x on the bus speed. Your 200 is 3x. If you want throughput, you need 100Mhz memory and that means a P-ii 350 or faster. The old rule for throughput is 1.8x times the speed of the single cpu. Two PP200 would effectively be a PP360. The P-II 350 w/PC100 memory can still be 1.5 times faster because the memory is 1.5 times faster. I have setiathome running on two WinNT machines and they crank out a work unit in 9-10 hours. The FreeBSD system with a Celeron 433 cranks out a work unit in 14-15 hours (~1.5). Kent > > Also, what would I need to do after the CPU upgrade? Recompile the kernel, or? I would think I would be able to just drop in the new processors and boot up right? > > William > > William > *************************************************************************** > Our funds have Star Power. Explore our site and share your investment > ideas and real-life experiences. Find the Transamerica Premier Fund that's > right for you. Visit > http://ad.doubleclick.net/clk;529412;3450872;h?http://www.transamericafunds. > com/legal.html > *************************************************************************** > > It's time for E*TRADE (SM) > Get your free @etrademail.com address at http://www.etrade.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 12:41:29 1999 Delivered-To: freebsd-smp@freebsd.org Received: from pi.yip.org (yip.org [199.45.111.121]) by hub.freebsd.org (Postfix) with ESMTP id E68DA1570E; Fri, 10 Sep 1999 12:41:22 -0700 (PDT) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id PAA02629; Fri, 10 Sep 1999 15:41:05 -0400 (EDT) (envelope-from melange@yip.org) Date: Fri, 10 Sep 1999 15:41:05 -0400 (EDT) From: Bob K X-Sender: melange@localhost To: Neil Bradley Cc: freebsd-questions@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: CPU upgrade 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 Fri, 10 Sep 1999, Neil Bradley wrote: > > I am currently running a Dual PP200 system with 128meg memory and am > > looking to upgrade the processors. What would you reccomend in the ay > > of fairly inexpensive processors? I was looking at the AMD line, mabe > > a k6-350, what do you think. Are these the same socket and voltage set > > up? > > Nope. The K6/K6-2's are socket 7, the Pentium Pro is not (I even forgot > the name of the socket). As long as you're not doing floating point, the Socket 8. You can only stick PPro's in it. > K6 is quite the viable option. FP Performance on it sucks compared to the > Pentium (I do a lot of 3d rendering so I have quite a bit of hardcore > experience with the K6). The one downside is that only Intel processors support APIC (the SMP we know and love); AMD's support OpenPIC, which is not supported by any known motherboard or chipset out there. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 13:27:32 1999 Delivered-To: freebsd-smp@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 961BA1522D; Fri, 10 Sep 1999 13:27:19 -0700 (PDT) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=mistress.oldserver.demon.nl) by post.mail.nl.demon.net with smtp (Exim 2.02 #1) id 11PXGP-0002SV-00; Fri, 10 Sep 1999 20:27:17 +0000 From: Marc Schneiders Reply-To: marc@oldserver.demon.nl Organization: The Lazy SunWorshipper Inc To: Mike Smith , Luoqi Chen Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX Date: Fri, 10 Sep 1999 21:55:23 +0200 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain Cc: iwasaki@jp.FreeBSD.ORG, stable@FreeBSD.ORG, jkh@FreeBSD.ORG, smp@FreeBSD.ORG References: <199909101719.KAA03219@dingo.cdrom.com> MIME-Version: 1.0 Message-Id: <99091022071400.02343@mistress.oldserver.demon.nl> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 10 Sep 1999, Mike Smith wrote: > > Hmm, this change doesn't belong in -stable. I remember I committed it > > to the head of the branch, how does it end up in -stable? It should > > definitely be taken out. > > It was merged after a request for comment didn't elict any responses. > Do you want to see the original patchset for the merge, in case > something else undesired came in? Professedly a complete newbie in many respects, I must say 3.3 SMP is working fine here. I do get some sort of error message, which I never saw in current (dmesg appended below). Top now shows more clearly boths CPU's working. In current (well of a week ago or so, when it died on my dual box when I tried to dual install a certain unmentionable OS) there was always one "run" and one "CPUx" under STATE. Or is this only related to top? Marc Schneiders marc@oldserver.demon.nl machine ECS Elite P6FX-2A 2 PentiumPro 200MHz @ 233 256k dmesg (partly) Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-19990909-RC #0: Fri Sep 10 20:57:38 CEST 1999 marc@unclad.oldserver.demon.nl:/usr/src/sys/compile/UNCLAD Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 268435456 (262144K bytes) avail memory = 258494464 (252436K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02a6000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ncr0: rev 0x12 int a irq 16 on pci0.9.0 bogus MP table, 2 IO APIC pins connected to the same PCI device or ISA/EISA interrupt Registered extra interrupt handler for int 18 (in addition to int 16) vga0: rev 0x06 int a irq 16 on pci0.11.0 [...] npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to da1s1a [...] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 14: 9:12 1999 Delivered-To: freebsd-smp@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 3415714A0B; Fri, 10 Sep 1999 14:09:09 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA00562; Fri, 10 Sep 1999 14:02:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199909102102.OAA00562@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luoqi Chen Cc: smp@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX In-reply-to: Your message of "Fri, 10 Sep 1999 15:17:30 EDT." <199909101917.PAA17952@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Sep 1999 14:02:13 -0700 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Hmm, this change doesn't belong in -stable. I remember I committed it > > > to the head of the branch, how does it end up in -stable? It should > > > definitely be taken out. > > > > It was merged after a request for comment didn't elict any responses. > > Do you want to see the original patchset for the merge, in case > > something else undesired came in? > > > I'm sorry I didn't see the message. I checked the cvs log, it was merged > on 8/24. I wasn't following the mailing list for the two weeks prior to > Labor day. I went through the diff, only this SMP related change should > be taken out (well, I know nothing about other changes, I presume they > are fine). Cool, thanks for checking! Mister Iwasaki, you have the knife! -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Sep 10 17:44: 8 1999 Delivered-To: freebsd-smp@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 61AFF15ECC; Fri, 10 Sep 1999 17:43:59 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA26590; Fri, 10 Sep 1999 17:43:16 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199909110043.RAA26590@gndrsh.dnsmgr.net> Subject: Re: CPU upgrade In-Reply-To: from Neil Bradley at "Sep 10, 1999 12:44:12 pm" To: neil@synthcom.com (Neil Bradley) Date: Fri, 10 Sep 1999 17:43:16 -0700 (PDT) Cc: freebsd-questions@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 am currently running a Dual PP200 system with 128meg memory and am > > looking to upgrade the processors. What would you reccomend in the ay > > of fairly inexpensive processors? I was looking at the AMD line, mabe > > a k6-350, what do you think. Are these the same socket and voltage set > > up? > > Nope. The K6/K6-2's are socket 7, the Pentium Pro is not (I even forgot > the name of the socket). Why it's just the next number in the series.... Socket 8 :-) -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 18:10: 6 1999 Delivered-To: freebsd-smp@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id B682314C10; Fri, 10 Sep 1999 18:09:53 -0700 (PDT) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id DAA29071; Sat, 11 Sep 1999 03:09:52 +0200 (CEST) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id DAA12018; Sat, 11 Sep 1999 03:09:50 +0200 Date: Sat, 11 Sep 1999 03:09:50 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: stable@FreeBSD.ORG Cc: smp@FreeBSD.ORG Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX In-Reply-To: <199909101230.VAA12112@tasogare.imasy.or.jp> Message-ID: <9909110305220.11927-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mitsuru IWASAKI wrote: > If you have problems on 3.3-RC SMP system with APM enabled, > please test the attached patch and give feedback to me ASAP. > > The problem I was reported is that a lot of userland programs get > signal 11 and core dumped on startup. It seems my bad MCF (8/24) > breaks extra GDT entries for SMP. I think I just spent an entire Friday evening wondering why with 3.3-RC /bin/csh kept coring immediately upon startup when the system was in multi-user mode, and inetd coring after having spawned telnetd once, and other various ugly stuff... I'd test your patch but I've just gotten home and I don't really feel like having that server down for another few hours right now, so unfortunately I won't be testing your patch. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Sep 10 22:42:47 1999 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 6D54814F3C; Fri, 10 Sep 1999 22:42:38 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb51.imasy.or.jp [202.227.24.179]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id OAA18338; Sat, 11 Sep 1999 14:42:26 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199909110542.OAA18338@tasogare.imasy.or.jp> To: mike@smith.net.au Cc: luoqi@watermarkgroup.com, smp@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX In-Reply-To: Your message of "Fri, 10 Sep 1999 14:02:13 -0700" <199909102102.OAA00562@dingo.cdrom.com> References: <199909102102.OAA00562@dingo.cdrom.com> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 11 Sep 1999 14:45:25 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 29 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Mister Mike, thanks alot for your support and commit. > > I'm sorry I didn't see the message. I checked the cvs log, it was merged > > on 8/24. I wasn't following the mailing list for the two weeks prior to > > Labor day. I went through the diff, only this SMP related change should > > be taken out (well, I know nothing about other changes, I presume they > > are fine). > > Cool, thanks for checking! Mister Iwasaki, you have the knife! I was wating for `Go for it' command last night preparing draft of commit log, but I could hardly stay awake, upset the timing to commit. #I think I was very strained and tired :) I'm sorry to troubled all of you and appreciated your cooperation. Here is my commit log draft for it (no longer used) :) Revert part of MFC (1.77 -> 1.77.2.1) on SMP. Previous version made a lot of userland programs got signal 11 and core dumped during startup on SMP system. SMP related changes should be taken out in RELENG_3. Pointed out by: msmith Approved by: jkh Tested by: Masayuki FUKUI , ohashi@mickey.ai.kyutech.ac.jp (Takeshi OHASHI), sada Untested by: iwasaki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Sep 11 10:19:47 1999 Delivered-To: freebsd-smp@freebsd.org Received: from jules.res.cmu.edu (JULES.RES.CMU.EDU [128.2.144.56]) by hub.freebsd.org (Postfix) with ESMTP id 9BEC614CC6 for ; Sat, 11 Sep 1999 10:19:43 -0700 (PDT) (envelope-from greg@jules.res.cmu.edu) Received: from jules.res.cmu.edu (localhost [127.0.0.1]) by jules.res.cmu.edu (8.9.3/8.9.2) with ESMTP id NAA00652 for ; Sat, 11 Sep 1999 13:19:33 GMT (envelope-from greg@jules.res.cmu.edu) Message-Id: <199909111319.NAA00652@jules.res.cmu.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-smp@FreeBSD.ORG Subject: repeated deadlocks in FS with SMP machine... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Sep 1999 13:19:33 +0000 From: greg Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi - I'm running a 3.3-RC machine right now an a dual P2 with an IBM DDRS-34560D DC1B through an adaptec 2940 u2w card. For the past 3 weeks the machine has been freezing up in a similar manner. When the disk is getting between very hard, I'll see processes enter the namecache state, or the inode state & never come back to life. Other processes run fine until they need to do read or write something. I'm not using softupdates or doing anything over NFS (though the NFS code is enabled in the kernel). I've included the config file at the end... I wasn't quite sure what I should set the SMP options for, so I only set the NCPU to 2, The motherboard is a supermicro p6dbe. the latest happened when I was running 2 instances of du - one of them within a subdirectory of the other. Both went into the namecache state at the same time & just stayed there. I went to ddb & panicked, so I have a whole bunch of data now... I'm just not sure about where to begin looking. The problem is fairly repeatable for me - I just need to really beat the fs... I did run2 du's in parallel (which caused deadlock in early versions of 3.0, 3.1 because of a hold & wait (or a race condition, i can't recall)) but this didn't cause any problem. Of course, I only ran it once, so I could be wrong... Has anybody else experienced problems like this? I've seen other reports of problems with NFS & softupdates, but none this simple... Does anybody know where I should begin digging? Unfortunately, I'm not to familiar with the kernel source area (though I am familiar with kernels...). Also, should I enable the INVARIANTS option? It already takes maybe 10 minutes before I can get a lockup anyway & I don't even know if anything would pop up (though I guess I can only try...). thanks alot... Greg machine "i386" ident JULES maxusers 32 makeoptions DEBUG="-g" options "MAXDSIZ=(256*1024*1024)" options "DFLDSIZ=(256*1024*1024)" #options PQ_LARGECACHE # color for 512k/16k cache options FAILSAFE options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on da0 dumps on da0 options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options NCPU=2 cpu "I686_CPU" options USER_LDT options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" options "VM86" options DDB options KTRACE #kernel tracing #options INVARIANTS #options INVARIANT_SUPPORT options DIAGNOSTIC options PERFMON options UCONSOLE options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver (user process ppp(8)) pseudo-device ppp 2 #Point-to-point protocol options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) options "ICMP_BANDLIM" options FFS #Fast filesystem options MFS #Memory File System options NFS #Network File System options "CD9660" #ISO 9660 filesystem options FDESC #File descriptor filesystem options KERNFS #Kernel filesystem options MSDOSFS #MS DOS File System options FFS_ROOT #FFS usable as root device options DEVFS #devices filesystem #options SOFTUPDATES options NSWAPDEV=5 options CODA #CODA filesystem. pseudo-device vcoda 4 #coda minicache <-> venus comm. options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" controller scbus0 #base SCSI code device da0 #SCSI direct access devices (aka disks) device cd0 #SCSI CD-ROMs pseudo-device pty 64 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device ccd 4 #Concatenated disk driver controller isa0 options PPS_SYNC controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? tty options MAXCONS=16 # number of virtual consoles options "STD8X16FONT" # Compile font in makeoptions "STD8X16FONT"="cp850" options SC_HISTORY_SIZE=200 # number of history buffer lines device npx0 at isa? port IO_NPX iosiz 0x0 flags 0x0 irq 13 controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM options IDE_DELAY=8000 # Be optimistic about Joe IDE device device acd0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 device ep0 at isa? port 0x300 net irq 10 device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 device pca0 at isa? port "IO_TIMER1" tty controller pci0 controller ahc1 device pn0 options COMPAT_LINUX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message