[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-usb-devel
Subject:    Re: [linux-usb-devel] Fuji 1300, 2.4.18, more information
From:       Matthew Dharm <mdharm-usb () one-eyed-alien ! net>
Date:       2002-07-28 19:42:21
[Download RAW message or body]

All these commands come from the drivers/scsi/sd.c file, I believe.  Or
another file in that directory.  It's (ultimately) generated from the
partition reading code.

The device should respond correctly to these requests.  A 4k read (8
sectors) isn't that unusual...

Matt

On Sun, Jul 28, 2002 at 08:38:33PM +1000, John August wrote:
> I've narrowed down the problem with running the 1300. The issue is not
> whether the 1400 driver is running it, its the buffer size on access.
> 
> Note when it works :
> 
> usb-storage: Command READ_10 (10 bytes)
> usb-storage: 28 00 00 00 00 00 00 00 02 00 00 00
> usb-storage: Call to usb_stor_control_msg() returned 12
> usb-storage: usb_stor_transfer_partial(): xfer 1024 bytes
> usb-storage: usb_stor_bulk_msg() returned 0 xferred 1024/1024
> usb-storage: usb_stor_transfer_partial(): transfer complete
> usb-storage: CBI data stage result is 0x0
> usb-storage: Current value of ip_waitq is: 0
> usb-storage: USB IRQ recieved for device on host 0
> usb-storage: -- IRQ data length is 2
> usb-storage: -- IRQ state is 0
> usb-storage: -- Interrupt Status (0x0, 0x0)
> usb-storage: -- Current value of ip_waitq is: -1
> usb-storage: Got interrupt data (0x0, 0x0)
> usb-storage: scsi cmd done, result=0x0
> usb-storage: *** thread sleeping.
>  sda1
> 
> When it does not :
> 
> usb-storage: Command READ_10 (10 bytes)
> usb-storage: 28 00 00 00 00 00 00 00 08 00 00 00
> usb-storage: Call to usb_stor_control_msg() returned 12
> usb-storage: usb_stor_transfer_partial(): xfer 4096 bytes
> usb-storage: USB IRQ recieved for device on host 0
> usb-storage: -- IRQ data length is 2
> usb-storage: -- IRQ state is 0
> usb-storage: -- Interrupt Status (0x0, 0x0)
> usb-storage: -- Current value of ip_waitq is: 0
> usb-storage: command_abort() called
> usb-storage: usb_stor_bulk_msg() returned -104 xferred 4032/4096
> usb-storage: usb_stor_transfer_partial(): unknown error
> usb-storage: CBI data stage result is 0x2
> usb-storage: Current value of ip_waitq is: 1
> usb-storage: Got interrupt data (0x0, 0x0)
> usb-storage: scsi cmd done, result=0x0
> usb-storage: *** thread sleeping.
> 
> This is the command which goes wrong, because 4096 bytes are requested
> rather than 1024. I think its the command which checks the partition
> table for partitions.
> 
> Where does this READ_10 command come from, and why is the buffer length
> set to 4096 ? With this bit of information, I'd probably be able to fix
> it myself.
> 
> Thanks,
> 
> -- 
> John August
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> linux-usb-devel@lists.sourceforge.net
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

I'm seen in many forms.  Now open your mouth.  It's caffeine time.
					-- Cola Man to Greg
User Friendly, 10/28/1998

[Attachment #3 (application/pgp-signature)]
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

[prev in list] [next in list] [prev in thread] [next in thread]