From: Russell Neches <russell-1vnkWVZi4QaVc3sceRu5cw@public.gmane.org>
To: ACPI-Devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: power-off on boot
Date: Sat, 24 Jul 2004 21:57:31 -0400 [thread overview]
Message-ID: <1090720651.3519.6.camel@localhost> (raw)
In-Reply-To: <1090363093.6236.27.camel-vxk6yBcOqypfHeH+O4PpjYdd74u8MsAO@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2645 bytes --]
Well, I seem to have found a work-around for this problem, but it raises
another question. The work around was to build the ACPI extensions (AC
Adapter, Battery, Button, Fan...) as modules. The culprit, I'm sure, was
Thermal Zone.
On my laptop, I have all of them built-in, and this problem doesn't
occur. Do ACPI extensions always have to be built as a module? Is it not
*supposed* to work at boot-time? The Debian boot-scripts seem to assume
that they will be built as modules...
Russell
On Tue, 2004-07-20 at 18:38, Russell Y. Neches wrote:
> Hey there --
>
> I have an "interesting" behavior with 2.6.6 and 2.6.7, and I was
> wondering if this list would mind helping me figure out what's causing
> it.
>
> Basically, my machine turns off while it's booting. It doesn't get far
> enough to mount any filesystems, so there aren't any logs. On a hunch, I
> turned on ACPI-debugging, and noticed that the kernel immediately begins
> spewing warnings about a critical trap (that's from memory, I can't be
> completely sure if that's literally the string), and that the CPU is
> over 120 degrees C. Now, I'm actually *underclocking* my CPU because I
> have very bad luck with hardware, and I happen to know that the
> temperature never goes above 38 degrees C (according to my BIOS and the
> hardware meter glued to the heat sync).
>
> 2.6.5 doesn't seem to have this problem (USB-related oopses
> notwithstanding), and Debian's 2.6.7-1-k7 kernel package boots without
> issue (Debian's module insanity notwithstanding). So, I know there is a
> solution to the problem somewhere, but without logs, I'm not sure how to
> even begin researching it.
>
> If it weren't for the fact that there are recent ACPI-enabled kernels
> that work fine, I'd guess that my motherboard has a broken DSTD.
>
> Would anyone mind orienting me and pointing me in the right direction?
>
> Thanks!
>
> Russell
>
> PS - The list moderator hasn't approved a previous email with some
> system information attached. So, instead of attaching it, I'll just link
> to it:
>
> http://vort.org/downloads/spew.txt
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-25 1:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 22:38 power-off on boot Russell Y. Neches
[not found] ` <1090363093.6236.27.camel-vxk6yBcOqypfHeH+O4PpjYdd74u8MsAO@public.gmane.org>
2004-07-25 1:57 ` Russell Neches [this message]
[not found] ` <1090720651.3519.6.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-07-25 2:23 ` Russell Neches
-- strict thread matches above, loose matches on Subject: below --
2004-07-18 5:44 Russell Neches
2004-08-09 14:04 ` 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=1090720651.3519.6.camel@localhost \
--to=russell-1vnkwvzi4qavc3sceru5cw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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