From owner-freebsd-current@FreeBSD.ORG Tue Mar 9 18:09:38 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 3AE7C16A4CE for ; Tue, 9 Mar 2004 18:09:38 -0800 (PST) Received: from mailgate.urz.tu-dresden.de (mailgate.urz.tu-dresden.de [141.30.66.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0553643D46 for ; Tue, 9 Mar 2004 18:09:38 -0800 (PST) (envelope-from der_julian@web.de) Received: from [127.0.0.1] (helo=localhost) by mailgate.urz.tu-dresden.de with esmtp (exim-4.22) for id 1B0tA8-0000eL-Vm; Wed, 10 Mar 2004 03:09:37 +0100 Received: from mailgate.urz.tu-dresden.de ([127.0.0.1]) by localhost (rks24 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02180-06 for ; Wed, 10 Mar 2004 03:09:36 +0100 (MET) Received: from [141.30.207.25] (helo=meta) by mailgate.urz.tu-dresden.de with esmtp (exim-4.22) for id 1B0tA8-0000dp-9e; Wed, 10 Mar 2004 03:09:36 +0100 To: current@freebsd.org References: <20040310002922.2242.qmail@web13121.mail.yahoo.com> From: Julian Date: Wed, 10 Mar 2004 03:11:29 +0100 In-Reply-To: (Bin Ren's message of "Wed, 10 Mar 2004 01:18:28 +0000") Message-ID: <86eks14fji.fsf@web.de> User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion, berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-TUD-Virus-Scanned: by amavisd-new at rks24.urz.tu-dresden.de X-TUD-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on rks24 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: Wed, 10 Mar 2004 02:09:38 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable 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? CPU: Unknown CPU Type (2008.53-MHz 686-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x681 Stepping =3D 1 Features=3D0x383fbff AMD Features=3D0xc0400000 Regards, =2D-=20 Julian Stecklina Key-ID: 0xD65B2AB5 FA38 DCD3 00EC 97B8 6DD8 D7CC 35D8 8D0E D65B 2AB5 "I meant," said Iplsore bitterly, "what is there in=20 this world that makes living worthwhile?" Death=20 thought about it. "CATS," he said eventually, "CATS=20 ARE NICE." - Terry Pratchett, Sourcery --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBATnlVNdiNDtZbKrURAr00AJ9QtP1i1396/2mLCLf8z70o8LVuHgCcCY09 /s1iDRrFQ0O9RKiia6hD2cM= =Db3+ -----END PGP SIGNATURE----- --=-=-=--