From owner-freebsd-questions@FreeBSD.ORG Mon Nov 28 11:07:48 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAB7616A41F for ; Mon, 28 Nov 2005 11:07:48 +0000 (GMT) (envelope-from elessar@bsdforen.de) Received: from postfix.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F76743D75 for ; Mon, 28 Nov 2005 11:07:22 +0000 (GMT) (envelope-from elessar@bsdforen.de) Received: by postfix.bsdforen.de (Postfix, from userid 20000) id 88FA0684A29; Mon, 28 Nov 2005 12:07:20 +0100 (CET) Received: from localhost (postfix [127.0.0.3]) by postfix.bsdforen.de (Postfix) with ESMTP id 27448684A1F for ; Mon, 28 Nov 2005 12:07:19 +0100 (CET) Received: from postfix.bsdforen.de ([127.0.0.3]) by localhost (postfix.bsdforen.de [127.0.0.3]) (amavisd-new, port 10024) with LMTP id 29726-03-3 for ; Mon, 28 Nov 2005 12:07:18 +0100 (CET) Received: from loki (p549CCF4A.dip.t-dialin.net [84.156.207.74]) by postfix.bsdforen.de (Postfix) with ESMTP id 61B39684A27 for ; Mon, 28 Nov 2005 12:07:18 +0100 (CET) Date: Mon, 28 Nov 2005 12:07:18 +0100 From: Joerg Pernfuss To: freebsd-questions@freebsd.org Message-ID: <20051128120718.2bbe7ffd@loki> In-Reply-To: <1133171032.78010.6.camel@localhost.localdomain> References: <20051128053521.78709.qmail@web51308.mail.yahoo.com> <1133171032.78010.6.camel@localhost.localdomain> X-Mailer: Sylpheed-Claws 1.9.13 (GTK+ 2.6.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at bsdforen.de X-DSPAM-Result: Innocent X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 438ae4e8323585438464370 X-DSPAM-User: global Subject: Re: Processor problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2005 11:07:49 -0000 On Mon, 28 Nov 2005 01:43:52 -0800 Remington wrote: > On Sun, 2005-11-27 at 21:35 -0800, drew hill wrote: > > When the machine boots the BIOS "sees" two processors running > > at 1.0GHz and 1G of ram. When I start freeBSD and run KDE through > > the "root" acct and go to view the processors it says I only have > > 1. This is another strange thing. I was running SuSE beforeand it > > was aware of the two processors, but referred to them as "processor > > 0" and "processor 1". In the processor field in KDE it's calling > > the one processor it seeing "processor 1". So does it know about > > the other processor and just not display the information about it > > or is it only aware of 1 of the 2 processors??? Please let me know > > what you think. Andrew. > > > Is BSD aware of the multiprocessors? Did you recompile the kernel with > SMP. If you did I wouldnt worry about what KDE says you have, as long > as the kernel knows what you have..... If you have a SMP kernel loaded, here are some indicators: dmesg will show you just below your memory/apic info FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 and SMP: AP CPU #1 Launched! just before init takes over. Also mptable(1) will give you actual output. If FreeBSD does not recognize your SMP configuration, enter your BIOS and search for an option that sounds like 'MP-Table', 'MP-OS', 'MP-Spec'... depends on your BIOS vendor. Possible values should at least bei 1.1 and 1.4. I've seen OS/2 and Unix too. Try them until you find a setting that reports a valid mptable to FreeBSD. There you go. If your SuSe version expects a different MP-specification than FreeBSD, it is normal that while SuSe 'sees' both cpus, FreeBSD does not. Joerg -- | /"\ ASCII ribbon | GnuPG Key ID | c7e4 d91d 64e2 6321 9988 | | \ / campaign against | 0xb248b614 | f27a 4e5b 06ce b248 b614 | | X HTML in email | .the next sentence is a lie. | | / \ and news | .the previous sentence was true. |