From: Oliver Neukum <oneukum@suse.com>
To: "David C. Partridge" <david.partridge@perdrix.co.uk>,
linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS
Date: Thu, 03 Dec 2020 14:16:46 +0100 [thread overview]
Message-ID: <918e298941f820a7cc3310c95dc211cca7596dba.camel@suse.com> (raw)
In-Reply-To: <000301d6c919$af7a94e0$0e6fbea0$@perdrix.co.uk>
Am Donnerstag, den 03.12.2020, 02:11 +0000 schrieb David C. Partridge:
Hi,
cool, thank your for testing! You having spent so much time
and effort on this, let's go through the log with a fine comb.
> Now with uas.ko and usb-storage.ko
>
> Dec 03 02:05:56 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
> Dec 03 02:05:56 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
> Dec 03 02:05:56 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> Dec 03 02:05:56 charon kernel: usb 2-1: Product: 2Big Quadra USB3
> Dec 03 02:05:56 charon kernel: usb 2-1: Manufacturer: LaCie
> Dec 03 02:05:56 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
This is from usbcore. It reports that a new device has been detected.
> Dec 03 02:05:56 charon mtp-probe[3108]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:05:56 charon mtp-probe[3108]: bus: 2, device: 2 was not an MTP device
From udev. It basically means that it is not a camera to import
pictures from.
> Dec 03 02:05:56 charon kernel: usb_storage: loading out-of-tree module taints kernel.
> Dec 03 02:05:56 charon kernel: usb_storage: module verification failed: signature and/or required key missing - tainting kernel
> Dec 03 02:05:56 charon kernel: usbcore: registered new interface driver usb-storage
The kernel identified the device as storage and udev has loaded drivers
now being probed.
> Dec 03 02:05:56 charon kernel: scsi host5: uas
> Dec 03 02:05:56 charon kernel: usbcore: registered new interface driver uas
UAS is taking the device.
> Dec 03 02:05:56 charon kernel: scsi 5:0:0:0: Direct-Access LaCie 2Big Quadra v3 051E PQ: 0 ANSI: 6
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
It is identified as a disk.
> Dec 03 02:05:56 charon mtp-probe[3117]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:05:56 charon mtp-probe[3117]: bus: 2, device: 2 was not an MTP device
Again, not a camera.
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Its size and caching attributes are determined. Is the size of 4 TB
correct?
> Dec 03 02:06:13 charon kernel: usb 2-1: USB disconnect, device number 2
A disconnect after 17 seconds. Whether this is a bug or not depends on
whether you pulled the plug. Did you?
> Dec 03 02:06:13 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Attached SCSI disk
This has to happen if the device is unavailable.
> Dec 03 02:06:15 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:06:15 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
> Dec 03 02:06:15 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> Dec 03 02:06:15 charon kernel: usb 2-1: Product: 2Big Quadra USB3
> Dec 03 02:06:15 charon kernel: usb 2-1: Manufacturer: LaCie
> Dec 03 02:06:15 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
> Dec 03 02:06:15 charon kernel: scsi host5: uas
> Dec 03 02:06:15 charon kernel: scsi 5:0:0:0: Direct-Access LaCie 2Big Quadra v3 051E PQ: 0 ANSI: 6
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> Dec 03 02:06:15 charon mtp-probe[3209]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:06:15 charon mtp-probe[3209]: bus: 2, device: 3 was not an MTP device
> Dec 03 02:06:15 charon mtp-probe[3212]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:06:15 charon mtp-probe[3212]: bus: 2, device: 3 was not an MTP device
This is basically a repeat of the first event.
> Dec 03 02:06:46 charon kernel: sd 5:0:0:0: tag#28 uas_eh_abort_handler 0 uas-tag 1 inflight: IN
> Dec 03 02:06:46 charon kernel: sd 5:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
This is a SCSI command: REPORT SUPPORTED OPERATION CODES command
Having this command fail is a bit ironic I suppose.
> Dec 03 02:06:46 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Dec 03 02:06:47 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:06:47 charon kernel: scsi host5: uas_eh_device_reset_handler success
> Dec 03 02:07:17 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Dec 03 02:07:17 charon kernel: sd 5:0:0:0: tag#28 uas_zap_pending 0 uas-tag 1 inflight:
> Dec 03 02:07:17 charon kernel: sd 5:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
> Dec 03 02:07:17 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:07:17 charon kernel: scsi host5: uas_eh_device_reset_handler success
And it happens again. This device is seriously buggy. Is it usable
after that or did you just cut the log?
Regards & Thanks
Oliver
next prev parent reply other threads:[~2020-12-03 13:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 10:56 Issues with LaCie USB3 drive and UAS David C. Partridge
2020-11-09 9:29 ` Oliver Neukum
2020-11-09 9:51 ` David C. Partridge
2020-11-09 10:13 ` Oliver Neukum
2020-11-09 11:21 ` David C. Partridge
2020-11-09 15:21 ` David C. Partridge
2020-11-09 16:47 ` David C. Partridge
2020-11-11 11:43 ` Oliver Neukum
2020-11-11 15:50 ` David C. Partridge
2020-11-11 19:18 ` Oliver Neukum
2020-11-11 20:54 ` David C. Partridge
2020-11-23 14:59 ` Oliver Neukum
2020-11-25 12:25 ` David C. Partridge
2020-11-26 8:24 ` Oliver Neukum
2020-11-26 9:33 ` David C. Partridge
2020-11-26 10:22 ` Oliver Neukum
[not found] ` <0000 01d6c89c$086812e0$193838a0$@perdrix.co.uk>
2020-12-02 11:12 ` David C. Partridge
[not found] ` <612be9a9cd6ffdb9492781e174859c7b4e69 4a86.camel@suse.com>
2020-12-02 11:38 ` Oliver Neukum
2020-12-02 13:39 ` David C. Partridge
2020-12-03 2:11 ` David C. Partridge
2020-12-03 13:16 ` Oliver Neukum [this message]
2020-12-03 14:30 ` David C. Partridge
2020-12-07 10:53 ` David C. Partridge
2020-12-08 14:03 ` Oliver Neukum
2020-12-08 16:06 ` David C. Partridge
2020-12-08 16:27 ` Alan Stern
2020-12-08 16:47 ` David C. Partridge
2020-12-08 17:45 ` 'Alan Stern'
2020-12-08 20:00 ` David C. Partridge
2020-12-09 11:11 ` Oliver Neukum
2020-12-03 14:06 ` Oliver Neukum
2020-12-03 14:46 ` David C. Partridge
2020-12-03 16:16 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=918e298941f820a7cc3310c95dc211cca7596dba.camel@suse.com \
--to=oneukum@suse.com \
--cc=david.partridge@perdrix.co.uk \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).