public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: L A Walsh <law@sgi.com>
To: "mike@morpheus" <mike@morpheus.streamgroup.co.uk>
Cc: Linux-kernel@vger.kernel.org
Subject: Re: mysterious power off problem 2.4.10-2.4.14 on laptop
Date: Mon, 12 Nov 2001 13:06:33 -0800	[thread overview]
Message-ID: <3BF039D9.D75809F2@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111122227140.24454-100000@morpheus.streamgroup.co.uk>

"mike@morpheus" wrote:
> Give ACPI a try, for a while I've noticed APM getting mixed up
> on my home box (its a VIA chipset, I've been told that probably
> why :), doing things like not powering off and changing the instant-off
> powerbutton to a wait-5-seconds powerbutton.
> 
> I switched to ACPI and everythings been working fine :)
---
	Thanks for the suggestion.  However APM was working superbly for
my architecture in 2.4.9 and before.  It turned off the display when I
wasn't using it.  It occasionally spun down disks w/the help of noflushd,
and when suspend was indicated, it correctly suspended to RAM where it
can stay for hours using <1%/hour.  

	I did try ACPI at some point, but it didn't work as well in
providing the same features and reliability when I tested it.  The
config option says "Experimental", ACPI isn't a feature complete as
APM and ACPI was in development.  It might work differently on different
hardware, for example.  While it is to be the replacement for APM, I
don't know if I am comfortable moving to it yet -- and even so, why should
APM mysteriously break when it has been working great since the early 
2.4 series and fairly well since 2.2 (X was a problem on my hardware at one
point).

	I'd prefer not to try an unknown, where if I have a problem, I
don't know if it is my hardware, a misconfiguration on my part, or the
Experimental Hardware.  That would likely take more time than simply
staying with APM -- a known 'working configuration', and finding what
changed in 2.4.10 (and remains in 2.4.14) that lead to the new problems.

	If it worked before, then something changed in the kernel to
break it, I'd generally classify that as a bug.  Now maybe there
are new utilities needed -- however, in SuSE 7.3, they use the 2.4.10
kernel and their default setup has the same problem.

:-(
-linda

  reply	other threads:[~2001-11-12 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 19:53 mysterious power off problem 2.4.10-2.4.14 on laptop L A Walsh
2001-11-12 22:29 ` mike@morpheus
2001-11-12 21:06   ` L A Walsh [this message]
2001-11-14  0:10     ` Pavel Machek
2001-11-13  0:34   ` Stuart Young
  -- strict thread matches above, loose matches on Subject: below --
2001-11-12 22:28 Thomas Winischhofer

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=3BF039D9.D75809F2@sgi.com \
    --to=law@sgi.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=mike@morpheus.streamgroup.co.uk \
    /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