From owner-freebsd-hackers Wed Sep 4 22:52:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA23660 for hackers-outgoing; Wed, 4 Sep 1996 22:52:21 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA23655 for ; Wed, 4 Sep 1996 22:52:15 -0700 (PDT) Received: from dns.ottawa.net by mail.crl.com with SMTP id AA01051 (5.65c/IDA-1.5 for ); Wed, 4 Sep 1996 22:50:45 -0700 Received: from ottawa.net (ppp-92.ottawa.net [205.211.4.92]) by dns.ottawa.net (8.7.5/1.2) with ESMTP id WAA06014 for ; Wed, 4 Sep 1996 22:42:01 -0400 (EDT) Received: (from brianc@localhost) by ottawa.net (8.7.5/8.7.3) id WAA01346 for freebsd-hackers@FreeBSD.org; Wed, 4 Sep 1996 22:36:29 -0400 (EDT) From: Brian Campbell Message-Id: <199609050236.WAA01346@ottawa.net> Subject: signal 10 (bus error) To: freebsd-hackers@FreeBSD.org (FreeBSD Hackers) Date: Wed, 4 Sep 1996 22:36:29 -0400 (EDT) Reply-To: brianc@pobox.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk For those others of you experiencing bus errors, you might want to try running pcvt rather than syscons. Of course I can't substantiate that suspicion other than to say that I've been running 2.1.5R for several weeks with absolutely no bus errors until today when I decided to try moving back to syscons (mostly for moused support and bold -- why can't pcvt do that) Anyway, it's worth a shot, and is certainly cheaper than suspecting your hardware and replacing it.