From owner-freebsd-multimedia  Fri Feb 21 21:00:56 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA21083
          for multimedia-outgoing; Fri, 21 Feb 1997 21:00:56 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA21073
          for <multimedia@freebsd.org>; Fri, 21 Feb 1997 21:00:51 -0800 (PST)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id VAA16572; Fri, 21 Feb 1997 21:00:49 -0800 (PST)
Message-Id: <199702220500.VAA16572@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Randall Hopper <rhh@ct.picker.com>
cc: multimedia@freebsd.org
Subject: Re: New BT848 driver 0.2 
In-reply-to: Your message of "Fri, 21 Feb 1997 23:39:17 EST."
             <19970221233917.00785@ct.picker.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 21 Feb 1997 21:00:48 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Well, not sure what to do in your case. I have let "tv" and "dtv" run
for hours over here both on my P100 and PPRO 200Mhz.

The only thing that I think of is your kernel version or your vga
card.

Unfortunatly this kind of problem is very, very difficult to track down.

I will see what I think of to help you out.

Anyone else seeing this kind of problem?

	Tnks,
	Amancio

>From The Desk Of Randall Hopper :
>      Thanks for the driver update.  The display is very nice there for
> anywhere from 1 to 26 seconds, and then my whole system freezes.
> 
>      I tried several tweaks to get rid of the freeze: changing PCI Bus
> Latencies (32 and 10), changing Window Sizes (640x480 and 320x240),
> building a -g kernel with DDB support hoping Ctrl-Alt-Esc would let me get
> to panic from ddb and dump a core (nope), running XFree 3.2A and then 3.2.
> BTW, this was at 1024x768 555 16bpp.
> 
>      The one thing I tried that did get rid of the freeze (albeit with a
> visible speed and image quality sacrifice) is to comment out the
> CAP_CONTINUOUS ioctl, and put a CAP_SINGLE inside the event loop.  So it
> seems the freeze could might be related to letting the card/driver run
> auto-pilot.
> 
>      What's the best way to approach debugging a problem like this?  I
> haven't done much kernel debugging, so digging through the driver code is
> the next thing that occurs to me.  Any ideas on what might be going on or
> suggestions on what to try next would be appreciated.
> 
> Thanks,
> 
> Randall