From owner-freebsd-questions Sat Nov 22 17:33:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA09407 for questions-outgoing; Sat, 22 Nov 1997 17:33:13 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from chaotic.ultra.net.au (chaotic.oz.org [203.20.237.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA09391 for ; Sat, 22 Nov 1997 17:33:02 -0800 (PST) (envelope-from simon@chaotic.ultra.net.au) Received: (from simon@localhost) by chaotic.ultra.net.au (8.8.7/8.8.5) id LAA00504 for questions@freebsd.org; Sun, 23 Nov 1997 11:32:47 +1000 (EST) Message-ID: X-Mailer: XFMail 1.2-beta-111997 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 IRC: X-IRC: Chaos @ mpx.sydney.oz.org Port 6666 Date: Sun, 23 Nov 1997 11:32:43 +1000 (EST) Organization: Chaotic Software From: Simon Coggins To: questions@freebsd.org Subject: MAJOR Problem in 2.2.5 (Related to 6x686 MMX 166 CPU) Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Last week i posted about having a problem with the kernel of 2.2.5 on the boot disk kernel panicing with this message: fatal trap 9 general protection fault while in kernel instruction pointer = 0x8:0xf01aad71 stack pointer = 0x10:0xefbfff98 frame pointer = 0x10:0xefbfffb0 code segment = base 0x0, limit 0xfffff, type 0x1b DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 0 () interrupt mask = net tty bio panic: general protection fault I've worked out the problem. 2.2.5 does not like my CPU. It detects it as: CPU: i486DX (486-class CPU) But it is really a IBM Cyrix 6x686 P166+ MMX (Bois shows it as M2-MMX-P166+) I swaped CPU's in another machine to a Cyrix P120+ and it worked fine so i installed FreeBSD 2.2.5 then swapped CPU's back and booted up (It booted from 2.2.2 Kernel after the upgrade). I recompiled kernel and rebooted. *BANG* Kernel panic. I have to load /kernel.old now because I can't boot up from the 2.2.5 Kernel.. HELP! (As of writting I'm CVSup'ing to -current to try and fix the problem) Regards Simon