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. On Tue, Jan 1, 2019 at 12:57 PM Nathan Royce <nroycea+kernel@xxxxxxxxx> wrote: > > Kernel 4.19.13 > > 00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB > xHCI Controller > > Around 400 "unknown event type 37" messages logged in a 2 second span. > ***** > Jan 01 02:08:07 computername tvheadend[2370]: linuxdvb: Auvitek AU8522 > QAM/8VSB Frontend #0 : ATSC-T #0 - poll TIMEOUT > Jan 01 02:08:00 computername tvheadend[2370]: linuxdvb: Auvitek AU8522 > QAM/8VSB Frontend #0 : ATSC-T #0 - poll TIMEOUT > Jan 01 02:07:56 computername kernel: xhci_hcd 0000:00:14.0: ERROR > unknown event type 37 > ... > Jan 01 02:07:55 computername kernel: xhci_hcd 0000:00:14.0: ERROR > unknown event type 37 > Jan 01 02:07:55 computername kernel: xhci_hcd 0000:00:14.0: ERROR > unknown event type 37 > Jan 01 02:07:52 computername tvheadend[2370]: linuxdvb: Auvitek AU8522 > QAM/8VSB Frontend #0 : ATSC-T #0 - poll TIMEOUT > Jan 01 02:07:44 computername tvheadend[2370]: linuxdvb: Auvitek AU8522 > QAM/8VSB Frontend #0 : ATSC-T #0 - poll TIMEOUT > ***** > > I question whether this also caused kemleak to crash as well (will > post after this). > > Regarding my tv tuner, it isn't supported by the kernel specifically, > but is close enough that all I have to do is alter a single source > file to include my device's pid, and it works just fine almost all of > the time.
