From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH 0/3] PM / sleep: Avoid filling up kernel log buffer with debug messages
Date: Wed, 19 Jul 2017 02:37:24 +0200 [thread overview]
Message-ID: <2539550.y54cRb749c@aspire.rjw.lan> (raw)
Hi,
The problem at hand is that on some systems suspend-to-idle can easily fill up
the kernel log buffer with debug messages in one cycle (if spurious wakeups
happen ofter enough).
I tried to make that somewhat better before, but it still turns out to be
problematic, so here's a patch series to possibly address this.
[1/3] adds a sysfs knob to turn debug messages from the core suspend/hibernate
code on and off (default) and a printk() wrapper taking that into account.
[2/3] adds some "info" messages to indicate when system power transitions start
and finish which IMO is useful to see in the log regardless.
[3/3] modifies the wrapper introduced by [1/3] to make it suitable for
tk_debug_account_sleep_time() and uses it in there instead of the
plain printk_deferred() as that also is a debug thing really and can
fill up the log buffer by itself in some cases.
Thanks,
Rafael
next reply other threads:[~2017-07-19 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 0:37 Rafael J. Wysocki [this message]
2017-07-19 0:38 ` [PATCH 1/3] PM / sleep: Do not print debug messages by default Rafael J. Wysocki
2017-07-19 0:39 ` [PATCH 2/3] PM / sleep: Mark suspend/hibernation start and finish Rafael J. Wysocki
2017-07-20 1:38 ` [PATCH v2 " Rafael J. Wysocki
2017-07-20 17:49 ` Mark Salyzyn
2017-07-20 21:05 ` Rafael J. Wysocki
2017-07-19 0:42 ` [PATCH 3/3] PM / timekeeping: Print debug messages when requested Rafael J. Wysocki
2017-07-20 21:52 ` Rafael J. Wysocki
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=2539550.y54cRb749c@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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
all inboxes | Powered by JetHome®