From owner-freebsd-bugs Sun Nov 23 05:50:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA11495 for bugs-outgoing; Sun, 23 Nov 1997 05:50:08 -0800 (PST) (envelope-from owner-freebsd-bugs) Received: (from gnats@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA11482; Sun, 23 Nov 1997 05:50:02 -0800 (PST) (envelope-from gnats) Resent-Date: Sun, 23 Nov 1997 05:50:02 -0800 (PST) Resent-Message-Id: <199711231350.FAA11482@hub.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@FreeBSD.ORG, chaos@ultra.net.au Received: (from nobody@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA11203; Sun, 23 Nov 1997 05:44:16 -0800 (PST) (envelope-from nobody) Message-Id: <199711231344.FAA11203@hub.freebsd.org> Date: Sun, 23 Nov 1997 05:44:16 -0800 (PST) From: chaos@ultra.net.au To: freebsd-gnats-submit@FreeBSD.ORG X-Send-Pr-Version: www-1.0 Subject: kern/5130: Kernel panic GPF imediatly on loading kernel when using a Cyrix P166+ MMX Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Number: 5130 >Category: kern >Synopsis: Kernel panic GPF imediatly on loading kernel when using a Cyrix P166+ MMX >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Nov 23 05:50:00 PST 1997 >Last-Modified: >Originator: Simon Coggins >Organization: N/A >Release: 2.2.5 AND 3.0-Current, 2.2.2 works fine >Environment: FreeBSD chaotic 2.2.2-RELEASE FreeBSD 2.2.2-RELEASE #0: Sat Nov 22 14:14:21 EST 1997 root@chaotic:/usr/src/sys/compile/Chaotic i386 >Description: When upgrading to 2.2.5 OR 3.0-Current, and using a Cyrix 6x86 P166+ MMX The kernel Panics Imediatly on decompressing the kernel (from the boot floppy) or when installing a new kernel. IE You can't boot the machine. >How-To-Repeat: Install a Cyrix 6x86 P166+ MMX and turn on the machine >Fix: Replace the CPU, I used a Cyrix P120+ and 2.2.5 booted fine. I managed to upgrade using the old CPU Then put the new CPU back in.. *BANG* dead again >Audit-Trail: >Unformatted: