From owner-freebsd-current@FreeBSD.ORG Thu Sep 12 18:17:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8001CD23 for ; Thu, 12 Sep 2013 18:17:15 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0822C269B for ; Thu, 12 Sep 2013 18:17:14 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.7/8.14.7) with ESMTP id r8CIHBxU057769; Thu, 12 Sep 2013 22:17:11 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.7/8.14.7/Submit) id r8CIHBtQ057768; Thu, 12 Sep 2013 22:17:11 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 12 Sep 2013 22:17:11 +0400 From: Gleb Smirnoff To: hiren panchasara Subject: Re: Intermittent hangs in vmem_periodic() Message-ID: <20130912181711.GI4574@glebius.int.ru> References: <20130912092737.GC4574@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2013 18:17:15 -0000 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.