From owner-freebsd-multimedia  Fri Feb 21 20:43:04 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA20080
          for multimedia-outgoing; Fri, 21 Feb 1997 20:43:04 -0800 (PST)
Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id UAA20073
          for <multimedia@freebsd.org>; Fri, 21 Feb 1997 20:42:56 -0800 (PST)
Received: from ct.picker.com by whqvax.picker.com with SMTP;
          Fri, 21 Feb 1997 23:41:42 -0500 (EST)
Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1)
	id AA25728; Fri, 21 Feb 97 23:41:35 EST
Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4)
	id XAA26633; Fri, 21 Feb 1997 23:39:18 -0500
Message-Id: <19970221233917.00785@ct.picker.com>
Date: Fri, 21 Feb 1997 23:39:17 -0500
From: Randall Hopper <rhh@ct.picker.com>
To: Amancio Hasty <hasty@rah.star-gate.com>
Cc: multimedia@freebsd.org
Subject: Re: New BT848 driver 0.2
References: <199702210031.QAA03850@rah.star-gate.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.61
In-Reply-To: <199702210031.QAA03850@rah.star-gate.com>; from Amancio Hasty on Feb 02, 1997 at 04:31:44PM
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

     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