public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org,
	suspend-devel List <suspend-devel@lists.sourceforge.net>,
	Frank Seidel <fseidel@suse.de>,
	akpm@linux-foundation.org, nigel@nigel.suspend2.net,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH, 2nd try] make disable_console_suspend runtime configurable
Date: Thu, 14 Jun 2007 00:23:08 +0200	[thread overview]
Message-ID: <20070613222308.GA17266@suse.de> (raw)
In-Reply-To: <20070613220800.GD2611@elf.ucw.cz>

On Thu, Jun 14, 2007 at 12:08:00AM +0200, Pavel Machek wrote:
> Hi!
> 
> > I hate having to recompile the kernel, just to be able to debug suspend.
> > Remove CONFIG_DISABLE_CONSOLE_SUSPEND, replace it by a tunable in
> > /sys/power/disable_console_suspend.
> 
> > Signed-off-by: Stefan Seyfried <seife@suse.de>
> > Signed-off-by: Frank Seidel <fseidel@suse.de>
> 
> I wonder if there's a better name?

Suggest one.

> Or maybe this should not be /sys configurable, but just have value for
> each console "this console can work while suspended"?
> 
> (serial can, vesafb can, netconsole can't)?

Go ahead, submit a patch. It won't be that trivial. And i wonder
if it is actually worth the hassle. This is a debugging facility.

> Exporting "crash-me" option to user does not seem that cool to me.

We have "echo c > /proc/sysrq-trigger" also.
This is a debugging option, and forcing users to recompile the kernel just
to debug suspend problems (not resume problems, the "it does not even go to
sleep" stuff is where this matters most) is IMO a bad idea.

We can also make this a boot parameter, i don't care, but i want to disable
console suspend without recompiling the kernel.
-- 
Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg  | "Well, surrounding them's out." 

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2007-06-13 22:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 20:03 [PATCH, 2nd try] make disable_console_suspend runtime configurable Stefan Seyfried
2007-06-13 21:36 ` Rafael J. Wysocki
2007-06-13 22:08 ` Pavel Machek
2007-06-13 22:23   ` Stefan Seyfried [this message]
2007-06-13 23:09     ` Rafael J. Wysocki
2007-06-14 12:14     ` Rafael J. Wysocki
2007-06-14 13:59       ` [PATCH, 3rd " Frank Seidel
2007-06-14 22:20         ` Rafael J. Wysocki
2007-06-17 21:35           ` Pavel Machek
2007-06-17 21:49             ` [Suspend-devel] " Pavel Machek
2007-06-18  5:27               ` Stefan Seyfried
2007-06-21 13:20                 ` Pavel Machek
2007-06-21 21:14                   ` Stefan Seyfried

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=20070613222308.GA17266@suse.de \
    --to=seife@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=fseidel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=suspend-devel@lists.sourceforge.net \
    /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