From owner-freebsd-current@FreeBSD.ORG  Mon Aug 23 18:59:26 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 5D9FC16A4CE
	for <current@freebsd.org>; Mon, 23 Aug 2004 18:59:26 +0000 (GMT)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 489D143D39
	for <current@freebsd.org>; Mon, 23 Aug 2004 18:59:26 +0000 (GMT)
	(envelope-from mux@freebsd.org)
Received: by elvis.mu.org (Postfix, from userid 1920)
	id 2F11F5C9B0; Mon, 23 Aug 2004 11:59:26 -0700 (PDT)
Date: Mon, 23 Aug 2004 20:59:26 +0200
From: Maxime Henrion <mux@freebsd.org>
To: current@freebsd.org
Message-ID: <20040823185926.GB92931@elvis.mu.org>
References: <41263718.9010201@xrays.de>
	<20040823175129.GA74302@fasolt.home.paeps.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040823175129.GA74302@fasolt.home.paeps.cx>
User-Agent: Mutt/1.4.2.1i
Subject: Re: vr0: watchdog timeout
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, 23 Aug 2004 18:59:26 -0000

Philip Paeps wrote:
> On 2004-08-20 19:38:32 (+0200), Corrado Ficicchia <dino@xrays.de> wrote:
> > cvsupped today from -current 15.Jul to 5.3-ALPHA.  When I now use vr I get
> > "vr0: watchdog timeout".  With kernel from 15.Jul vr worked...
> 
> I am seeing the same thing here, a kernel from 25 July worked, a kernel from
> today doesn't.  That narrows it down some.  I'm trying to figure out which
> checkin caused the problem.  Toggling ACPI on/off does not seem to fix the
> problem for me.

Can you please try to set vm.old_contigmalloc to 1 with the new kernel, and
then load the vr(4) driver as a module and see if that helps?

Cheers,
Maxime