We got another report about a device where ata smart probing causes USB resets:
$ sudo skdump /dev/sdc
Device: sat12:/dev/sdc
Type: 12 Byte SCSI ATA SAT Passthru
Size: 1907348 MiB
Awake: Operation not supported
ATA SMART not supported.
Shortly after getting the skdump, the device was offlined:
Nov 4 20:00:02 bauer kernel: [ 4981.580059] usb 1-3: reset high speed USB device using ehci_hcd and address 3
Nov 4 20:00:33 bauer kernel: [ 5012.124040] usb 1-3: reset high speed USB device using ehci_hcd and address 3
Nov 4 20:01:04 bauer kernel: [ 5042.668039] usb 1-3: reset high speed USB device using ehci_hcd and address 3
Nov 4 20:01:14 bauer kernel: [ 5053.024045] usb 1-3: reset high speed USB device using ehci_hcd and address 3
Nov 4 20:01:24 bauer kernel: [ 5063.268100] usb 1-3: USB disconnect, address 3
Nov 4 20:01:24 bauer kernel: [ 5063.268779] scsi 6:0:0:0: Device offlined - not ready after error recovery
(This is with disabling the udev rule for dk-d ata smart probe; with it, the device doesn't appear at all).
(libatasmart 016)
Should I get an strace from the reporter? Or should we just blacklist this device?
We got another report about a device where ata smart probing causes USB resets:
$ sudo skdump /dev/sdc
Device: sat12:/dev/sdc
Type: 12 Byte SCSI ATA SAT Passthru
Size: 1907348 MiB
Awake: Operation not supported
ATA SMART not supported.
Shortly after getting the skdump, the device was offlined:
Nov 4 20:00:02 bauer kernel: [ 4981.580059] usb 1-3: reset high speed USB device using ehci_hcd and address 3
Nov 4 20:00:33 bauer kernel: [ 5012.124040] usb 1-3: reset high speed USB device using ehci_hcd and address 3
Nov 4 20:01:04 bauer kernel: [ 5042.668039] usb 1-3: reset high speed USB device using ehci_hcd and address 3
Nov 4 20:01:14 bauer kernel: [ 5053.024045] usb 1-3: reset high speed USB device using ehci_hcd and address 3
Nov 4 20:01:24 bauer kernel: [ 5063.268100] usb 1-3: USB disconnect, address 3
Nov 4 20:01:24 bauer kernel: [ 5063.268779] scsi 6:0:0:0: Device offlined - not ready after error recovery
(This is with disabling the udev rule for dk-d ata smart probe; with it, the device doesn't appear at all).
(libatasmart 016)
Should I get an strace from the reporter? Or should we just blacklist this device?
lsusb -v: tions 1
Bus 001 Device 012: ID 0928:0000 Oxford Semiconductor, Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0928 Oxford Semiconductor, Ltd
idProduct 0x0000
bcdDevice 0.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigura