From: L A Walsh <law@sgi.com>
To: Linux-kernel@vger.kernel.org
Subject: mysterious power off problem 2.4.10-2.4.14 on laptop
Date: Mon, 12 Nov 2001 11:53:56 -0800 [thread overview]
Message-ID: <3BF028D4.C131A42D@sgi.com> (raw)
I haven't had time to track this down since I found it. I'm throwing
it out in case anyone has seen anything that might figure in to this.
Machine: Dell Inspiron 8000.
Problem: using same options, (starting with 249.config, and using make oldconfig
for new kernel version), I get a kernel that has a bad habit of turning
itself off after some period of time -- not shutting down, just turning off.
This started in 2.4.10 and, and not having the time to debug it, I just
went back to using 2.4.9 which didn't exhibit the problem.
Things tried that haven't worked (not necessarily in any particular order)
1) 2.4.14 kernel
2) disabling power management from the KDE desktop.
3) renaming the apm binary would allow apm control.
4) Turning off apm support in the kernel.
5) Turning off BIOS apm management completely.
a) BIOS PM on AC-power was set to
i) turn off inactive video in 10 minutes
ii) turn off inactive hard disk in 30 minutes
iii) Suspend: disabled.
iv) S2D Timeout: disabled
b) BIOS PM on battery still _is_ set to
i) turn off inactive video in 3 minutes
ii) turn off in hard disks in 5 minutes
iii) Suspend: disabled
iv) S2D Timeout: 1 hour
common options:
v) Smart CPU: enabled
vi) Display lid closed: <don't shut down, remain active>
vii) all auto 'wake'/'resume' (on lan, alarm, ring, at time)
disabled
viii) CPU Mode: Battery Optimized
----
Other details:
1) I noticed when the machine was on battery -- it turned off in about
3 minutes -- it might have been 5, but seemed closer to 3. I note this
coincides with the Video timeout. Previously when the timeout
would occur on AC power -- it seemed that the inactivity timeout was
about 10 minutes. My estimations may be wrong, but part of the problem
could be related to the video timeout.
2) testing this problem is a pain, since my disks are still the
primitive 'ext2' file system and the multi-gig, laptop-speed disks
are slow to check.
So am just wondering if someone has seen this, or its a known 'feature change'
with the workaround or solution being 'X'.
I note in the changelog that ACPI changes went into 2.4.10. I am still using
APM, not ACPI, but it it possible there is common code to both that got
changed?
Thanks for any help.
-linda
next reply other threads:[~2001-11-12 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 19:53 L A Walsh [this message]
2001-11-12 22:29 ` mysterious power off problem 2.4.10-2.4.14 on laptop mike@morpheus
2001-11-12 21:06 ` L A Walsh
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=3BF028D4.C131A42D@sgi.com \
--to=law@sgi.com \
--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