From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [patch] suspend debugging: simulate suspend-to-RAM
Date: Thu, 25 Jan 2007 14:30:04 +0100 [thread overview]
Message-ID: <20070125133004.GB23620@elf.ucw.cz> (raw)
In-Reply-To: <200701251429.25081.rjw@sisk.pl>
On Thu 2007-01-25 14:29:24, Rafael J. Wysocki wrote:
> On Thursday, 25 January 2007 14:07, Pavel Machek wrote:
> > Hi!
> >
> > > Subject: [patch] suspend debugging: simulate suspend-to-RAM
> > > From: Ingo Molnar <mingo@elte.hu>
> > >
> > > most resume bugs are due to the kernel hanging or crashing while trying
> > > to resume a specific device. It is extremely hard to debug such hangs
> > > because often when the hang happens there's no console available
> > > yet.
> >
> > While the functionality is useful, no I do not think this should be
> > configured by sysctl or kernel parameter.
> >
> > Perhaps right interface is "echo fake-mem > /sys/power/state"?
>
> Yes, the "test" and "testproc" debug modes are started via /sys/power/state,
> so let's make it consistent.
Ok, so this one should be "testmem".
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-01-25 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 11:33 [patch] suspend debugging: simulate suspend-to-RAM Ingo Molnar
2007-01-25 13:07 ` Pavel Machek
2007-01-25 13:29 ` Rafael J. Wysocki
2007-01-25 13:30 ` Pavel Machek [this message]
2007-01-25 18:03 ` Andrey Borzenkov
2007-01-25 21:26 ` Matt Mackall
2007-01-25 22:41 ` Rafael J. Wysocki
2007-01-29 15:41 ` Andi Kleen
2007-01-31 9:12 ` Ingo Molnar
2007-01-31 9:25 ` Andi Kleen
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=20070125133004.GB23620@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=torvalds@osdl.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 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.