From: "Sören Brinkmann" <soeren.brinkmann@gmail.com>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Willy Tarreau <w@1wt.eu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION 3.10.1] System does not wake up from suspend
Date: Tue, 16 Jul 2013 19:57:20 -0700 [thread overview]
Message-ID: <20130717025720.GA1267@skorgonTP.att.net> (raw)
In-Reply-To: <51E39BAB.4060308@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
On Mon, Jul 15, 2013 at 12:20:19PM +0530, Srivatsa S. Bhat wrote:
> On 07/15/2013 10:24 AM, Willy Tarreau wrote:
> > On Sun, Jul 14, 2013 at 09:36:25PM -0700, Sören Brinkmann wrote:
> >> Hi Greg,
> >>
> >> since upgrading to 3.10.1 I find my system not waking up from suspend
> >> from time to time. Unfortunately, I couldn't figure out how to reliably
> >> reproduce the issue. Sometimes it works just fine.
> >>
> >> All I know so far:
> >> On 3.10 I had my system completely freezing a few times. But that did
> >> not seem to be related to suspend/resume. I never experienced the
> >> behavior described below on 3.10.
> >>
> >> On 3.10.1 I hit this bug a few times, that my system did not wake up.
> >> I.e. the screen stayed black and the power LED kept flashing. But
> >> nothing brought the system back up and I had to longpress power to reset
> >> the system.
> >> I had none of the system freezes like the ones described above anymore.
> >
> > Fortunately, 3.10.1 is very small. The only patch it contains which is
> > related to suspend is 18/19 (cpufreq ondemand governor). Maybe you're
> > having a problem with cpufreq on this machine in fact.
> >
> > You may want to try to force it to performance mode or powersave mode
> > and try for a while, it is possible that both 3.10 and 3.10.1 will work
> > fine.
> >
>
> Or, you could try applying the patch shown below on top of 3.10.1 and
> see if it fixes the suspend/resume regression for you.
>
> https://lkml.org/lkml/2013/7/11/661
>
> (Just apply patch 1, not the entire patchset).
So, this didn't end well. With that patch applied I end up in a kernel
panic on suspend, reproducible - well two out of two is a small test set,
but anyway. Unfortunately too late to get any information about it
and my logs don't show anything either. But it's seems worse than the
rather occasional hangs on resume on the vanilla 3.10.1 kernel.
Sören
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-07-17 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 4:36 Sören Brinkmann
2013-07-15 4:54 ` Willy Tarreau
2013-07-15 6:50 ` Srivatsa S. Bhat
2013-07-16 2:12 ` Sören Brinkmann
2013-07-17 2:57 ` Sören Brinkmann [this message]
2013-07-17 4:57 ` Srivatsa S. Bhat
2013-07-17 5:38 ` Sören Brinkmann
2013-07-17 6:04 ` Sören Brinkmann
2013-07-17 6:38 ` Srivatsa S. Bhat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130717025720.GA1267@skorgonTP.att.net \
--to=soeren.brinkmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®