From owner-freebsd-bugs Mon Apr 14 14:10:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA14379 for bugs-outgoing; Mon, 14 Apr 1997 14:10:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA14369; Mon, 14 Apr 1997 14:10:03 -0700 (PDT) Resent-Date: Mon, 14 Apr 1997 14:10:03 -0700 (PDT) Resent-Message-Id: <199704142110.OAA14369@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, rb@gid.co.uk Received: from isbalham.ist.co.uk ([192.31.26.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14182 for ; Mon, 14 Apr 1997 14:04:53 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id VAA20380 for freebsd.org!FreeBSD-gnats-submit; Mon, 14 Apr 1997 21:44:49 +0100 (BST) Message-Id: <20851.199704142045@seagoon.gid.co.uk> Date: Mon, 14 Apr 1997 21:45:58 +0100 From: Bob Bishop Reply-To: rb@gid.co.uk To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/3292: Cyrix 486 performance problem Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 3292 >Category: kern >Synopsis: Cyrix 486 performance problem >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Apr 14 14:10:01 PDT 1997 >Last-Modified: >Originator: Bob Bishop >Organization: GID ltd >Release: FreeBSD 3.0-CURRENT i386 >Environment: Cyrix 486DX2/80, ISA M/B, 20Mb, Adaptec1542CF >Description: With kernels built after around 20 March, CPU runs an order of magnitude slower than it should. Eg, kernel build takes 3.25 hours against 28 min; tiny program containing nested for loops takes 51 sec against 4 sec. Old (ie good) kernels identify the CPU as: CPU: Cy486DLC (486-class CPU) Origin = "Cyrix" Newer (broken) kernels: CPU: Cyrix 486DX2 (486-class CPU) Origin = "CyrixInstead" Device ID = 0x321b Stepping=3 Revision=2 I surmise that the CPU initialisation code got broken sometime around 20 March. >How-To-Repeat: Run anything on this machine with a current-ish kernel. >Fix: Work around by using an old kernel :-( >Audit-Trail: >Unformatted: