From owner-freebsd-current  Mon Sep 21 06:17:26 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA05566
          for freebsd-current-outgoing; Mon, 21 Sep 1998 06:17:26 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05518;
          Mon, 21 Sep 1998 06:17:16 -0700 (PDT)
          (envelope-from roger@cs.strath.ac.uk)
Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10])
	by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id OAA15646
	Mon, 21 Sep 1998 14:16:43 +0100 (BST)
Message-ID: <360651BA.59E2@cs.strath.ac.uk>
Date: Mon, 21 Sep 1998 14:16:42 +0100
From: Roger Hardiman <roger@cs.strath.ac.uk>
Organization: University of Strathclyde
X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha)
MIME-Version: 1.0
To: current@FreeBSD.ORG, multimedia@FreeBSD.ORG
Subject: wd0 / bt848 causing IDE timeouts
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Recently two people have reported seeing wd0 timeouts when
using fxtv to watch tv on their TV capture cards.

I've included Victors message. Does anyone know what may be
causing this.

Victor wrote
>  On a related topic: the Sep 2nd and 7th versions of your driver
> (Version 1.53) seem to cause wd0 timeouts on my PC: I only notice
> messages about this on the console when I use fxtv. It says
> something like "wd0: timeout (Status = 55)" (I'm not quite sure about > the '55'). No timouts on wd2, which is on the secondary EIDE
> controller.
> I need some more time to see how I can reproduce them.


Andrew wrote
> ... but there are also driver interactions; in particular, somthing
> nasty seems to happen when trying to capture from a
> flaky/non-existant UHF source.  'nasty' here includes causing the
> IDE driver to report timeout errors, and - presumably as a result of
> the disc problems impacting swap - locking up the machine for 20
> seconds at a time or sometimes forever).
> May just be BIOS/PCI configuration on these machines; I'll let you
> know when I have investigated further.

I'm throwing this open to ideas?

I think it is possible the bt848 driver is causing lots of interrupts
when there is not a TV signal but there is lots of noise.
Would excessive IRQs (say 100 a second) cause the IDE to timeout?

Help!
Roger Hardiman
Strathclyde Uni Telepresnce Group

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message