Date: Mon, 5 Jul 2004 13:06:21 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: phk@phk.freebsd.dk Cc: current@FreeBSD.org Subject: Re: current syncer bug... Message-ID: <200407052006.i65K6Lrf001926@gw.catspoiler.org> In-Reply-To: <3633.1089055553@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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().
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407052006.i65K6Lrf001926>