From owner-freebsd-hackers  Thu Jul 20 01:11:34 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id BAA27205
          for hackers-outgoing; Thu, 20 Jul 1995 01:11:34 -0700
Received: from vetch.cs.washington.edu (vetch.cs.washington.edu [128.95.2.2])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id BAA27199
          for <hackers@freebsd.org>; Thu, 20 Jul 1995 01:11:32 -0700
Received: from vetch.cs.washington.edu (localhost [127.0.0.1]) by vetch.cs.washington.edu (8.6.12/7.2ws+) with ESMTP id BAA12714; Thu, 20 Jul 1995 01:09:43 -0700
Message-Id: <199507200809.BAA12714@vetch.cs.washington.edu>
X-Mailer: exmh version 1.6.1 5/23/95
To: Bruce Evans <bde@zeta.org.au>, David Greenman <davidg@Root.COM>
cc: hackers@freebsd.org
Subject: Re: One cause of 2.05R instability found 
In-reply-to: Your message of "Mon, 17 Jul 1995 17:09:23 +1000."
             <199507170709.RAA22674@godzilla.zeta.org.au> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 20 Jul 1995 08:09:43 GMT
From: Voradesh Yenbut <yenbut@cs.washington.edu>
Sender: hackers-owner@freebsd.org
Precedence: bulk

Thanks for opening up my eyes on memory problem.  The system is Premiere/PCI 
II Expandable Desktop system built by Intel.  It does not seem to have a way 
to change any timing options on memory.  When I have a chance, I might try 
removing or rearranging memory to see if the system can be more stable.
Right now, the system has never stayed up longer than a week.

Voradesh Yenbut				
Computer Science & Engineering		Phone:	+1 206 685-0912
BOX 352350,  U of Washington		FAX:	+1 206 543-2969
Seattle, WA 98195			Email: yenbut@cs.washington.edu