From owner-freebsd-smp Mon Mar 25 8:40:39 2002 Delivered-To: freebsd-smp@freebsd.org Received: from mail15.speakeasy.net (mail15.speakeasy.net [216.254.0.215]) by hub.freebsd.org (Postfix) with ESMTP id 324DC37B41B for ; Mon, 25 Mar 2002 08:40:23 -0800 (PST) Received: (qmail 8211 invoked from network); 25 Mar 2002 16:40:22 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 25 Mar 2002 16:40:22 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g2PGf2v82728; Mon, 25 Mar 2002 11:41:02 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020323041624.S90182@locore.ca> Date: Mon, 25 Mar 2002 11:40:24 -0500 (EST) From: John Baldwin To: Jake Burkholder Subject: Re: FreeBSD 4.5: Second CPU Not Working on Dell PowerEdge 1650 Cc: freebsd-smp@FreeBSD.ORG, Andy Isaacson Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 23-Mar-2002 Jake Burkholder wrote: > Apparently, On Fri, Mar 22, 2002 at 10:05:27AM -0500, > John Baldwin said words to the effect of; > >> >> On 22-Mar-2002 Andy Isaacson wrote: >> > On Thu, Mar 21, 2002 at 05:35:58PM -0800, Lars Eggert wrote: >> >> Barney Wolff wrote: >> >> > Remember that in computing, counting begins at 0. :) >> >> > You have 2 cpu's running fine. >> >> >> >> Since this has come up a few times already, maybe we should change the >> >> message to read: >> >> >> >> SMP: Another CPU (AP CPU #1) Launched! >> > >> > How about >> > SMP: AP CPU #1 Launched, 2 running >> > >> > Or just stick a "%d CPUs running" at the end of the launch loop. >> >> In current you get a 'FreeBSD/SMP: Multiprocessor system: X cpus' message >> during startup that is identical on all platforms. > > How about we remove both of these messages altogether and print identify > lines for all cpus in the system. They can even look something like > newbus device probes. Some folks would like CPU's to be proper new-bus devices. I wouldn't mind these types of messages. > cpu0: Sun Microsystems UltraSparc-II Processor (450.07 MHZ CPU) > cpu1: Sun Microsystems UltraSparc-II Processor (450.07 MHZ CPU) > cpu2: Sun Microsystems UltraSparc-II Processor (450.07 MHZ CPU) > cpu3: Sun Microsystems UltraSparc-II Processor (450.07 MHZ CPU) > nexus0: > > The SMP: AP CPU #%d Launched! message is dangerous because it is printed > before the non-boot cpus can safely acquire Giant; most architectures do > it wrong. Hmmmm. Well, we really need proper printf locking (which probably shouldn't use blocking locks). > Jake -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message