From owner-freebsd-usb@FreeBSD.ORG Thu Aug 16 12:22:11 2007 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA0F416A41B for ; Thu, 16 Aug 2007 12:22:11 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from gateway.cybervisiontech.com.ua (gateway.cybervisiontech.com.ua [88.81.251.18]) by mx1.freebsd.org (Postfix) with ESMTP id 5356713C4A6 for ; Thu, 16 Aug 2007 12:22:11 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (hq.cybervisiontech.com [127.0.0.1]) by gateway.cybervisiontech.com.ua (Postfix) with ESMTP id A23A0ED5441 for ; Thu, 16 Aug 2007 15:22:10 +0300 (EEST) X-Virus-Scanned: amavisd-new at cybervisiontech.com Received: from gateway.cybervisiontech.com.ua ([127.0.0.1]) by localhost (hq.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ON37VYqaku+g for ; Thu, 16 Aug 2007 15:22:09 +0300 (EEST) Received: from [10.2.1.87] (rein.cybervisiontech.com.ua [10.2.1.87]) by gateway.cybervisiontech.com.ua (Postfix) with ESMTP id 5C5B8ED543A for ; Thu, 16 Aug 2007 15:22:09 +0300 (EEST) Message-ID: <46C44170.3040108@icyb.net.ua> Date: Thu, 16 Aug 2007 15:22:08 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: scsi_da quirk for a device with "no name" X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2007 12:22:11 -0000 I have ASUS P535 PPC+phone with Windows Mobile 5 on it. It has an option to act as a USB mass storage (instead of attempting acivesync). When I tried it, it first got recognized by umass and then it immediately panicked my system. >From messages: kernel: umass0: ASUS Generic Mass Storage, rev 2.00/0.00, addr 3 kernel: da0 at umass-sim0 bus 0 target 0 lun 0 kernel: da0: < > Removable Direct Access SCSI-0 device kernel: da0: 1.000MB/s transfers kernel: da0: 1952MB (3998720 512 byte sectors: 255H 63S/T 248C) >From panic (typed from memory): umass0: Invalid CSW: tag 7 should be 8 (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x0, scsi status == 0x4 I googled up several reports of similar and not so similar panics. Here's a small overview that is not directly related to a question that I really want to ask: 1. Invalid CSW problems where a signature is wrong, I see that WRONG_CSWSIG umass quirk is recommended for that; 2. Invalid CSW problems where a tag is wrong and the values are very different, I see that one person attempted to cure that with a new hand-rolled quirk to simply ignore the mismatch; 3. Invalid CSW problems where a tag is wrong and the difference is exactly one. I don't know if there is anything special about that, but it looks the most interesting of all the cases. In some cases but not all "Invalid CSW" comes together with "Synchronize cache failed" and DA_Q_NO_SYNC_CACHE scsi_da quirk is recommended for that. So I attempted the latter quirk and it helped me! But there is one not good thing about the way I did that - I used wild cards ("*") for all three of vendor, product and revision. This is because they all appear to be empty/unset. This is shown in both kernel messages and by camcontrol devlist and by camcontrol inquiry. I am not sure if there are any risks of applying the quirk to all possible da devices, there will be only umass ones in my case, but I still would like to do something more specific to the device in question. Will empty patterns work ? I mean if I put "", "", "" entry into the quirk array. Actually, I can test this myself soon, but not today. Thank you. P.S. some links to the problems that others have reported: http://www.freebsd.org/cgi/query-pr.cgi?pr=114916&cat= http://osdir.com/ml/os.freebsd.devel.usb/2005-12/msg00039.html http://lists.freebsd.org/pipermail/freebsd-bugs/2004-November/010483.html http://lists.freebsd.org/pipermail/freebsd-bugs/2004-January/005170.html http://lists.freebsd.org/mailman/htdig/freebsd-usb/2004-December/000318.html http://lists.freebsd.org/mailman/htdig/freebsd-usb/2005-February/000660.html -- Andriy Gapon