From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: 2.6.21-rc1: T60 resume from suspend to RAM issues Date: Tue, 27 Feb 2007 11:14:51 +0100 Message-ID: <20070227101451.GA11981@elte.hu> References: <20070223020904.c8fc8a3e.akpm@linux-foundation.org> <20070224211141.GA4425@mellanox.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20070224211141.GA4425@mellanox.co.il> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: "Michael S. Tsirkin" Cc: linux-acpi@vger.kernel.org, mingo@redhat.com, len.brown@intel.com, Andrew Morton , bunk@stusta.de, linux-kernel@vger.kernel.org, linux-pm@linux-foundation.org List-Id: linux-pm@vger.kernel.org * Michael S. Tsirkin wrote: > > > 2. As a separate test, I enabled DynTicks in .config. Seems to = > > > work fine but won't come out of suspend to memory at all: pressing = > > > Fn/F4 seems to have no effect. > > = > > Do you believe that the second problem was caused by dynticks? > = > Assuming these are 2 different problems, yes, the second one seems to = > be caused by dyntics. on my T60 current -git does not resume even without dynticks. v2.6.20 = with the same .config resumes fine (except for the display). after pressing Fn/F4 the disk light flashes briefly, which suggests that = action is probably back to the Linux kernel at that point, and that we = hung somewhere there. Will try a bisection thing. Ingo