From owner-freebsd-current  Sat Mar 28 13:40:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA12928
          for freebsd-current-outgoing; Sat, 28 Mar 1998 13:40:14 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12923
          for <current@FreeBSD.ORG>; Sat, 28 Mar 1998 13:40:12 -0800 (PST)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA23551;
	Sat, 28 Mar 1998 13:39:39 -0800 (PST)
Message-Id: <199803282139.NAA23551@implode.root.com>
To: Mark Murray <mark@grondar.za>
cc: current@FreeBSD.ORG
Subject: Re: VX driver in current acting up? 
In-reply-to: Your message of "Sat, 28 Mar 1998 23:34:40 +0200."
             <199803282134.XAA02359@greenpeace.grondar.za> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sat, 28 Mar 1998 13:39:39 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>David Greenman wrote:
>>    This happens when FreeBSD doesn't get any more interrupts from the card.
>> There is a one-second watchdog that notices some input and that's the reason
>> for the strange 0 to 1 second RTTs.
>
>Hmm. Does this imply broken hardware or a broken driver? Is there an 
>interrupt driver that is never clearing the card's status?
>
>I wonder....

   I'm more inclined to believe that the driver is broken, but it could be
either.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

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