From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751549AbXB0LGc (ORCPT ); Tue, 27 Feb 2007 06:06:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751550AbXB0LGc (ORCPT ); Tue, 27 Feb 2007 06:06:32 -0500 Received: from agminet01.oracle.com ([141.146.126.228]:51185 "EHLO agminet01.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751549AbXB0LGb (ORCPT ); Tue, 27 Feb 2007 06:06:31 -0500 Date: Tue, 27 Feb 2007 11:59:22 +0100 From: Jens Axboe To: Ingo Molnar Cc: Pavel Machek , Adrian Bunk , Linus Torvalds , Andrew Morton , Linux Kernel Mailing List , "Michael S. Tsirkin" , Thomas Gleixner , linux-pm@lists.osdl.org, Michal Piotrowski , Daniel Walker Subject: Re: 2.6.21-rc1: known regressions (part 2) Message-ID: <20070227105922.GD2250@kernel.dk> References: <20070225175559.GC12392@stusta.de> <20070227100202.GV3822@kernel.dk> <20070227102109.GG6745@elf.ucw.cz> <20070227103021.GA2250@kernel.dk> <20070227103407.GA17819@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070227103407.GA17819@elte.hu> X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 27 2007, Ingo Molnar wrote: > > * Jens Axboe wrote: > > > > > x60 doesn't resume from S2R either, it doesn't matter if > > > > CONFIG_NO_HZ is set or not though. 2.6.20 worked fine. > > > > > > It somehow works for me. As long as I do not play with bluetooth and > > > suspend to disk... > > > > It locks solid here on resume, going back to 2.6.20 makes it work > > perfectly again. In between 2.6.20 and 2.6.21-rc1 some ACPI change > > broke resume, but that got fixed. Some other change later snuck in > > that broke it AGAIN for me, sigh. > > > > I don't use bluetooth nor suspend to disk. > > resume is stock on my T60 too. So you mean v2.6.21-rc1 vanilla works > fine? Do you know a commit ID that works for sure? I'd like to bisect Nope, 2.6.21-rc1 vanilla does not work. 2.6.20 works. 2.6.20-gitX worked until some acpi change broke it, the below patch fixed that for me. That got merged in a later 2.6.20-gitY, but then some other patch broke it again so that 2.6.21-rc1 is broken. Not much luck there :-) So it looks like: - c5a7156959e89b32260ad6072bbf5077bcdfbeee broke 2.6.20-git - f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38 should fix that. - Something later than f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38 broke it again. > this, but this way i might just find that ACPI change that got already > fixed later on (and then got re-broken). Yeah, it gets trickier. I'll try f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38 now and see if that works, then bisect to 2.6.21-rc1 to find the other offender. I hope the other offender didn't get added before f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38, we'll see :-) -- Jens Axboe From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: 2.6.21-rc1: known regressions (part 2) Date: Tue, 27 Feb 2007 11:59:22 +0100 Message-ID: <20070227105922.GD2250@kernel.dk> References: <20070225175559.GC12392@stusta.de> <20070227100202.GV3822@kernel.dk> <20070227102109.GG6745@elf.ucw.cz> <20070227103021.GA2250@kernel.dk> <20070227103407.GA17819@elte.hu> 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: <20070227103407.GA17819@elte.hu> 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: Ingo Molnar Cc: linux-pm@lists.osdl.org, Thomas Gleixner , Michal Piotrowski , Pavel Machek , Daniel Walker , "Michael S. Tsirkin" , Andrew Morton , Linus Torvalds , Linux Kernel Mailing List , Adrian Bunk List-Id: linux-pm@vger.kernel.org On Tue, Feb 27 2007, Ingo Molnar wrote: > = > * Jens Axboe wrote: > = > > > > x60 doesn't resume from S2R either, it doesn't matter if = > > > > CONFIG_NO_HZ is set or not though. 2.6.20 worked fine. > > > = > > > It somehow works for me. As long as I do not play with bluetooth and = > > > suspend to disk... > > = > > It locks solid here on resume, going back to 2.6.20 makes it work = > > perfectly again. In between 2.6.20 and 2.6.21-rc1 some ACPI change = > > broke resume, but that got fixed. Some other change later snuck in = > > that broke it AGAIN for me, sigh. > > = > > I don't use bluetooth nor suspend to disk. > = > resume is stock on my T60 too. So you mean v2.6.21-rc1 vanilla works = > fine? Do you know a commit ID that works for sure? I'd like to bisect = Nope, 2.6.21-rc1 vanilla does not work. 2.6.20 works. 2.6.20-gitX worked until some acpi change broke it, the below patch fixed that for me. That got merged in a later 2.6.20-gitY, but then some other patch broke it again so that 2.6.21-rc1 is broken. Not much luck there :-) So it looks like: - c5a7156959e89b32260ad6072bbf5077bcdfbeee broke 2.6.20-git - f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38 should fix that. - Something later than f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38 broke it again. > this, but this way i might just find that ACPI change that got already = > fixed later on (and then got re-broken). Yeah, it gets trickier. I'll try f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38 now and see if that works, then bisect to 2.6.21-rc1 to find the other offender. I hope the other offender didn't get added before f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38, we'll see :-) -- = Jens Axboe