Re: Resume regression on MBA2,1 triggered by2167e2399dc5e69c62db56d933e9c8cbe107620a

From: Bruno PrÃmont
Date: Thu Dec 12 2013 - 07:38:20 EST


Hi Greg,

On Tue, 10 December 2013 Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> On Wed, Dec 11, 2013 at 01:08:52AM +0100, Bruno PrÃmont wrote:
> > I have bisected failing resume from S3 on my MBA2,1 to be caused by
> > the following patch (introduced between 3.13-rc2 and 3.13-rc3 - rc2
> > resuming as expected, rc3 failing to resume).
> >
> > Unfortunately I have no trace for the failing resume though CPU seems
> > to not be busy as fan does not start blowing (even when waiting more
> > than 10 minutes for the resume to eventually proceed which it does not).
> >
> > Kernel config and dmesg are attached (gzip compressed).
> >
> > commit 2167e2399dc5e69c62db56d933e9c8cbe107620a
> > Author: BjÃrn Mork <bjorn@xxxxxxx>
> > Date: Tue Dec 3 12:14:32 2013 +0100
> > Subject: cpufreq: fix garbage kobjects on errors during suspend/resume
>
> This has already been reverted in Linus's tree, see commit
> d4faadd5d5b368a7051fef374ee933ec3606713b for the details.
>
> Does Linus's tree still have the same problem for you?

The revert in Linus's tree does fix the resume problem,
(tested commit: 9538e10086bd1301fe, merge of linux-watchdog).

thanks,
Bruno

> thanks,
>
> greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/