From owner-freebsd-current@FreeBSD.ORG  Mon Feb 16 08:24:23 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4D63C16A4CE
	for <current@freebsd.org>; Mon, 16 Feb 2004 08:24:23 -0800 (PST)
Received: from gvr.gvr.org (gvr-gw.gvr.org [80.126.103.228])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1EAF543D1F
	for <current@freebsd.org>; Mon, 16 Feb 2004 08:24:23 -0800 (PST)
	(envelope-from guido@gvr.org)
Received: by gvr.gvr.org (Postfix, from userid 657)
	id 7AC8445; Mon, 16 Feb 2004 17:24:22 +0100 (CET)
Date: Mon, 16 Feb 2004 17:24:22 +0100
From: Guido van Rooij <guido@gvr.org>
To: current@freebsd.org
Message-ID: <20040216162422.GA67596@gvr.gvr.org>
References: <20040216141941.GA65927@gvr.gvr.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040216141941.GA65927@gvr.gvr.org>
Subject: Re: problem with ndis
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2004 16:24:23 -0000

On Mon, Feb 16, 2004 at 03:19:41PM +0100, Guido van Rooij wrote:
> 
> After each link down event, I had to manually reconfigure tha card.

This turns out not be true:
Feb 16 17:22:06 beck kernel: ndis0: link down
Feb 16 17:22:22 beck kernel: ndis0: link up

I don't know why it had to wait for 16 seconds to automatically come back up
again.

Still no clue on what causes the watchdog timeout.

-Guido