Date: Mon, 03 Nov 1997 11:15:32 +1030 From: Mike Smith <mike@smith.net.au> To: Donald Burr <dburr@POBoxes.com> Cc: FreeBSD Questions <freebsd-questions@FreeBSD.ORG>, FreeBSD Hardware <freebsd-hardware@FreeBSD.ORG> Subject: Re: programs dying with SIGBUS after long uptime Message-ID: <199711030045.LAA00564@word.smith.net.au> In-Reply-To: Your message of "Sun, 02 Nov 1997 03:33:21 -0800." <XFMail.971102034223.dburr@POBoxes.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> After the system has been up and in use for a lengthy period of > time (from several hours to a whole day or more), programs start dying with > signal 10's (SIBGUS). You should be checking that none of your system components (eg. CPU, disk) are overheating. If you have a fan-cooled processor, you should definitely check that the fan is still working. Then you should check the output of 'vmstat -m', and look for abnormally large allocations. > 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. Note that once a text image has been corrupted during execution, repeated execution of the same image will run the (corrupted) sticky copy in core until same is flushed; this basically means that once a program has died due to memory corruption you need to reboot. > 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 ... > documentation) Could this be due to some BIOS configurations that aren't > set right (memory timings, cache timings, PCI bus stuff, ...?) Yes and yes. mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711030045.LAA00564>