All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: Ottawa Linux Power Management Summit, June 25-26, 2007 - Minutes
Date: Tue, 25 Sep 2007 14:00:41 +0200	[thread overview]
Message-ID: <1190721641.4035.311.camel@chaos> (raw)
In-Reply-To: <200709251339.37601.rjw@sisk.pl>

On Tue, 2007-09-25 at 13:39 +0200, Rafael J. Wysocki wrote:
> On Monday, 24 September 2007 21:41, Dave Jones wrote:
> > On Sun, Sep 09, 2007 at 02:26:39PM +0200, Rafael J. Wysocki wrote:
> > 
> >  > > Dave mentioned that Fedora Core 7 32-bit is now shipping with
> >  > > CONFIG_NOHZ=y and CONFIG_HZ=1000.
> >  > 
> >  > CONFIG_NOHZ is known to break suspend and resume on some machines.  These
> >  > problems are being fixed over time, but that's a risky decision for a
> >  > distribution to switch it on by default.
> > 
> > Expect to see everyone else doing the same thing in the next versions.
> > Without field-testing this stuff it remains busted.  A lot of bugs got
> > found and fixed by having this in Fedora that weren't tripped over
> > by linux-kernel testers at all.
> 
> Well, that's certainly true.
> 
> Still, we have open suspend bugs in which NO_HZ appears to be the culprit,
> eg. http://bugzilla.kernel.org/show_bug.cgi?id=8680

Grr, kernel.org bugzilla is down. I take a look later.

Btw. I got an interesting private response to the latest ACPI fixes:

> >    ACPI: disable lower idle C-states across suspend/resume
> > 
> > Finally, the weird suspend/resume behavior of my Dell-420 laptop has
> > disapeared (no way to adjust brightness after a suspend when not in the
> > docking station). It was always dark after a resume and made the laptop
> > unuseable in practice.
> 
> I cheered too early:
> I just discovered that suspending to ram works well for the first time,
> but after that it's still the same problem. Suspend to disk always
> worked well btw. But somehow there is a difference now: when switching
> to a normal console (ctrl-alt-F1 e.g.) and switching back to X the
> brightness works again. Another thing: I now can also suspend *in* the
> docking station, take it *out* and resume without problems, which never
> worked before :)

Len, did you / Venki look into a similar solution for cpuidle yet ? I'd
like to update -hrt ASAP. If not I just hack it in for now.

	tglx

  reply	other threads:[~2007-09-25 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05  8:26 Ottawa Linux Power Management Summit, June 25-26, 2007 - Minutes Len Brown
2007-09-09 12:26 ` Rafael J. Wysocki
2007-09-24 19:41   ` Dave Jones
2007-09-25 11:39     ` Rafael J. Wysocki
2007-09-25 12:00       ` Thomas Gleixner [this message]
2007-10-28 13:54 ` cpufreq-set problems [Was: Re: Ottawa Linux Power Management Summit, June 25-26, 2007 - Minutes] Dominik Brodowski
2007-10-29 13:26   ` Igor Stoppa

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=1190721641.4035.311.camel@chaos \
    --to=tglx@linutronix.de \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    /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.