From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 19:55:56 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83670106564A for ; Sun, 25 Jan 2009 19:55:56 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id 4C25A8FC0A for ; Sun, 25 Jan 2009 19:55:55 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.38] (S0106001372fd1e07.vs.shawcable.net [70.71.171.106]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id n0PJtriO071231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 25 Jan 2009 11:55:54 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <497CC3C4.1070708@FreeBSD.org> Date: Sun, 25 Jan 2009 11:55:48 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Peter Jeremy References: <200901241638.18591.hselasky@c2i.net> <497B7A80.4060002@FreeBSD.org> <20090125063441.GC1755@server.vk2pj.dyndns.org> In-Reply-To: <20090125063441.GC1755@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: Prblem whit USB in FreeBSD 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2009 19:55:56 -0000 Peter Jeremy wrote: > On 2009-Jan-24 12:30:56 -0800, Maxim Sobolev wrote: >> I wonder if this situation can be handled automatically. To my ignorant >> view, our USB mass storage driver can try sending "synchronize cache" >> command and if that fails then failback to the NO_SYNCHRONIZE_CACHE >> behavior. > > This has been discussed in the past. The problem is that some drives > lock up when you send a "synchronize cache" command so this isn't a > general solution. So what? The drive that is not in the quirks won't work anyway, so that if by auto-detection you can make at least fraction of those drivers working out of the box it would be an improvement. I wonder how other operating systems (Windows, Linux) cope with this issue. Not sure about a Linux, but I really doubt Windows has anything like our quirks, yet all drives work with it. -Maxim