From owner-freebsd-current@FreeBSD.ORG  Mon Jul  5 20:06:29 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 84B0616A4CF
	for <current@FreeBSD.org>; Mon,  5 Jul 2004 20:06:29 +0000 (GMT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3D6F443D4C
	for <current@FreeBSD.org>; Mon,  5 Jul 2004 20:06:29 +0000 (GMT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i65K6Lrf001926;
	Mon, 5 Jul 2004 13:06:25 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200407052006.i65K6Lrf001926@gw.catspoiler.org>
Date: Mon, 5 Jul 2004 13:06:21 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: phk@phk.freebsd.dk
In-Reply-To: <3633.1089055553@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: current@FreeBSD.org
Subject: Re: current syncer bug...
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, 05 Jul 2004 20:06:29 -0000

On  5 Jul, Poul-Henning Kamp wrote:
> 
> Waiting (max 60 seconds) for system process `vnlru' to stop...stopped
> Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped
> Waiting (max 60 seconds) for system process `syncer' to stop...0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Interesting ...

Does it ever print "stopped", or does it hit the 60 second timeout?

Is this a reboot in single user mode when nothing has been written?  If
so, the condition for calling kthread_suspend_check() probably needs to
look for (last_work_seen == -1 && net_worklist_len == 0), and
net_worklist_len needs to be set before this point.

Otherwise, in the following code fragment in sched_sync():

                if (syncer_state != SYNCER_RUNNING && starttime != time_second)
                        printf("%d ", net_worklist_len);

get rid of the (starttime != time_second) condition and add
last_work_seen to the printf().