From owner-freebsd-stable@FreeBSD.ORG Sun Jan 28 00:47:00 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 9C30B16A400 for ; Sun, 28 Jan 2007 00:47:00 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.freebsd.org (Postfix) with SMTP id 013F613C48D for ; Sun, 28 Jan 2007 00:46:59 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 27 Jan 2007 20:34:01 +0000 (GMT) Date: Sat, 27 Jan 2007 20:34:00 +0000 From: David Malone To: Pekka Savola Message-ID: <20070127203400.GA7155@walton.maths.tcd.ie> References: <45BA86B6.3090609@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-stable@freebsd.org Subject: Re: 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: Sun, 28 Jan 2007 00:47:00 -0000 On Sat, Jan 27, 2007 at 09:22:43AM +0200, Pekka Savola wrote: > malloc(c0d40100,c06eab00,2,c620dc00,c5ff6600,...) at malloc+0x81 This is a very big malloc (0xc0d40100 bytes) - it looks like a pointer has been passed instead of a size. > g_read_data(c60fb480,0,0,c0d40100,0,0) at g_read_data+0x3c This is trying to read from the disk - again, it thinks the read length is 0xc60fb480. > g_mbr_taste(c0709040,c620dc00,0) at g_mbr_taste+0x127 This means it is trying to read the MBR at the time and the length it passes is supposed to be the sector size! I'd guess that either there is something very weird about the disk, something is forgetting to initialise the sector size or there's memory corruption going on. David.