On Thu, 18 Aug 2005, Olav Kongas wrote: > > On Thu, 18 Aug 2005, Fukumoto Akira wrote: > > > Nice to hear you, > > try to answer on your questions: > > 1. sometimes I get the error message when I switch on the board without > > connected USB-Device. When I connect an USB-Stick I get all messages which > > shown successful communication between platform and stick. > > I have never seen those messages like 'connect-debounce > failed' or 'Not ready to ready change ...' myself. > connect-debounse means that the root hub port status didn't > stabilize during 1.5s, which is a *long* time. As you have > the same problem with 2 different flash drives, but not with > mice which are low speed devices, may indicate an electrical > problem with your board. Another possiblity is that both > types of flash drives you have are picky about delays. I > have seen a few times people complaining about "Not ready to > ready change, medium ..." messages with other host > controllers too.
It's generally caused by slow/buggy firmware in the USB storage device. For a workaround, see this patch: http://marc.theaimsgroup.com/?l=linux-scsi&m=112117962214214&w=2 > > 2. I have two different sort of USB-Sticks to test. Both behave different > > during connection but later I can mount then successfully. > > First Stick: > > hub 1-0:1.0: connect-debounce failed, port 1 disabled > > hub 1-0:1.0: connect-debounce failed, port 1 disabled > > usb 1-1: new full speed USB device using isp116x-hcd and address 2 > > usb 1-1: Product: Mass storage > > usb 1-1: Manufacturer: USB > > usb 1-1: SerialNumber: D42CB0684156B126 > > scsi0 : SCSI emulation for USB Mass Storage devices > > Vendor: Model: Flash Disk Rev: 2.00 > > Type: Direct-Access ANSI SCSI revision: 02 > > sda: Unit Not Ready, sense: > > : Current: sense key: Unit Attention > > Additional sense: Not ready to ready change, medium may have changed > > sda : READ CAPACITY failed. > > sda : status=1, message=00, host=0, driver=08 > > sd: Current: sense key: Unit Attention > > Additional sense: Not ready to ready change, medium may have changed > > sda: test WP failed, assume Write Enabled > > sda: assuming drive cache: write through > > sda: Unit Not Ready, sense: > > : Current: sense key: Unit Attention > > Additional sense: Not ready to ready change, medium may have changed > > sda : READ CAPACITY failed. > > sda : status=1, message=00, host=0, driver=08 > > sd: Current: sense key: Unit Attention > > Additional sense: Not ready to ready change, medium may have changed > > sda: test WP failed, assume Write Enabled > > sda: assuming drive cache: write through > > SCSI device sda: 1024000 512-byte hdwr sectors (524 MB) > > sda: Write Protect is off > > sda: assuming drive cache: write through > > sda: sda1 > > Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 > > Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 > > With PTD_TRACE and URB_TRACE I can get huge report of td: and <- from and to > > the Stick. Within there are blocks with partition tables which are > > definitely correct. But depending on the Stick I see more than one cycles of > > attemption to collect all information for the SCSI-Subsystem (look above). See this explanation (for some unknown reason the message wasn't archived at marc.theaimsgroup.com): http://sourceforge.net/mailarchive/message.php?msg_id=12670805 > > Are there any race-condition between USB and SCSI-Subsystem. No. Alan Stern ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
