From owner-freebsd-questions  Wed Sep 27 22:53:52 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id WAA04857
          for questions-outgoing; Wed, 27 Sep 1995 22:53:52 -0700
Received: from MediaCity.com (easy1.mediacity.com [205.216.172.10])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA04852
          for <freebsd-questions@freebsd.org>; Wed, 27 Sep 1995 22:53:50 -0700
Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id WAA26583; Wed, 27 Sep 1995 22:57:28 -0700
From: Brian Litzinger <brian@MediaCity.com>
Message-Id: <199509280557.WAA26583@MediaCity.com>
Subject: Re: STILL faulting..
To: jason@purcell.jlc.net (Jason T. Nelson)
Date: Wed, 27 Sep 1995 22:57:28 -0700 (PDT)
Cc: freebsd-questions@freebsd.org
In-Reply-To: <9509280428.AA00297@purcell.jlc.net> from "Jason T. Nelson" at Sep 28, 95 00:28:19 am
X-Mailer: ELM [version 2.4 PL24 ME7a]
Content-Type: text
Content-Length: 686       
Sender: owner-questions@freebsd.org
Precedence: bulk

> 
> I got the recent 2.1.0 snapshot as Justin requested, but I'm still having 
> some problems (though not as much!). /usr/libexec/cc1 died once of signal 
> 11, then after I continued the kernel compile, the kernel paniced for the 
> same reason as before: "page fault while in kernel mode". Perhaps there 
> are still problems with the 294x support?

I can say I'm using 2940's (and Wides) very heavily in -current without
any such problems.

I've noticed that the sig11's caused by the ffs bug were reliably
and repeatable, while sig11's that happen at various/random times
are related to flaky hardware, most often I find related to the
cache.

Brian Litzinger
brian@mediacity.com