From owner-freebsd-current@FreeBSD.ORG Thu Jul 12 23:43:26 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A1FD4106566B; Thu, 12 Jul 2012 23:43:26 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 419FA8FC18; Thu, 12 Jul 2012 23:43:26 +0000 (UTC) Received: by qcsg15 with SMTP id g15so2169105qcs.13 for ; Thu, 12 Jul 2012 16:43:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:cc:x-mailer; bh=cDZ2IcC/PteIDB98nPSbbKQgAO56aex/8xQN3HmL/7w=; b=hFdutBDQF3VzHAw9VZavhLk8MsEG+ZWXFDUnNrkwmxIBw7MkiyrAuMX61Qxummh8I8 anWDBPFFV0BuOa/sAD+zmNyLrRf2UdCb+WnGuhEyO+HJUYcZClfaHwoi32xtGihtN8iC p0hhsR5mwjGAd+DmHjBsNIzc9FJhEH3+Uzp44yUNd3A0t18wT0sZyyOiLD3/KB7UOzjz oE0uUFKrpZRkIREK8tghdn2apmCu5U2Xy6zW1gbZlZgYL7a169otNbhEyAoAsM5Mzn7Z iKl6c/fKRMSm6nGYq63As9VJw1/g+C2IC1zvP86/gnt4yDVD5CuAaqCpVtmCKMfNa8qn ohsA== Received: by 10.224.40.2 with SMTP id i2mr7901951qae.62.1342136605547; Thu, 12 Jul 2012 16:43:25 -0700 (PDT) Received: from triad.knownspace (pool-71-163-84-156.washdc.fios.verizon.net. [71.163.84.156]) by mx.google.com with ESMTPS id cg7sm8859632qab.19.2012.07.12.16.43.24 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Jul 2012 16:43:24 -0700 (PDT) Message-Id: From: Justin Hibbits To: FreeBSD PowerPC ML Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Thu, 12 Jul 2012 19:43:23 -0400 X-Mailer: Apple Mail (2.936) Cc: freebsd-current Subject: panic with DEBUG_MEMGUARD on PowerPC 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: Thu, 12 Jul 2012 23:43:26 -0000 When tracking down a panic exposed by INVARIANTS, I tried setting DEBUG_MEMGUARD, so I could find the culprit that's trashing freed memory. However, this causes a panic at bootup. It shows up right after the first WARNING: WITNESS message, with the following: panic: kmem_suballoc: bad status return of 3 cpuid = 0 KDB: stack backtrace: 0xd0004ad0: at kdb_backtrace+0x4c 0xd0004b40: at panic+0x224 0xd0004ba0: at kmem_suballoc+0x8c 0xd0004bd0: at kmeminit+0x1ac 0xd0004c20: at mi_startup+0x13c 0xd0004c50: at btext+0xc0 Tracing, and printf() debugging, I see arguments to vm_map_findspace(): start: 0xD0000000, length: 4246446080, and map- >max_offset = 4026531839. Beyond that, I'm lost with tracking this down. Machine is a dual processor PowerPC G4, with 2GB RAM. Anyone have any ideas? Thanks, Justin