On 06/02/2017 12:27 AM, Kai-Heng Feng wrote:
> Sounds like there are two problems here,
> 1. The external drive does not work well in UAS mode (see previous comment)
> 2. The VIA hub has a remote wakeup bug.
>
> uname -a
Linux P9X79 4.12.0-041200rc2-generic #201705212331 SMP Mon May 22
03:32:26 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I connected the WD My Passport to a motherboard USB 3.0 port. It was
recognized. A level 0 dump completed:
DUMP: 160901600 blocks (157130.47MB) on 1 volume(s)
DUMP: finished in 1970 seconds, throughput 81675 kBytes/sec
Note: the tunables are at the kernel default settings.
Remote wakeup: tested with a Broadcom Bluetooth device.
> lsusb
Bus 002 Device 003: ID 0cf3:3005 Qualcomm Atheros Communications AR3011
Bluetooth
Bus 002 Device 002: ID 8087:0024 Intel Corp.Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 009: ID 1058:25e2 Western Digital Technologies, Inc.
Bus 006 Device 004: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 006 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 006 Device 002: ID 2109:0810 VIA Labs, Inc. VL81x Hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 004: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 005 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 005 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 045e:00cb MicrosoftCorp. Basic Optical Mouse v2.0
Bus 001 Device 003: ID 045e:0768 Microsoft Corp. Sidewinder X4
Bus 001 Device 002: ID 8087:0024 Intel Corp.Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Connect a bluetooth device to the external USB 3.0 hub.
> lsusb | grep Bluetooth
Bus 002 Device 003: ID 0cf3:3005 Qualcomm Atheros Communications AR3011
Bluetooth
Bus 005 Device 007: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
A device other than the WD My Passport is recognized upon connection to
the external USB 3.0 hub.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1693842
Title:
USB 3.0 Disk Drive Not Recognized.
Status in linux package in Ubuntu:
Confirmed
Bug description:
WD My Passport 2T USB 3.0 Disk Drive.
External Plugable 7 port USB 3.0 hub.
When I connect the WD drive to the external USB 3.0 hub it is not recognized.
The drive led blinks one time and it is not in dmesg or in the output of
lsusb.
> sudo lsusb -v causes the drive led to blink several times and it is
recognized.
With Autosuspend good for this device, long access applications like dump
fail.
After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes
and then dump asks for operator intervention. Looking at dmesg the drive
(initially sdf) was disconnected and reconnected as sdg.
Bad Autosuspend for USB device xHCI Host Controller [usb6]
seems to correct this behavior but not the initial connection problem.
Some discussion and testing in bug 1242321.
If I connect the drive to a USB 3.0 port on the motherboard, it is
recognized.
There is no problem with an Plugable 7-port USB 2.0 hub.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-78-generic 4.4.0-78.99
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: tomdean 3698 F.... pulseaudio
/dev/snd/controlC0: tomdean 3698 F.... pulseaudio
Date: Fri May 26 09:05:20 2017
HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a
InstallationDate: Installed on 2016-05-15 (375 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
IwConfig:
lo no wireless extensions.
eno1 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic
root=UUID=47d8903b-afb2-4432-bc92-b1f4e30209ef ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-78-generic N/A
linux-backports-modules-4.4.0-78-generic N/A
linux-firmware 1.157.8
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P9X79 PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4801:bd07/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693842/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
