[Bug 212113] New: USB stops working few minutes seemingly after specific actions on the PC

[bugzilla-daemon@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=212113

            Bug ID: 212113
           Summary: USB stops working few minutes seemingly after specific
                    actions on the PC
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.10.18-1-MANJARO
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: andrej.trnkoci@gmail.com
        Regression: No

When the problem occurs, my usb3 devices stop working and I can find following
error in logs viewed by dmesg:

[28231.353917] xhci_hcd 0000:03:00.0: ERROR unknown event type 15
[28236.265786] xhci_hcd 0000:03:00.0: xHCI host not responding to stop endpoint
command.
[28236.265793] xhci_hcd 0000:03:00.0: USBSTS:
[28236.265819] xhci_hcd 0000:03:00.0: xHCI host controller not responding,
assume dead
[28236.265838] xhci_hcd 0000:03:00.0: HC died; cleaning up

I seem to be able to reproduce this problem every time I run clickable
development tool for building, installing and running ubuntu touch mobile
application using clickable
https://clickable.bhdouglass.com/en/latest/index.html. The clickable tool uses
docker and possibly android debug (adb) to install and run the application. The
clickable command finishes the actions without problems but after few minutes
my usb stops working and I can find the above error in logs.

I am not 100 percent sure if this is the trigger for this issue but last +-5
times I tried running "clickable" command on my project the problems happend.
But if I run "clickable desktop" command (this command does not install the app
on mobile phone just runs it in a docker container) the problem seems to never
happen. Also if I use the ssh interface of clickable tool the problem does not
seem to happen at all. My guess is therefore that the problem could be caused
by the adb (android debug) tool. However it is only my speculation.

Below I provide a small subset of my system information:

Processor               : AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G
Memory          : 6025MB (1980MB used)
Machine Type            : Desktop
Operating System                : Manjaro Linux
-Display-
Resolution              : 1680x1050 pixels
OpenGL Renderer         : AMD KAVERI (DRM 2.50.0, 5.10.18-1-MANJARO, LLVM
11.1.0)

-USB Devices-
008:003         : VIA Labs, Inc. Hub
008:002         : VIA Labs, Inc. Hub
008:001         : Linux Foundation 3.0 root hub
007:004         : VIA Labs, Inc. Hub
007:003         : VIA Labs, Inc. Hub
007:002         : ASUSTek Computer, Inc. USB-AC56 802.11a/b/g/n/ac Wireless
Adapter [Realtek RTL8812AU]
007:001         : Linux Foundation 2.0 root hub
002:001         : Linux Foundation 2.0 root hub
004:001         : Linux Foundation 1.1 root hub
001:003         : Focusrite-Novation (Unknown)
001:004         : MosArt Semiconductor Corp. Wireless Keyboard/Mouse
001:002         : Terminus Technology Inc. Hub
001:001         : Linux Foundation 2.0 root hub
003:001         : Linux Foundation 1.1 root hub
006:001         : Linux Foundation 3.0 root hub
005:001         : Linux Foundation 2.0 root hub

I hope the provided information will be helpful, I will be glad to provide more
information if needed.

Best Regards
Andrej

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.