From owner-freebsd-usb@FreeBSD.ORG Sun Nov 26 07:59:50 2006 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B99316A403 for ; Sun, 26 Nov 2006 07:59:50 +0000 (UTC) (envelope-from crossd@cs.rpi.edu) Received: from cliffclavin.cs.rpi.edu (cliffclavin.cs.rpi.edu [128.213.1.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5898043D55 for ; Sun, 26 Nov 2006 07:58:57 +0000 (GMT) (envelope-from crossd@cs.rpi.edu) Received: from [10.1.2.205] (cpe-74-70-181-55.nycap.res.rr.com [74.70.181.55]) (authenticated bits=0) by cliffclavin.cs.rpi.edu (8.13.6/8.13.6) with ESMTP id kAQ7xatd002657 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sun, 26 Nov 2006 02:59:42 -0500 (EST) From: "David E. Cross" To: freebsd-usb@freebsd.org Content-Type: text/plain Date: Sun, 26 Nov 2006 02:59:36 -0500 Message-Id: <1164527976.18604.6.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Report: Spam Report from cliffclavin.cs.rpi.edu: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP X-Scanned-By: MIMEDefang 2.57 on 128.213.1.9 Subject: Problem with 6.2-RC1 da0/umass and Mitsumi FDD 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: Sun, 26 Nov 2006 07:59:50 -0000 I have a mitsumi USB FDD as follows under 6.2-RC1 (the same problem existed under 6.1-p10) umass0: MITSUMI MITSUMI USB FDD, rev 1.10/1.00, addr 2 umass0: UFI over CBI with CCI (using CBI); quirks = 0x0000 umass0:6:0:-1: Attached to scbus6 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers (as you can see I have already enabled USB_DEBUG) Reading from the device works, although it is SLOW. 4K/sec slow. Writing to the device does NOT work, it just hangs indefinitely (but the machine stays responsive, until I unplug the device at which point it panics.. but that's for another email) Kernel messages from writing are: umass0: CBI reset failed, TIMEOUT umass0: CBI bulk-in stall clear failed, TIMEOUT umass0: CBI bulk-out stall clear failed, TIMEOUT umass0: CBI reset failed, TIMEOUT umass0: CBI bulk-in stall clear failed, TIMEOUT umass0: CBI bulk-out stall clear failed, TIMEOUT umass0: CBI reset failed, TIMEOUT umass0: CBI bulk-in stall clear failed, TIMEOUT umass0: CBI bulk-out stall clear failed, TIMEOUT umass0: CBI reset failed, TIMEOUT umass0: CBI bulk-in stall clear failed, TIMEOUT umass0: CBI bulk-out stall clear failed, TIMEOUT umass0: CBI reset failed, TIMEOUT What I have tried (to date) to resolve this issue: 1) USB quirk to force the protocol to USB_CBI (instead of USB_CBI_I) 2) SCSI DA quirk to set NO_SYNC (a previous kernel message which I don't have a copy of made mention that there was an unsupported UFI call of 0x35 (verbage of that is wrong, but "unsupported" "UFI" and "0x35" is right) followed by a sync failure. Also in the mailing list I noticed some other similar problems with other devices were cured by that. Anyway, I am looking for some guidance before I beat against this some more. -- David E. Cross