mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Andy Isaacson <adi@hexapodia.org>, linux-kernel@vger.kernel.org
Cc: Zou Nan hai <nanhai.zou@intel.com>
Subject: Re: [2.6.36-rc2 regression] X201s: resume-from-S2R hangs
Date: Tue, 07 Sep 2010 10:12:34 -0700	[thread overview]
Message-ID: <87fwxlbhq5.fsf@pollan.anholt.net> (raw)
In-Reply-To: <20100906090536.GA12250@hexapodia.org>

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

On Mon, 6 Sep 2010 02:05:36 -0700, Andy Isaacson <adi@hexapodia.org> wrote:
> I have a Thinkpad X201s on which suspend-to-RAM was quite reliable until
> after 2.6.36-rc1; with problematic kernels, suspend seems to work OK
> (the machine goes to sleep with the moon LED steadily lit) but on resume
> the LCD never lights up (and it's not just the backlight, the screen
> isn't drawing at all) and the keyboard and network are dead.  Nothing
> makes it to syslog, either.  The moon LED is turned off though.
> 
> There seems to be some timing component to the problem -- some problem
> kernels will suspend reliably 25% or 50% of the time and hang the rest.
> There also seems to be some per-reboot state involved; one problem
> kernel suspended successfully and survived 25 suspends in a row without
> triggering a failure.  (But after a reboot, the first suspend hung...)
> Other problem kernels fail on 4 out of 4 reboots.
> 
> Bisecting is pretty hard under these conditions, but it seems to point
> to

Weird.  That's exactly the hardware that I tested RC6 on, and I haven't
seen a single resume failure on mine.  Sounds like time to revert for
this release.

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-09-07 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06  9:05 Andy Isaacson
2010-09-07 17:12 ` Eric Anholt [this message]
2010-09-07 17:37   ` Chris Wilson
2010-09-08  1:00     ` Zou, Nanhai
2010-09-08  2:38     ` Andy Isaacson
2010-09-08  6:47     ` Andy Isaacson

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=87fwxlbhq5.fsf@pollan.anholt.net \
    --to=eric@anholt.net \
    --cc=adi@hexapodia.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nanhai.zou@intel.com \
    /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®