From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 17 15:13:59 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9882C106564A; Mon, 17 Sep 2012 15:13:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6ECC98FC08; Mon, 17 Sep 2012 15:13:59 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id DB83AB911; Mon, 17 Sep 2012 11:13:58 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 17 Sep 2012 08:15:11 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201209170815.11113.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 17 Sep 2012 11:13:58 -0400 (EDT) Cc: hackers@freebsd.org, Vijay Singh Subject: Re: vm info from a hung system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Sep 2012 15:13:59 -0000 On Friday, September 14, 2012 1:32:43 am Vijay Singh wrote: > Need some expert help. I have a system that is hung hard, and I was > able to get it into gdb. From show_vmstat I see: > > (kgdb-amd64-7.4-95) show_vmstat > SYSTEM MEMORY INFORMATION: > mem_wire: 285970432 ( 272MB) Wired: disabled for paging out > mem_active: + 400105472 ( 381MB) Active: recently referenced > mem_inactive:+ 56840192 ( 54MB) Inactive: recently not referenced > mem_cache: + 0 ( 0MB) Cached: almost avail. for allocation > mem_free: + 0 ( 0MB) Free: fully available for allocation > mem_gap_vm: + 753664 ( 0MB) Memory gap: vm > -------------- ------------ ----------- ------ > mem_all: = 743669760 ( 709MB) Total real memory managed > mem_gap_sys: + 22765568 ( 21MB) Memory gap: system > -------------- ------------ ----------- > mem_phys: = 766435328 ( 730MB) Total phys memory > -------------- ------------ ----------- > > SYSTEM MEMORY SUMMARY: > mem_used: 709595136 ( 676MB) Used memory > mem_avail: + 56840192 ( 54MB) Available memory > -------------- ------------ ----------- ------ > mem_total: = 766435328 ( 730MB) Total memory > > What is this telling me? Oof. I think we generally don't cope with not having any free memory at all (mem_cache + mem_free). That is, I imagine the system was unable to make forward progress, possibly it had to malloc() something (GEOM is terrible for doing this) while trying to page out something to free up space. I would look at the state of the pagedaemon kthread to see why it isn't able to run. -- John Baldwin