From: Greg KH <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Azat Khuzhin <dohardgopro@gmail.com>,
linux-acpi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Feng Tang <feng.tang@intel.com>, Lv Zheng <lv.zheng@intel.com>,
Len Brown <lenb@kernel.org>,
"Moore, Robert" <robert.moore@intel.com>
Subject: Re: ACPI errors with 3.7-rc3
Date: Thu, 8 Nov 2012 05:47:15 +0100 [thread overview]
Message-ID: <20121108044715.GA12652@kroah.com> (raw)
In-Reply-To: <41011456.LYWJPCi9Xt@vostro.rjw.lan>
On Wed, Nov 07, 2012 at 10:49:40PM +0100, Rafael J. Wysocki wrote:
> On Tuesday, November 06, 2012 01:48:26 PM Greg KH wrote:
> > On Tue, Nov 06, 2012 at 04:42:24PM +0400, Azat Khuzhin wrote:
> > > I'v also have such errors on my macbook pro.
> > >
> > > $ dmesg | tail
> > > [17056.008564] ACPI Error: Method parse/execution failed
> > > [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff88026547ea10), AE_TIME
> > > (20120711/psparse-536)
> > > [17056.011194] ACPI Error: Method parse/execution failed
> > > [\_SB_.BAT0.UBST] (Node ffff88026547e678), AE_TIME
> > > (20120711/psparse-536)
> > > [17056.013793] ACPI Error: Method parse/execution failed
> > > [\_SB_.BAT0._BST] (Node ffff88026547e740), AE_TIME
> > > (20120711/psparse-536)
> > > [17056.016383] ACPI Exception: AE_TIME, Evaluating _BST (20120711/battery-464)
> > > [17056.511373] ACPI: EC: input buffer is not empty, aborting transaction
> > > [17056.512672] ACPI Exception: AE_TIME, Returned by Handler for
> > > [EmbeddedControl] (20120711/evregion-501)
> > > [17056.515256] ACPI Error: Method parse/execution failed
> > > [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff88026547ea10), AE_TIME
> > > (20120711/psparse-536)
> > > [17056.517886] ACPI Error: Method parse/execution failed
> > > [\_SB_.BAT0.UBST] (Node ffff88026547e678), AE_TIME
> > > (20120711/psparse-536)
> > > [17056.520479] ACPI Error: Method parse/execution failed
> > > [\_SB_.BAT0._BST] (Node ffff88026547e740), AE_TIME
> > > (20120711/psparse-536)
> > > [17056.523070] ACPI Exception: AE_TIME, Evaluating _BST (20120711/battery-464)
> >
> > I'm seeing this again right now. I'm wondering if it's because I'm
> > running on battery power at the moment:
> >
> > [41694.309264] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20120913/evregion-501)
> > [41694.309282] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff88045cc64618), AE_TIME (20120913/psparse-536)
> > [41694.309300] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff88045cc64988), AE_TIME (20120913/psparse-536)
> > [41694.309310] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff88045cc648c0), AE_TIME (20120913/psparse-536)
> > [41694.309324] ACPI Exception: AE_TIME, Evaluating _BST (20120913/battery-464)
> > [41694.809093] ACPI: EC: input buffer is not empty, aborting transaction
> >
> > ec_storm_threshold is still set to 8 in /sys/module/acpi/parameters/ so that's
> > not the issue here.
> >
> > > And also loadavg is too high ~ 10
> > > While there is no process that load CPU up to 100% or like that.
> > > I think that this because of processes that is done in kernel space.
> > > (basically that one who write such errors)
> > >
> > > $ uname -a
> > > Linux macbook-pro-sq 3.6.5macbook-pro-custom-v0.1 #4 SMP Sun Nov 4
> > > 12:39:03 UTC 2012 x86_64 GNU/Linux
> >
> > Ah, ok, that means it's not something new in 3.7-rc, so maybe it's just never
> > worked properly for this hardware :)
> >
> > So it's not a regression, just an ACPI issue, any ACPI developer have an idea
> > about this?
>
> Can you please send the output of acpidump from the affected machine(s)?
# ./acpidump
ACPI tables were not found. If you know location of RSD PTR table (from dmesg, etc), supply it with either --addr or -a option
What am I doing wrong here?
Is there a newer version of pmtools than the one labled pmtools-20071116
that I should be using? A link to download it would be appreciated.
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-08 4:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 1:45 ACPI errors with 3.7-rc3 Greg KH
2012-10-31 9:11 ` Rafael J. Wysocki
2012-10-31 17:33 ` Greg KH
2012-11-06 12:42 ` Azat Khuzhin
2012-11-06 12:48 ` Greg KH
2012-11-06 13:04 ` Azat Khuzhin
2012-11-07 21:49 ` Rafael J. Wysocki
2012-11-08 4:47 ` Greg KH [this message]
2012-11-08 9:15 ` Azat Khuzhin
2012-11-08 9:27 ` Rafael J. Wysocki
2013-01-26 12:23 ` Carlos R. Mafra
2013-01-26 13:23 ` Rafael J. Wysocki
2013-01-26 13:39 ` Carlos R. Mafra
2013-01-26 13:55 ` Rafael J. Wysocki
2013-01-26 21:23 ` Azat Khuzhin
2013-01-27 12:37 ` Carlos R. Mafra
2012-11-09 9:28 ` Feng Tang
2012-11-09 14:30 ` Moore, Robert
2012-11-09 16:36 ` Feng Tang
2012-11-09 16:45 ` Moore, Robert
2012-11-11 10:00 ` Azat Khuzhin
2012-11-13 0:41 ` Moore, Robert
2012-11-14 17:33 ` Azat Khuzhin
2012-11-17 5:40 ` Robert Hancock
2012-12-01 20:59 ` Azat Khuzhin
2012-12-01 21:54 ` Azat Khuzhin
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=20121108044715.GA12652@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dohardgopro@gmail.com \
--cc=feng.tang@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rjw@sisk.pl \
--cc=robert.moore@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;
as well as URLs for NNTP newsgroup(s).