Date: Thu, 12 Sep 2013 09:31:17 -0700 From: hiren panchasara <hiren.panchasara@gmail.com> To: Gleb Smirnoff <glebius@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Intermittent hangs in vmem_periodic() Message-ID: <CALCpEUHp81UCpFRfytd03iOrY1UT4M5ttMWkGuywVLr9sT6e7Q@mail.gmail.com> In-Reply-To: <CALCpEUGiAh_t-VPkQnU0wyUpEy7mqrLFfSNv_b5pdMg8ednAMw@mail.gmail.com> References: <CALCpEUGherrJbmW9PBO7kSQk1Gj4zigGvvsRiyAwjk-USOXTUw@mail.gmail.com> <20130912092737.GC4574@FreeBSD.org> <CALCpEUGiAh_t-VPkQnU0wyUpEy7mqrLFfSNv_b5pdMg8ednAMw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 12, 2013 at 8:16 AM, hiren panchasara < hiren.panchasara@gmail.com> wrote: > > On Sep 12, 2013 2:27 AM, "Gleb Smirnoff" <glebius@freebsd.org> wrote: > > > > On Wed, Sep 11, 2013 at 09:51:16PM -0700, hiren panchasara wrote: > > h> I am seeing really weird system freeze for 2-3 seconds every minute > or so. > > h> > > h> % uname -a > > h> FreeBSD flymockour-l7.corp.yahoo.com 10.0-CURRENT FreeBSD > 10.0-CURRENT #2 > > h> r255423M: Mon Sep 9 12:29:22 PDT 2013 root@flymocko > > h> ur-l7.corp.yahoo.com:/usr/obj/usr/home/hirenp/head/sys/GENERIC amd64 > > h> > > h> Simple comands like "man top" hangs and this is what I see in ctrl+T > > h> % man top > > h> load: 1.59 cmd: zcat 76574 [*kmem arena] 2.16r 0.00u 1.82s 16% 2000k > > h> load: 1.70 cmd: zcat 76574 [*kmem arena] 7.19r 0.00u 1.82s 7% 2000k > > h> load: 1.89 cmd: zcat 76574 [*kmem arena] 12.58r 0.00u 1.82s 3% 2000k > > h> load: 1.90 cmd: zcat 76574 [*kmem arena] 14.58r 0.00u 1.82s 2% 2000k > > h> > > h> I see similar things while trying to "exit" a terminal window. > > h> > > h> I see following in pmcstat: > > h> > > h> PMC: [INSTR_RETIRED_ANY] Samples: 117647 (100.0%) , 6885 unresolved > > h> > > h> %SAMP CALLTREE > > h> 75.9 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked > > h> vmem_periodic(75.9%) > > > > You probably got DIAGNOSTIC in your kernel config. > > Yes. And I've always had that. Never been a problem before. What has > changed? > Thanks Gleb. I've removed DIAGNOSTIC and the problem is gone now. But the way system was behaving with DIAGNOSTIC, its unusable. Thanks again, Hiren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALCpEUHp81UCpFRfytd03iOrY1UT4M5ttMWkGuywVLr9sT6e7Q>