From: Greg KH <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: ACPI errors with 3.7-rc3
Date: Wed, 31 Oct 2012 10:33:36 -0700 [thread overview]
Message-ID: <20121031173336.GA28991@kroah.com> (raw)
In-Reply-To: <2089727.VKpW8oC7hj@vostro.rjw.lan>
On Wed, Oct 31, 2012 at 10:11:21AM +0100, Rafael J. Wysocki wrote:
> Hi Greg,
>
> On Tuesday, October 30, 2012 06:45:27 PM Greg KH wrote:
> > Hi Len and Rafael,
> >
> > With 3.7-rc3, I'm seeing a constant stream of these errors in the kernel
> > log for my MacBook Pro:
> >
> > [30443.430133] ACPI: EC: input buffer is not empty, aborting transaction
> > [30443.430145] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20120913/evregion-501)
> > [30443.430162] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff88045cc64618), AE_TIME (20120913/psparse-536)
> > [30443.430179] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff88045cc64988), AE_TIME (20120913/psparse-536)
> > [30443.430188] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff88045cc648c0), AE_TIME (20120913/psparse-536)
> > [30443.430202] ACPI Exception: AE_TIME, Evaluating _BST (20120913/battery-464)
> >
> > They never showed up before in 3.7-rc2.
> >
> > Anything I should try out to resolve this?
>
> Well, there are the following two post-3.6 EC-related commits:
>
> commit 67bfa9b60bd689601554526d144b21d529f78a09
> Author: Feng Tang <feng.tang@intel.com>
> Date: Fri Sep 28 15:22:01 2012 +0800
>
> ACPI: EC: Add a quirk for CLEVO M720T/M730T laptop
>
> commit a520d52e99b14ba7db135e916348f12f2a6e09be
> Author: Feng Tang <feng.tang@intel.com>
> Date: Fri Sep 28 15:22:00 2012 +0800
>
> ACPI: EC: Make the GPE storm threshold a module parameter
>
> Can you please check if reverting the second one helps?
That last one seems like it would be it, if the module parameter got
changed. And now I can't duplicate it at all, 3.7-rc3 works fine. Ick,
sorry for the noise, I don't know what happened. If I see the above
errors again, I'll let you know, and I'll also check the ec module
parameter first to ensure it didn't change from the default of 8.
thanks,
greg k-h
next prev parent reply other threads:[~2012-10-31 17:33 UTC|newest]
Thread overview: 27+ 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 [this message]
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
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-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=20121031173336.GA28991@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.