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

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

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

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 + Rick Macklem

Failed buildworld buildkernel: /usr/obj/. . ./arm.armv7/tmp/usr/bin/ld: cannot find -lgcc_s for all_subdir_lib/libdl (a build race?)

I tried to amd64 -> armv7 cross build head -r332861 and got an error about -lgcc_s not being found. I backed off to -r332858 for other reasons (powerpc* related). Retrying the armv7 build then worked. I had first upgraded the amd64 context the first time and had backed off amd64 first the second

Re: SCHED_ULE makes 256Mbyte i386 unusable

> On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: > > I decided to start a new thread on current related to SCHED_ULE, since I see > > more than just performance degradation and on a recent current kernel. > > (I cc'd a couple of the people discussing performance problems in > >

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

Cy Schubert wrote: >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 >> >

Re: SCHED_ULE makes 256Mbyte i386 unusable

Konstantin Belousov wrote: >On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: >> I decided to start a new thread on current related to SCHED_ULE, since I see >> more than just performance degradation and on a recent current kernel. >> (I cc'd a couple of the people discussing

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

In message , Rick Macklem writes: > Cy Schubert wrote: > >In message <201804212227.w3lmrp5w002...@slippy.cwsent.com>, Cy Schubert > writes: > >> In message <20180421234934.10d7d...@kalimero.tijl.coosemans.org>,

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

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 > >

Re: SCHED_ULE makes 256Mbyte i386 unusable

On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote: > I decided to start a new thread on current related to SCHED_ULE, since I see > more than just performance degradation and on a recent current kernel. > (I cc'd a couple of the people discussing performance problems in >

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

On Sat, 21 Apr 2018 21:09: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

SCHED_ULE makes 256Mbyte i386 unusable

I decided to start a new thread on current related to SCHED_ULE, since I see more than just performance degradation and on a recent current kernel. (I cc'd a couple of the people discussing performance problems in freebsd-stable recently under a subject line of "Re: kern.sched.quantum: Creepy,

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

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