public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: bgamari.foss@gmail.com
Subject: (no subject)
Date: Tue, 20 Apr 2010 19:00:56 -0700	[thread overview]
Message-ID: <201004210200.o3L20uTU016700@smtp1.linux-foundation.org> (raw)

>From nobody Tue Apr 20 22:00:38 2010
From: Ben Gamari <bgamari.foss@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [REGRESSION 2.6.34] Suspend fails in pm_test=processor on Dell
	laptop
In-Reply-To: <201004200533.13219.rjw@sisk.pl>
References: <4bcb1cf2.116bdc0a.2008.6f5a@mx.google.com>
	<201004200533.13219.rjw@sisk.pl>
Date: Tue, 20 Apr 2010 15:11:52 -0400
Message-ID: <87633mey6f.fsf@ben-laptop.i-did-not-set--mail-host-address--so-tickle-me>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Tue, 20 Apr 2010 05:33:13 +0200, "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> On Sunday 18 April 2010, Ben Gamari wrote:
[snip]
> > It seems that something in the 2.6.34 merge cycle has broken suspend to RAM on
> > my Dell Latitude D830. While suspend has been rock solid for several release
> > cycles, as of 2.6.34-rc4 it locks up on suspend. All of the pm_test options up
> > to processor work fine, precluding a driver issue.
> 
> Hmm, does the "processors" work?

Nope. Processors is the first failing phase.

I'm still working on getting a bisection, but it'll be a few more days
due to various school-related delays.

- Ben

             reply	other threads:[~2010-04-21  2:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  2:00 bgamari.foss [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-17 12:36 (no subject) xuluqxulu
     [not found] <BLU102-W1030ED196ED7B94722F2A7EB830@phx.gbl>
     [not found] ` <Pine.LNX.4.44L0.1008241029000.1652-100000@iolanthe.rowland.org>
2010-08-24 15:17   ` Runtime power management during system resume Raj Kumar
2010-08-25 13:27     ` Raj Kumar
2010-08-26 13:40       ` Raj Kumar
2010-09-18 11:49         ` (no subject) Raj Kumar
2009-06-11 22:44 Rafael J. Wysocki
2009-06-11 21:48 Rafael J. Wysocki
2007-07-30  7:24 Trujillo
2007-07-29  0:46 Smartschan
2007-07-27 16:05 Agatha C. Walter
2007-07-21 23:57 Mathilda S. Corbett
2007-07-20  4:13 Palmer
2007-04-11 13:13 Jojo Keiser
2007-04-08 10:40 Maung Nadir Ali
2007-01-31 19:06 operators country
2006-06-22  8:46 legwpjv
2006-06-17 12:56 cycrypxz
2006-06-15  5:07 icjoqtc
2006-04-26  2:23 Nichole
2006-02-21 12:41 rasmit.ranjan

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=201004210200.o3L20uTU016700@smtp1.linux-foundation.org \
    --to=bgamari.foss@gmail.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