From owner-freebsd-stable@FreeBSD.ORG Fri Jan 26 18:39:33 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0D9516A402 for ; Fri, 26 Jan 2007 18:39:33 +0000 (UTC) (envelope-from pekkas@netcore.fi) Received: from netcore.fi (netcore.fi [193.94.160.1]) by mx1.freebsd.org (Postfix) with ESMTP id 4F84B13C494 for ; Fri, 26 Jan 2007 18:39:33 +0000 (UTC) (envelope-from pekkas@netcore.fi) Received: from localhost (pekkas@localhost) by netcore.fi (8.12.11.20060614/8.12.11) with ESMTP id l0QHt3sL032667 for ; Fri, 26 Jan 2007 19:55:03 +0200 Date: Fri, 26 Jan 2007 19:55:03 +0200 (EET) From: Pekka Savola To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.88.7/2492/Thu Jan 25 21:04:35 2007 on otso.netcore.fi X-Virus-Status: Clean X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS autolearn=failed version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on otso.netcore.fi Subject: panic: kmem_malloc boot error w/ 6.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 18:39:33 -0000 Hello, (Not subscribed, let's hope this gets through..) I saw the strangest case I've yet seen today when upgrading a dual-P3 system using sources (buildworld etc.) from FreeBSD 5.5 to RELENG_6 (6.2). The system paniced at boot with a message like: panic: kmem_malloc(-1059844096): kmem_map too small: 2990080 total allocated This seemed to be just before one would mount the root filesystem. GENERIC kernel on 6.2-RELEASE boot CD worked though. FreeSBIE 2.0 kernel (6.2-RELEASE) panicked in the same way, as well as another Rescue CD based on FreeBSD 6.1. I did a fair bit of bisecting (about 10 compiles) to find out which feature in GENERIC removes this panic, and came to a suprising conclusion: makeoptions DEBUG=-g .. when I added this, boot works fine. When removing it, you get the panic. Strange, huh? :-/ Below is a snippet of the boot log: ... acd0: DVDROM at ata0-master UDMA33 afd0: 6869804134400MB at ata2-master PIO3 acd1: CDROM at ata2-slave PIO3 amr0: delete logical drives supported by controller amrd0: on amr0 amrd0: 139900MB (286515200 sectors) RAID 1 (optimal) panic: kmem_malloc(-1059844096): kmem_map too small: 2990080 total allocated Uptime: 2s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings