mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stuart Young <sgy@amc.com.au>
To: Linux-kernel@vger.kernel.org
Cc: L A Walsh <law@sgi.com>
Subject: Re: mysterious power off problem 2.4.10-2.4.14 on laptop
Date: Tue, 13 Nov 2001 11:34:05 +1100	[thread overview]
Message-ID: <5.1.0.14.0.20011113112416.00a1e570@mail.amc.localnet> (raw)
In-Reply-To: <3BF039D9.D75809F2@sgi.com>
In-Reply-To: <Pine.LNX.4.33.0111122227140.24454-100000@morpheus.streamgroup.co.uk>

At 01:06 PM 12/11/01 -0800, L A Walsh wrote:
>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.

There was mention recently about some changes to APM to fix some "broken" 
behavior regarding the way it set/reset values. Some of these were cases 
where APM seemed to blindly set values instead of leaving them as is. I 
don't remember just how long ago, but you might try looking over the archives.

If this is the case, then it's possible that the APM code was checking 
status, and then blindly setting things to suit that status instead of what 
was read. Makes sense, but potentially broken. If the BIOS is broken and 
doesn't set these values correctly, then this could produce the symptoms 
you describe. Check for a BIOS upgrade anyway - usually a good manufacturer 
will have some sort of changelog with the BIOS, so if there is a new 
version, you might find APM was broken and fixed.

It's also possible that this never made it into those kernels, and they've 
been using the broken behavior since 2.4.10 which is causing your problems. 
I'd also suggest checking out the latest of the 2.4.14pre* kernels. My 
memory of the list (I may be wrong) makes me think the discussion was quite 
recent.

Good luck.

AMC Enterprises P/L    - Stuart Young
First Floor            - Network and Systems Admin
3 Chesterville Rd      - sgy@amc.com.au
Cheltenham Vic 3192    - Ph:  (03) 9584-2700
http://www.amc.com.au/ - Fax: (03) 9584-2755


  parent reply	other threads:[~2001-11-13  0:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12 19:53 L A Walsh
2001-11-12 22:29 ` mike@morpheus
2001-11-12 21:06   ` L A Walsh
2001-11-14  0:10     ` Pavel Machek
2001-11-13  0:34   ` Stuart Young [this message]
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=5.1.0.14.0.20011113112416.00a1e570@mail.amc.localnet \
    --to=sgy@amc.com.au \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=law@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

all inboxes | Powered by JetHome®