Arch Linux

Smokehead

Member

Registered: 2018-04-17

Posts: 3

Android-Studio USB-Crash after some minutes - AMD-Workstation

Hi,

i'm facing some trouble using Android Studio to develop an Android app on Arch-Linux. On my main workstation i get an error after a while when using Android Studio to compile and install the app on the smartphone. The Smartphone loses connection and i'm not able to reconnect any USB-Device after that.

Keyboard and Mouse are still working but i can't use NumLock and CapsLock anymore on the keyboard. After reconnecting mouse and keyboard none of them are recognized. The only option to solve this issue is to reboot.

Errors (via dmesg | grep usb):

[ 2922.026323] usb usb2-port2: attempt power cycle
[ 2922.447773] usb 2-2: new SuperSpeed USB device number 42 using xhci_hcd
[ 2927.532395] usb 2-2: device descriptor read/8, error -110
[ 2927.636197] usb 2-2: new SuperSpeed USB device number 42 using xhci_hcd
[ 2932.652379] usb 2-2: device descriptor read/8, error -110
[ 2932.955435] usb 2-2: new SuperSpeed USB device number 43 using xhci_hcd
[ 2938.284206] usb 2-2: device descriptor read/8, error -110
[ 2938.387996] usb 2-2: new SuperSpeed USB device number 43 using xhci_hcd

After rebooting i can use everything again until the error occures again. I tried downgrading the kernel but it still didn't work. Same machine with ubuntu works. On my Notebook i have the same settings with Arch-Linux and same software-versions. It works without any problems too. I also tried different Android devices.

Workstation Specs:

    AMD Ryzen 5 1600X
    AMD Radeon RX 560
    2x 8 GB DDR4-2133 MHz RAM
    Samsung 960 Pro 250 GB SSD

Notebook Specs:

    Intel i7-7500u
    8 GB DDR4-2133 MHz RAM
    Toshiba NVMe 512 GB SSD

Maybe someone can help me and explain the problem to me. I tried using all USB-Ports on my machine but get the same error again and again. I thought of some USB-3 (xHCI) problems but the USB-2 Ports will give me the same error.

Thanks in advance!

Last edited by Smokehead (2018-04-17 16:50:39)

Smokehead

Member

Registered: 2018-04-17

Posts: 3

Re: Android-Studio USB-Crash after some minutes - AMD-Workstation

No idea??

Some updates didn't brought any solution.

Last edited by Smokehead (2018-05-03 13:44:54)

Smokehead

Member

Registered: 2018-04-17

Posts: 3

Re: Android-Studio USB-Crash after some minutes - AMD-Workstation

After almost reinstalling the whole system i pulled the plug for some time and tried it again.
It works now as supposed without any interruptions and/or errors.

Does anyone have an idea what it could have been?

D4VID0x2

Member

Registered: 2024-06-02

Posts: 1

Re: Android-Studio USB-Crash after some minutes - AMD-Workstation

I've faced the same issue for the past 2 years or so, same behavior, after an hour or so of running Android Studio, the system stops recognizing new usb devices and keyboard led indicators stop working with the device descriptor read/8, error -110.

I've found a temporary fix: by running

 # rmmod xhci_pci; modprobe xhci_pci 

it goes back to a functioning state for a while again so I didn't have to reboot each time which made it much less annoying.

I've tried uninstalling it, even by just deleting ~/.local/share/JetBrains/Toolbox/apps/android-studio, ~/.local/share/Google/AndroidStudio..., ~/.config/Google/AndroidStudio..., ~/.cache/Google/AndroidStudio... but with no luck. Then I tried to make a new system user and run Android Studio under it and there it didn't have the issue, it run just fine, so I figured it must be something with my user and not system wide.

And I ended up fixing it by deleting the ~/.gradle directory. Not sure what exactly went wrong but I don't have the issue anymore.

So if anyone out there is still experiencing the same issue, try that.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,932

Re: Android-Studio USB-Crash after some minutes - AMD-Workstation

Thanks for your input, D4VID0x2 .

OP hasn't posted in years,  so I'm closing this thread.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky