From owner-freebsd-stable@FreeBSD.ORG Mon Dec 17 22:18:33 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 865281CF for ; Mon, 17 Dec 2012 22:18:33 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-wg0-f52.google.com (mail-wg0-f52.google.com [74.125.82.52]) by mx1.freebsd.org (Postfix) with ESMTP id 0D6A38FC14 for ; Mon, 17 Dec 2012 22:18:32 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id 12so2846381wgh.31 for ; Mon, 17 Dec 2012 14:18:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=r2QSjauhtRrBjFM8er+6haW/fN6CudBeBeewzR+BGhE=; b=ghJH8SbgYGc8eaoeBUOAJOoOb4hv8zINj1vY5BrnPyR1jYUYXQ9+3iGOhXGn1Vi/j/ yE/cpld0IAOubbFkUkCXS0IyiwgQ5sWq/ECo59R57kCpvHkhztvk6I51hM4bIbQqegqL oc3XXFF/scOcH2PB7mRpli4jKISV4WoO0W8SUG+qiU1rceKG46LSuLH95jjVgo+oWzJ3 XFEVAikvbYoHGdB1sHwDS9DGljx9Pj21jZ78L8R6PsXk5f5yeanwrpyJD98f172wIFiq TyXnD4QUZKhdETSg1bevL9KamMh+sgR+hS0ZozPupj5it1sIlK8gfbcApPWOfDx+Zo6W FABg== Received: by 10.194.83.36 with SMTP id n4mr9493295wjy.59.1355782711935; Mon, 17 Dec 2012 14:18:31 -0800 (PST) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id w5sm13138634wif.11.2012.12.17.14.18.30 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Dec 2012 14:18:31 -0800 (PST) Sender: Alexander Motin Message-ID: <50CF9A2F.5080300@FreeBSD.org> Date: Tue, 18 Dec 2012 00:18:23 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120628 Thunderbird/13.0.1 MIME-Version: 1.0 To: Mike Tancsa Subject: Re: WRITE_FPDMA_QUEUED CAM status: ATA Status Error References: <50CF97A5.6090806@sentex.net> In-Reply-To: <50CF97A5.6090806@sentex.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Dec 2012 22:18:33 -0000 Hi. On 18.12.2012 00:07, Mike Tancsa wrote: > Is there a way to tell / narrow down if an issue with errors like below > are due to a bad cable or bad port multiplier ? The disks in a > particular cage are throwing errors like these below. (RELENG9 from today) All the controller, the port multiplier and the disks are firmware- based devices. All of them may have firmware problems, that is not possible to diagnose from outside. When controller is talking to disk, multiplier is transparent, so it may be impossible to say where exactly problem happen. Speaking about cables and physical links, the only kind of information I can imagine to check physical link is counters represented below: > SATA Phy Event Counters (GP Log 0x11) > ID Size Value Description > 0x0001 2 1 Command failed due to ICRC error > 0x0002 2 1 R_ERR response for data FIS > 0x0003 2 0 R_ERR response for device-to-host data FIS > 0x0004 2 1 R_ERR response for host-to-device data FIS > 0x0005 2 0 R_ERR response for non-data FIS > 0x0006 2 0 R_ERR response for device-to-host non-data FIS > 0x0007 2 0 R_ERR response for host-to-device non-data FIS > 0x000a 2 0 Device-to-host register FISes sent due to a COMRESET > 0x000b 2 1 CRC errors within host-to-device FIS > 0x8000 4 7720 Vendor specific They may be reported by disks. IIRC they may also be reported by port multiplier, but I've never tried to access them and haven't seen the existing tools for it, except via doing bin-banging with camcontrol. Whether the controller can report something alike, I don't remember. -- Alexander Motin