Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CALaQ_hoq+QfxGTi5aggfm6RehsiZOvmYk-Mz-Geu3TLdNrRXcg@mail.gmail.com>
 <CALaQ_hp26KFcF95-yY31rtdhiG3XKJ_A4_B7nsysbJMPEy6k5g@mail.gmail.com>
In-Reply-To: <CALaQ_hp26KFcF95-yY31rtdhiG3XKJ_A4_B7nsysbJMPEy6k5g@mail.gmail.com>
From:   Nathan Royce <nroycea+kernel@gmail.com>
Date:   Wed, 2 Jan 2019 02:12:14 -0600
Message-ID: <CALaQ_hof-z=20ZUxBfnVM7evgjieq8WorZesURegV7v_ZQ7VDg@mail.gmail.com>
Subject: Re: kernel: xhci_hcd 0000:00:14.0: ERROR unknown event type 37 -
 Kernel 4.19.13
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
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

...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.