From owner-freebsd-firewire@FreeBSD.ORG Thu Dec 13 22:42:31 2007 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8D3D16A469; Thu, 13 Dec 2007 22:42:31 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id A08FC13C458; Thu, 13 Dec 2007 22:42:31 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 5733961B10A; Thu, 13 Dec 2007 14:42:31 -0800 (PST) Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21742-04; Thu, 13 Dec 2007 14:42:30 -0800 (PST) Received: from iago.office.miralink.com (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id BE64161B0EE; Thu, 13 Dec 2007 14:42:30 -0800 (PST) Message-ID: <4761B556.5090601@miralink.com> Date: Thu, 13 Dec 2007 14:42:30 -0800 From: Sean Bruno User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: freebsd-firewire@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu Dec 13 14:42:31 2007 X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4761b557275371848420296 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Status: No, score=-4.499 tagged_above=-10 required=6.6 autolearn=ham tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599, DSPAM_HAM=-0.1] X-Spam-Score: -4.499 X-Spam-Level: Cc: Hidetoshi Shimokawa Subject: sbp_targ debug errors? X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2007 22:42:31 -0000 I'm seeing some data inconsistency when writing to a backend disk, and I wondered how to interpret the following debug messages? sbp_targ_action1: XPT_CONT_TARGET_IO sbp_targ_action1: data_size(1024) != dxfer_len(512) sbp_targ_action1: XPT_CONT_TARGET_IO sbp_targ_action1: data_size(1024) != dxfer_len(512) sbp_targ_send_status: STATUS_OK sbp_targ_cmd: ORB_POINTER sean