From owner-freebsd-questions Sun Jul 28 18:19:22 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22468 for questions-outgoing; Sun, 28 Jul 1996 18:19:22 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts9-line16.uoregon.edu [128.223.150.97]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA22463 for ; Sun, 28 Jul 1996 18:19:20 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id SAA00505; Sun, 28 Jul 1996 18:19:14 -0700 (PDT) Date: Sun, 28 Jul 1996 18:19:14 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Robert Eckardt cc: questions@freebsd.org Subject: Re: repeated bus errors on sh In-Reply-To: <199607280815.KAA08000@ghost.mep.ruhr-uni-bochum.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 28 Jul 1996, Robert Eckardt wrote: > a short time ago I observed a strange behaviour on my system at home > (2.1R, 16MB RAM): > Suddenly, the console started logging > Jul 28 02:15:01 ghost /kernel: pid 7495: sh: uid 0: exited on signal 10 > Jul 28 02:20:00 ghost /kernel: pid 7498: sh: uid 0: exited on signal 10 > [..] > Jul 28 02:31:05 ghost /kernel: pid 7523: sh: uid 100: exited on signal 10 Hm. This could indicate bad RAM or a corrupted file on disk. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major