From owner-freebsd-current@FreeBSD.ORG  Thu Sep 12 15:16:41 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 36E24899;
 Thu, 12 Sep 2013 15:16:41 +0000 (UTC)
 (envelope-from hiren.panchasara@gmail.com)
Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com
 [IPv6:2a00:1450:4013:c01::231])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9E24729D9;
 Thu, 12 Sep 2013 15:16:40 +0000 (UTC)
Received: by mail-ea0-f177.google.com with SMTP id f15so5295052eak.8
 for <multiple recipients>; Thu, 12 Sep 2013 08:16:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=FCzvyi26wuSqKjjXb3QRe6MT7w92i/U7EPQcAGajSDA=;
 b=DoOGkMSEMMEGhV1B7loLQ6CnzOs5SZ3SVtMNoems04TocqiXEWKw+jNJCXHweDKzum
 nzuLGtwT4MavZxTX6gzgg/QpOd8hYgIrqSRjT+vg/8bA44zl7WJAlD61XHiHxXDuMQDa
 icgGxw+DTsRRTLjwIm8P80qLzGWKerkKIzzM1102kJzSrfe7PBfdaaP3AsVZq2EKhxVs
 Xm53puyCrCqlroJkOLrLcQ9biEjRTbrvCamf/8CLibL6YrfT2fsoCPm1DrRLdfmvjZva
 RkUwKboVjOLIUhOOAgdwo7YhyWww8nrVsXrGnQXsIm5WleMdN6Nai2T86qb8OnGUn03P
 Apcg==
MIME-Version: 1.0
X-Received: by 10.14.119.196 with SMTP id n44mr530949eeh.116.1378998998959;
 Thu, 12 Sep 2013 08:16:38 -0700 (PDT)
Received: by 10.14.105.137 with HTTP; Thu, 12 Sep 2013 08:16:38 -0700 (PDT)
Received: by 10.14.105.137 with HTTP; Thu, 12 Sep 2013 08:16:38 -0700 (PDT)
In-Reply-To: <20130912092737.GC4574@FreeBSD.org>
References: <CALCpEUGherrJbmW9PBO7kSQk1Gj4zigGvvsRiyAwjk-USOXTUw@mail.gmail.com>
 <20130912092737.GC4574@FreeBSD.org>
Date: Thu, 12 Sep 2013 08:16:38 -0700
Message-ID: <CALCpEUGiAh_t-VPkQnU0wyUpEy7mqrLFfSNv_b5pdMg8ednAMw@mail.gmail.com>
Subject: Re: Intermittent hangs in vmem_periodic()
From: hiren panchasara <hiren.panchasara@gmail.com>
To: Gleb Smirnoff <glebius@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: freebsd-current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2013 15:16:41 -0000

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,
Hiren
>
> --
> Totus tuus, Glebius.