From owner-freebsd-multimedia@FreeBSD.ORG  Fri Feb 11 05:58:38 2005
Return-Path: <owner-freebsd-multimedia@FreeBSD.ORG>
Delivered-To: freebsd-multimedia@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E06C316A4CE
	for <freebsd-multimedia@freebsd.org>;
	Fri, 11 Feb 2005 05:58:38 +0000 (GMT)
Received: from freckleface.aedifice.net
	(adsl-209-233-30-172.dsl.snfc21.pacbell.net [209.233.30.172])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2114843D1F
	for <freebsd-multimedia@freebsd.org>;
	Fri, 11 Feb 2005 05:58:38 +0000 (GMT)
	(envelope-from myers@aedifice.net)
Received: from [10.0.0.20] (dmz2 [192.168.1.2])j1B5o8f19308
	for <freebsd-multimedia@freebsd.org>;
	Thu, 10 Feb 2005 21:50:13 -0800 (PST)
Message-ID: <420C4987.3080306@aedifice.net>
Date: Thu, 10 Feb 2005 21:58:31 -0800
From: "David C. Myers" <myers@aedifice.net>
User-Agent: Mozilla Thunderbird 1.0 (X11/20050105)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-multimedia@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: pvr250: intermittent corrupt captures
X-BeenThere: freebsd-multimedia@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Multimedia discussions <freebsd-multimedia.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia>,
	<mailto:freebsd-multimedia-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-multimedia>
List-Post: <mailto:freebsd-multimedia@freebsd.org>
List-Help: <mailto:freebsd-multimedia-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia>,
	<mailto:freebsd-multimedia-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2005 05:58:39 -0000



Every so often, my PVR-250 (using the most recent cxm driver) will 
generate a corrupt capture.  From that point on, every successive 
capture will also be corrupt.  Sometimes, the system log will show a 
message

  cxm0: encoder dma status 0xb

(although this seems to appear during the second corrupt capture, not 
the first).  The correlation between this message and the corrupt 
captures is not perfect -- sometimes, there is no message at all.

Interestingly, it takes a full reboot of the box to restore the card to 
proper operation.  A simple 'kldunload cxm' followed by 'kldload cxm' 
doesn't work.  After a reboot, it seems to go a couple of days before 
the problem crops up again.

Any ideas on this?  I'm running 5.3; kernel built about a week ago.

I'm trying to capture from over-the-air broadcasts.

-David.