From: Nathan Royce <nroycea+kernel@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>,
mathias.nyman@linux.intel.com, gregkh@linuxfoundation.org
Subject: Re: kernel: xhci_hcd 0000:00:14.0: ERROR unknown event type 37 - Kernel 4.19.13
Date: Wed, 2 Jan 2019 02:12:14 -0600 [thread overview]
Message-ID: <CALaQ_hof-z=20ZUxBfnVM7evgjieq8WorZesURegV7v_ZQ7VDg@mail.gmail.com> (raw)
In-Reply-To: <CALaQ_hp26KFcF95-yY31rtdhiG3XKJ_A4_B7nsysbJMPEy6k5g@mail.gmail.com>
...But then again, maybe it wasn't the cable. It's acting up again.
On Tue, Jan 1, 2019 at 3:14 PM Nathan Royce <nroycea+kernel@gmail.com> wrote:
>
> Looks like this particular issue may have been due to a touchy/finicky
> connection.
>
> I removed my tuner from my hub and removed the hub from my
> motherboard's USB and put my tuner in directly.
> It STILL produced the error, but after I put everything back and
> played around a little, the errors stopped.
>
> Just to be sure, I also rebooted and it's still fine. No xhci errors at all.
> The only thing I've done recently (within the past few days) was play
> with my scanner which is also on that hub and maybe brushed my tuner
> cable or something.
next prev parent reply other threads:[~2019-01-02 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 18:57 kernel: xhci_hcd 0000:00:14.0: ERROR unknown event type 37 - Kernel 4.19.13 Nathan Royce
2019-01-01 21:14 ` Nathan Royce
2019-01-02 8:12 ` Nathan Royce [this message]
2019-01-02 11:36 ` Mathias Nyman
2019-01-06 19:33 ` Nathan Royce
2019-01-09 3:01 ` Nathan Royce
2019-01-09 10:35 ` Nathan Royce
2019-01-09 22:11 ` Nathan Royce
2019-01-24 15:57 ` Mathias Nyman
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='CALaQ_hof-z=20ZUxBfnVM7evgjieq8WorZesURegV7v_ZQ7VDg@mail.gmail.com' \
--to=nroycea+kernel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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).