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_hrE9kX1F2sYab7rC6i15x1=vvJdOr4aTY3Oyx8w49sA7A@mail.gmail.com>
Date:   Wed, 9 Jan 2019 04:35:17 -0600
From:   Nathan Royce <nroycea+kernel@...il.com>
To:     Mathias Nyman <mathias.nyman@...ux.intel.com>
Cc:     linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
        Alan Stern <stern@...land.harvard.edu>,
        gregkh@...uxfoundation.org
Subject: Re: kernel: xhci_hcd 0000:00:14.0: ERROR unknown event type 37 -
 Kernel 4.19.13

You can ignore the last set of files with a sample of 1.
I got a nice sample of like 150 about 6 hours ago.
The link I included in the previous reply contains the same filenames,
just updated.
The journal timestamps (to correspond with the trace times) go from
"[513438.430253] computername kernel: xhci_hcd 0000:00:14.0: ERROR
unknown event type 37"
to
"[513438.796965] computername kernel: xhci_hcd 0000:00:14.0: ERROR
unknown event type 37"
That's 150 of them in less than 1/2 second.

On Wed, Jan 2, 2019 at 5:32 AM Mathias Nyman
<mathias.nyman@...ux.intel.com> wrote:
>
> The event type 37 is a host controller event, most likely a event ring full error.
>
> So there are probably so many events that we fill the event ring before we can handle them.
>
> Could you take traces of this?
> Note that the trace file will be huge.
>
> mount -t debugfs none /sys/kernel/debug
> echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb
> echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable
>
> copy the traces somewhere safe once the error is triggered:
> cp /sys/kernel/debug/tracing/trace  /<somewhere>
>
> -Mathias