From owner-freebsd-hackers  Fri May 31 06:45:44 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA12860
          for hackers-outgoing; Fri, 31 May 1996 06:45:44 -0700 (PDT)
Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA12852
          for <hackers@freebsd.org>; Fri, 31 May 1996 06:45:39 -0700 (PDT)
Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id XAA04373 for hackers@freebsd.org; Fri, 31 May 1996 23:45:29 +1000
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
Message-Id: <199605311345.XAA04373@rf900.physics.usyd.edu.au>
Subject: XFree86 Trio64V+ lockup with AHA-2940
To: hackers@freebsd.org
Date: Fri, 31 May 1996 23:45:29 +1000 (EST)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I recall that some time ago there was a report here of machine lockup
when starting the XFree86 S3 server with at Trio64V+ PCI card in a machine
with an AHA-2940.  I vaguely recall a comment from someone saying it might
have been related to a problem with the 2940 driver.  Does anyone have
any further information on this?

I'm asking because we (XFree86) have been getting quite a few reports of
this type, and the 2940 seems to be the common factor.  We've had reports
for both FreeBSD and Linux.  We've also found that if there is no (or minimal)
disk activity during the server startup, then there is no problem (a typical
way of ensuring this is to do 'cat /usr/X11R6/bin/XF86_S3 > /dev/null'
before starting the server).

David