From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 207065] C-media USB audio device stops working from 5.2.0-rc3 onwards
Date: Tue, 29 Sep 2020 10:58:12 +0000 [thread overview]
Message-ID: <bug-207065-208809-e8UN1dIQrF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207065-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207065
--- Comment #13 from Florian Meyer (florianmey@gmx.de) ---
So I'm not entirely sure if this is related to my previous problem but I'm now
encountering a different kind of USB problems. USB equipment is still the same
as described in the first message.
The new problem leads to all USB devices getting disconnected, USB audio as
well as mouse. The USB keyboard continues working because I guess it is working
via PS2 internally?
The problem has been occurring pretty much since the previous issue was fixed
but only sporadically. Today it occurred for the first time in ~4 weeks and
sometimes it happened several times in a day.
The last messages in the dmesg log are:
[ 7075.685892] xhci_hcd 0000:2a:00.3: xHCI host not responding to stop endpoint
command.
[ 7075.685895] xhci_hcd 0000:2a:00.3: USBSTS:
[ 7075.701768] xhci_hcd 0000:2a:00.3: xHCI host controller not responding,
assume dead
[ 7075.701775] xhci_hcd 0000:2a:00.3: HC died; cleaning up
[ 7075.701808] usb 3-1: USB disconnect, device number 2
[ 7075.766108] usb 3-2: USB disconnect, device number 3
[ 7075.766110] usb 3-2.4: USB disconnect, device number 4
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-09-29 10:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 15:57 [Bug 207065] New: C-media USB audio device stops working from 5.2.0-rc3 onwards bugzilla-daemon
2020-04-02 16:00 ` [Bug 207065] " bugzilla-daemon
2020-04-02 16:01 ` bugzilla-daemon
2020-04-08 10:08 ` bugzilla-daemon
2020-04-09 12:32 ` bugzilla-daemon
2020-04-09 14:01 ` Alan Stern
2020-04-09 12:34 ` bugzilla-daemon
2020-04-09 14:01 ` bugzilla-daemon
2020-04-10 17:58 ` bugzilla-daemon
2020-04-14 10:07 ` bugzilla-daemon
2020-04-14 16:30 ` bugzilla-daemon
2020-04-14 16:30 ` bugzilla-daemon
2020-04-14 16:34 ` bugzilla-daemon
2020-04-16 13:00 ` bugzilla-daemon
2020-09-29 10:58 ` bugzilla-daemon [this message]
2020-09-29 10:59 ` bugzilla-daemon
2020-09-29 11:02 ` bugzilla-daemon
2020-09-29 11:50 ` bugzilla-daemon
2020-09-29 11:53 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-207065-208809-e8UN1dIQrF@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).