From owner-freebsd-current@FreeBSD.ORG Fri Mar 19 09:19:35 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 8785B16A4CE for ; Fri, 19 Mar 2004 09:19:35 -0800 (PST) Received: from TRANG.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 687CB43D46 for ; Fri, 19 Mar 2004 09:19:35 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by TRANG.nuxi.com (8.12.11/8.12.10) with ESMTP id i2JHJYJI017981; Fri, 19 Mar 2004 09:19:34 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.11/8.12.11/Submit) id i2JHJXJU017980; Fri, 19 Mar 2004 09:19:33 -0800 (PST) (envelope-from obrien) Date: Fri, 19 Mar 2004 09:19:33 -0800 From: "David O'Brien" To: Julian Message-ID: <20040319171933.GC12898@dragon.nuxi.com> Mail-Followup-To: David O'Brien , Julian , current@freebsd.org References: <20040310002922.2242.qmail@web13121.mail.yahoo.com> <86eks14fji.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86eks14fji.fsf@web.de> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: current@freebsd.org Subject: Re: garbage string as cpu identifier X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2004 17:19:35 -0000 On Wed, Mar 10, 2004 at 03:11:29AM +0100, Julian wrote: > Bin Ren writes: > > > The patch is not to 'fix' your problem by replacing garbage > > string with a sane one, but rather to make sure on your > > Athlon CPU, 'cpuid' does return garbage string expectedly. > > This could mean a very tricky software initialization bug > > or even a hardware bug. After confirming fault 'cpuid', > > I'll try to find the very reason and fix it. > > Perhaps not as unusual as reporting garbage, my CPU (AMD Athlon XP > 2400+) claims to be "Unknown CPU Type". E.g. mprime chokes on this and > detects it as Cyrix... Could this be fixed by a BIOS upgrade? It is possible. It is the BIOS that sets that particular string. Your BIOS probably doesn't understand Thorobred cores, only Palamino and Thunderbird. -- -- David (obrien@FreeBSD.org)