Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mvebu_u3d: USB3.0 device mode not working properly #3

Open
mmgu opened this issue Sep 4, 2017 · 1 comment
Open

mvebu_u3d: USB3.0 device mode not working properly #3

mmgu opened this issue Sep 4, 2017 · 1 comment

Comments

@mmgu
Copy link

mmgu commented Sep 4, 2017

While testing linux-4.4.52-armada-17.08 on our Armada-7040 based board, we found g_mass_storage module can only work for the first time. Just run the following command after booting up:

# modprobe g_mass_storage file=/dev/sda

The host side (Windows PC) recognized USB mass storage device successfully.

If we try to unload g_mass_storage module and load it for a second time, system either crashes or USB device can not be recognized by host. If USB cable is left connected when we do rmmod g_mass_storage, kernel will crash. If we disconnect USB cable and then rmmod g_mass_stroage; modprobe g_mass_storage file=/dev/sda, the Windows host will report "unrecognized USB device" error.

'dmesg' shows:

[ 1217.560142] USB device: connected
[ 1218.404488] USB device: warm reset
[ 1219.036488] USB device: warm reset
[ 1219.667488] USB device: warm reset
[ 1219.780754] USB device: suspend

Disconnecting/reconnecting USB cable won't help; however, it will work if we connect a USB2.0 cable.

@smurfix
Copy link

smurfix commented Dec 24, 2017

Any feedback on this problem – or is this issue tracker a black hole?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants