Date: Sun, 11 Feb 2007 18:56:19 +0100
From: Jens Axboe <jens.axboe@oracle.com>
To: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
Cc: Len Brown <lenb@kernel.org>, linux-acpi@vger.kernel.org,
       linux-kernel@vger.kernel.org
Subject: Re: current git breaks resume
Message-ID: <20070211175619.GB3999@kernel.dk>
References: <20070209190307.GC6152@kernel.dk> <200702110002.38328.lenb@kernel.org> <20070211165302.GO6458@kernel.dk> <45CF52F4.3060108@linux.intel.com> <20070211173624.GU6458@kernel.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070211173624.GU6458@kernel.dk>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1199
Lines: 37

On Sun, Feb 11 2007, Jens Axboe wrote:
> On Sun, Feb 11 2007, Alexey Starikovskiy wrote:
> > Jens Axboe wrote:
> > >On Sun, Feb 11 2007, Len Brown wrote:
> > >  
> > >>On Friday 09 February 2007 14:03, Jens Axboe wrote:
> > >>    
> > >>>Hi,
> > >>>
> > >>>Unfortunately I'm a little short on time as I'll be travelling tomorrow,
> > >>>but of course preparing a new kernel for the laptop is something you
> > >>>want to do right before leaving. So I discovered that the current (well
> > >>>as of yesterday, HEAD is 5986a2ec35836a878350c54af4bd91b1de6abc59)
> > >>>doesn't resume on my x60. 2.6.20 works fine, so something broke since
> > >>>then.
> > >>>      
> > >>resume from RAM, or resume from disk?
> > >>    
> > >
> > >Resume from RAM, I never use suspend-to-disk.
> > >
> > >  
> > Jens,
> > Could you please test the patch I've sent?
> 
> Just saw it, will do.

With that patch applied, current git works as expected. Thanks!

-- 
Jens Axboe

-
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/