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

Bug#782442: USB3 external HDD not recognized [regression]





On 06/06/2015 04:56 AM, Ralf Jung wrote:
Hi,

I got some untested and not yet reviewed usb3 resume race fixes from Zhuang Jin Can
If you can try them out and see if they help it would be great.
They are sitting in a topic branch called "xhci_usb3_pm_fixes" in my tree:
(5 extra patches on top of current usb-linus)

git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git xhci_usb3_pm_fixes
This is my production and (main and only) work machine. If you tell me
testing that branch is safe and won't mess up my file systems or
hardware, I can give it a try.

I tested that branch (HEAD commit 190f6b0b), and the issue is still the
same. Directly after booting, if I plug in the disk, it doesn't work
(with the "root hub lost power" error). Removing the cable, setting
power/control to "on" for all PCI devices, then plugging it back in, the
disk works fine.

"root hub lost power" is not an error message. It shows when host controller
needs to reset on a resume.

Do you mind sending a dmesg data with usbcore and xhci_hcd dynamic debug
enabled? Sorry if you have posted one.

echo -n 'module xhci_hcd +p' > /sys/kernel/debug/dynamic_debug/control
echo -n 'module usbcore +p' > /sys/kernel/debug/dynamic_debug/control

Thanks,
Baolu


What was the  model of the USB3 disk again? some Seagate Expansion Disk?
I'll see If I can find one of those myself somehow
lsusb says:
Bus 003 Device 002: ID 0bc2:3312 Seagate RSS LLC

The package says "Seagate Expansion 5TB". But I'm not sure these are all
using the same controller; for example, I also have a "Seagate Expansion
3TB" that works fine.

(I'm removing Wang, Yu <yu.y.wang@intel.com> from the recipients, as I
keep getting bounces from that address.)

Kind regards,
Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html



Reply to: