From owner-freebsd-questions Mon Nov 24 12:00:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA29464 for questions-outgoing; Mon, 24 Nov 1997 12:00:42 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA29459 for ; Mon, 24 Nov 1997 12:00:39 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id MAA12900; Mon, 24 Nov 1997 12:00:34 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 24 Nov 1997 12:00:34 -0800 (PST) From: Doug White Reply-To: Doug White To: Simon Coggins cc: questions@FreeBSD.ORG Subject: Re: 2.2.5 Boot Floppy and Kernel Panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Nov 1997, Simon Coggins wrote: > Motherboard: TekRam H5P30 HS V1.0 I think it is (it has built in scsi) > CPU: P166 MMX Cyrix > RAM: 64 Meg of ram in 4x16 EDO Hm, we've had random occurances of 64 meg machines panicking. Remove a SIMM and try it. > >> 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 Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major