public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: mru-UNjuZkX4dYU@public.gmane.org (Måns Rullgård)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Tell user when ACPI is killing machine
Date: Thu, 04 Dec 2003 12:24:16 +0100	[thread overview]
Message-ID: <yw1x8ylsltb3.fsf@kth.se> (raw)
In-Reply-To: 20031204105621.GE11044@atrey.karlin.mff.cuni.cz

Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org> writes:

>> I have a similar problem since test10 and test11 (2.4.23 is ok, test9 is
>> ok too). ACPI reports bogus temperatures and powers the machine
>> down.
>
>> If you have a patch that could fix that problem, I'm ready to try it and
>> report success or failure ;)
>
> I have ugly workaround ("if temperature reported is > 200Celsius,
> ignore it").

I'm just curious, are these (and other ACPI related) problems caused
by bugs in Linux, or by hardware/firmware bugs?

-- 
Måns Rullgård
mru-UNjuZkX4dYU@public.gmane.org



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

  reply	other threads:[~2003-12-04 11:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04  5:27 Tell user when ACPI is killing machine Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720BFD-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-04  9:54   ` Pavel Machek
     [not found]     ` <20031204095454.GC6911-jyMamyUUXNJG4ohzP4jBZS1Fcj925eT/@public.gmane.org>
2003-12-04 10:01       ` Damien Sandras
     [not found]         ` <1070532076.1645.42.camel-yzJ1TzNew8IqMp+WYRx65w@public.gmane.org>
2003-12-04 10:56           ` Pavel Machek
2003-12-04 11:24             ` Måns Rullgård [this message]
     [not found]               ` <yw1x8ylsltb3.fsf-UNjuZkX4dYU@public.gmane.org>
2003-12-06 11:14                 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2003-12-08  3:26 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C05-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-09 11:25   ` Pavel Machek
2003-11-28 14:55 Pavel Machek
     [not found] ` <20031128145558.GA576-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2003-11-28 16:52   ` Pavel Machek
2003-11-28 22:01 ` Aaron Lehmann
2003-11-28 23:43   ` 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=yw1x8ylsltb3.fsf@kth.se \
    --to=mru-unjuzkx4dyu@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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