Matthew,

Ok, I've recompiled the kernel (Mandrake's latest development kernel 
2.4.13-12mdk) with the debugging turned on. Here's the output:

Nov 28 22:10:48 taz kernel: hub.c: USB new device connect on bus2/1, 
assigned device number 2
Nov 28 22:10:48 taz kernel: usb.c: USB device 2 (vend/prod 0x54c/0x58) 
is not claimed by any active driver.
Nov 28 22:10:48 taz kernel: Initializing USB Mass Storage driver...
Nov 28 22:10:48 taz kernel: usb.c: registered new driver usb-storage
Nov 28 22:10:48 taz kernel: usb-storage: act_altsettting is 0
Nov 28 22:10:48 taz kernel: usb-storage: id_index calculated to be: 68
Nov 28 22:10:48 taz kernel: usb-storage: Array length appears to be: 77
Nov 28 22:10:48 taz kernel: usb-storage: USB Mass Storage device detected
Nov 28 22:10:48 taz kernel: usb-storage: Endpoints: In: 0xdb322388 Out: 
0xdb322374 Int: 0xdb322360 (Period 1)
Nov 28 22:10:48 taz kernel: usb-storage: New GUID 054c00580000000000000000
Nov 28 22:10:48 taz kernel: usb-storage: Transport: Control/Bulk/Interrupt
Nov 28 22:10:48 taz kernel: usb-storage: Protocol: 8070i
Nov 28 22:10:48 taz kernel: usb-storage: Allocating IRQ for CBI transport
Nov 28 22:10:48 taz kernel: usb-storage: usb_submit_urb() returns 0
Nov 28 22:10:48 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:10:48 taz kernel: scsi1 : SCSI emulation for USB Mass Storage 
devices
Nov 28 22:10:48 taz kernel: usb-storage: queuecommand() called
Nov 28 22:10:48 taz kernel: usb-storage: *** thread awakened.
Nov 28 22:10:48 taz kernel: usb-storage: Command INQUIRY (6 bytes)
Nov 28 22:10:48 taz kernel: usb-storage: 12 00 00 00 ff 00 12 c0 00 00 00 00
Nov 28 22:10:48 taz kernel: usb-storage: USB IRQ recieved for device on 
host 1
Nov 28 22:10:48 taz kernel: usb-storage: -- IRQ data length is 2
Nov 28 22:10:48 taz kernel: usb-storage: -- IRQ state is 0
Nov 28 22:10:48 taz kernel: usb-storage: -- Interrupt Status (0x3a, 0x0)
Nov 28 22:10:48 taz kernel: usb-storage: -- not a command-completion IRQ
Nov 28 22:10:48 taz kernel: usb-storage: Call to usb_stor_control_msg() 
returned 12
Nov 28 22:10:48 taz kernel: usb-storage: usb_stor_transfer_partial(): 
xfer 255 bytes
Nov 28 22:10:48 taz kernel: usb-storage: usb_stor_bulk_msg() returned 0 
xferred 56/255
Nov 28 22:10:48 taz kernel: usb-storage: CBI data stage result is 0x1
Nov 28 22:10:48 taz kernel: usb-storage: Current value of ip_waitq is: 0
Nov 28 22:10:54 taz kernel: usb-storage: command_abort() called
Nov 28 22:10:54 taz kernel: usb-storage: -- simulating missing IRQ
Nov 28 22:10:54 taz kernel: usb-storage: -- nothing to abort
Nov 28 22:10:54 taz kernel: usb-storage: device_reset() called
Nov 28 22:10:54 taz kernel: usb-storage: CB_reset() called
Nov 28 22:10:54 taz kernel: usb-storage: Did not get interrupt on CBI
Nov 28 22:10:54 taz kernel: usb-storage: -- transport indicates command 
was aborted
Nov 28 22:10:54 taz kernel: usb-storage: Fixing INQUIRY data to show 
SCSI rev 2
Nov 28 22:10:54 taz kernel: usb-storage: scsi command aborted
Nov 28 22:10:54 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:10:54 taz kernel: usb-uhci.c: interrupt, status 3, frame# 725
Nov 28 22:10:54 taz kernel: usb-storage: CB[I] soft reset failed -32
Nov 28 22:10:54 taz kernel: usb-storage: bus_reset() called
Nov 28 22:10:54 taz kernel: usb-storage: -- releasing irq URB
Nov 28 22:10:54 taz kernel: usb-storage: USB IRQ recieved for device on 
host 1
Nov 28 22:10:54 taz kernel: usb-storage: -- IRQ data length is 2
Nov 28 22:10:54 taz kernel: usb-storage: -- IRQ state is -2
Nov 28 22:10:54 taz kernel: usb-storage: -- Interrupt Status (0x3a, 0x0)
Nov 28 22:10:54 taz kernel: usb-storage: -- device has been removed
Nov 28 22:10:54 taz kernel: usb-storage: -- usb_unlink_urb() returned 0
Nov 28 22:10:54 taz kernel: usb.c: USB disconnect on device 2
Nov 28 22:10:54 taz kernel: hub.c: USB new device connect on bus2/1, 
assigned device number 3
Nov 28 22:10:59 taz kernel: usb-storage: host_reset() requested but not 
implemented
Nov 28 22:11:09 taz kernel: scsi: device set offline - command error 
recover failed: host 1 channel 0 id 0 lun 0
Nov 28 22:11:09 taz kernel: usb-storage: queuecommand() called
Nov 28 22:11:09 taz kernel: usb-storage: *** thread awakened.
Nov 28 22:11:09 taz kernel: usb-storage: Bad target number (1/0)
Nov 28 22:11:09 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:11:09 taz kernel: usb-storage: queuecommand() called
Nov 28 22:11:09 taz kernel: usb-storage: *** thread awakened.
Nov 28 22:11:09 taz kernel: usb-storage: Bad target number (2/0)
Nov 28 22:11:09 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:11:09 taz kernel: usb-storage: queuecommand() called
Nov 28 22:11:09 taz kernel: usb-storage: *** thread awakened.
Nov 28 22:11:09 taz kernel: usb-storage: Bad target number (3/0)
Nov 28 22:11:09 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:11:09 taz kernel: usb-storage: queuecommand() called
Nov 28 22:11:09 taz kernel: usb-storage: *** thread awakened.
Nov 28 22:11:09 taz kernel: usb-storage: Bad target number (4/0)
Nov 28 22:11:09 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:11:09 taz kernel: usb-storage: queuecommand() called
Nov 28 22:11:09 taz kernel: usb-storage: *** thread awakened.
Nov 28 22:11:09 taz kernel: usb-storage: Bad target number (5/0)
Nov 28 22:11:09 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:11:09 taz kernel: usb-storage: queuecommand() called
Nov 28 22:11:09 taz kernel: usb-storage: *** thread awakened.
Nov 28 22:11:09 taz kernel: usb-storage: Bad target number (6/0)
Nov 28 22:11:09 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:11:09 taz kernel: usb-storage: queuecommand() called
Nov 28 22:11:09 taz kernel: usb-storage: *** thread awakened.
Nov 28 22:11:09 taz kernel: usb-storage: Bad target number (7/0)
Nov 28 22:11:09 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:11:09 taz kernel: WARNING: USB Mass Storage data integrity not 
assured
Nov 28 22:11:09 taz kernel: USB Mass Storage device found at 2
Nov 28 22:11:09 taz kernel: USB Mass Storage support registered.
Nov 28 22:11:09 taz kernel: usb-storage: act_altsettting is 0
Nov 28 22:11:09 taz kernel: usb-storage: id_index calculated to be: 68
Nov 28 22:11:09 taz kernel: usb-storage: Array length appears to be: 77
Nov 28 22:11:09 taz kernel: usb-storage: USB Mass Storage device detected
Nov 28 22:11:09 taz kernel: usb-storage: Endpoints: In: 0xdb3224c8 Out: 
0xdb3224b4 Int: 0xdb3224a0 (Period 1)
Nov 28 22:11:09 taz kernel: usb-storage: New GUID 054c00580000000000000000
Nov 28 22:11:09 taz kernel: usb-storage: Transport: Control/Bulk/Interrupt
Nov 28 22:11:09 taz kernel: usb-storage: Protocol: 8070i
Nov 28 22:11:09 taz kernel: usb-storage: Allocating IRQ for CBI transport
Nov 28 22:11:09 taz kernel: usb-storage: usb_submit_urb() returns 0
Nov 28 22:11:09 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:11:09 taz kernel: scsi2 : SCSI emulation for USB Mass Storage 
devices
Nov 28 22:11:09 taz kernel: usb-storage: queuecommand() called
Nov 28 22:11:09 taz kernel: usb-storage: *** thread awakened.
Nov 28 22:11:09 taz kernel: usb-storage: Command INQUIRY (6 bytes)
Nov 28 22:11:09 taz kernel: usb-storage: 12 00 00 00 ff 00 00 00 00 00 00 00
Nov 28 22:11:09 taz kernel: usb-storage: USB IRQ recieved for device on 
host 2
Nov 28 22:11:09 taz kernel: usb-storage: -- IRQ data length is 2
Nov 28 22:11:09 taz kernel: usb-storage: -- IRQ state is 0
Nov 28 22:11:09 taz kernel: usb-storage: -- Interrupt Status (0x28, 0x0)
Nov 28 22:11:09 taz kernel: usb-storage: -- not a command-completion IRQ
Nov 28 22:11:09 taz kernel: usb-storage: Call to usb_stor_control_msg() 
returned 12
Nov 28 22:11:09 taz kernel: usb-storage: usb_stor_transfer_partial(): 
xfer 255 bytes
Nov 28 22:11:09 taz kernel: usb-storage: usb_stor_bulk_msg() returned 0 
xferred 56/255
Nov 28 22:11:09 taz kernel: usb-storage: CBI data stage result is 0x1
Nov 28 22:11:09 taz kernel: usb-storage: Current value of ip_waitq is: 0
Nov 28 22:11:15 taz kernel: usb-storage: command_abort() called
Nov 28 22:11:15 taz kernel: usb-storage: -- simulating missing IRQ
Nov 28 22:11:15 taz kernel: usb-storage: -- nothing to abort
Nov 28 22:11:15 taz kernel: usb-storage: device_reset() called
Nov 28 22:11:15 taz kernel: usb-storage: CB_reset() called
Nov 28 22:11:15 taz kernel: usb-storage: Did not get interrupt on CBI
Nov 28 22:11:15 taz kernel: usb-storage: -- transport indicates command 
was aborted
Nov 28 22:11:15 taz kernel: usb-storage: Fixing INQUIRY data to show 
SCSI rev 2
Nov 28 22:11:15 taz kernel: usb-storage: scsi command aborted
Nov 28 22:11:15 taz kernel: usb-storage: *** thread sleeping.
Nov 28 22:11:15 taz kernel: usb-uhci.c: interrupt, status 3, frame# 1339
Nov 28 22:11:15 taz kernel: usb-storage: CB[I] soft reset failed -32
Nov 28 22:11:15 taz kernel: usb-storage: bus_reset() called
Nov 28 22:11:15 taz kernel: usb-storage: -- releasing irq URB
Nov 28 22:11:15 taz kernel: usb-storage: USB IRQ recieved for device on 
host 2
Nov 28 22:11:15 taz kernel: usb-storage: -- IRQ data length is 2
Nov 28 22:11:15 taz kernel: usb-storage: -- IRQ state is -2
Nov 28 22:11:15 taz kernel: usb-storage: -- Interrupt Status (0x28, 0x0)
Nov 28 22:11:15 taz kernel: usb-storage: -- device has been removed
Nov 28 22:11:15 taz kernel: usb-storage: -- usb_unlink_urb() returned 0

