From owner-freebsd-multimedia Mon Nov 4 10:20:59 1996 Return-Path: owner-multimedia Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11253 for multimedia-outgoing; Mon, 4 Nov 1996 10:20:59 -0800 (PST) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA11242; Mon, 4 Nov 1996 10:20:54 -0800 (PST) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.6/8.7.3) with ESMTP id KAA02367; Mon, 4 Nov 1996 10:20:42 -0800 (PST) Message-Id: <199611041820.KAA02367@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Mark Tinguely cc: jkh@time.cdrom.com, hackers@freebsd.org, multimedia@freebsd.org Subject: Re: Matrox Meteor and PPRO problem found In-reply-to: Your message of "Mon, 04 Nov 1996 12:13:26 CST." <199611041813.MAA29835@plains.nodak.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Nov 1996 10:20:42 -0800 From: Amancio Hasty Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Mark Tinguely : > > If memory does not failed me I have taken out all PCI devices except for t he > > ide controller and whrn saving images or running vic the meteor crashes > > my PPRO . > > try this, do not run X on the capturing machine; display the vic on another > machine. This trick for the most part) works on the neptune. I know the > display and meteor were on different IRQs. I think the problem is other > traffic on the PCI bus. > > --mark. Oh, I have code which does not use the display and it crashes hard the system. I think that you are right about other traffic being on the bus affecting the Meteor. Most likely is when the Meteor attempts to generate a halt or similar operation to stop and then resume. Cheers, Amancio