From owner-freebsd-questions Sun Nov 2 04:43:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA18447 for questions-outgoing; Sun, 2 Nov 1997 04:43:41 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA18441 for ; Sun, 2 Nov 1997 04:43:35 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA01585; Sun, 2 Nov 1997 04:46:16 -0800 (PST) Message-Id: <199711021246.EAA01585@implode.root.com> To: Donald Burr cc: FreeBSD Questions Subject: Re: programs dying with SIGBUS after long uptime In-reply-to: Your message of "Sun, 02 Nov 1997 03:33:21 PST." From: David Greenman Reply-To: dg@root.com Date: Sun, 02 Nov 1997 04:46:16 -0800 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Many programs, however, still work fine. For example, right now, I CANNOT >start StarOffice or Executor (SIGBUS), but I CAN compile WINE (a rather >large package, IMHO), use Netscape (the 3.04Gold BSDi version), and read >and compose mail using XFMail. > >What could be going on here? I doubt it's the program or libraries, as >I've tried reloading them from scratch, with similar results. Could my >memory or CPU be going bad, or possibly overheating? (it has been very >hot around here the past few days) Sounds like bad memory to me, but could also be bad memory timing. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project