From owner-freebsd-current@FreeBSD.ORG Tue Jul 20 11:55:31 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 B751D1065679 for ; Tue, 20 Jul 2010 11:55:31 +0000 (UTC) (envelope-from staale@kristoffersen.ws) Received: from mail-forward.uio.no (mail-forward.uio.no [129.240.10.42]) by mx1.freebsd.org (Postfix) with ESMTP id 36CA08FC0C for ; Tue, 20 Jul 2010 11:55:31 +0000 (UTC) Received: from mail-mx4.uio.no ([129.240.10.45]) by pat.uio.no with esmtp (Exim 4.67) (envelope-from ) id 1ObBQ1-0006ti-M1; Tue, 20 Jul 2010 13:55:29 +0200 Received: from putsch.kolbu.ws ([158.36.191.193]) by mail-mx4.uio.no with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1ObBQ1-0005Pm-8j; Tue, 20 Jul 2010 13:55:29 +0200 Received: from chiller by putsch.kolbu.ws with local (Exim 4.71 (FreeBSD)) (envelope-from ) id 1ObBQ0-000AOP-PA; Tue, 20 Jul 2010 13:55:28 +0200 Date: Tue, 20 Jul 2010 13:55:28 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen To: Marius Strobl Message-ID: <20100720115528.GA88965@putsch.kolbu.ws> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20100720101736.GD4706@alchemy.franken.de> User-Agent: Mutt/1.5.18 (2008-05-17) X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 787E571645372D1179EA67C39B36EB5C8270904F X-UiO-SPAM-Test: remote_host: 158.36.191.193 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 1766 max/h 11 blacklist 0 greylist 0 ratelimit 0 Cc: freebsd-current@freebsd.org, =?iso-8859-1?Q?St=E5le?= Kristoffersen 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: Tue, 20 Jul 2010 11:55:31 -0000 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. I'm trying to update the firmware on some of the drives now to see if that helps with the timeouts. -- Ståle Kristoffersen