Date: Sun, 15 Sep 2013 17:52:13 -0700 From: Davide Italiano <davide@freebsd.org> To: hiren panchasara <hiren.panchasara@gmail.com> Cc: Gleb Smirnoff <glebius@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: Intermittent hangs in vmem_periodic() Message-ID: <CACYV=-F20pxB0cQ9xEatO_u6F0j5jSO4_AnxsetM9%2B-v0Nfoxg@mail.gmail.com> 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
> > Thanks Gleb. > I've removed DIAGNOSTIC and the problem is gone now. > JFYI, I hit this problem today as well. I don't think you really need to disable DIAGNOSTIC completely in order to get rid of that. I've noticed Peter Holm has recently committed a new sysctl that allows you to selectively disable calls to vmem_check (debug.vmem_check), which should (probably) help. Thanks, -- Davide "There are no solved problems; there are only problems that are more or less solved" -- Henri Poincare
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACYV=-F20pxB0cQ9xEatO_u6F0j5jSO4_AnxsetM9%2B-v0Nfoxg>