>The device is advertising usb-storage compliance, but it's not talking
>nicely with the driver.
>
>If you recompile your kernel with USB Mass Storage Verbose Debugging turned
>on, I can probably help you from the logs.
>
>Matt
>
>On Wed, Nov 28, 2001 at 03:24:00PM +0800, Stefan van der Eijk wrote:
>
>>  I'm trying to get USB mass storage to work on my Sony Clie PDA (Sony 
>>PEG Mass Storage).
>>
>>When I use the MSimport application on the PDA to connect to the PC, the 
>>Linux kernel does recognize the device, but I can't find a device in 
>>order to mount it.
>>
>>/dev/sda, /dev/sdb and /dev/sdc are my SCSI disks on the sym53c8xx 
>>controller. /dev/sdd doesn't want to be fdisked:
>>
>>[root@taz usb]# fdisk /dev/sdd
>>
>>Unable to open /dev/sdd
>>
>>
>>/var/log/syslog gives:
>>
>>Nov 28 13:24:32 taz kernel: hub.c: USB new device connect on bus1/2, 
>>assigned device number 3
>>Nov 28 13:24:32 taz kernel: usb.c: USB device 3 (vend/prod 0x54c/0x58) 
>>is not claimed by any active driver.
>>Nov 28 13:24:34 taz kernel: Initializing USB Mass Storage driver...
>>Nov 28 13:24:34 taz kernel: usb.c: registered new driver usb-storage
>>Nov 28 13:24:34 taz kernel: scsi1 : SCSI emulation for USB Mass Storage 
>>devices
>>Nov 28 13:24:40 taz 
>>kernel: usb-uhci.c: interrupt, status 3, frame# 1743
>>Nov 28 13:24:40 taz kernel: usb.c: USB disconnect on device 3
>>Nov 28 13:24:40 taz kernel: hub.c: USB new device connect on bus1/2, 
>>assigned device number 4
>>Nov 28 13:24:45 taz kernel: usb-storage: host_reset() requested but not 
>>implemented
>>Nov 28 13:24:55 taz ypbind[1414]: broadcast: RPC: Timed out.
>>Nov 28 13:24:55 taz kernel: scsi: device set offline - command error 
>>recover failed: host 1 channel 0 id 0 lun 0
>>Nov 28 13:24:55 taz kernel: WARNING: USB Mass Storage data integrity not 
>>assured
>>Nov 28 13:24:55 taz kernel: USB Mass Storage device found at 3
>>Nov 28 13:24:55 taz kernel: USB Mass Storage support registered.
>>Nov 28 13:24:55 taz kernel: scsi2 : SCSI emulation for USB Mass Storage 
>>devices
>>Nov 28 13:25:01 taz kernel: usb-uhci.c: interrupt, status 3, frame# 299
>>
>>[root@taz scsi]# cat scsi
>>Attached devices:
>>Host: scsi0 Channel: 00 Id: 00 Lun: 00
>>  Vendor: IBM
>> OEM  Model: DCHS09W          Rev: 2222
>>  Type:   Direct-Access                    ANSI SCSI revision: 02
>>Host: scsi0 Channel: 00 Id: 01 Lun: 00
>>  Vendor: IBM      Model: DDYS-T18350N     Rev: S93E
>>  Type:   Direct-Access                    ANSI SCSI revision: 03
>>Host: scsi0 Channel: 00 Id: 02 Lun: 00
>>  Vendor: SEAGATE  Model: ST39236LW        Rev: 0010
>>  Type:   Direct-Access                    ANSI SCSI revision: 03
>>Host: scsi2 Channel: 00 Id: 00 Lun: 00
>>  Vendor:          Model:                  Rev:    
>>  Type:   <NULL>                ANSI SCSI revision: ffffffff
>>
>>[root@taz scsi]# find
>>.
>>./usb-storage-1
>>./usb-storage-1/2
>>./usb-storage-0
>>./sym53c8xx
>>./scsi
>>
>>Am I doing something wrong?
>>
>>
>>_______________________________________________
>>[EMAIL PROTECTED]
>>To unsubscribe, use the last for
>>m field at:
>>https://lists.sourceforge.net/lists/listinfo/linux-usb-users
>>
>




_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to