[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#925204: marked as done (linux-image-4.19.0-2-amd64: Using USB 3.0 interface in VMWare and UAS device is not working)

Your message dated Sun, 27 Nov 2022 09:48:57 +0100 (CET)
with message-id <20221127084857.300F5BE2DE0@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #925204,
regarding linux-image-4.19.0-2-amd64: Using USB 3.0 interface in VMWare and UAS device is not working
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
925204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925204
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-amd64
Version: 4.19+102
Severity: important

Hi,

The UAS device drivers are not working under VMWare. I have to use a work
around and blacklist the UAS driver to get device working.

This is the output of dmesg before blacklisting and after:

[18853.525588] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[18853.555794] usb 4-1: New USB device found, idVendor=152d, idProduct=3562,
bcdDevice=63.02
[18853.555797] usb 4-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[18853.555799] usb 4-1: Product: AD TO BE II
[18853.555800] usb 4-1: Manufacturer: ADMKIV
[18853.555802] usb 4-1: SerialNumber: DB1234567897B0
[18853.618227] usbcore: registered new interface driver usb-storage
[18853.630722] scsi host3: uas
[18853.631660] usbcore: registered new interface driver uas
[18853.634778] usb 4-1: stat urb: status -32
[18853.634836] scsi 3:0:0:0: tag#4 data cmplt err -32 uas-tag 1 inflight: CMD
[18853.634839] scsi 3:0:0:0: tag#4 CDB: Inquiry 12 00 00 00 24 00
[18874.274509] scsi 3:0:0:0: tag#4 uas_eh_abort_handler 0 uas-tag 1 inflight:
CMD
[18874.274517] scsi 3:0:0:0: tag#4 CDB: Inquiry 12 00 00 00 24 00
[18874.299065] scsi host3: uas_eh_device_reset_handler start
[18874.436689] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using
xhci_hcd
[18874.471991] scsi host3: uas_eh_device_reset_handler success
[18874.474250] usb 4-1: stat urb: status -32
[18874.475158] scsi 3:0:0:0: tag#4 uas_eh_abort_handler 0 uas-tag 1 inflight:
CMD
[18874.475182] scsi 3:0:0:0: tag#4 CDB: Test Unit Ready 00 00 00 00 00 00
[18874.475190] scsi host3: uas_eh_device_reset_handler start
[18874.718701] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using
xhci_hcd
[18874.747546] scsi host3: uas_eh_device_reset_handler success
[18874.747552] scsi 3:0:0:0: Device offlined - not ready after error recovery
[18899.867372] usbcore: deregistering interface driver uas
[18910.834000] usbcore: deregistering interface driver usb-storage
[18914.787331] usb 4-1: UAS is blacklisted for this device, using usb-storage
instead
[18914.787333] usb-storage 4-1:1.0: USB Mass Storage device detected
[18914.788277] usb-storage 4-1:1.0: Quirks match for vid 152d pid 3562: 800000
[18914.788371] scsi host3: usb-storage 4-1:1.0
[18914.788721] usbcore: registered new interface driver usb-storage
[18915.795385] scsi 3:0:0:0: Direct-Access     ADplus   SuperVer         6302
PQ: 0 ANSI: 6
[18915.796367] scsi 3:0:0:0: Attached scsi generic sg1 type 0
[18915.816273] sd 3:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00
TB/932 GiB)
[18915.817608] sd 3:0:0:0: [sda] Write Protect is off
[18915.817612] sd 3:0:0:0: [sda] Mode Sense: 33 00 00 08
[18915.820683] sd 3:0:0:0: [sda] No Caching mode page found
[18915.820690] sd 3:0:0:0: [sda] Assuming drive cache: write through
[18915.827904]  sda: sda1 sda2 sda3
[18915.834691] sd 3:0:0:0: [sda] Attached SCSI disk




-- System Information:
Debian Release: buster
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:ro (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.19.0-2-amd64  4.19.16-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: