From owner-freebsd-hardware@FreeBSD.ORG Sat Aug 30 18:31:34 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 406801A0; Sat, 30 Aug 2014 18:31:34 +0000 (UTC) Received: from mail-vc0-x235.google.com (mail-vc0-x235.google.com [IPv6:2607:f8b0:400c:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E683719DA; Sat, 30 Aug 2014 18:31:33 +0000 (UTC) Received: by mail-vc0-f181.google.com with SMTP id ij19so3872043vcb.26 for ; Sat, 30 Aug 2014 11:31:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=fqD4uRCLZey9I+F6EfVpgOTJQHszeo8FW363UXm/qCU=; b=wbBtxLG01n0lEPthgaszC4n7DNGijbOSiCJFFS4F6eTZTr4GjCrDjt4p6Guav9J73w L0rkmnarWnpD2hfJAZWNTUup1SRnF6KzyVqhbx7NUFxqJS+0iRs7zNH8XQgF7bedaa42 pKGrq2YkYqr9A349SzZ1GjjbO8zAspGKijqtUA0wxhenbH/vMWf+DevsgWuuPR/t6W9U Uuf57VQHH1cvDtsHKFuN+hZoQVc1sHZZS0RowCAmtB0ODvsWxnpCVrhLX1GlJCC1Sng0 VURQrUYVorH116gjewgxnWPFD66mP+2gQ39o5wXr51IMjUGXuua/8yGIjGsFJfBv9KkL ybfQ== MIME-Version: 1.0 X-Received: by 10.220.251.200 with SMTP id mt8mr16625221vcb.24.1409423492798; Sat, 30 Aug 2014 11:31:32 -0700 (PDT) Received: by 10.221.64.74 with HTTP; Sat, 30 Aug 2014 11:31:32 -0700 (PDT) Date: Sat, 30 Aug 2014 14:31:32 -0400 Message-ID: Subject: CAM_REQ_CMP_ERR From: grarpamp To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Aug 2014 18:31:34 -0000 I get a lot of these. Searching doesn't say much about them. What do they mean? A data corruption error on the media? (Seems to happen at random (nonrepeating) locations, so I doubt this.) Is sysctl kern.cam.da.retry_count the correct way to bump this retry count? (I tried that and it seems to bump, but doesn't seem to have much result as far as turning the error into a later success.) Can I force various interface speeds like USB 1.0, 2.0, etc? Thanks. cam.h: CAM_REQ_CMP_ERR, /* CCB request completed with an error */ 8 STABLE r269631 kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR kernel: (da0:umass-sim0:0:0:0): Retrying command ... kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR kernel: (da0:umass-sim0:0:0:0): Error 5, Retries exhausted ugen3.2: at usbus3 umass0: on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x4100 umass0:3:0:-1: Attached to scbus3 (probe0:umass-sim0:0:0:0): Down reving Protocol Version from 2 to 0? pass2 at umass-sim0 bus 0 scbus3 target 0 lun 0 pass2: Removable Direct Access SCSI-0 device pass2: Serial Number num pass2: 40.000MB/s transfers GEOM: new disk da0 da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: Serial Number num da0: 40.000MB/s transfers da0: sizeMB (count 512 byte sectors: 64H 32S/T sizeC) da0: quirks=0x2 da0: Delete methods: