From: Todd Brandt <todd.e.brandt@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
len.brown@intel.com, todd.e.brandt@intel.com
Subject: Re: [BUG] function_graph trace causes hang when using sleepgraph (4.15.0-rc1 and newer)
Date: Wed, 10 Jan 2018 16:21:08 -0800 [thread overview]
Message-ID: <1515630068.17761.16.camel@linux.intel.com> (raw)
In-Reply-To: <20180109111334.2628dcc5@vmware.local.home>
On Tue, 2018-01-09 at 11:13 -0500, Steven Rostedt wrote:
> On Mon, 08 Jan 2018 17:25:15 -0800
> Todd Brandt <todd.e.brandt@linux.intel.com> wrote:
>
> > Can you reproduce the issue there? I just want to be sure it's not
> > something local to our machines here, as long as you have CONFIG_PM
> > enabled it should work the same hopefully.
>
> Just to let you know, I'm currently traveling, so my testing ability
> is
> limited at the time being.
ok, it's not an emergency, we're using a patched version of the kernel
with those two commits removed in the interim. I tried running kgdb
over serial console, but unfortunately it doesn't work over a USB-to-
Serial dongle (even Greg K-H says it won't work, :P). This is the best
output I could get, considering:
# run the test script here
[ 545.733458] PM: suspend entry (deep)
[ 545.734535] PM: Syncing filesystems ... done.
[ 546.580551] Freezing user space processes ... (elapsed 0.013
seconds) done.
[ 546.594846] OOM killer disabled.
[ 546.595002] Freezing remaining freezable tasks ... (elapsed 0.005
seconds) done.
[ 557.808719] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0
So it's definitely a hard lockup, I just can't get the stack trace
without a system with a built in serial console.
>
> -- Steve
next prev parent reply other threads:[~2018-01-11 0:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 23:55 [BUG] function_graph trace causes hang when using sleepgraph (4.15.0-rc1 and newer) Todd Brandt
2018-01-09 1:02 ` Todd Brandt
2018-01-09 1:07 ` Steven Rostedt
2018-01-09 1:25 ` Todd Brandt
2018-01-09 3:07 ` Todd Brandt
2018-01-09 16:13 ` Steven Rostedt
2018-01-11 0:21 ` Todd Brandt [this message]
2018-01-18 17:21 ` Todd Brandt
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=1515630068.17761.16.camel@linux.intel.com \
--to=todd.e.brandt@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=todd.e.brandt@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.