From owner-freebsd-questions Sun Jul 28 01:15:50 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA05688 for questions-outgoing; Sun, 28 Jul 1996 01:15:50 -0700 (PDT) Received: from ghost.mep.ruhr-uni-bochum.de (ghost.mep.ruhr-uni-bochum.de [134.147.6.16]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA05680 for ; Sun, 28 Jul 1996 01:15:41 -0700 (PDT) Received: (from re@localhost) by ghost.mep.ruhr-uni-bochum.de (8.6.12/8.6.9) id KAA08000 for questions@freebsd.org; Sun, 28 Jul 1996 10:15:39 +0200 From: Robert Eckardt Message-Id: <199607280815.KAA08000@ghost.mep.ruhr-uni-bochum.de> Subject: repeated bus errors on sh To: questions@freebsd.org Date: Sun, 28 Jul 1996 10:15:36 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, 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 It happened only when starting sh -- bash, ps, ls worked fine. Swap space looked at that time: Device 1K-blocks Used Avail Capacity Type /dev/wd0s2b 25832 20928 4840 81% Interleaved /dev/sd0s2b 27648 21044 6540 76% Interleaved /dev/sd1s3b 27648 20792 6792 75% Interleaved Total 80936 62764 18172 78% (The machine was/is up for 3 days, had netscape, emacs, ctwm, and several color_xterms running (all about since 3 days)) After exiting (just from the menu -- no kill) netscape, sh worked like ever and wap looked like Device 1K-blocks Used Avail Capacity Type /dev/wd0s2b 25832 16924 8844 66% Interleaved /dev/sd0s2b 27648 17112 10472 62% Interleaved /dev/sd1s3b 27648 17264 10320 63% Interleaved Total 80936 51300 29636 63% Netscape's running again now and sh still works -- but how can it be that sh spits bus errors ? Error in the VM ? (No read errors on the hard disks, but how can I _really_ test.) Any other information on the system (it's still running :-) ? Robert