From: Steven Rostedt <rostedt@goodmis.org>
To: Will Hawkins <hawkinsw@borlaugic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help with trace-cmd/ftrace recording process ID information
Date: Mon, 17 Jul 2017 16:17:12 -0400 [thread overview]
Message-ID: <20170717161712.6bc38c83@gandalf.local.home> (raw)
In-Reply-To: <CADx9qWj2+T0bd1GN1DOV+9_uKPc3FMqkqGJCmeTLL8y=FNMLCg@mail.gmail.com>
On Mon, 17 Jul 2017 16:06:37 -0400
Will Hawkins <hawkinsw@borlaugic.com> wrote:
> This seems to be the problem:
>
> On the "good" system, that file is up-to-date with cached PIDs and
> comms. On the bad host, there are no cached entries from any of the
> traces that I've run.
>
> Because these are running old kernels, there is no saved_cmdlines_size
> knob to turn. Do you have any idea why the saved_cmdlines would not be
> getting updated appropriately on the "bad" host? I know this is not
> ideal, but I can try to reboot that host and see if something is
Yeah, a reboot may work.
> simply wedged. The system has been online for almost a year, so it's
> possible that something has gone wrong.
>
> Any help you can offer would be great! Thank you, again, for your response!
The recording of command lines only happens when tracing is done, and
there were a few bugs with the older kernels that caused it to either
stop and never start again, or to simply just miss a bunch of recording.
It may be that it stopped and never started again, so you will only
have a stale file.
-- Steve
next prev parent reply other threads:[~2017-07-17 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 19:18 Will Hawkins
2017-07-17 19:53 ` Steven Rostedt
2017-07-17 20:06 ` Will Hawkins
2017-07-17 20:08 ` Will Hawkins
2017-07-17 20:17 ` Steven Rostedt [this message]
2017-07-17 22:31 ` Will Hawkins
2017-07-18 0:45 ` Steven Rostedt
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=20170717161712.6bc38c83@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=hawkinsw@borlaugic.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®