From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 12:55:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9AB816A4CE for ; Tue, 9 Mar 2004 12:55:02 -0800 (PST) Received: from red.csi.cam.ac.uk (red.csi.cam.ac.uk [131.111.8.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39DD143D1F for ; Tue, 9 Mar 2004 12:55:02 -0800 (PST) (envelope-from br260@cam.ac.uk) Received: from br260.wolfson.cam.ac.uk ([131.111.242.109] helo=[192.168.0.2]) by red.csi.cam.ac.uk with esmtp (Exim 4.12) id 1B0oFh-0000Fu-00; Tue, 09 Mar 2004 20:55:01 +0000 In-Reply-To: <20040309180326.42561.qmail@web13126.mail.yahoo.com> References: <20040309180326.42561.qmail@web13126.mail.yahoo.com> Mime-Version: 1.0 (Apple Message framework v612) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <06D0C7CB-720C-11D8-BBA4-000A9576014E@cam.ac.uk> Content-Transfer-Encoding: 7bit From: Bin Ren Date: Tue, 9 Mar 2004 20:54:58 +0000 To: Doom Neine X-Mailer: Apple Mail (2.612) cc: Current FreeBSD Subject: Re: garbage string as cpu identifier X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2004 20:55:02 -0000 On 9 Mar 2004, at 18:03, Doom Neine wrote: > hello all, > doug white pointed out that my cpu string being garbaged was > interesting, i noticed it but i didn't think it was a big deal. I personally find this very interesting indeed. > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: > \M-5\M^@f\M-A\M-a\^P\M-~\M-C\M-h\M-7\M^?fY\M-1\^Z\M^J\M-C\M-~\M-H\M- > h\M- 686-class CPU) > > Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 > > Features=0x383fbff ,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE> > > AMD Features=0xc0400000 After digging around, I locate the origin as 'cpuid()' functions. Here, please answer a few questions: 1) What's your CPU option in kernel configuration file: I686_CPU or I386_CPU? I guess yours is I686_CPU. 2) What's the specific model of your CPU? AMD Duron or Athlon? What's the speed? With your these answers, I could write a small patch. If you're willing to try that, let's see how it goes. Cheers, Bin