linux-kernel - Re: [patch] suspend debugging: simulate suspend-to-RAM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 25 Jan 2007 14:29:24 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Pavel Machek <pavel@....cz>
Cc:	Ingo Molnar <mingo@...e.hu>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>,
	Len Brown <lenb@...nel.org>
Subject: Re: [patch] suspend debugging: simulate suspend-to-RAM

On Thursday, 25 January 2007 14:07, Pavel Machek wrote:
> Hi!
> 
> > Subject: [patch] suspend debugging: simulate suspend-to-RAM
> > From: Ingo Molnar <mingo@...e.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.

Greetings,
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/