public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Németh Márton" <nm127@freemail.hu>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"lenb@kernel.org" <lenb@kernel.org>
Subject: Re: AE_ERROR, ACPI thermal trip point state changed
Date: Mon, 08 Dec 2008 07:59:24 +0100	[thread overview]
Message-ID: <493CC5CC.70309@freemail.hu> (raw)
In-Reply-To: <1228718909.7929.133.camel@rzhang-dt>

Zhang Rui wrote:
> On Mon, 2008-12-08 at 14:04 +0800, Németh Márton wrote:
>> Andi Kleen wrote:
>>> On Wed, Nov 19, 2008 at 11:20:17PM +0100, Németh Márton wrote:
>>>> Hi,
>>>>
>>>> Andi Kleen wrote:
>>>>> Németh Márton <nm127@freemail.hu> writes:
>>>>>> As of 2.6.27-rc3 the patch is still not included in the mainstream. I
>>>>>> hope that this patch was not forgotten completely.
>>>>> It's already in Linus' tree, will be in rc4.
>>>> I compiled and tried 2.6.28-rc5. In the dmesg I get the following message:
>>>>
>>>> [   63.589603] ACPI Exception (thermal-0538): AE_ERROR, ACPI thermal trip point state changed
>>>> [   63.589669] Please send acpidump to linux-acpi@vger.kernel.org
>>>> [   63.589805]  [20080926]
>>>>
>>>> The original patch still applies for 2.6.28-rc5 (with some offsets). This patch
>>>> is not included in 2.6.28-rc5, yet. The "AE_ERROR..." message does not appear
>>>> any more if I apply the patch. I attached this original patch for easier reference.
>>> Hmm sorry I must have confused it with some other patch back then.
>>> Anyways Len Brown is handling ACPI again now, so he'll have to sort
>>> it out. cc'ed (the original patch is on linux-acpi)
>> This is just a status report about 2.6.28-rc7, nothing more. The AE_ERROR
>> message is still in the dmesg. The patch still solves the problem.
>>
> do you mean this patch:
> http://marc.info/?l=linux-acpi&m=120522267418715&w=2

Yes, exactly.

	Márton Németh


  reply	other threads:[~2008-12-08  6:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47B328AA.1000800@freemail.hu>
     [not found] ` <47B3F147.7000704@freemail.hu>
2008-03-06  7:01   ` AE_ERROR, ACPI thermal trip point state changed Németh Márton
2008-03-05 22:49     ` Zhang, Rui
2008-03-06  8:05       ` Zhang, Rui
2008-03-07  6:54         ` Németh Márton
2008-03-07  7:19           ` Zhang, Rui
2008-03-07  7:24           ` Zhang, Rui
2008-03-08  7:41             ` Németh Márton
2008-03-10  1:52               ` Zhang, Rui
2008-08-20  9:08                 ` Németh Márton
2008-08-20 10:02                   ` Andi Kleen
2008-11-19 22:20                     ` Németh Márton
2008-11-19 23:22                       ` Andi Kleen
2008-12-08  6:04                         ` Németh Márton
2008-12-08  6:48                           ` Zhang Rui
2008-12-08  6:59                             ` Németh Márton [this message]
2009-01-05  6:22                               ` Németh Márton
2009-01-15 21:56                   ` Len Brown

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=493CC5CC.70309@freemail.hu \
    --to=nm127@freemail.hu \
    --cc=andi@firstfloor.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@intel.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