From owner-freebsd-smp  Fri Jun 19 11:12:36 1998
Return-Path: <owner-freebsd-smp@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA05986
          for freebsd-smp-outgoing; Fri, 19 Jun 1998 11:12:36 -0700 (PDT)
          (envelope-from owner-freebsd-smp@FreeBSD.ORG)
Received: from gw2.asacomputers.com (gw1.asacomputers.com [204.69.220.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05849;
          Fri, 19 Jun 1998 11:11:44 -0700 (PDT)
          (envelope-from kedar@asacomputers.com)
Received: from kedar.asacomputers.com (alan.asacomputers.com [204.153.176.86])
	by gw2.asacomputers.com (8.8.8/8.8.8) with SMTP id LAA04113;
	Fri, 19 Jun 1998 11:11:37 -0700 (PDT)
	(envelope-from kedar@asacomputers.com)
Message-Id: <2.2.32.19980619180827.014fad94@gw1>
X-Sender: rajadnya@gw1
X-Mailer: Windows Eudora Pro Version 2.2 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Fri, 19 Jun 1998 11:08:27 -0700
To: sos@FreeBSD.ORG
From: Kedar Rajadnya <kedar@asacomputers.com>
Subject: Re: TYAN 1668 anyone ??
Cc: smp@FreeBSD.ORG
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA05896
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

We had that happen to us with NT systems and the 1668.  Sometimes, it had to
do with memory.  We found that we had to use *very* specific SIMMS.
Specially if they are 64MB SIMMS or above.  They tended not to like EDO
simms and preferred parity.  Above 192MB, they almost always cause problems.

It might be one of the reasons?

Regards,
Kedar.

At 08:58 AM 6/19/98 +0200, you wrote:
>
>I have this most odd problem with at least 3 of these boards
>(TYAN 1668 dual P6).
>
>The problem is that those boards can lock up totally given a set
>of specific events:
>
>Run in a high res graphics mode, that uses linear addressing.
>Use the mouse together with disk activity.
>
>This can be done in either X, win95 or winNT with the same sad
>result, a total lockup of the system.
>
>If I use the mouse in a textmode, or in a graphics mode that
>uses banking, the problem doesn't appear.
>
>We have tried anything here, we have the problem in 3 machines
>all of them have had their motherboards changed several times,
>we have tried different videocards, mouses, tried SCSI vs IDE,
>you name it, everytime with the same result.
>
>They can all "make world" for days in an xterm, given that you
>dont touch the mouse, if you do move the mouse and hit a bottom
>that will hang the machin solid in 80% of the cases.
>
>I have a TYAN 1662 board which is allmost the same just AT instead
>of ATX, and it doesn't show this behavior, even with the same
>parts put into the machine....
>
>Any ideas, I'm totally at a loss here....
>
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
>                Even more code to hack -- will it ever end?
>..
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-smp" in the body of the message
>
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message