All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: James Hogan <james@albanarts.com>
Cc: Len Brown <len.brown@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	ACPI Devel Mailing List <linux-acpi@gver.kernel.org>,
	Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: 2.6.38-rc1 resume hang (da8aeb92 "ACPI/Battery: Update information on info notification and resume")
Date: Fri, 21 Jan 2011 21:30:26 +0100	[thread overview]
Message-ID: <201101212130.26693.rjw@sisk.pl> (raw)
In-Reply-To: <20110121140031.GA3280@gandalf>

On Friday, January 21, 2011, James Hogan wrote:
> Hi,
> 
> After updating from 2.6.37 to 2.6.28-rc1, resume from suspend is broken
> on my Dell M1210 Laptop.
> 
> I tried pm_trace and both block and battery matched the hash, so I
> bisected the problem to commit da8aeb92 (see below).
> 
> I've reverted this commit on 2.6.38 and it doesn't die on resume anymore.
> 
> My bisection log and .config are pasted below.
> 
> Let me know if I can provide any more info or help test any patches etc.

This should have been fixed already in the current Linus' tree by this commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b23fffd778c312b8fb258d342051fcbdf6712128

Can you verify, please?

Rafael

  parent reply	other threads:[~2011-01-21 20:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 14:25 2.6.38-rc1 resume hang (da8aeb92 "ACPI/Battery: Update information on info notification and resume") James Hogan
2011-01-21 14:29 ` James Hogan
2011-01-21 14:29 ` James Hogan
2011-01-21 20:30 ` Rafael J. Wysocki
2011-01-21 20:30 ` Rafael J. Wysocki [this message]
2011-01-21 21:20   ` James Hogan
2011-01-21 21:20   ` James Hogan
2011-01-21 14:25 James Hogan

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=201101212130.26693.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=james@albanarts.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@gver.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.