From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Richard Weinberger <richard@nod.at>,
"Amanieu d'Antras" <amanieu@gmail.com>,
Chris Metcalf <cmetcalf@ezchip.com>,
Andy Lutomirski <luto@amacapital.net>,
Davidlohr Bueso <dave@stgolabs.net>,
Vladimir Davydov <vdavydov@parallels.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: WARNING in set_restore_sigmask
Date: Fri, 29 Jan 2016 09:32:35 -0500 [thread overview]
Message-ID: <20160129093235.22532397@gandalf.local.home> (raw)
In-Reply-To: <alpine.DEB.2.11.1601291505580.3886@nanos>
On Fri, 29 Jan 2016 15:10:18 +0100 (CET)
Thomas Gleixner <tglx@linutronix.de> wrote:
> The time depends on the serial speed and the trace buffer size and the number
> of cpus. Don't worry about the uptime. The buffer is a ringbuffer with limited
> capacity, so the dump time is constant.
>
> If you want that /proc/sys/kernel/ftrace_dump_on_oops spills out on warnings
> as well, you need to enable
>
> /proc/sys/kernel/traceoff_on_warning
> /proc/sys/kernel/ftrace_dump_on_oops
>
> and
>
> /proc/sys/kernel/panic_on_warn
>
> because we do not dump on warnings.
To save time in the wait, you may also want to do:
# echo 50 > /sys/kernel/debug/tracing/buffer_size_kb
which will make each per cpu buffer 50 kb, instead of the default of a
meg each. That will cut down the time to spit out the ftrace buffer to
serial console, but it wont have as much data. 50 kb should be enough
to trace back to the problem point though.
-- Steve
next prev parent reply other threads:[~2016-01-29 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 9:16 Dmitry Vyukov
2016-01-29 9:24 ` Dmitry Vyukov
2016-01-29 11:53 ` Thomas Gleixner
2016-01-29 13:16 ` Dmitry Vyukov
2016-01-29 13:57 ` Thomas Gleixner
2016-01-29 14:05 ` Dmitry Vyukov
2016-01-29 14:10 ` Thomas Gleixner
2016-01-29 14:32 ` Steven Rostedt [this message]
2016-01-29 14:13 ` Oleg Nesterov
2016-01-29 14:16 ` Thomas Gleixner
2016-02-01 22:46 ` Andrew Morton
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=20160129093235.22532397@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=amanieu@gmail.com \
--cc=cmetcalf@ezchip.com \
--cc=dave@stgolabs.net \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=vdavydov@parallels.com \
/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®