In message <201804212227.w3lmrp5w002...@slippy.cwsent.com>, Cy Schubert 
writes:
> In message <20180421234934.10d7d...@kalimero.tijl.coosemans.org>, Tijl 
> Cooseman
> s writes:
> > --MP_/TDsO+CDIra7UXGs=vVO3NTB
> > Content-Type: text/plain; charset=US-ASCII
> > Content-Transfer-Encoding: 7bit
> > Content-Disposition: inline
> >
> > On Sat, 21 Apr 2018 21:09:09 +0000 Rick Macklem <rmack...@uoguelph.ca> wrot
> e:
> > > 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
> >
> > See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227404
> > I have a patch (attached) but haven't been able to test it yet.
>
> I've noticed this as well on my old Penium-M laptop (updated about 
> twice a year). I'll try your patch this weekend or early next week.

Works perfectly.


-- 
Cheers,
Cy Schubert <cy.schub...@cschubert.com>
FreeBSD UNIX:  <c...@freebsd.org>   Web:  http://www.FreeBSD.org

        The need of the many outweighs the greed of the few.


_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to