Re: 2.6.10 usb-storage too verbose

[Andreas Unterkircher]

don't know your .config & kernel version - but possible u should disable
CONFIG_USB_STORAGE_DEBUG there ;)

andi

Am Dienstag, den 16.11.2004, 20:40 +1100 schrieb Eyal Lebedinsky:
> When I mount/read/unmount a USB disk I end up with tons of messages like
> below. Should it be this verbose on a stable kernel (I would understand
> debugging)?
> 
> usb-storage: scsi cmd done, result=0x0
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand called
> usb-storage: *** thread awakened.
> usb-storage: Command READ_10 (10 bytes)
> usb-storage:  28 00 00 0b 0d a8 00 00 80 00
> usb-storage: Bulk Command S 0x43425355 T 0x32c L 65536 F 128 Trg 0 LUN 0 CL 12
> usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
> usb-storage: Status code 0; transferred 31/31
> usb-storage: -- transfer complete
> usb-storage: Bulk command transfer result=0
> usb-storage: usb_stor_bulk_transfer_sglist: xfer 65536 bytes, 1 entries
> usb-storage: Status code 0; transferred 65536/65536
> usb-storage: -- transfer complete
> usb-storage: Bulk data transfer result 0x0
> usb-storage: Attempting to get CSW...
> usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
> usb-storage: Status code 0; transferred 13/13
> usb-storage: -- transfer complete
> usb-storage: Bulk status result = 0
> usb-storage: Bulk Status S 0x53425355 T 0x32c R 0 Stat 0x0
> usb-storage: scsi cmd done, result=0x0
> usb-storage: *** thread sleeping.
> usb-storage: queuecommand called
> usb-storage: *** thread awakened.
> usb-storage: Command READ_10 (10 bytes)
> usb-storage:  28 00 00 0b 0e 28 00 00 80 00
> usb-storage: Bulk Command S 0x43425355 T 0x32d L 65536 F 128 Trg 0 LUN 0 CL 12
> usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
> usb-storage: Status code 0; transferred 31/31
> usb-storage: -- transfer complete
> usb-storage: Bulk command transfer result=0
> usb-storage: usb_stor_bulk_transfer_sglist: xfer 65536 bytes, 2 entries
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/