Re: i386 hangs during halt "vnodes remaining... 0 time out"

In message <YQBPR0101MB104221AA5DB8907D08A3CE02DD8A0_at_YQBPR0101MB1042.CAN
PRD01.P
ROD.OUTLOOK.COM>, Rick Macklem writes:
> Cy Schubert wrote:
> >In message <201804212227.w3LMRp5W002975_at_slippy.cwsent.com>, Cy Schubert
> writes:
> >> In message <20180421234934.10d7dfab_at_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 <rmacklem_at_uoguelph.ca> w
> rot
> >> 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.
> Patch seems to work for my i386 as well.
>
> Thanks, rick

Yes, thank you.


-- 
Cheers,
Cy Schubert <Cy.Schubert_at_cschubert.com>
FreeBSD UNIX:  <cy_at_FreeBSD.org>   Web:  http://www.FreeBSD.org

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