Date: Thu, 12 Sep 2013 22:17:11 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: hiren panchasara <hiren.panchasara@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Intermittent hangs in vmem_periodic() Message-ID: <20130912181711.GI4574@glebius.int.ru> In-Reply-To: <CALCpEUHp81UCpFRfytd03iOrY1UT4M5ttMWkGuywVLr9sT6e7Q@mail.gmail.com> References: <CALCpEUGherrJbmW9PBO7kSQk1Gj4zigGvvsRiyAwjk-USOXTUw@mail.gmail.com> <20130912092737.GC4574@FreeBSD.org> <CALCpEUGiAh_t-VPkQnU0wyUpEy7mqrLFfSNv_b5pdMg8ednAMw@mail.gmail.com> <CALCpEUHp81UCpFRfytd03iOrY1UT4M5ttMWkGuywVLr9sT6e7Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 12, 2013 at 09:31:17AM -0700, hiren panchasara wrote: h> > > h> PMC: [INSTR_RETIRED_ANY] Samples: 117647 (100.0%) , 6885 unresolved h> > > h> h> > > h> %SAMP CALLTREE h> > > h> 75.9 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked h> > > h> vmem_periodic(75.9%) h> > > h> > > You probably got DIAGNOSTIC in your kernel config. h> > h> > Yes. And I've always had that. Never been a problem before. What has h> > changed? h> > h> h> Thanks Gleb. h> I've removed DIAGNOSTIC and the problem is gone now. h> h> But the way system was behaving with DIAGNOSTIC, its unusable. Please report that to Jeff. With DIAGNOSTIC the system can be slower, more chatty on console, but should be usable. -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130912181711.GI4574>