From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: bbpetkov@yahoo.de
Cc: Andrew Morton <akpm@linux-foundation.org>,
len.brown@intel.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc4-mm1: acpi reboots machine... solved
Date: Tue, 11 Dec 2007 17:08:59 -0700 [thread overview]
Message-ID: <200712111709.00313.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20071211205255.GB5013@gollum.tnic>
On Tuesday 11 December 2007 01:52:55 pm Borislav Petkov wrote:
> From what i can roughly tell so far it seems like an resource conflict between acpi and
> the pnp requested regions in your patch which result in the acpi_thermal code
> to read the wrong (0xff) temperature value and halt the machine, but i might be
> wrong on the details since acpi is such a big code chunk to swallow.
I don't see any obvious conflict from the log you posted. For the sake
of comparison, can you post the corresponding dmesg log after you removed
the patch?
acpi_thermal_get_temperature() only evaluates _TMP, which isn't very
interesting. I wonder if there's some conflict between that AML method
and the EC driver or something.
If you can also collect the DSDT, maybe I can poke around in there and
see what _TMP is really doing.
Thanks,
Bjorn
next prev parent reply other threads:[~2007-12-12 0:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 7:50 2.6.24-rc4-mm1: acpi reboots machine Borislav Petkov
2007-12-09 9:19 ` Borislav Petkov
2007-12-11 17:44 ` 2.6.24-rc4-mm1: acpi reboots machine... solved Borislav Petkov
2007-12-11 20:00 ` Bjorn Helgaas
2007-12-11 20:52 ` Borislav Petkov
2007-12-12 0:08 ` Bjorn Helgaas [this message]
2007-12-12 10:11 ` Borislav Petkov
2007-12-12 10:38 ` Alexey Starikovskiy
2007-12-12 16:21 ` Bjorn Helgaas
2007-12-13 7:09 ` Borislav Petkov
2007-12-13 16:17 ` Bjorn Helgaas
2007-12-13 21:29 ` Borislav Petkov
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=200712111709.00313.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=akpm@linux-foundation.org \
--cc=bbpetkov@yahoo.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--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