From owner-freebsd-current Fri Mar 21 20:23:31 2003 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 8792037B401 for ; Fri, 21 Mar 2003 20:23:29 -0800 (PST) Received: from smtp1.Stanford.EDU (smtp1.Stanford.EDU [171.64.14.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 057F143F75 for ; Fri, 21 Mar 2003 20:23:29 -0800 (PST) (envelope-from jstockdale@stanford.edu) Received: from quenya (quenya.Stanford.EDU [128.12.44.61]) by smtp1.Stanford.EDU (8.12.8/8.12.8) with ESMTP id h2M4NQ5u025607 for ; Fri, 21 Mar 2003 20:23:27 -0800 (PST) From: "John Stockdale" To: Subject: RE: mdconfig/mdmfs problems -> kernel panic Date: Fri, 21 Mar 2003 20:23:16 -0800 Message-ID: <000801c2f02a$c3ab47b0$3d2c0c80@quenya> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, I tried to recompile with the max users set to 256 to see if that would help things and while I was copying over the /src/sys tree to /mnt (the md0 device, 512MB) I got: panic: kmem_malloc(4096): kmem_map too small: 296222720 total allocated cpuid = 3; lapic.id = 070000000 Debugger("panic") Any suggestions? -----Original Message----- From: John Stockdale [mailto:jstockdale@stanford.edu] Sent: Monday, March 17, 2003 11:41 AM To: 'freebsd-current@FreeBSD.ORG' Subject: RE: mdconfig/mdmfs problems -> kernel panic Ahh, that explains why the multiple /dev/md* didn't help the problem. I'm looking into the vmstat options, but can't figure out how to extract the malloc-per-bucket-quota limit for the system (I've read man vmstat, and tried vmstat -z and vmstat -m, but the only "Limit" listed is under vmstat -z, and nothing indicates if any displayed limits are relavent to this discussion). Additionally, if I am hitting this limit, how can I increase the limit/what kind of impact would increasing the impact have on the system except in allowing me to user larger /dev/md*? Thanks. -John -----Original Message----- From: Poul-Henning Kamp [mailto:phk@phk.freebsd.dk] Sent: Monday, March 17, 2003 11:27 AM To: John Stockdale Cc: freebsd-current@FreeBSD.ORG Subject: Re: mdconfig/mdmfs problems -> kernel panic In message <000b01c2ecb7$1c089510$3d2c0c80@quenya>, "John Stockdale" writes: >OS: FreeBSD 5.0-CURRENT, JPSNAP20030314 > >I'm running a Dual Xeon system with 1GB DDRRAM, and trying to create a >ram disk to compile under, specifically to compile the kernel. > >I've tried several methods, involving either creating one 512MB disk >with mdconfig or mdmfs. No matter what options I specify, the mounted >mfs works fine until I start filling it up more. For instance, I can >usually copy the entire /usr/src/sys to /mnt and make depend, but a >while after I make the kernel panics as a result of the ram disk. >(specifically citing malloc errors, one time it speicifically spat out >a number in the order of 251XXXXXX and indicated a malloc bucket limit >exceeded or something like that) quote from md(4): malloc Backing store is allocated using malloc(9). Only one malloc- bucket is used, which means that all md devices with malloc backing must share the malloc-per-bucket-quota. The exact size of this quota varies, in particular with the amount of RAM in the system. The exact value can be determined with vmstat(8). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message