public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mike Travis <travis@sgi.com>
Cc: Pavel Machek <pavel@suse.cz>,
	Jeff Chua <jeff.chua.linux@gmail.com>,
	kernel list <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: 2.6.29-rc1: thinkpad problems during resume
Date: Sat, 17 Jan 2009 01:13:09 +0100	[thread overview]
Message-ID: <200901170113.09724.rjw@sisk.pl> (raw)
In-Reply-To: <49711EBC.5050101@sgi.com>

On Saturday 17 January 2009, Mike Travis wrote:
> Rafael J. Wysocki wrote:
> > On Friday 16 January 2009, Pavel Machek wrote:
> >> On Tue 2009-01-13 23:21:17, Jeff Chua wrote:
> >>> On Tue, Jan 13, 2009 at 10:36 PM, Pavel Machek <pavel@suse.cz> wrote:
> >>>> resumes fine with CONFIG_SMP unset.
> >>> On my X60s, I had problem with s2ram, and I switch to the following ...
> >>>
> >>> echo mem > /sys/power/state
> >>>
> >>> Try and see if it works for you.
> >> I tried that; unlike s2ram, this actually produces some oopses that
> >> can be viewed. Unfortunately, they scroll a bit too fast.
> >>
> >> cpu hotplug vs. cpufreq seems to be responsible in my case, looking at
> >> the logs from "echo 1 > online".
> > 
> > There are three patches from Mike Travis that can help:
> > http://lkml.org/lkml/2009/1/16/377
> > 
> > Thanks,
> > Rafael
> 
> Note that these don't really fix anything, just replaces the current
> method of using set_cpus_allowed with the work_on_cpu call.  If
> the laptop worked before the [bad] patch, then it should work again
> now with this one.

Thanks for the clarification, I misread the changelogs.

OK, so we still have a cpufreq vs CPU hotplug problem, it seems.  I can't
reproduce it myself, though.

Thanks,
Rafael

  reply	other threads:[~2009-01-17  0:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  8:13 2.6.29-rc1: thinkpad problems during resume Pavel Machek
2009-01-13 11:39 ` Rafael J. Wysocki
2009-01-13 12:42   ` Christian Borntraeger
2009-01-13 13:03     ` AW: " Morten P.D. Stevens
2009-01-13 13:28     ` Pavel Machek
2009-01-13 13:33       ` Jeff Chua
2009-01-16 10:44         ` Pavel Machek
2009-01-16 13:23           ` Jeff Chua
2009-01-17 14:46           ` Christian Borntraeger
2009-01-17 15:48             ` 2.6.29-rc1: [SOLVED] " Christian Borntraeger
2009-01-17 16:49               ` Maciej Rutecki
2009-01-17 19:48               ` Mike Travis
2009-01-17 23:42                 ` Christian Borntraeger
2009-01-19 16:59                   ` Mike Travis
2009-01-19 17:09                     ` Ingo Molnar
2009-01-13 13:05   ` 2.6.29-rc1: " Pavel Machek
2009-01-13 14:06     ` Rafael J. Wysocki
2009-01-13 14:36       ` Pavel Machek
2009-01-13 14:36 ` Pavel Machek
2009-01-13 15:21   ` Jeff Chua
2009-01-16 14:39     ` Pavel Machek
2009-01-16 22:06       ` Rafael J. Wysocki
2009-01-16 23:56         ` Mike Travis
2009-01-17  0:13           ` Rafael J. Wysocki [this message]
2009-01-26 15:44             ` Pavel Machek
2009-01-26 16:40               ` Rafael J. Wysocki

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=200901170113.09724.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=hpa@zytor.com \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=travis@sgi.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