linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <roland@purestorage.com>
To: Tomasz Chmielewski <tch@wpkg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.5-rc7 - can no longer wake up from suspend to RAM
Date: Sat, 21 Jul 2012 15:11:03 -0700	[thread overview]
Message-ID: <CAL1RGDU8TVBkZ4yP=kjwqvGUsrnQcBGpLa_x-7c=Gu54piVwyw@mail.gmail.com> (raw)
In-Reply-To: <50079125.3020007@wpkg.org>

On Wed, Jul 18, 2012 at 9:46 PM, Tomasz Chmielewski <tch@wpkg.org> wrote:
> After upgrading to 3.5-rc7, my laptop no longer wakes up reliable from suspend to RAM. 3.4.x worked fine.

FWIW, I've been having similar problems with 3.5-rc7.  With 3.5-rc6 my
laptop resumed fine, but since updating to -rc7, it often seems to just
sit there after opening the lid -- the moon/sleep LED stays on, and the
power LED smoothly cycles on and off, as if it's fast asleep.  Even pressing
the power button doesn't have any effect (until I hold down the power
button long enough to turn off).

I guess I'll start a bisection, but it's slow going because it takes multiple
tries to know for sure if a kernel is bad.

The only commit between rc6 and rc7 that looks like it might be related
is dc332fdf9f373a87b1e2f423b5b004b2a3c37e1a ("ACPI / PM: Leave
Bus Master Arbitration enabled for suspend/resume"), which apparently
fixes some other laptops.  But perhaps I'll try reverting that and see how
it goes.

 - R.

  reply	other threads:[~2012-07-21 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19  4:46 3.5-rc7 - can no longer wake up from suspend to RAM Tomasz Chmielewski
2012-07-21 22:11 ` Roland Dreier [this message]
2012-07-22  2:07   ` Hugh Dickins
2012-07-22  5:48     ` Roland Dreier
2012-07-22  5:51       ` Tomasz Chmielewski

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='CAL1RGDU8TVBkZ4yP=kjwqvGUsrnQcBGpLa_x-7c=Gu54piVwyw@mail.gmail.com' \
    --to=roland@purestorage.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tch@wpkg.org \
    /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;
as well as URLs for NNTP newsgroup(s).