From owner-freebsd-current@FreeBSD.ORG Wed Feb 15 01:51:12 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FFEF16A420 for ; Wed, 15 Feb 2006 01:51:12 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69FE443D48 for ; Wed, 15 Feb 2006 01:51:10 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k1F1p7d6054088 for ; Wed, 15 Feb 2006 03:51:07 +0200 (EET) (envelope-from dmitry@atlantis.dp.ua) Date: Wed, 15 Feb 2006 03:51:07 +0200 (EET) From: Dmitry Pryanishnikov To: freebsd-current@freebsd.org Message-ID: <20060215024339.N22450@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Wed, 15 Feb 2006 02:40:33 +0000 Subject: Virtual memory consumption (both user and kernel) in modern CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 15 Feb 2006 01:51:12 -0000 Hello! I've got a relatively fresh (12-Feb-2006 14:20 UTC) CURRENT on my ASUS M5A notebook (CPU Pentium M 1.86GHz, 256 Mb memory), kernel config is: ftp://external.atlantis.dp.ua/FreeBSD/CURRENT/NOTEBOOK I have several questions regarding virtual memory use, both user-mode and kernel. 1) Is it normal that virtual memory size for almost every non-kernel process is close to 50Mb now: ftp://external.atlantis.dp.ua/FreeBSD/CURRENT/top.txt Is it miscalculation or real growth of virtual address space? 2) I can _trivially_ crash my box by extracting and deleting Openoffice.org distribution: cd /usr/ports/editors/openoffice.org-2.0 NOCLEANDEPENDS=yes make extract clean However, I can't obtain crash dump in most cases, see the picture: ftp://external.atlantis.dp.ua/FreeBSD/CURRENT/nodump.jpg Is it due to new ATA DMA dump code, or due to some other reason? I've never seen such dump failures before. 3) Once I was lucky enought to obtain a valid crash dump in this situation. Here is the backtrace: ftp://external.atlantis.dp.ua/FreeBSD/CURRENT/bt What tunables can I use to prevent this panic? Alas tuning(7) doesn't say anything about "mem_map too small". Is it tuning issue at all or a bug? Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE