All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Dave Jones <davej@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux PM List <linux-pm@lists.linux-foundation.org>,
	Thomas Renninger <trenn@suse.de>
Subject: Re: [Regression] Hibernation failure on dual core Athlon 64 (64-bit)
Date: Tue, 4 Aug 2009 18:27:37 +0200	[thread overview]
Message-ID: <200908041827.38547.rjw@sisk.pl> (raw)
In-Reply-To: <20090803222359.GA3770@Krystal>

On Tuesday 04 August 2009, Mathieu Desnoyers wrote:
> * Rafael J. Wysocki (rjw@sisk.pl) wrote:
> > Hi Mathieu,
> > 
> > As reported at
> > 
> > http://bugzilla.kernel.org/show_bug.cgi?id=13903
> > 
> > one of my test systems suffers from a hibernation regression where the second
> > attempt to hibernate in a row makes it hang solid right before creating the
> > image.
> > 
> > Bisection turned up your commit 3f4a782b5ce2698b1870b5a7b573cd721d4fce33
> > ([CPUFREQ] fix (utter) cpufreq_add_dev mess) as the first bad one.
> > 
> 
> Can you try with the following patch applied ?
>
> http://www.spinics.net/lists/cpufreq/msg00964.html
>
> Subject: [PATCH 1/5] CPUFREQ: Fix a kobject reference bug related to managed CPUs
> From: Thomas Renninger <trenn@suse.de>

Tested (/me hates mailing list archives where you can't download raw messages
or at least raw patches) and it works.
 
Thanks a lot,
Rafael

      parent reply	other threads:[~2009-08-04 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03 21:03 [Regression] Hibernation failure on dual core Athlon 64 (64-bit) Rafael J. Wysocki
2009-08-03 21:03 ` Rafael J. Wysocki
2009-08-03 22:23 ` Mathieu Desnoyers
2009-08-03 22:23 ` Mathieu Desnoyers
2009-08-04 16:27   ` Rafael J. Wysocki
2009-08-04 16:27   ` Rafael J. Wysocki [this message]

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=200908041827.38547.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=trenn@suse.de \
    /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.