Date: Sun, 22 Apr 2018 00:09:46 +0200 From: Claude Buisson <clbuisson@orange.fr> To: Rick Macklem <rmacklem@uoguelph.ca>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: i386 hangs during halt "vnodes remaining... 0 time out" Message-ID: <247bdb2f-d8b7-aba0-997d-050717cab100@orange.fr> In-Reply-To: <YQBPR0101MB1042BF37F603335C9CE6346BDD8B0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM> References: <YQBPR0101MB1042BF37F603335C9CE6346BDD8B0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?247bdb2f-d8b7-aba0-997d-050717cab100>