From owner-freebsd-stable Sat Mar 18 11:46:16 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 6F59537B8DB for ; Sat, 18 Mar 2000 11:46:14 -0800 (PST) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id OAA63261; Sat, 18 Mar 2000 14:46:13 -0500 (EST) (envelope-from bandix@looksharp.net) Date: Sat, 18 Mar 2000 14:46:13 -0500 (EST) From: "Brandon D. Valentine" To: Brad Knowles Cc: FreeBSD-STABLE Subject: Re: SMP oddity In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Mar 2000, Brad Knowles wrote: > I get the same on my two SMP boxes (Dual PIII/450s) running >3.2-RELEASE and 3.4-STABLE, respectively. On a non-SMP box (single >PII/335) I have running 3.0-RELEASE, I do get a speed indicator. > > I don't (yet) have any other boxes running FreeBSD, so I can't >say for sure if this is a PIII issue or an SMP issue. I get the same on a Dual P233MMX. It's a problem with the way identcpu.c handles SMP systems. You're welcome to hack it if it bothers you that much. I think a guy I know on IRC had written a messy hacked identcpu.c at one point for his dual celeron systems. If you're interested I'd be happy to find out if he still has it and send it your way. ------------------------------------------------------------- | -Brandon D. Valentine bandix at looksharp.net | bandix on EFnet IRC BVRiker on AIM ------------------------------------------------------------- | "...and as for hackers, we note that all of those known to | The Register are so strapped financially that seizing their | property would be tantamount to squeezing blood from a | stone." -- The Register, 02/17/2000 ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message