From owner-freebsd-current@freebsd.org  Sat Apr 21 22:09:57 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00E77FA822B
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sat, 21 Apr 2018 22:09:57 +0000 (UTC)
 (envelope-from clbuisson@orange.fr)
Received: from smtp.smtpout.orange.fr (smtp13.smtpout.orange.fr
 [80.12.242.135])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (Client CN "Bizanga Labs SMTP Client Certificate",
 Issuer "Bizanga Labs CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 62FE182C19
 for <freebsd-current@freebsd.org>; Sat, 21 Apr 2018 22:09:55 +0000 (UTC)
 (envelope-from clbuisson@orange.fr)
Received: from localhost ([90.5.43.84]) by mwinf5d75 with ME
 id dA9m1x00Q1oxXYi03A9nHo; Sun, 22 Apr 2018 00:09:48 +0200
X-ME-Helo: localhost
X-ME-Auth: Y2xidWlzc29uQHdhbmFkb28uZnI=
X-ME-Date: Sun, 22 Apr 2018 00:09:48 +0200
X-ME-IP: 90.5.43.84
Subject: Re: i386 hangs during halt "vnodes remaining... 0 time out"
To: Rick Macklem <rmacklem@uoguelph.ca>,
 "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
References: <YQBPR0101MB1042BF37F603335C9CE6346BDD8B0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM>
From: Claude Buisson <clbuisson@orange.fr>
Message-ID: <247bdb2f-d8b7-aba0-997d-050717cab100@orange.fr>
Date: Sun, 22 Apr 2018 00:09:46 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <YQBPR0101MB1042BF37F603335C9CE6346BDD8B0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Apr 2018 22:09:57 -0000

On 04/21/2018 23:09, Rick Macklem wrote:
> With a recent head/current kernel (doesn't happen when running a Dec. 2017 one),
> when I do a halt, it gets as far as:
> 
> vnodes remaining... 0 time out
> 
> and that's it (the time out appears several seconds after the first "0").
> With a Dec. 2017 kernel there would be several "0"s printed.
> It appears that it is stuck in the first iteration of the sched_sync() loop after
> it is no longer in SYNCER_RUNNING state.
> 
> Any ideas? rick
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
> 

There is a PR which seems related: 227404

I was hit by this problem when upgrading an i386 UP system from r329142 
to r332518. The culprit appears to be r329612.

I reverted 4 files:

sys/kern/vfs_bio.c -> r329187
sys/kern/vfs_subr.c -> r328643
sys/sys/buf.h -> r329078
sys/sys/bufobj.h -> r326256

rebuild the system, and the hang disappeared.

I have now 2 i386 UP and 1 amd64 MP systems running with this 
modification, and 1 RPI2 in the pipe line.

Hope it helps

Claude Buisson