From owner-freebsd-stable@FreeBSD.ORG Sat Mar 13 17:47:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2D021065674 for ; Sat, 13 Mar 2010 17:47:23 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [76.96.27.228]) by mx1.freebsd.org (Postfix) with ESMTP id A5A5B8FC1D for ; Sat, 13 Mar 2010 17:47:23 +0000 (UTC) Received: from omta19.emeryville.ca.mail.comcast.net ([76.96.30.76]) by qmta15.emeryville.ca.mail.comcast.net with comcast id sg3x1d0061eYJf8AFhnQkw; Sat, 13 Mar 2010 17:47:24 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta19.emeryville.ca.mail.comcast.net with comcast id shnP1d0033S48mS01hnPKj; Sat, 13 Mar 2010 17:47:23 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 2BA779B436; Sat, 13 Mar 2010 09:47:22 -0800 (PST) Date: Sat, 13 Mar 2010 09:47:22 -0800 From: Jeremy Chadwick To: Torfinn Ingolfsen Message-ID: <20100313174722.GA95395@icarus.home.lan> References: <20100131144217.ca08e965.torfinn.ingolfsen@broadpark.no> <20100306141944.95ec8cb6.torfinn.ingolfsen@broadpark.no> <20100307122913.2f634018.torfinn.ingolfsen@broadpark.no> <20100313141113.cd215e62.torfinn.ingolfsen@broadpark.no> <20100313163848.GA94056@icarus.home.lan> <20100313183259.40fe1db2.torfinn.ingolfsen@broadpark.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100313183259.40fe1db2.torfinn.ingolfsen@broadpark.no> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Mar 2010 17:47:24 -0000 On Sat, Mar 13, 2010 at 06:32:59PM +0100, Torfinn Ingolfsen wrote: > On Sat, 13 Mar 2010 08:38:48 -0800 > Jeremy Chadwick wrote: > > > That enclosure also doesn't state if it has a SAF-TE or SES-2 chip on > > it. It's impossible to tell from the photos since the metallic > > enclosure cover up the backplane. > > Unfortunately, the "manual" is very brief and lacks such technical details / specs. > This is a very simple enclosure; I don't think it even has any sensors except for the fan and temperature sensors, > which are available at the signal out connector on the backplane. ...which is probably wired to some sort of interface chip that would toggle a buzzer/etc. if something goes awry. SAF-TE and/or SES-2 provide this capability, but so can a very simple circuit. How do you tune the thresholds for the temperature or fan? If they're DIP switches, then chances are SAF-TE or SES-2 aren't involved and it's probably just some cheap/generic logic chip that does the work. > > If it does, such chips can/will yank devices off the bus when the chip > > considers the drive "faulty". At least in the SCSI world with SES-2, > > Well, the manual states that this is a host function: > > 2.2 HDD FAIL system > 2.2.1 This product can not provide the signal, unless the HOST supports this function. > 2.2.2 If the Host can provide HDD fail signal, connect the cable to the HOST and to the backplane HDD FAIL 1 - 2 - 3 - 4 - 5. > 2.2.3 When the HDD is damaged, the light will show in red. > > There is a separate connector for HDD fail input signals on the backplane. There are also output signals for power, access for each drive. Is it a 4-pin connector? If so, what the manual is (horribly) trying to document is probably an SGPIO connector. SGPIO is a 4-pin connector which connects a SATA/SAS enclosure to a SATA/SAS HBA (controller) so that the two have a direct way to signal that a disk has physically failed -- otherwise, the controller has to make guesses about the state of things, and timeouts can take a while. SGPIO can also be used to provide other things; it's a generic communication interface with an official specification. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |