mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel+linux-ftrace@molgen.mpg.de>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@kernel.org>
Cc: 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>,
	regressions@leemhuis.info
Subject: Re: Suspend/resume with FTRACE enabled doesn’t work anymore
Date: Wed, 17 Jan 2018 16:19:59 +0100	[thread overview]
Message-ID: <771ccd34-d9dd-1a96-5e26-ba04377dda65@molgen.mpg.de> (raw)
In-Reply-To: <696324c4-0a21-8ee8-1ff8-e90e87020ff7@molgen.mpg.de>

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]

Dear Linux folks,


On 01/17/18 15:20, Paul Menzel wrote:

> 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)
> ```
> 
> Please find the configuration file used for the Lenovo T60 attached.

I first thought it might be related to the UBSAN enabled, but it’s not it.

Here the results for the Dell XPS 13 9360.

Trying Linux 4.13.0-26-generic shipped with Ubuntu 16.04 everything 
works as expected with `sleepgraph`. The system suspends and resumes. 
(Though it wakes up before the power button LED turns off.)

Using their mainline Linux kernel 4.15-rc8 build from [1], Linux 
4.15-rc8 also freezes during suspend as originally reported.


Kind regards,

Paul


> [1] https://01.org/suspendresume
[2] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc8/


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]

  reply	other threads:[~2018-01-17 15:20 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 [this message]
2018-01-17 16:10 ` Steven Rostedt
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=771ccd34-d9dd-1a96-5e26-ba04377dda65@molgen.mpg.de \
    --to=pmenzel+linux-ftrace@molgen.mpg.de \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@dell.com \
    --cc=mingo@kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=regression@leemhuis.info \
    --cc=regressions@leemhuis.info \
    --cc=rostedt@goodmis.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®