From owner-freebsd-current@FreeBSD.ORG Wed Apr 21 11:21:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DB4B16A4DA for ; Wed, 21 Apr 2004 11:21:47 -0700 (PDT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8212743D2F for ; Wed, 21 Apr 2004 11:21:46 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc11) with ESMTP id <2004042118214401100phq90e>; Wed, 21 Apr 2004 18:21:45 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA32270; Wed, 21 Apr 2004 11:21:43 -0700 (PDT) Date: Wed, 21 Apr 2004 11:21:42 -0700 (PDT) From: Julian Elischer To: Nate Lawson In-Reply-To: <20040421104132.B37432@root.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "Vyacheslav I. Ivanchenko" cc: current@freebsd.org Subject: Re: Trouble with EHCI controller and USB Flash Disk. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 21 Apr 2004 18:21:47 -0000 On Wed, 21 Apr 2004, Nate Lawson wrote: > On Wed, 21 Apr 2004, Vyacheslav I. Ivanchenko wrote: > > Hello Nate Lawson! > > > > I use -CURRENT from April, 20 2004. > > # ident kernel | grep "scsi_da.c" > > $FreeBSD: src/sys/cam/scsi/scsi_da.c,v 1.167 2004/04/19 13:38:10 mux Exp $ > > > > I have problems with mine USB2.0 Mobile Disk III and EHCI controller. > > (http://www.twinmos.com/flash/flash_p_usb20_mobile3.htm) > > > > When I try to use EHCI controller, my system finds out > > the device /dev/da0, but does not find out the > > device /dev/da0s1. > > > > With UHCI controller no problem. > > Since it works with UHCI, it's likely an EHCI problem. Unfortunately, I > don't know much about EHCI so I'm moving this to -current. The ehci driver has quite a few problems. It workd in some cases but not in others. I have not yet isolated what the defining factor is. > > EHCI messages: > kernel: umass0: TTI-TTI U20 Mobile Disk, rev 2.00/2.00, addr 2 > kernel: umass0:0:0:-1: Attached to scbus0 > kernel: (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR > kernel: (probe0:umass-sim0:0:0:0): Retrying Command > kernel: (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR > kernel: (probe0:umass-sim0:0:0:0): Retrying Command > kernel: (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR > kernel: (probe0:umass-sim0:0:0:0): Retrying Command > kernel: (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR > kernel: (probe0:umass-sim0:0:0:0): Retrying Command > kernel: (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR > kernel: (probe0:umass-sim0:0:0:0): error 5 > kernel: (probe0:umass-sim0:0:0:0): Retries Exausted > kernel: pass0 at umass-sim0 bus 0 target 0 lun 0 > kernel: pass0: Removable Direct Access SCSI-2 device > kernel: pass0: 1.000MB/s transfers > kernel: GEOM: new disk da0 > kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > kernel: da0: Removable Direct Access SCSI-2 device > kernel: da0: 1.000MB/s transfers > kernel: da0: 250MB (512000 512 byte sectors: 64H 32S/T 250C) > kernel: (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x10, scsi > status == 0x0 > 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): Synchronize cache failed, status == 0x10, scsi > status == 0x0 > kernel: umass0: at uhub4 port 8 (addr 2) disconnected > kernel: (pass0:umass-sim0:0:0:0): lost device > kernel: (pass0:umass-sim0:0:0:0): removing device entry > kernel: (da0:umass-sim0:0:0:0): lost device > kernel: (da0:umass-sim0:0:0:0): removing device entry > kernel: umass0: detached I've seen this behaviour once.. the drive isn't able to be read, which means that the fdisk table (MBR) can not be read, so geom doesn't make any subdevices. I do not have an answer at this time.. however it is possible that an MFC of the umass driver (which I am partly though) might help. > > UHCI messages (working): > kernel: umass0: TTI-TTI U20 Mobile Disk, rev 2.00/2.00, addr 2 > kernel: umass0:0:0:-1: Attached to scbus0 > kernel: pass0 at umass-sim0 bus 0 target 0 lun 0 > kernel: pass0: Removable Direct Access SCSI-2 device > kernel: pass0: Serial Number ^_ > kernel: pass0: 1.000MB/s transfers > kernel: GEOM: new disk da0 > kernel: (da0:umass-sim0:0:0:0): Retrying Command > kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > kernel: da0: Removable Direct Access SCSI-2 device > kernel: da0: Serial Number ^_ > kernel: da0: 1.000MB/s transfers > kernel: da0: 250MB (512000 512 byte sectors: 64H 32S/T 250C) > kernel: [0] f:80 typ:11 s(CHS):0/1/1 e(CHS):998/15/32 s:32 l:511456 > kernel: [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 > kernel: [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 > kernel: [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 > kernel: GEOM: Configure da0s1, start 16384 length 261865472 end 261881855 > kernel: umass0: at uhub3 port 2 (addr 2) disconnected > kernel: (da0:umass-sim0:0:0:0): lost device > kernel: (da0:umass-sim0:0:0:0): removing device entry > kernel: (pass0:umass-sim0:0:0:0): lost device > kernel: (pass0:umass-sim0:0:0:0): removing device entry > kernel: umass0: detached > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >