From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 12 03:36:32 2009 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92383106566C for ; Thu, 12 Feb 2009 03:36:32 +0000 (UTC) (envelope-from spork@bway.net) Received: from xena.bway.net (xena.bway.net [216.220.96.26]) by mx1.freebsd.org (Postfix) with ESMTP id 497B08FC17 for ; Thu, 12 Feb 2009 03:36:32 +0000 (UTC) (envelope-from spork@bway.net) Received: (qmail 74604 invoked by uid 0); 12 Feb 2009 03:36:31 -0000 Received: from unknown (HELO toasty.nat.fasttrackmonkey.com) (spork@96.57.144.66) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 12 Feb 2009 03:36:31 -0000 Date: Wed, 11 Feb 2009 22:36:30 -0500 (EST) From: Charles Sprickman X-X-Sender: spork@toasty.nat.fasttrackmonkey.com To: Scott Long In-Reply-To: <49911C68.6030203@samsco.org> Message-ID: References: <49911C68.6030203@samsco.org> User-Agent: Alpine 2.00 (OSX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-scsi@freebsd.org Subject: Re: 7.1 Panic on degraded disk w/mpt X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2009 03:36:32 -0000 More info... On Mon, 9 Feb 2009, Scott Long wrote: > Charles Sprickman wrote: >> (posted on -stable already, no takers - added info: full dmesg, crash info >> from panic when array finished rebuilding, some comments on dmesg) >> >> Howdy, >> >> I dug around and can't find a PR on this, and the only other report I saw >> was in this mailing list post that has no replies: >> >> http://www.nabble.com/7.1-BETA2-panic-on-mpt-degrade-td20183173.html >> >> The hardware is a Dell PowerEdge 860 with the Dell/LSI SAS5 controller: >> >> mpt0: port 0xec00-0xecff mem >> 0xfe9fc000-0xfe9fffff,0xfe9e0000-0xfe9effff irq 16 at device 8.0 on pci2 >> mpt0: MPI Version=1.5.13.0 >> >> The panic is repeatable by forcing the array into a degraded state. When >> the array finishes rebuilding, the box also panics. >> >> Here's my best shot at getting info out of kgdb (panic on array going to >> degraded state): > > I wonder if the MPT card is temporarily detaching and then reattaching > the logical drive when the rebuild completes. The info you posted is > inconclusive here. I was able to get it to panic again, and grabbed a picture of the console that includes the output just before the panic. It does appear the device goes away: mpt0: mpt_cam_event: 0x16 mpt0: mpt_cam_event: 0x12 mpt0: mpt_cam_event: 0x16 (mpt0:vol0:1): Physical Disk Status Changed mpt0: mpt_cam_event: 0x15 mpt0: mpt_cam_event: 0x21 (mpt0:vol0:1): Physical Disk Status Changed mpt0:vol0(mpt0:0:0): Volume Status Changed mpt0: mpt_cam_event: 0x15 mpt0: mpt_cam_event: 0x21 mpt0: mpt_cam_event: 0x15 mpt0: mpt_cam_event: 0x21 mpt0:vol0(mpt0:0:0): RAID-1 - Degraded mpt0:vol0(mpt0:0:0): Status ( Enabled ) (mpt0:vol0:1): No longer configured Fatal Trap 12.... blah blah blah Is that information of any use? Does "No longer configured" = device detached? Thanks, Charles > CAM (the FreeBSD SCSI layer) has had some problems handling device > detaches, but we've been very fortunate to have someone examining and > fixing this recently. Would it be possible for you to upgrade to the > most recent 8-CURRENT tree, and re-run your test? If not, I'll see > about generating a patchset against 7.1. > > Scott >