Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764620AbYBVNHB (ORCPT ); Fri, 22 Feb 2008 08:07:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754173AbYBVNGw (ORCPT ); Fri, 22 Feb 2008 08:06:52 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:44146 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752671AbYBVNGv (ORCPT ); Fri, 22 Feb 2008 08:06:51 -0500 Date: Fri, 22 Feb 2008 14:06:15 +0100 From: Ingo Molnar To: Matthew Garrett Cc: Jeff Chua , Jesse Barnes , Romano Giannetti , Linus Torvalds , suspend-devel List , Dave Airlie , Greg KH , lkml , "Rafael J. Wysocki" , linux-acpi@vger.kernel.org Subject: Re: [Suspend-devel] 2.6.25-rc2 System no longer powers off aftersuspend-to-disk. Screen becomes green. Message-ID: <20080222130615.GA29123@elte.hu> References: <200802211302.27002.jesse.barnes@intel.com> <200802211623.55450.jesse.barnes@intel.com> <20080222103727.GA25781@srcf.ucam.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080222103727.GA25781@srcf.ucam.org> User-Agent: Mutt/1.5.17 (2007-11-01) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1986 Lines: 43 * Matthew Garrett wrote: > The s2ram command has a built-in whitelist used to set up video > rePOSTing. If you want to test, reboot and do > > echo mem >/sys/power/state > > without i915 being loaded. If you get a console back on resume then > the platform is reinitialising video for you, but otherwise it's your > userspace. btw., why isnt there an in-kernel whitelist, with perhaps a dynamic, convenient /debug/s2r/whitelist append-API for distros (and testers) to add more entries to the whitelist/blacklist? (for cases where the kernel whitelist has not caught up yet) Which would eventually converge to Utopia: s2ram that just works out of box. This would be a lot more flexible (people could even temporarily extend the whitelist via rc.local if need to be, etc.), a lot more robust and a lot more user friendly than the "dont use /sys/power/state, rely on some user-space tool to work around bugs" approach. Really, i couldnt make the s2ram API/quirks situation much worse even if i deliberately tried to design the whole code to be as hard to use and as confusing as possible :-/ These types of half-kernel half-userspace solutions usually result in constant finger-pointing and constant lag, and they result in about the crappiest user experience that is possible to achieve physically. ( Sorry about the strong words, while there's lots of good and positive development lately i havent seen much change in this particular area of s2ram in the past 1-2 years, and the whole chain is only as strong as the weakest link - so someone finally has to deliver this message to the cozy fire of s2r hackers while our testers and users are standing out in the cold rain ... ) Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/