From: Zhang Rui <rui.zhang@intel.com>
To: "rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Renninger <trenn@suse.de>,
"clarkt@cnsp.com" <clarkt@cnsp.com>,
"Brown, Len" <len.brown@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [BUG] kacpi_notify goes into an infinite loop (luckly it calls cond_resched)
Date: Mon, 31 May 2010 10:57:50 +0800 [thread overview]
Message-ID: <1275274670.9119.4419.camel@rzhang1-desktop> (raw)
In-Reply-To: <1275094882.22648.607.camel@gandalf.stny.rr.com>
Hi, Steve,
On Sat, 2010-05-29 at 09:01 +0800, Steven Rostedt wrote:
> I just replaced Windows with F12 on my wife's computer, to have nothing
> but issues. But anyway, one of the issues I had on this box was in
> vanilla linux kernel 2.6.34 (all the fedora kernels had other issues),
> the kacpi_notify would go into an infinite loop.
>
> I debugged it a bit with ftrace and saw that the kacpi_notify workqueue
> was constantly requeuing itself (thanks to the workqueue trace events).
>
> I bisected this, and it came down to this change:
>
> commit fa80945269f312bc609e8384302f58b03c916e12
> Author: Thomas Renninger <trenn@suse.de>
> Date: Sat Feb 20 11:44:27 2010 +0100
>
> ACPI thermal: Don't invalidate thermal zone if critical trip point is bad
>
>
This patch enables the ACPI thermal control which is used to be disabled
on some laptops.
Maybe this triggers an interrupt storm on this box.
please attach the output of "grep . /sys/firmware/acpi/interrupts/*".
please attach the acpidump output of your laptop as well.
thanks,
rui
next prev parent reply other threads:[~2010-05-31 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 1:01 Steven Rostedt
2010-05-31 2:57 ` Zhang Rui [this message]
2010-06-30 13:40 ` Steven Rostedt
2010-06-30 15:17 ` Len Brown
2010-06-30 16:06 ` Steven Rostedt
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=1275274670.9119.4419.camel@rzhang1-desktop \
--to=rui.zhang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=clarkt@cnsp.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=trenn@suse.de \
/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
all inboxes | Powered by JetHome®