From owner-freebsd-current@FreeBSD.ORG Tue Sep 27 00:34:03 2005 Return-Path: X-Original-To: current@freebsd.org 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 7188A16A41F for ; Tue, 27 Sep 2005 00:34:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF64943D53 for ; Tue, 27 Sep 2005 00:34:02 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [70.30.70.180]) by elvis.mu.org (Postfix) with ESMTP id A4A941A3C19; Mon, 26 Sep 2005 17:34:02 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6B435513C1; Mon, 26 Sep 2005 20:34:01 -0400 (EDT) Date: Mon, 26 Sep 2005 20:34:01 -0400 From: Kris Kennaway To: Pawel Worach Message-ID: <20050927003401.GE72460@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d01dLTUuW90fS44H" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org Subject: Re: [releng_6] mpt(4) Memory modified after free panic 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: Tue, 27 Sep 2005 00:34:03 -0000 --d01dLTUuW90fS44H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Sep 26, 2005 at 11:55:53PM +0200, Pawel Worach wrote: > Trying to use a mpt controller with only one disk attached so it's not > possible to configure a RAID-1 volume. > Trying to boot 6.0-BETA1 install cd results in this panic. Should it > possible to use a single disk behind an mpt(4) with the updated driver? This > configuration works fine on 5.4. You should retry with 6.0-BETA5 - dozens of bugs have been fixed since then. If it persists, you should set up DEBUG_MEMGUARD to watch the M_BUS malloc type..this requires some minor source file editing and a kernel recompile (you can build it on e.g. 5.4). > Memory modified after free 0xc28a5710(12) val=0 @ 0xc28a5710 > panic: Most recently used by bus Kris --d01dLTUuW90fS44H Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDOJN5Wry0BWjoQKURAl9pAJ9j4Gkry1U7hdPUDPinvEb5HOgGrACg0932 J4f104sDVbCZeyn+ezyV8T8= =XSSu -----END PGP SIGNATURE----- --d01dLTUuW90fS44H--