From: Steven Rostedt <rostedt@goodmis.org>
To: Paul Menzel <pmenzel+linux-ftrace@molgen.mpg.de>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, regression@leemhuis.info,
Mario Limonciello <mario.limonciello@dell.com>,
Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: Suspend/resume with FTRACE enabled doesn’t work anymore
Date: Wed, 17 Jan 2018 11:10:31 -0500 [thread overview]
Message-ID: <20180117111031.69f46195@gandalf.local.home> (raw)
In-Reply-To: <696324c4-0a21-8ee8-1ff8-e90e87020ff7@molgen.mpg.de>
On Wed, 17 Jan 2018 15:20:42 +0100
Paul Menzel <pmenzel+linux-ftrace@molgen.mpg.de> wrote:
> Dear Linux folks and Dell XPS 13 9360 users,
>
>
> Testing Linux 4.15-rc8 on a Lenovo T60 (32 bit) and Dell XPS 13 9360 (64
> bit) suspend to and resume from ACPI S3 doesn’t work anymore.
> `./sleepgraph.py -config config/suspend-callgraph.cfg` [1] is used to
> enable the FTRACE framework.
>
> On the Lenovo T60 the system seems to enter ACPI S3 state just fine, but
> doesn’t wake up.
>
> On the Dell XPS 13 9360 the system doesn’t enter ACPI S3 and just
> freezes with the display still on, and the messages below.
>
> ```
> […]
> INITIALIZING FTRACE...
> Setting trace buffers to 3145728 kB (786432 kB per cpu)
> ```
It's been fixed, and the the patch is in Linus's tree already:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0e3a18f4baf8e3754ac1e56f0ade924d0c0c721
-- Steve
next prev parent reply other threads:[~2018-01-17 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 14:20 Paul Menzel
2018-01-17 15:19 ` Paul Menzel
2018-01-17 16:10 ` Steven Rostedt [this message]
2018-01-17 16:19 ` Steven Rostedt
2018-01-17 16:25 ` Steven Rostedt
2018-01-18 9:33 ` Paul Menzel
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=20180117111031.69f46195@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=mingo@kernel.org \
--cc=pmenzel+linux-ftrace@molgen.mpg.de \
--cc=rafael.j.wysocki@intel.com \
--cc=regression@leemhuis.info \
/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®