Re: smp kernel
Michael P. Soulier wrote: Hello, Is SMP enabled in the GENERIC kernel? I have a hyperthreading box, and on Linux it shows up with two cpus. When I do a top on the box in FreeBSD I still see only one CPU. Also, sysctl -a | grep cpu only shows a dev.cpu.0. The GENERIC does not support SMP. If you look into the config files you will see two kernel configuration files: SMP and GENERIC, SMP simply changes the IDENT, sets option SMP and includes GENERIC. Simply build and install your kernel, # make KERNCONF=SMP buildkernel # make KERNCONF=SMP installkernel to get an SMP enabled GENERIC kernel. Cheers, Erik (I assume you're on v. 6.x). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: smp kernel
Michael P. Soulier schrieb: Hello, Is SMP enabled in the GENERIC kernel? I have a hyperthreading box, and on Linux it shows up with two cpus. When I do a top on the box in FreeBSD I still see only one CPU. Also, sysctl -a | grep cpu only shows a dev.cpu.0. If you install FreeBSD 6.1 then you can choose between a generic kernel without SMP support and an SMP enabled kernel. These kernels are named "GENERIC" and "SMP". If you missed that point you can install it subsequently: # mount /cdrom # cd /cdrom/6.1-RELEASE/kernels # ./install SMP # echo 'kernel="SMP"' >> /boot/loader.conf # shutdown -r now Regards Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: smp kernel
On Tuesday 20 June 2006 19:01, Andy Reitz wrote: > On Tue, 20 Jun 2006, Michael P. Soulier wrote: > > Hello, > > > > Is SMP enabled in the GENERIC kernel? I have a hyperthreading box, and on > > Linux it shows up with two cpus. When I do a top on the box in FreeBSD I > > still see only one CPU. Also, sysctl -a | grep cpu only shows a > > dev.cpu.0. > > Hi Mike, > > If you have the kernel source code installed, you can read > /usr/src/sys//conf/GENERIC, to see what options are in the GENERIC > kernel. I'm pretty sure that most FreeBSD releases don't have the SMP > option in the generic kernel, but I haven't used them all, so I can't be > sure. :) > > HTH, > -Andy. > > ___ all you need to do is edit your kernel configuration file and add this: options SMP and btw, top in freebsd does not seem to have the '1' toggle that linux has, so after you compile your new kernel, your just going to have to have faith in sysctl -a|grep cpu :) cheers, jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: smp kernel
On Tue, 20 Jun 2006, Michael P. Soulier wrote: > Hello, > > Is SMP enabled in the GENERIC kernel? I have a hyperthreading box, and on > Linux it shows up with two cpus. When I do a top on the box in FreeBSD I still > see only one CPU. Also, sysctl -a | grep cpu only shows a dev.cpu.0. Hi Mike, If you have the kernel source code installed, you can read /usr/src/sys//conf/GENERIC, to see what options are in the GENERIC kernel. I'm pretty sure that most FreeBSD releases don't have the SMP option in the generic kernel, but I haven't used them all, so I can't be sure. :) HTH, -Andy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SMP kernel
On Tue, 15 Feb 2005, Kara Chapman wrote:
> Thanks for your help -- that seems to have fixed the problem. You
> mentioned that it was only a temporary fix, so what do you suggest doing
> now? Is this a bug that I should report?
FYI, the error below is probably not causing actual problems, but we
should work to track don the source of the error. If possible, could you
try running with the attached patch to uipc_syscalls.c and see if you get
kernel printf output associated with the error? What I'd like to do is
figure out what the particular source of the EINVAL is, since there are
several possible sources.
Thanks!
Robert N M Watson
Index: uipc_syscalls.c
===
RCS file: /home/ncvs/src/sys/kern/uipc_syscalls.c,v
retrieving revision 1.200.2.3
diff -u -r1.200.2.3 uipc_syscalls.c
--- uipc_syscalls.c 31 Jan 2005 23:26:18 - 1.200.2.3
+++ uipc_syscalls.c 17 Feb 2005 12:14:55 -
@@ -347,6 +347,7 @@
error = head->so_error;
head->so_error = 0;
ACCEPT_UNLOCK();
+ printf("accept: head->so_error %d\n", error);
goto noconnection;
}
so = TAILQ_FIRST(&head->so_comp);
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Errors from postfix with mpsafenet=1 (Re: SMP kernel)
On Tue, Feb 15, 2005 at 09:39:20AM -1000, Kara Chapman wrote: > Hi Kris, > > Thanks for your help -- that seems to have fixed the problem. You > mentioned that it was only a temporary fix, so what do you suggest doing > now? Is this a bug that I should report? Yes, Robert Watson might be interested in this (CC'ed). It's possible that there's already a fix for this in 5.3-STABLE, but he'd have a better idea of that. Kris > > Kara > > -Original Message- > From: Kris Kennaway [mailto:[EMAIL PROTECTED] > Sent: Monday, February 14, 2005 3:10 PM > To: Kara Chapman > Cc: freebsd-questions@freebsd.org > Subject: Re: SMP kernel > > On Mon, Feb 14, 2005 at 02:08:25PM -1000, Kara Chapman wrote: > > Hi, > > > > > > > > I am running FreeBSD 5.3 and have recently rebuilt the kernel to use > > SMP. Ever since, I get these error messages from postfix on a regular > > basis: > > > > > > > > postfix/smtpd[49491]: fatal: accept connection: Invalid argument > > > > > > > > Does anyone know what this means and if it's at all related to the new > > kernel? Other than adding SMP, the kernel is using all the defaults. > > Do the messages persist if you set debug.mpsafenet=0 in your > /boot/loader.conf and reboot (this is only a workaround since it > causes relative performance degradation, but it will help to identify > where the problem might be)? > > Kris > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > pgp7M0S1MWqYM.pgp Description: PGP signature
RE: SMP kernel
Hi Kris, Thanks for your help -- that seems to have fixed the problem. You mentioned that it was only a temporary fix, so what do you suggest doing now? Is this a bug that I should report? Kara -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Monday, February 14, 2005 3:10 PM To: Kara Chapman Cc: freebsd-questions@freebsd.org Subject: Re: SMP kernel On Mon, Feb 14, 2005 at 02:08:25PM -1000, Kara Chapman wrote: > Hi, > > > > I am running FreeBSD 5.3 and have recently rebuilt the kernel to use > SMP. Ever since, I get these error messages from postfix on a regular > basis: > > > > postfix/smtpd[49491]: fatal: accept connection: Invalid argument > > > > Does anyone know what this means and if it's at all related to the new > kernel? Other than adding SMP, the kernel is using all the defaults. Do the messages persist if you set debug.mpsafenet=0 in your /boot/loader.conf and reboot (this is only a workaround since it causes relative performance degradation, but it will help to identify where the problem might be)? Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP kernel
On Mon, Feb 14, 2005 at 02:08:25PM -1000, Kara Chapman wrote: > Hi, > > > > I am running FreeBSD 5.3 and have recently rebuilt the kernel to use > SMP. Ever since, I get these error messages from postfix on a regular > basis: > > > > postfix/smtpd[49491]: fatal: accept connection: Invalid argument > > > > Does anyone know what this means and if it's at all related to the new > kernel? Other than adding SMP, the kernel is using all the defaults. Do the messages persist if you set debug.mpsafenet=0 in your /boot/loader.conf and reboot (this is only a workaround since it causes relative performance degradation, but it will help to identify where the problem might be)? Kris pgpaDYI6WcpHl.pgp Description: PGP signature
Re: SMP kernel with RAID
Dan Rue > > On Tue, Mar 09, 2004 at 11:22:51AM -0600, Dan Rue wrote: > > Howdy, > > > > Ok, Here's the brief specs > > dual 2.4 Xeons > > Adaptec Raid-5 SCSI > > > > Is SMP flaky in 4.9 or something? This is my first SMP build.. No problems here with two SMP systems, but they are both older PII/PIII systems running on Supermicro P6DLH and P6DGH boards. One (P6DGH) is running two RAID 5 arrays via vinum. Mike Squires ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP kernel with RAID
On Tue, Mar 09, 2004 at 11:22:51AM -0600, Dan Rue wrote: > Howdy, > > Ok, Here's the brief specs > dual 2.4 Xeons > Adaptec Raid-5 SCSI > > Everything works fine with a 4.9-p3 generic kernel. However, when I > enable SMP and rebuild the kernel, boot hangs at this step: > > >Waiting 15 seconds for SCSI devices to settle > >(noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > > At that point, I have to reboot and boot back to generic kernel. > > Here's the only two lines in the kernel that I change: > >options SMP # Symmetric MultiProcessor Kernel > >options APIC_IO # Symmetric (APIC) I/O Follow-up: LINT mentions that you need to: "Be sure to disable 'cpu I386_CPU' && 'cpu I486_CPU' for SMP kernels." So, I tried that as well, with the same results. Is SMP flaky in 4.9 or something? This is my first SMP build.. dan > > Any ideas? > > tia, > Dan > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP kernel option
On Monday 19 January 2004 18:15, Didier WIROTH wrote: > In /usr/src/sys/i386/conf/NOTES it is written: > # Be sure to disable 'cpu I386_CPU' for SMP kernels. > > Do they mean you have to completely remove the "cpu" option from the custom > file, at this time I'm using this in my custom kernel: > cpu I686_CPU > options SMP > device apic > > Can I leave this? Or should I only have: Yes, you can leave this, other wise it would say "remove any cpu line" or "remove cpu Ix86_CPU lines". -- Melvyn === FreeBSD sarevok.idg.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #3: Tue Dec 30 14:31:47 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG i386 === pgp0.pgp Description: signature
Re: SMP kernel hanging after testing 8254 intr delivery (RELENG_4)
-- Hello, anything news concerning my SMP problem with the Fujitsu-Siemens RX300 system? Would be nice to have SMP running at Friday evening, when I have to go into production. Thanks and best regards Lars -- E-Mail: [EMAIL PROTECTED]\ Lars Köller [EMAIL PROTECTED] \ CC University of PGP: http://www.uk.pgp.net/pgpnet/wwwkeys.html \ Bielefeld, Germany Key-ID: A430D499 \ Tel: +49 521 106 4964 --- FreeBSD, what else? http://www.freebsd.org - ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMP kernel hanging after testing 8254 intr delivery (RELENG_4)
-- Hi, sorry, I've forgotten in my last mail to attache the mp_table output. Is anything else needed? === MPTable, version 2.0.15 --- MP Floating Pointer Structure: location: BIOS physical address: 0x000f6b20 signature:'_MP_' length: 16 bytes version: 1.4 checksum: 0xdf mode: Virtual Wire --- MP Config Table Header: physical address: 0x0009e8d0 signature:'PCMP' base table length:300 version: 1.4 checksum: 0x64 OEM ID: 'FSCD1409' Product ID: 'PRIMERGY' OEM table pointer:0x OEM table size: 0 entry count: 29 local APIC address: 0xfee0 extended table length:308 extended table checksum: 175 --- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model StepFlags 6 0x14BSP, usable 15 2 7 0xbfebfbff 0 0x14AP, usable 15 2 7 0xbfebfbff -- Bus:Bus ID Type 0 PCI 1 PCI 2 PCI 3 PCI 4 PCI 5 ISA -- I/O APICs: APIC ID Version State Address 2 0x11usable 0xfec0 3 0x11usable 0xfec1 -- I/O Ints: TypePolarityTrigger Bus ID IRQAPIC ID PIN# ExtINT active-hiedge5 0 20 INT active-hiedge5 1 21 INT active-hiedge5 0 22 INT active-hiedge5 3 23 INT active-hiedge5 4 24 INT active-hiedge5 6 26 INT active-hiedge5 7 27 INT active-hiedge5 8 28 INT active-hiedge512 2 12 INT active-hiedge513 2 13 INT active-hiedge514 2 14 INT active-hiedge515 2 15 INT active-lo level0 15:A 29 INT active-lo level2 0:A 32 INT active-lo level2 0:B 33 INT active-lo level3 4:A 3 10 INT active-lo level3 4:B 3 11 -- Local Ints: TypePolarityTrigger Bus ID IRQAPIC ID PIN# ExtINT active-hiedge5 02550 NMI active-hiedge5 02551 --- MP Config Extended Table Entries: -- System Address Space bus ID: 0 address type: I/O address address base: 0x0 address range: 0x1800 -- System Address Space bus ID: 3 address type: I/O address address base: 0x1800 address range: 0xd00 -- System Address Space bus ID: 0 address type: I/O address address base: 0x2500 address range: 0xdb00 -- System Address Space bus ID: 0 address type: memory address address base: 0xfb00 address range: 0x130 -- System Address Space bus ID: 2 address type: memory address address base: 0xfc30 address range: 0x3ff800 -- System Address Space bus ID: 0 address type: memory address address base: 0xfc6ff800 address range: 0x800 -- System Address Space bus ID: 3 address type: memory address address base: 0xfc70 address range: 0x38 -- System Address Space bus ID: 0 address type: memory address address base: 0xfca8 address range: 0x238 -- System Address Space bus ID: 0 address type: memory address address base: 0xfef0 address range: 0x110 -- System Address Space bus ID: 0 address type: memory address address base: 0xa address range: 0x2 -- System Address Space bus ID: 0 address type: memory address address base: 0xd4000 address range: 0xc000 -- Bus Heirarchy bus ID: 5 bus info: 0x01
Re: SMP kernel hanging after testing 8254 intr delivery (RELENG_4)
-- Hello Gregor, In reply to Gregor Bittel who wrote: > Moin, > tschuldigung, ich schreibe jetzt einfach mal in deutscher Sprache, > da tu ich mir einfach leichter... > Ist schon komisch, daß immer die gleichen Hardwarehersteller > Probleme bereiten, leider zählen dazu mittlerweile auch die > Fujitsu-Siemens-Boards - zumindest aus meiner Sicht, denn > das D1306 macht auch extreme Probleme, sobald es ein > SMP-Kernel verwendet wird... > Du könntest mal diesen Patch versuchen: > http://www.bnv-bamberg.de/home/ba3294/smp/files/notes/n000107.txt This patch didn't fix the problem. > vielleicht funktioniert er ja (wobei ich mir allerdings überhaupt > nicht sicher bin, einen Versuch könnte man ja mal starten). > > Aber bevor(!) du den Patch probierst, möchte ich noch, daß du > diese Zeile aus deinem Kernelconfig entfernst und dann noch > einmal den Kernel erstellst: > device apm0at isa? This didn't help. > Gibt immer wieder mal Probleme mit APM, ist eigentlich eine > Standardempfehlung, die ich immer gebe (wenn ich es im config > entdecke und der Kernel nicht so richtig mag). > > Wenn es dann tut, will ich zumindest einen dmesg+mptable-Auszug haben, > um ihn auf meine Seite[1] hochzuladen - Apropos: was spricht überhaupt > mptable (so ein Utility, welches auch mit Single-Prozessorkernel > funktioniert - es liest die aktuelle Multiprozessor-Tabelle aus, die > im BIOS hinterlegt wird)? > Ich sammele nämlich diese Informationen, ist eines meiner größten > Hobbys, neben den Handbüchern für Multiprozessorsysteme (leider > ist das für das D1409 noch nicht online, gibts dafür überhaupt eins?). Yes, I have it on a CD here. The mptable output is attached. The boot output follows: Type '?' for a list of commands, 'help' for more detailed help. ok unload ok load kernel.smp /kernel.smp text=0x1be3e0 data=0x2a4a0+0x22a50 syms=[0x4+0x2d1b0+0x4+0x33691] ok boot Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-STABLE #0: Tue Jul 1 09:10:14 GMT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/VSCAN.FSC-SMP Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2400.10-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1073741824 (1048576K bytes) avail memory = 1041534976 (1017124K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 6, version: 0x00050014, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00050014, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 io1 (APIC): apic id: 3, version: 0x000f0011, at 0xfec1 Preloaded elf kernel "kernel.smp" at 0xc036e000. module_register_init: MOD_LOAD (vesa, c02722e8, 0) error 6 Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 16 entries at 0xc00fdec0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #0 intpin 9 -> irq 2 pci0: on pcib0 pci0: at 4.0 atapci0: port 0x1400-0x140f,0x374-0x377,0x170-0x177 ,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ohci0: mem 0xfc001000-0xfc001fff irq 2 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered isab0: at device 15.3 on pci0 isa0: on isab0 pcib1: on motherboard pci1: on pcib1 pcib2: on motherboard IOAPIC #1 intpin 2 -> irq 5 IOAPIC #1 intpin 3 -> irq 9 pci2: on pcib2 bge0: mem 0xfc30 -0xfc30,0xfc31-0xfc31 irq 5 at device 0.0 on pci2 bge0: Ethernet address: 00:30:05:2f:dc:9f miibus0: on bge0 ukphy0: on miibus0 ukphy0: 100baseTX, 100baseTX-FDX brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX -FDX, auto ukphy1: on miibus0 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ukphy2: on miibus0 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ukphy3: on miibus0 ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ukphy4: on miibus0 ukphy4: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ukphy5: on miibus0 ukphy5: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ukphy6: on miibus0 ukphy6: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ukphy7: on miibus0 ukphy7: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ukphy8: on miibus0 ukphy8: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ukphy9: on miibus0 ukphy9: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ukphy10: on miibus0 ukphy10: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ukphy11: on miibus0 ukphy11: 10baseT, 10baseT-FDX, 10
Re: SMP kernel installation
On Wed, Jan 08, 2003 at 06:37:56PM +, Stacey Roberts wrote: > > > > You just need to uncomment/enable these options in the GENERIC kernel > > configuration like so: > > > > #cpuI486_CPU > > cpu I586_CPU > > cpu I686_CPU > > Is *this* actually correct? > > Looks as if you've enabled two different CPU classes here in the kernel. That's ok - it means that the kernel will run on both (i.e. less optimization). Ceri -- May the fire of my ancestors bring your last day! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: SMP kernel installation
On Wed, 2003-01-08 at 13:08, Khairil Yusof wrote: > On Tue, 2003-01-07 at 14:18, shubha mr wrote: > > > For a multiprocessor machine,to install FreeBSD,is > > something extra needs to be done from what will be > > done to install the OS for a uni processor machine?I > > mean is there anything different to be installed for a > > symmetric multi processor machine? > > Posted a reply to this a while back (check the archives). > > After installation you just need to recompile the kernel (see the > freebsd handbook). > > You just need to uncomment/enable these options in the GENERIC kernel > configuration like so: > > #cpu I486_CPU > cpu I586_CPU > cpu I686_CPU Is *this* actually correct? Looks as if you've enabled two different CPU classes here in the kernel. Regards, Stacey > > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O > > recompile and reboot: > > #cat /var/run/dmesg.boot | grep SMP > > should give you this message: > > SMP: AP CPU #1 Launched! > > If you're curious, you can run top. It will have a CPU column. -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: SMP kernel installation
On Tue, 2003-01-07 at 14:18, shubha mr wrote: > For a multiprocessor machine,to install FreeBSD,is > something extra needs to be done from what will be > done to install the OS for a uni processor machine?I > mean is there anything different to be installed for a > symmetric multi processor machine? Posted a reply to this a while back (check the archives). After installation you just need to recompile the kernel (see the freebsd handbook). You just need to uncomment/enable these options in the GENERIC kernel configuration like so: #cpuI486_CPU cpu I586_CPU cpu I686_CPU options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O recompile and reboot: #cat /var/run/dmesg.boot | grep SMP should give you this message: SMP: AP CPU #1 Launched! If you're curious, you can run top. It will have a CPU column. -- Khairil Yusof <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Re: SMP kernel installation
Sorry after re-reading my reply one thing I did not make clear Install freebsd as you would with a uniprocessor machine, then boot that install and do what I recommend below - Mike > > You need to recompile the kernel with the SMP options turned on, install > the kernel and reboot. On a reasonable modern machine takes less than 10 > minutes. > > See /usr/src/sys/i386/conf/GENERIC and the FreeBSD Handbook. > > - Mike > > > Hi, > > For a multiprocessor machine,to install FreeBSD,is > > something extra needs to be done from what will be > > done to install the OS for a uni processor machine?I > > mean is there anything different to be installed for a > > symmetric multi processor machine? > > > > thanks > > shubha > > > > __ > > Do You Yahoo!? > > Everything you'll ever need on one web page > > from News and Sport to Email and Music Charts > > http://uk.my.yahoo.com > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: SMP kernel installation
You need to recompile the kernel with the SMP options turned on, install the kernel and reboot. On a reasonable modern machine takes less than 10 minutes. See /usr/src/sys/i386/conf/GENERIC and the FreeBSD Handbook. - Mike > Hi, > For a multiprocessor machine,to install FreeBSD,is > something extra needs to be done from what will be > done to install the OS for a uni processor machine?I > mean is there anything different to be installed for a > symmetric multi processor machine? > > thanks > shubha > > __ > Do You Yahoo!? > Everything you'll ever need on one web page > from News and Sport to Email and Music Charts > http://uk.my.yahoo.com > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
