linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Koehrer Mathias (ETAS/ESW5)" <mathias.koehrer@etas.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference on 3.18.13-rt10
Date: Tue, 14 Jul 2015 10:15:51 -0400	[thread overview]
Message-ID: <20150714101551.2f39f196@gandalf.local.home> (raw)
In-Reply-To: <523c30ce4e4c4b53befcd288db178db9@FE-MBX1012.de.bosch.com>

On Tue, 14 Jul 2015 07:38:46 +0000
"Koehrer Mathias (ETAS/ESW5)" <mathias.koehrer@etas.com> wrote:

> > What's the test that was run, and how did it enable function tracing?
> 
> The tracing was enabled within an init script using the following bash commands:
>     if ! grep -q "/sys/kernel/debug" /proc/mounts; then
>         mount -t debugfs nodev /sys/kernel/debug
>     fi
>     if [ -d /sys/kernel/debug/tracing ]; then
>         (
>         cd /sys/kernel/debug/tracing
>         echo "function" > current_tracer
>         echo "1" > tracing_on
> 
>         echo "1" > /proc/sys/kernel/ftrace_dump_on_oops
>         )
>     fi
> 
> 
> The test was to reboot the PC permanently (every minute).
> The reboot has been initiated by another PC that remotely controls the PC under test.
> 

How reproducible is this?

-- Steve

  reply	other threads:[~2015-07-14 14:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 10:49 BUG: unable to handle kernel NULL pointer dereference on 3.18.13-rt10 Koehrer Mathias (ETAS/ESW5)
2015-07-09 14:11 ` Thomas Gleixner
2015-07-09 18:35   ` Josh Cartwright
2015-07-10 12:49   ` Koehrer Mathias (ETAS/ESW5)
2015-07-10 13:23     ` Sebastian Andrzej Siewior
2015-07-13  6:18       ` Koehrer Mathias (ETAS/ESW5)
2015-07-13  9:12         ` Sebastian Andrzej Siewior
2015-07-13 15:34           ` Steven Rostedt
2015-07-14  7:38             ` Koehrer Mathias (ETAS/ESW5)
2015-07-14 14:15               ` Steven Rostedt [this message]
2015-07-14 14:24                 ` Mathias Koehrer
2015-07-14 14:29                   ` Steven Rostedt
2015-07-14 14:33                     ` Koehrer Mathias (ETAS/ESW5)
2015-07-13  7:39       ` Koehrer Mathias (ETAS/ESW5)
2015-07-13  7:55         ` Sebastian Andrzej Siewior
2015-07-13  8:56           ` Koehrer Mathias (ETAS/ESW5)
2015-07-13  8:58             ` Sebastian Andrzej Siewior
2015-07-15  7:12               ` Mathias Koehrer
2015-07-20  7:38                 ` AW: " eg Engleder Gerhard
2015-07-20 14:56                   ` Sebastian Andrzej Siewior
2015-07-21  6:13                     ` AW: " eg Engleder Gerhard
2015-07-22  6:26                       ` Koehrer Mathias (ETAS/ESW5)
2015-07-22 13:26                         ` Steven Rostedt
2015-07-24 19:02                           ` Thomas Gleixner
2015-07-24 19:21                             ` Steven Rostedt
2015-07-24 20:21                               ` Gratian Crisan
2015-07-24 20:51                                 ` Steven Rostedt
2015-08-05  1:20                             ` 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=20150714101551.2f39f196@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mathias.koehrer@etas.com \
    --cc=tglx@linutronix.de \
    /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).