From owner-freebsd-stable Wed Jul 9 00:11:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01987 for stable-outgoing; Wed, 9 Jul 1997 00:11:15 -0700 (PDT) Received: from cypress.netc.net.au (cypress.netc.net.au [203.13.34.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA01974 for ; Wed, 9 Jul 1997 00:10:54 -0700 (PDT) Received: from localhost (dave@localhost) by cypress.netc.net.au (8.8.5/8.8.5) with SMTP id RAA16683 for ; Wed, 9 Jul 1997 17:10:18 +1000 (EST) Date: Wed, 9 Jul 1997 17:10:18 +1000 (EST) From: David Lay To: freebsd-stable@freebsd.org Subject: SIGBUS under 2.2.2-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently added 4MB RAM to my machine (Intel 486dx2-66 ISA/VLB) taking it from 16MB to 20MB. It's running 2.2.2-RELEASE, and I compiled a new kernel with BOUNCE_BUFFERS enabled. Since then I seem to be getting a lot of bus errors. They occur mostly, but not only, when I try to login. If I manage to login I see from /var/log/messages that it's my login shell, tcsh, that's getting SIGBUS. I've also seen the C compiler terminate with SIGBUS, but it mainly seems to affect tcsh. I've also noticed that the bus errors occur more frequently once the machine has been up a few days. After a reboot I can usually login succesasfuly straight away, but after two or three days, I get SIGBUS on about 95% of all login attempts. What exactly is a bus error (as opposed to a segmentation fault), and why would I be getting so many of them now ? -- David Lay dave@netc.net.au