From owner-freebsd-smp Sat Dec 28 14:57:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA29984 for smp-outgoing; Sat, 28 Dec 1996 14:57:52 -0800 (PST) Received: from atlantis.nconnect.net (root@[206.54.227.6]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA29977 for ; Sat, 28 Dec 1996 14:57:49 -0800 (PST) Received: from arabian.astrolab.org (dial211.nconnect.net [206.54.227.211]) by atlantis.nconnect.net (8.8.4/8.7.3) with SMTP id QAA22356; Sat, 28 Dec 1996 16:54:31 -0600 (CST) Message-ID: <32C5A57C.41C67EA6@nconnect.net> Date: Sat, 28 Dec 1996 16:55:56 -0600 From: Randy DuCharme X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Steve Passe CC: smp@freebsd.org Subject: Re: starting 2nd cpu References: <199612282201.PAA20854@clem.systemsix.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Steve Passe wrote: > > Hi, > > > I think I'm a bit confused as to what exactly it is I need to enable > > SMP. I've gotten the SMP sources via sup (cvsup) as per > > http://www.freebsd.org/~fsmp/smp.html. I've also cvsupped the entire > > 3.0 source tree and, while this eliminated the 'bad register name' > > errors, and allowed me to build the kernel, rebooting and doing (single, > > or multi-user) a sysctl -w kern.smp_active=2 returns "unknown oid > > 'kern.smp_active'. Please forgive me if this is a really stupid > > question, but... just what tree(s) exactly do I need to grab?? > > I think you just failed to add "options SMP" to your kernel config file. > > -- > Steve Passe | powered by > smp@csn.net | FreeBSD Hi Steve, Here,s my config file.... # $Id: ARABIAN_SMP, v 1.0.0 1996/12/26 rdd Exp $ machine "i386" cpu "I586_CPU" ident ARABIAN_SMP maxusers 10 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console #options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options "MAXMEM=98284" options "AUTO_EOI_1" options "AUTO_EOI_2" options CHILD_MAX=128 options OPEN_MAX=128 options SMP options NCPU=2 config kernel root on sd1 controller isa0 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 controller ahc0 controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # 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 # Mandatory, don't remove device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty # 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 controller snd0 device pas0 at isa? port 0x388 irq 10 drq 6 vector pasintr device sb0 at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # 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 It's definitely in there. Any other ideas? Thanks Randy