From: Peter Chen <peter.chen@kernel.org>
To: "jinguang.yu" <949347424@qq.com>
Cc: linux-usb@vger.kernel.org, Mathias Nyman <mathias.nyman@intel.com>
Subject: Re: xhci-hcd xhci-hcd.0.auto: ERROR unknown event type 37
Date: Sun, 14 Mar 2021 13:22:37 +0800 [thread overview]
Message-ID: <20210314052237.GB30122@b29397-desktop> (raw)
In-Reply-To: <tencent_BC210BFA458561BB06202CD4A82A21677708@qq.com>
On 21-03-13 16:36:39, jinguang.yu wrote:
> Hi Peter,
>
>
> Recently, we met a problem about xhci driver, which show "ERROR unknown event type 37" in xhci_handle_event() when we using a usb camera. Beside I have found your commit dc0ffbea5729a3abafa577ebfce87f18b79e294b in kernel to solve this problem. Could you provide some advise for ours to solve this problem? I uploaded this Error log in attachment. I'm very very grateful for your response.
>
>
Cc: USB ML and Mathias,
Hi Jinguang,
Please wrap your line up 75 characters next time.
What's your kernel version, and does my patch work for you? It usually
occurs when the software submits the requests faster than the requests
has handled.
--
Thanks,
Peter Chen
parent reply other threads:[~2021-03-14 5:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tencent_BC210BFA458561BB06202CD4A82A21677708@qq.com>]
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=20210314052237.GB30122@b29397-desktop \
--to=peter.chen@kernel.org \
--cc=949347424@qq.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox