| 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
| ||
|
Message-ID: <20070505100855.GC25704@elf.ucw.cz> Date: Sat, 5 May 2007 12:08:55 +0200 From: Pavel Machek <pavel@....cz> To: Ingo Molnar <mingo@...e.hu> Cc: Greg KH <gregkh@...e.de>, Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>, linux-pm@...ts.osdl.org Subject: Re: [patch] suspend/resume debugging: device filter Hi! > > Here's a (compile tested only) patch that does this on a per-device > > basis, which is smaller, and should work just as well as your patch. > > > > It creates a new file in the power/ directory for every device called > > "can_suspend". Write a '0' to it to prevent that device from being > > suspended. > > > > Does this work for you? > > yeah, i was able to use this too to debug suspend/resume problems. But > i've added the check to the resume path too - for example sw-suspend > does a resume of devices during its suspend cycle, cutting off much of > the netconsole output. > > which makes the can_suspend flag mis-named - perhaps rename it to > exclude_pm ? debug_exclude_pm? I do not want people playing with it, then complaining that they broke the suspend. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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/
Powered by blists - more mailing lists