From owner-freebsd-stable@FreeBSD.ORG Thu Aug 1 20:20:31 2013 Return-Path: Delivered-To: freebsd-stable@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 96DB65CE; Thu, 1 Aug 2013 20:20:31 +0000 (UTC) (envelope-from msa@latt.net) Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 49A9328E1; Thu, 1 Aug 2013 20:20:31 +0000 (UTC) Received: from puck.nether.net (localhost [127.0.0.1]) by puck.nether.net (8.14.7/8.14.5) with ESMTP id r71KGhMr002422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 1 Aug 2013 16:16:44 -0400 Received: (from majdi@localhost) by puck.nether.net (8.14.7/8.14.7/Submit) id r71KGgu4002419; Thu, 1 Aug 2013 16:16:42 -0400 X-Authentication-Warning: puck.nether.net: majdi set sender to msa@latt.net using -f Date: Thu, 1 Aug 2013 16:16:42 -0400 From: "Majdi S. Abbas" To: Marius Strobl Subject: Re: i386/179112: 9.1 installer panics with a kmem_malloc() failure on i386 embedded systems Message-ID: <20130801201640.GA25247@puck.nether.net> References: <201308011322.r71DMlPO089919@freefall.freebsd.org> <20130801192222.GV56034@alchemy.franken.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20130801192222.GV56034@alchemy.franken.de> X-Message-Flag: Follow up User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.1 (puck.nether.net [127.0.0.1]); Thu, 01 Aug 2013 16:16:44 -0400 (EDT) Cc: Adrian Chadd , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2013 20:20:31 -0000 On Thu, Aug 01, 2013 at 09:22:22PM +0200, Marius Strobl wrote: > That's a very vague description of a test case. At least extracting > the six release tarballs is no longer a problem, though. If it helps any, it'd usually panic when expanding base.tgz during the install. Failing that, src. You can't predict which large file would do it, but without both parameters set, it would fail 100% of the time. However, it's possible that removing CTL from GENERIC frees up enough RAM for it to squeak by with no other changes. 64M would be an interesting test case. Here's what one of the panics looked like: FreeBSD Installer ÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒ ÏÒÒÒÒÒÒÒÒÒÒÒÒArchive ExtractionÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÎ ¯ ¯ ¯ base.txz [ 57% ] ¯ ¯ kernel.txz [ Pending ]panic: kmem_malloc( 4096): kmem_map too small: 38060032 total allocated ¯ cpuid = 0 ¯ Extracting distribution files... ¯ KDB: stack backtrace: ¯ #0 0xc0af3aff at kdb_backtrace+0x4fssÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÎ ¯ #1 0xc0ac052f at panic+0x16f 53% ¯ ¯ #2 0xc0d2caea at kmem_malloc+0x28aÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÍ ¯ #3 0xc0d202b7 at page_alloc+0x27ÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÒÍ #4 0xc0d22bca at keg_alloc_slab+0x10a #5 0xc0d23164 at keg_fetch_slab+0xd4 #6 0xc0d234ec at zone_fetch_slab+0x4c #7 0xc0d24ade at uma_zalloc_arg+0x4ae #8 0xc0aab29a at malloc+0x5a #9 0xc0ce922a at newjsegdep+0x2a #10 0xc0cf5a89 at newjaddref+0x69 #11 0xc0cf5b16 at softdep_setup_inomapdep+0x56 #12 0xc0cd9398 at ffs_nodealloccg+0x728 #13 0xc0cd3d91 at ffs_hashalloc+0x41 #14 0xc0cd8913 at ffs_valloc+0x4a3 #15 0xc0d15c14 at ufs_makeinode+0xa4 #16 0xc0d164a0 at ufs_create+0x30 #17 0xc0e48412 at VOP_CREATE_APV+0x42 Uptime: 8m5s Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. --msa