On Tue, Feb 21, 2017 at 06:39:08AM -0800, David Wolfskill wrote:
> This morning's daily "head" update & smoke-test was from:
> FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #263  
> r313988M/313991:1200021: Mon Feb 20 06:31:32 PST 2017     
> r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  amd64
> to
> FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #264  
> r314036M/314036:1200021: Tue Feb 21 05:52:20 PST 2017     
> r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  amd64
> On reboot, the system was very sluggish; unfortunately, I failed
> to try to quantify that until I had already started the reboot to
> stable/11 -- I had been waiting for it to finish the reboot for
> around 5 minutes, watching:  "Syncing disks, vnodes remaining ..."
> when the thought of noting the amount of elapsed time between reports
> of the numbers of remaining vnodes occurred to me: it was about 10
> seconds each.
> Normally, it's closer to 2 seconds, if that, IIRC.
> In any case, overall behavior seemed fairly consistent with that
> magnitude of a slowdown overall.

Can you check if the problem IS NOT present on r313995 but IS present on
r313996? Only rebuilding the kernel + modules is necessary.

If the problem was not introduced by r313996 I'm afraid you will have to

Mateusz Guzik <mjguzik gmail.com>
freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to