From owner-freebsd-current@FreeBSD.ORG Tue Sep 27 22:28:23 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 3D5E916A41F for ; Tue, 27 Sep 2005 22:28:23 +0000 (GMT) (envelope-from scottl@pooker.samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C469B43D48 for ; Tue, 27 Sep 2005 22:28:22 +0000 (GMT) (envelope-from scottl@pooker.samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j8RMSKrd014171; Tue, 27 Sep 2005 16:28:20 -0600 (MDT) (envelope-from scottl@pooker.samsco.org) Date: Tue, 27 Sep 2005 16:28:20 -0600 (MDT) From: Scott To: Pawel Worach In-Reply-To: Message-ID: <20050927162641.N5371@pooker.samsco.org> References: <20050927003401.GE72460@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org X-Mailman-Approved-At: Wed, 28 Sep 2005 11:22:52 +0000 Cc: current@freebsd.org, Kris Kennaway 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 22:28:23 -0000 On Tue, 27 Sep 2005, Pawel Worach wrote: > On 9/27/05, Kris Kennaway wrote: >> 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). > > False alarm, BETA5 with WITNESS and INVARIANTS re-enabled works just fine. > BETA1 was the only thing I had handy the first time and since mpt(4) > was unchanged I thought it would still be broken, I'll try to think > less next time :) > For future reference, how do I get hold of the M_BUS malloc type in > kern_malloc.c ? > > -- > Pawel > mpt likely is not the problem. It's the one that catches the misbehavior. Scott