linux-kernel - Re: kernel: xhci_hcd 0000:00:14.0: ERROR unknown event type 37

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALaQ_hof-z=20ZUxBfnVM7evgjieq8WorZesURegV7v_ZQ7VDg@mail.gmail.com>
Date:   Wed, 2 Jan 2019 02:12:14 -0600
From:   Nathan Royce <nroycea+kernel@...il.com>
To:     linux-kernel@...r.kernel.org
Cc:     linux-usb@...r.kernel.org, Alan Stern <stern@...land.harvard.edu>,
        mathias.nyman@...ux.intel.com, gregkh@...uxfoundation.org
Subject: Re: kernel: xhci_hcd 0000:00:14.0: ERROR unknown event type 37 -
 Kernel 4.19.13

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