From owner-freebsd-current@FreeBSD.ORG Wed Jun 30 00:41:59 2004 Return-Path: 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 D5AFC16A4CE for ; Wed, 30 Jun 2004 00:41:59 +0000 (GMT) Received: from smtp15.wxs.nl (smtp15.wxs.nl [195.121.6.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0DB543D4C for ; Wed, 30 Jun 2004 00:41:59 +0000 (GMT) (envelope-from ronald-freebsd7@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210]) by smtp15.wxs.nlSMTP id <0I0300C1VJ8VIQ@smtp15.wxs.nl> for current@freebsd.org; Wed, 30 Jun 2004 02:41:19 +0200 (CEST) Received: (qmail 9013 invoked from network); Wed, 30 Jun 2004 00:41:18 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Wed, 30 Jun 2004 00:41:18 +0000 Received: (qmail 2731 invoked from network); Wed, 30 Jun 2004 00:41:18 +0000 Received: from unknown (HELO guido.thuis.klop.ws) (192.168.0.2) by 192.168.0.16 with SMTP; Wed, 30 Jun 2004 00:41:18 +0000 Received: (qmail 5589 invoked from network); Wed, 30 Jun 2004 00:41:17 +0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; Wed, 30 Jun 2004 00:41:17 +0000 Date: Wed, 30 Jun 2004 02:41:16 +0200 From: Ronald Klop In-reply-to: To: current@freebsd.org Message-id: MIME-version: 1.0 Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT User-Agent: Opera M2/7.51 (FreeBSD, build 689) References: Subject: Re: panic: kmem_malloc; Should I increase some setting? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 30 Jun 2004 00:42:00 -0000 I have more info. When untarring a bzip2 archive of 30MB the nr of wired mem in top goes up, until it reaches 120MB and than it panics. (Normally it is around 50/60MB.) How can I debug this more or can others reproduce this? Greetings, Ronald. On Wed, 30 Jun 2004 02:10:16 +0200, Ronald Klop wrote: > Hello, > > I get the following panics while untarring a 30MB archive on an md device > create with: > tmpmfs="YES" > tmpsize="256m" > > There is plenty of disk space and plenty of swap on the time of the > panic. > What info can I provide. The kernel will not make a kernel dump on > /dev/ad1s1b, but I don't know why. > My dmesg is attached. > > Greetings, Ronald. > > > > > panic: kmem_malloc(16384): kmem_map too small: 86233088 total allocated > > syncing disks, buffers remaining... panic: kmem_malloc(4096): kmem_map > too > small > : 86233088 total allocated > Uptime: 4m1s > Dumping 255 MB > ad1: timeout waiting for write DRQad1: timeout waiting for write DRQ > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc04a5653 > stack pointer = 0x10:0xcbb8933c > frame pointer = 0x10:0xcbb89358 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 44 (syncer) > trap number = 12 > panic: page fault > Uptime: 4m2s > pfs_vncache_unload(): 1 entries remaining > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > > > > > And I just got another one: (This one gives a M_WAITOK) > > panic: kmem_malloc(4096): kmem_map too small: 86233088 total allocated > > syncing disks, buffers remaining... panic: malloc(M_WAITOK) returned NULL > Uptime: 3m33s > Dumping 255 MB > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc04a5653 > stack pointer = 0x10:0xcbb893c0 > frame pointer = 0x10:0xcbb893dc > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 44 (syncer) > trap number = 12 > panic: page fault > Uptime: 3m34s > pfs_vncache_unload(): 1 entries remaining > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > -- Ronald Klop Amsterdam, The Netherlands