From owner-freebsd-hackers Mon Apr 20 06:05:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15172 for freebsd-hackers-outgoing; Mon, 20 Apr 1998 06:05:34 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15156 for ; Mon, 20 Apr 1998 13:05:30 GMT (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.8/8.8.4) with ESMTP id JAA02609 for ; Mon, 20 Apr 1998 09:05:10 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by dignus.com (8.8.5/8.8.5) with ESMTP id IAA08348 for ; Mon, 20 Apr 1998 08:35:49 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.7/8.6.9) id IAA00271 for freebsd-hackers@freefall.cdrom.com; Mon, 20 Apr 1998 08:12:59 -0400 (EDT) Date: Mon, 20 Apr 1998 08:12:59 -0400 (EDT) From: Thomas David Rivers Message-Id: <199804201212.IAA00271@lakes.dignus.com> To: freebsd-hackers@freefall.FreeBSD.org Subject: Sudden SEGVs? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just started suddenly getting weird SEGV failures on a 2.2.5-RELEASE box that had been running perfectly. I suspect a hardware problem (like, maybe some memory has gone bad.) But, I thought it worthwhile to check here, as I've heard stories of interesting VM issues in 2.2.5-RELEASE (likely fixed in 2.2.6.) This machine has been running fairly well for quite some time... to suddenly demonstrate a software problem would be unlikely, but not unheard off... Anyway, what happens is that suddenly, all programs simply get segmentation violations... everything that was running continues to run; but any new program blows up. The machine is nowhere near loaded and I'm nowhere near out of processes, file descriptors, etc.... A reboot totally solves things. Here are my questions: 1) Does this sound like a familiar problem? (either VM or exec())? 2) If it's familiar, I'm guessing an upgrade to 2.2.6 is in order... right? 3) If it's not familiar - has anyone got an idea? [remember the machine only has problems with starting programs, it doesn't spontaneously reboot, or anything...] Here's the particulars: FreeBSD 2.2.5-RELEASE on a Pentium-mmx 200 mhz, 32 meg of ram, Matrox Millenium II, ne2000, aha2940... - Thanks - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message