From owner-freebsd-current Tue Jan 16 08:20:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA23167 for current-outgoing; Tue, 16 Jan 1996 08:20:00 -0800 (PST) Received: from dw3f.ess.harris.com (dw3f.ess.harris.com [130.41.9.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA23160 for ; Tue, 16 Jan 1996 08:19:50 -0800 (PST) Received: from suw2k.hisd.harris.com (borg [158.147.23.50]) by dw3f.ess.harris.com (8.6.9/mdb(941103)) with SMTP id LAA26455 for ; Tue, 16 Jan 1996 11:19:22 -0500 Received: by suw2k.hisd.harris.com (4.1/SMI-4.1) id AA09264; Tue, 16 Jan 96 11:16:19 EST Date: Tue, 16 Jan 96 11:16:19 EST From: jleppek@suw2k.hisd.harris.com (James Leppek) Message-Id: <9601161616.AA09264@suw2k.hisd.harris.com> To: freebsd-current@freefall.FreeBSD.org Subject: general protection faults Sender: owner-current@FreeBSD.ORG Precedence: bulk Lately I have had continual crashes caused by general protection faults and they are occuring in the idle task. The system dumps don't help much because the trace back is just trap,fatal_trap, boot :-( Is this an indication of bad hardware? The system has been running fbsd for years. system info: fbsd-current supped and built every few days (got caught by the clock changes which made for a lively night :-) ) 486dx4 100 tried with 32 and 16 Meg of memory IDE disks DOS and windows work (well, as good as could be expected :-) ) I ran a few memory checkers and nothing showed up, although they are not that great. Any hints?? Thanks Jim Leppek