From owner-freebsd-scsi@freebsd.org Wed Jul 8 07:35:21 2015 Return-Path: Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88B5899698F for ; Wed, 8 Jul 2015 07:35:21 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1ED371D25 for ; Wed, 8 Jul 2015 07:35:20 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by wgck11 with SMTP id k11so187741550wgc.0 for ; Wed, 08 Jul 2015 00:35:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=Bv1GYo55/ZOiCYSpeqLXrv+L7UWzkM6EcxbbJKWYUbc=; b=IqMzuvy3zvf1BRy47qiyOzSKI7RwDgIvsk5dE4QF6Slu1W/Eo7mfiBSsseD10hJCiu b8cNlsQCB5ftD8vW57wBp+yYFOyP6HYknGfodI2FgedtjYbgzjobUl8uFo8u7Nv1JfT/ ovMzpvHm8n+I0egWj8LfQlo5nPBtavBcbvu1MU7peqNgoXVyg87MIQE+9mgvAlIF6ZWh khP3LMjE04gHV0awFz57pc2kNqPH+E3Fl5YEoZicFK2AalEvzAsmlMH/ysnxBwsciC+M abv8ZJfsOu+ux+mTbS9U5GLlZG2de0qTeUE+aZJXX1o3U/oUN7TZmCCrZTSSH2XGFMx2 Nwnw== X-Gm-Message-State: ALoCoQkQ6fHpz42Ah2N/Ga1XVaqOf7IK4Wn3Sh6jDJJZn7VImFfXaMPtsKHUOpetAGZovidwmSgX X-Received: by 10.180.188.48 with SMTP id fx16mr71531067wic.35.1436340918422; Wed, 08 Jul 2015 00:35:18 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by smtp.gmail.com with ESMTPSA id c2sm1945437wjf.18.2015.07.08.00.35.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Jul 2015 00:35:17 -0700 (PDT) Subject: Re: Device timeouts(?) with LSI SAS3008 on mpr(4) To: Yamagi Burmeister References: <20150707132416.71b44c90f7f4cd6014a304b2@yamagi.org> <9426ced85d7def424e106fdefd7448ae@mail.gmail.com> <20150707183135.2c3f5aa45696b55a17e2f87f@yamagi.org> <559C0184.4050102@multiplay.co.uk> <20150708074652.07a815e6aa08526d569f3077@yamagi.org> Cc: freebsd-scsi@freebsd.org From: Steven Hartland Message-ID: <559CD2B3.7000404@multiplay.co.uk> Date: Wed, 8 Jul 2015 08:35:15 +0100 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 MIME-Version: 1.0 In-Reply-To: <20150708074652.07a815e6aa08526d569f3077@yamagi.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jul 2015 07:35:21 -0000 Actually not, it could indicate a design problem with the midplane / backplane is the cause of the issue. We've had a number of Supermicro and Dell chassis when used in combination with 6Gbps+ devices particularly SSD's that exhibit timeouts like you describe, all turned out to be a backplane issue. We proved this in by connecting the drives direct to the controller with high quality cables eliminating the hotswap backplane, after which the timeouts stopped. This is a PITA to test as power is supplied by the hotswap backplane, but I wouldn't recommend you look anywhere else till you've eliminated this as a potential cause. Regards Steve On 08/07/2015 06:46, Yamagi Burmeister wrote: > Hello Steven, > since the issue occures on all 3 servers it's at least unlikely. But > I'll see what I can do. > > Regards, > Yamagi > > On Tue, 7 Jul 2015 17:42:44 +0100 > Steven Hartland wrote: > >> Have you eliminated the midplane / cabling as the issue as that's very >> common. >>