From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 14:34:53 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 CD506106564A for ; Sun, 18 Jul 2010 14:34:53 +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 52B3E8FC08 for ; Sun, 18 Jul 2010 14:34:53 +0000 (UTC) Received: from mail-mx2.uio.no ([129.240.10.30]) by pat.uio.no with esmtp (Exim 4.67) (envelope-from ) id 1OaUx9-0002em-QD; Sun, 18 Jul 2010 16:34:51 +0200 Received: from putsch.kolbu.ws ([158.36.191.193]) by mail-mx2.uio.no with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1OaUx9-0003bG-9H; Sun, 18 Jul 2010 16:34:51 +0200 Received: from chiller by putsch.kolbu.ws with local (Exim 4.71 (FreeBSD)) (envelope-from ) id 1OaUx8-0005rM-OI; Sun, 18 Jul 2010 16:34:50 +0200 Date: Sun, 18 Jul 2010 16:34:50 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen To: =?iso-8859-1?Q?St=E5le?= Kristoffersen Message-ID: <20100718143450.GA29150@putsch.kolbu.ws> References: <20100715123423.GC52222@putsch.kolbu.ws> <20100715160048.GA61891@alchemy.franken.de> <20100715175225.GA52693@putsch.kolbu.ws> <20100716103125.GA73878@putsch.kolbu.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20100716103125.GA73878@putsch.kolbu.ws> 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: 08548F51E483148FA44EB6B7C839CDD4464D3756 X-UiO-SPAM-Test: remote_host: 158.36.191.193 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 1729 max/h 11 blacklist 0 greylist 0 ratelimit 0 Cc: freebsd-current@freebsd.org, Marius Strobl 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: Sun, 18 Jul 2010 14:34:53 -0000 On 2010-07-16 at 12:31, Ståle Kristoffersen wrote: > On 2010-07-15 at 19:52, Ståle Kristoffersen wrote: > > On 2010-07-15 at 18:00, Marius Strobl wrote: > > > On Thu, Jul 15, 2010 at 02:34:23PM +0200, Stle Kristoffersen wrote: > > > > Upgraded to from stable to current yesterday and very quickly received a > > > > panic. It did however not dump it's core, so I was unable to debug it. > > > > Today it did panic again, and I took a picture: (Sorry about the bad > > > > quality) > > > > > > > > http://folk.uio.no/stalk/mpt/IMG_1403.JPG > > > > > > > > And from the backtrace: > > > > http://folk.uio.no/stalk/mpt/IMG_1404.JPG > > > > > > > > Both times I hade the mpt0: request timed out just before the panic. > > > > > > > > I'm not sure why it's not dumping it's core (It was working under stable, > > > > and I have dumpdev="AUTO" and dumpdir="/var/crash" in rc.conf) > > > > > > What revision were you using? > > > > Not sure exactly what revision I was using, is there an easy way to figure > > that out? I ran cvsupdate around 13:00 CEST yesterday. > > > > > Does using current as of r209598 make a difference? > > > > Downgrading now... > > And it crashed again, with current from r209598... It still keeps on crashing :/ I grabbed the output of show alllocks: http://folk.uio.no/stalk/mpt/IMAG0047.jpg To me it looks like maybe there is a race condition or something that makes TAILQ_REMOVE-call in mpt_scsi_tmf_reply_handler() work on an element that has been removed, but this is an un-educated guess ;) I do not understand enough of the driver to follow the flow of the requests around the driver. -- Ståle Kristoffersen