From owner-freebsd-stable@FreeBSD.ORG  Fri Aug 22 01:08:42 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 98FFA16A4DA
	for <freebsd-stable@freebsd.org>;
	Fri, 22 Aug 2003 01:08:42 -0700 (PDT)
Received: from rootlabs.com (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id C830743FEC
	for <freebsd-stable@freebsd.org>;
	Fri, 22 Aug 2003 01:08:41 -0700 (PDT)
	(envelope-from nate@rootlabs.com)
Received: (qmail 2990 invoked by uid 1000); 22 Aug 2003 08:08:41 -0000
Date: Fri, 22 Aug 2003 01:08:41 -0700 (PDT)
From: Nate Lawson <nate@root.org>
To: freebsd-stable@freebsd.org, current@freebsd.org
In-Reply-To: <20030822080505.GA7057@pir.net>
Message-ID: <20030822010556.M2981@root.org>
References: <20030822001610.Q2740@root.org> <20030822072807.GD11682@spc.org>
 <20030822005127.C2916@root.org> <20030822080505.GA7057@pir.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: HEADSUP:  USB da(4) quirks disabled for 4.9 and 5.2
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Aug 2003 08:08:43 -0000

On Fri, 22 Aug 2003, Peter Radcliffe wrote:
> Nate Lawson <nate@root.org> probably said:
> > Sure it's common.  But no one has mentioned that it really needs the
> > NO_SYNC_CACHE quirk.  So unless I hear otherwise, I will assume it doesn't
> > need the quirk and it will continue to work fine.
>
> It appears to need it;
>
>   umass0: Unsupported UFI command 0x35
>   (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6,
>    scsi status == 0x0

Unless that causes an actual problem (i.e. crash, data loss), it is not
necessary to have a quirk for it.  There are two kinds of "unsupported"
commands:  those that cause the device to hang or crash and those that
successfully reject commands they don't want with the proper return value.
Quirks will only be added for the former.

Try to mount/unmount it a few times and see if there really is a problem.

zzz,
-Nate