public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Disconnect <lkml@sigkill.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Laptops & CPU frequency
Date: Mon, 12 Jan 2004 15:11:11 -0500	[thread overview]
Message-ID: <1073938271.2156.10.camel@slappy> (raw)
In-Reply-To: <1073937159.28098.46.camel@cog.beaverton.ibm.com>

On Mon, 2004-01-12 at 14:52, john stultz wrote:
> More info please. What type of hardware is this?  Could you send me your
> dmesg for booting both with and without AC power? 

I had a similar problem with 2.4 (with and without acpi, speedstep, etc)
on an Inspiron 8500.  Unfortunately, Dell only gives "use speedstep"
(boot in powersave on battery, performance on ac)  and "always in lowest
performance mode" options in the bios.  (Dell, you listening? How about
"don't use speedstep, only use [powersave/performance] mode"? Or "Boot
in last-used mode"..)

When the machine is suspended (swsusp) while on AC, it must be resumed
on AC (and same if suspended on battery) or the kernel gets very
confused.  Time doubles (or halves), etc.  No amount of arguing with
speedstep (or acpi in general, if speedstep wasn't applied/used) will
get it sane.  (FWIW XP gets this right - hibernate XP on battery, resume
on ac, hibernate, resume on battery, etc and it does fine.)

Perhaps linux would benefit from some form of "make sure the cpu is
doing what we think it is" knob?  Something that could be triggered by
scripts (or even swsusp/apm directly) as early in a resume as possible,
before the miscalculation cascades into crashes.  (This would be
completely independent from speedstep or acpi, since I suspect that the
same problems may occur independently of acpi on other machines with
similar braindamaged bios.)

Thoughts?  I can do more rigorous testing and report back if needed.  (I
spent 2 days playing with it a few months ago, then gave it up as
hopeless.)

-- 
Disconnect <lkml@sigkill.net>


  reply	other threads:[~2004-01-12 20:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11  2:56 Laptops & CPU frequency jlnance
2004-01-11  3:17 ` Robert Love
2004-01-11  4:12   ` Valdis.Kletnieks
2004-01-11  6:16   ` Willy Tarreau
2004-01-11 10:27   ` Xavier Bestel
2004-01-11 10:33     ` Xavier Bestel
2004-01-12 16:58       ` Jerry Cooperstein
2004-01-12 21:19         ` Xavier Bestel
2004-01-12 19:52       ` john stultz
2004-01-12 20:11         ` Disconnect [this message]
2004-01-12 23:19           ` john stultz
2004-01-12 21:28         ` Xavier Bestel
2004-01-12 22:07           ` john stultz
2004-01-13  9:13             ` Xavier Bestel
2004-01-11 17:06   ` Matthew Garrett
2004-01-11 17:13     ` Robert Love
2004-01-11 17:44       ` Matthew Garrett
2004-01-11 17:54         ` Robert Love
2004-01-14  4:59           ` Dave Jones
2004-01-14 19:11             ` Daniel Gryniewicz
2004-01-14 19:17               ` Robert Love
2004-01-14 19:23                 ` Daniel Gryniewicz
2004-01-15 20:42                 ` Pavel Machek
2004-01-15 21:18                   ` Daniel Gryniewicz
2004-01-15 22:21                   ` John Bradford
2004-01-15 22:48                     ` Pavel Machek
2004-01-19 17:44             ` Ducrot Bruno
2004-01-16 10:47         ` Pavel Machek

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=1073938271.2156.10.camel@slappy \
    --to=lkml@sigkill.net \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox