From: Michal Pecio <michal.pecio@gmail.com>
To: Martin Alderson <martinalderson@gmail.com>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>, linux-usb@vger.kernel.org
Subject: Re: xhci_hcd: AMD Raphael/Granite Ridge USB 2.0 xHCI [1022:15b8] dies on resume from suspend
Date: Sat, 30 May 2026 00:57:42 +0200 [thread overview]
Message-ID: <20260530005742.25893efa.michal.pecio@gmail.com> (raw)
In-Reply-To: <CA+_z3hSMRvW6qhZ4wB54hQyY89z+Mm0C48MGA40aqG7_+spX2g@mail.gmail.com>
On Fri, 29 May 2026 13:04:49 +0100, Martin Alderson wrote:
> Bus 007 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
So this is the problem device. Until we have any better idea what to
try, please add usbcore and usbhid dynamic debug and keep collecting
logs - maybe something useful will show up.
Looking at usbhid, it seems it may fail to suspend if some operations
are ongoing. And then usbcore may apparently suspend the device anyway
and usbhid will presumably try to continue its thing on the suspended
device. AFAIK any URB submissions should fail then, but there might be
a bug. I haven't yet looked closely at how it all works.
BTW, are you able to test patched kernels in case dynamic debug proves
insufficient to figure out what's going on?
Regards,
Michal
next prev parent reply other threads:[~2026-05-29 22:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 21:52 xhci_hcd: AMD Raphael/Granite Ridge USB 2.0 xHCI [1022:15b8] dies on resume from suspend martinalderson
2026-03-30 0:07 ` Michal Pecio
2026-04-04 12:04 ` Martin Alderson
2026-04-04 13:24 ` Michal Pecio
2026-05-09 14:51 ` Martin Alderson
2026-05-09 16:06 ` Michal Pecio
2026-05-10 16:29 ` Martin Alderson
2026-05-12 10:03 ` Michal Pecio
2026-05-12 14:01 ` Mathias Nyman
2026-05-28 11:52 ` Martin Alderson
2026-05-28 22:10 ` Michal Pecio
2026-05-28 23:06 ` Martin Alderson
2026-05-29 10:22 ` Michal Pecio
2026-05-29 12:04 ` Martin Alderson
2026-05-29 22:57 ` Michal Pecio [this message]
2026-06-06 13:12 ` Martin Alderson
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=20260530005742.25893efa.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=martinalderson@gmail.com \
--cc=mathias.nyman@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.