linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Royce <nroycea+kernel@gmail.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>,
	gregkh@linuxfoundation.org
Subject: Re: kernel: xhci_hcd 0000:00:14.0: ERROR unknown event type 37 - Kernel 4.19.13
Date: Sun, 6 Jan 2019 13:33:09 -0600	[thread overview]
Message-ID: <CALaQ_hpy==CbwmF25eoYM6xb7dAxQZ3y1DmFMDDv-GtK8p3NPg@mail.gmail.com> (raw)
In-Reply-To: <824caf1d-f5db-a439-fc77-deda67df5bfc@linux.intel.com>

I'm only posting to say I'm still waiting...
The error came up while I slept, and when I copied that log and looked
at it (yes, it WAS huge, just as you said), the timestamps at the
head/tail were much later than the journal logged times.
So I made a little script to monitor the journal kernel entries for
that message and have it copy the file after maybe 5 seconds. And now,
I'm just waiting for that error to occur again.

On Wed, Jan 2, 2019 at 5:32 AM Mathias Nyman
<mathias.nyman@linux.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

  reply	other threads:[~2019-01-06 19:33 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
2019-01-02 11:36 ` Mathias Nyman
2019-01-06 19:33   ` Nathan Royce [this message]
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_hpy==CbwmF25eoYM6xb7dAxQZ3y1DmFMDDv-GtK8p3NPg@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).