From owner-freebsd-current@FreeBSD.ORG Fri Sep 24 16:42:14 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA7A9106564A for ; Fri, 24 Sep 2010 16:42:14 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 3A21A8FC14 for ; Fri, 24 Sep 2010 16:42:13 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id o8OGgCrq017189; Fri, 24 Sep 2010 18:42:12 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id o8OGgCAI017188; Fri, 24 Sep 2010 18:42:12 +0200 (CEST) (envelope-from marius) Date: Fri, 24 Sep 2010 18:42:12 +0200 From: Marius Strobl To: =?unknown-8bit?Q?St=E5le?= Kristoffersen Message-ID: <20100924164212.GO46946@alchemy.franken.de> References: <20100715123423.GC52222@putsch.kolbu.ws> <20100715160048.GA61891@alchemy.franken.de> <20100715175225.GA52693@putsch.kolbu.ws> <20100716103125.GA73878@putsch.kolbu.ws> <20100718122022.GW4706@alchemy.franken.de> <20100719170654.GA19889@putsch.kolbu.ws> <20100720101736.GD4706@alchemy.franken.de> <20100720115528.GA88965@putsch.kolbu.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100720115528.GA88965@putsch.kolbu.ws> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: current + mpt = panic: Bad link elm 0xffffff80002d6480 next->prev != elm 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: Fri, 24 Sep 2010 16:42:14 -0000 On Tue, Jul 20, 2010 at 01:55:28PM +0200, Stle Kristoffersen wrote: > On 2010-07-20 at 12:17, Marius Strobl wrote: > > On Mon, Jul 19, 2010 at 07:06:54PM +0200, Stle Kristoffersen wrote: > > > On 2010-07-18 at 14:20, Marius Strobl wrote: > > > > > > Downgrading now... > > > > > > > > > > And it crashed again, with current from r209598... > > > > > > > > > > > > > Ok, this at least means that your problem isn't caused by the recent > > > > changes to mpt(4) as the pre-r209599 version only differed from the > > > > 8-STABLE one in a cosmetic change at that time. > > > > > > I have another data-point, I cvsup'ed to the latest current again, and > > > rebuilt without INVARIANT and WITNESS, and now it seems to survive the > > > timeouts. > > > > That's more or less expected as the sanity check issuing the panic > > just isn't compiled in then. However, my understanding was that with > > STABLE you don't get the timeouts in the first place, or do you see > > them there also? > > I got the timeouts with STABLE as well, that was the reason for me to > try out CURRENT. I'm sorry I didn't mention that earlier. > > My main concern is to get rid of the timeouts, but a panic on one can't be > right. How can I debug this further? I can get timeout fairly consistent by > putting a bit of load on the drives. If it would help I can also provide > remote access. > FYI, that panic is fixed with r213105. Marius