* ACPI errors with 3.7-rc3 @ 2012-10-31 1:45 Greg KH 2012-10-31 9:11 ` Rafael J. Wysocki 0 siblings, 1 reply; 26+ messages in thread From: Greg KH @ 2012-10-31 1:45 UTC (permalink / raw) To: lenb, rjw; +Cc: linux-acpi, linux-kernel 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? thanks, greg k-h ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 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 0 siblings, 1 reply; 26+ messages in thread From: Rafael J. Wysocki @ 2012-10-31 9:11 UTC (permalink / raw) To: Greg KH; +Cc: lenb, linux-acpi, linux-kernel 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? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-10-31 9:11 ` Rafael J. Wysocki @ 2012-10-31 17:33 ` Greg KH 2012-11-06 12:42 ` Azat Khuzhin 0 siblings, 1 reply; 26+ messages in thread From: Greg KH @ 2012-10-31 17:33 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: lenb, linux-acpi, linux-kernel 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 ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-10-31 17:33 ` Greg KH @ 2012-11-06 12:42 ` Azat Khuzhin 2012-11-06 12:48 ` Greg KH 0 siblings, 1 reply; 26+ messages in thread From: Azat Khuzhin @ 2012-11-06 12:42 UTC (permalink / raw) To: Greg KH; +Cc: Rafael J. Wysocki, lenb, linux-acpi, Linux Kernel Mailing List 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) 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 On Wed, Oct 31, 2012 at 9:33 PM, Greg KH <gregkh@linuxfoundation.org> wrote: > 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 > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Azat Khuzhin ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 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 0 siblings, 2 replies; 26+ messages in thread From: Greg KH @ 2012-11-06 12:48 UTC (permalink / raw) To: Azat Khuzhin Cc: Rafael J. Wysocki, lenb, linux-acpi, Linux Kernel Mailing List 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? thanks, greg k-h ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-11-06 12:48 ` Greg KH @ 2012-11-06 13:04 ` Azat Khuzhin 2012-11-07 21:49 ` Rafael J. Wysocki 1 sibling, 0 replies; 26+ messages in thread From: Azat Khuzhin @ 2012-11-06 13:04 UTC (permalink / raw) To: Greg KH; +Cc: Rafael J. Wysocki, lenb, linux-acpi, Linux Kernel Mailing List When this messages appears, I was running from AC, not from battery. On Tue, Nov 6, 2012 at 4:48 PM, Greg KH <gregkh@linuxfoundation.org> 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? > > thanks, > > greg k-h -- Azat Khuzhin ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 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-09 9:28 ` Feng Tang 1 sibling, 2 replies; 26+ messages in thread From: Rafael J. Wysocki @ 2012-11-07 21:49 UTC (permalink / raw) To: Greg KH, Azat Khuzhin Cc: linux-acpi, Linux Kernel Mailing List, Feng Tang, Lv Zheng, Len Brown, Moore, Robert 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)? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-11-07 21:49 ` Rafael J. Wysocki @ 2012-11-08 4:47 ` Greg KH 2012-11-08 9:15 ` Azat Khuzhin ` (2 more replies) 2012-11-09 9:28 ` Feng Tang 1 sibling, 3 replies; 26+ messages in thread From: Greg KH @ 2012-11-08 4:47 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Azat Khuzhin, linux-acpi, Linux Kernel Mailing List, Feng Tang, Lv Zheng, Len Brown, Moore, Robert 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 ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 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 2 siblings, 0 replies; 26+ messages in thread From: Azat Khuzhin @ 2012-11-08 9:15 UTC (permalink / raw) To: Greg KH Cc: Rafael J. Wysocki, linux-acpi, Linux Kernel Mailing List, Feng Tang, Lv Zheng, Len Brown, Moore, Robert Here is mine - https://gist.github.com/4037687 To Greg: acpidump 20100513-3.1 And I don't have pmtools installed On Thu, Nov 8, 2012 at 8:47 AM, Greg KH <gregkh@linuxfoundation.org> wrote: > 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 -- Azat Khuzhin ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 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 2 siblings, 0 replies; 26+ messages in thread From: Rafael J. Wysocki @ 2012-11-08 9:27 UTC (permalink / raw) To: Greg KH Cc: Azat Khuzhin, linux-acpi, Linux Kernel Mailing List, Feng Tang, Lv Zheng, Len Brown, Moore, Robert On Thursday, November 08, 2012 05:47:15 AM Greg KH wrote: > 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. On my system, which is a reasonably current Tumbleweed, acpidump is in the acpica-20120518-7.1.2.x86_64 package. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 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 2 siblings, 1 reply; 26+ messages in thread From: Carlos R. Mafra @ 2013-01-26 12:23 UTC (permalink / raw) To: Greg KH Cc: Rafael J. Wysocki, Azat Khuzhin, linux-acpi, Linux Kernel Mailing List, Feng Tang, Lv Zheng, Len Brown, Moore, Robert On Thu, 8 Nov 2012 at 5:47:15 +0100, Greg KH wrote: > 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. I'd like to ask what happened to this issue, because I'm seeing similar messages on latest 3.8-rc4 as well, and I cannot read the battery info anymore once this happens and the laptop does not suspend to RAM anymore -- it suspends fine before these messages. The laptop is a Macbook Pro with retina display and I'm using the develpoment version of openSUSE 12.3 updated as of yesterday. Here is the output from dmesg: [49367.993080] ACPI: EC: input buffer is not empty, aborting transaction [49367.993091] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) [49367.993112] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) [49367.993136] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) [49367.993147] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) [49367.993166] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) [49368.491802] ACPI: EC: input buffer is not empty, aborting transaction [49368.491812] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) [49368.491833] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) [49368.491857] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) [49368.491869] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) [49368.491888] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) [49372.985311] ACPI: EC: input buffer is not empty, aborting transaction [49372.985322] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) [49372.985344] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) [49372.985368] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) [49372.985380] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) [49372.985400] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) Anyone has more information about this? ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2013-01-26 12:23 ` Carlos R. Mafra @ 2013-01-26 13:23 ` Rafael J. Wysocki 2013-01-26 13:39 ` Carlos R. Mafra 0 siblings, 1 reply; 26+ messages in thread From: Rafael J. Wysocki @ 2013-01-26 13:23 UTC (permalink / raw) To: Carlos R. Mafra Cc: Greg KH, Azat Khuzhin, linux-acpi, Linux Kernel Mailing List, Feng Tang, Lv Zheng, Len Brown, Moore, Robert On Saturday, January 26, 2013 12:23:37 PM Carlos R. Mafra wrote: > On Thu, 8 Nov 2012 at 5:47:15 +0100, Greg KH wrote: > > 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. > > I'd like to ask what happened to this issue, because I'm seeing similar > messages on latest 3.8-rc4 as well, and I cannot read the battery > info anymore once this happens and the laptop does not suspend to RAM > anymore -- it suspends fine before these messages. > > The laptop is a Macbook Pro with retina display and I'm using the > develpoment version of openSUSE 12.3 updated as of yesterday. > > Here is the output from dmesg: > > [49367.993080] ACPI: EC: input buffer is not empty, aborting transaction > [49367.993091] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > [49367.993112] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > [49367.993136] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > [49367.993147] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > [49367.993166] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > [49368.491802] ACPI: EC: input buffer is not empty, aborting transaction > [49368.491812] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > [49368.491833] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > [49368.491857] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > [49368.491869] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > [49368.491888] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > [49372.985311] ACPI: EC: input buffer is not empty, aborting transaction > [49372.985322] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > [49372.985344] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > [49372.985368] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > [49372.985380] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > [49372.985400] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > > Anyone has more information about this? Is acpidump still not working? What's under /sys/firmware/acpi/tables/ ? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 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 0 siblings, 2 replies; 26+ messages in thread From: Carlos R. Mafra @ 2013-01-26 13:39 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Carlos R. Mafra, Greg KH, Azat Khuzhin, linux-acpi, Linux Kernel Mailing List, Feng Tang, Lv Zheng, Len Brown, Moore, Robert On Sat, 26 Jan 2013 at 14:23:12 +0100, Rafael J. Wysocki wrote: > On Saturday, January 26, 2013 12:23:37 PM Carlos R. Mafra wrote: > > On Thu, 8 Nov 2012 at 5:47:15 +0100, Greg KH wrote: > > > 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. > > > > I'd like to ask what happened to this issue, because I'm seeing similar > > messages on latest 3.8-rc4 as well, and I cannot read the battery > > info anymore once this happens and the laptop does not suspend to RAM > > anymore -- it suspends fine before these messages. > > > > The laptop is a Macbook Pro with retina display and I'm using the > > develpoment version of openSUSE 12.3 updated as of yesterday. > > > > Here is the output from dmesg: > > > > [49367.993080] ACPI: EC: input buffer is not empty, aborting transaction > > [49367.993091] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > > [49367.993112] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > > [49367.993136] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > > [49367.993147] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > > [49367.993166] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > > [49368.491802] ACPI: EC: input buffer is not empty, aborting transaction > > [49368.491812] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > > [49368.491833] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > > [49368.491857] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > > [49368.491869] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > > [49368.491888] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > > [49372.985311] ACPI: EC: input buffer is not empty, aborting transaction > > [49372.985322] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > > [49372.985344] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > > [49372.985368] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > > [49372.985380] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > > [49372.985400] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > > > > Anyone has more information about this? > > Is acpidump still not working? It works for me, I've uploaded it to http://www.damtp.cam.ac.uk/user/crm66/acpidump-rmbp.txt And my 'dmesg' from a freshly-booted 3.8-rc5 is here http://www.damtp.cam.ac.uk/user/crm66/dmesg-3.8-rc5.txt > What's under /sys/firmware/acpi/tables/ ? [mafra@linux-ahr8:~]$ ls /sys/firmware/acpi/tables/ APIC DSDT ECDT FACS MCFG SSDT1 SSDT11 SSDT2 SSDT4 SSDT6 SSDT8 DMAR dynamic/ FACP HPET SBST SSDT10 SSDT12 SSDT3 SSDT5 SSDT7 SSDT9 I should say that sometimes it takes +3 days for this problem to appear, with many successful s2ram in between, sometimes it takes less than 1 day. I could not figure out a pattern. Any other info I can provide? ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2013-01-26 13:39 ` Carlos R. Mafra @ 2013-01-26 13:55 ` Rafael J. Wysocki 2013-01-26 21:23 ` Azat Khuzhin 1 sibling, 0 replies; 26+ messages in thread From: Rafael J. Wysocki @ 2013-01-26 13:55 UTC (permalink / raw) To: Carlos R. Mafra Cc: Carlos R. Mafra, Greg KH, Azat Khuzhin, linux-acpi, Linux Kernel Mailing List, Feng Tang, Lv Zheng, Len Brown, Moore, Robert On Saturday, January 26, 2013 01:39:37 PM Carlos R. Mafra wrote: > On Sat, 26 Jan 2013 at 14:23:12 +0100, Rafael J. Wysocki wrote: > > On Saturday, January 26, 2013 12:23:37 PM Carlos R. Mafra wrote: > > > On Thu, 8 Nov 2012 at 5:47:15 +0100, Greg KH wrote: > > > > 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. > > > > > > I'd like to ask what happened to this issue, because I'm seeing similar > > > messages on latest 3.8-rc4 as well, and I cannot read the battery > > > info anymore once this happens and the laptop does not suspend to RAM > > > anymore -- it suspends fine before these messages. > > > > > > The laptop is a Macbook Pro with retina display and I'm using the > > > develpoment version of openSUSE 12.3 updated as of yesterday. > > > > > > Here is the output from dmesg: > > > > > > [49367.993080] ACPI: EC: input buffer is not empty, aborting transaction > > > [49367.993091] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > > > [49367.993112] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > > > [49367.993136] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > > > [49367.993147] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > > > [49367.993166] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > > > [49368.491802] ACPI: EC: input buffer is not empty, aborting transaction > > > [49368.491812] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > > > [49368.491833] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > > > [49368.491857] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > > > [49368.491869] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > > > [49368.491888] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > > > [49372.985311] ACPI: EC: input buffer is not empty, aborting transaction > > > [49372.985322] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > > > [49372.985344] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > > > [49372.985368] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > > > [49372.985380] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > > > [49372.985400] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > > > > > > Anyone has more information about this? > > > > Is acpidump still not working? > > It works for me, I've uploaded it to > > http://www.damtp.cam.ac.uk/user/crm66/acpidump-rmbp.txt > > And my 'dmesg' from a freshly-booted 3.8-rc5 is here > > http://www.damtp.cam.ac.uk/user/crm66/dmesg-3.8-rc5.txt > > > What's under /sys/firmware/acpi/tables/ ? > > [mafra@linux-ahr8:~]$ ls /sys/firmware/acpi/tables/ > APIC DSDT ECDT FACS MCFG SSDT1 SSDT11 SSDT2 SSDT4 SSDT6 SSDT8 > DMAR dynamic/ FACP HPET SBST SSDT10 SSDT12 SSDT3 SSDT5 SSDT7 SSDT9 > > I should say that sometimes it takes +3 days for this problem to appear, > with many successful s2ram in between, sometimes it takes less than 1 day. > I could not figure out a pattern. > > Any other info I can provide? Well, I can't really say at the moment. Please file a bug at bugzilla.kernel.org against ACPI and assign it to Lv Zheng. Please put all of the information you've collected so far in there and add the output of acpidump as an attachment. Thanks, Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 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 1 sibling, 1 reply; 26+ messages in thread From: Azat Khuzhin @ 2013-01-26 21:23 UTC (permalink / raw) To: Carlos R. Mafra Cc: Rafael J. Wysocki, Carlos R. Mafra, Greg KH, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Feng Tang, Lv Zheng, Len Brown, Moore, Robert Carlos, did you try this patch? https://bugzilla.kernel.org/attachment.cgi?id=73510 On Sat, Jan 26, 2013 at 5:39 PM, Carlos R. Mafra <crmafra@gmail.com> wrote: > On Sat, 26 Jan 2013 at 14:23:12 +0100, Rafael J. Wysocki wrote: >> On Saturday, January 26, 2013 12:23:37 PM Carlos R. Mafra wrote: >> > On Thu, 8 Nov 2012 at 5:47:15 +0100, Greg KH wrote: >> > > 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. >> > >> > I'd like to ask what happened to this issue, because I'm seeing similar >> > messages on latest 3.8-rc4 as well, and I cannot read the battery >> > info anymore once this happens and the laptop does not suspend to RAM >> > anymore -- it suspends fine before these messages. >> > >> > The laptop is a Macbook Pro with retina display and I'm using the >> > develpoment version of openSUSE 12.3 updated as of yesterday. >> > >> > Here is the output from dmesg: >> > >> > [49367.993080] ACPI: EC: input buffer is not empty, aborting transaction >> > [49367.993091] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) >> > [49367.993112] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) >> > [49367.993136] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) >> > [49367.993147] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) >> > [49367.993166] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) >> > [49368.491802] ACPI: EC: input buffer is not empty, aborting transaction >> > [49368.491812] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) >> > [49368.491833] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) >> > [49368.491857] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) >> > [49368.491869] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) >> > [49368.491888] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) >> > [49372.985311] ACPI: EC: input buffer is not empty, aborting transaction >> > [49372.985322] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) >> > [49372.985344] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) >> > [49372.985368] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) >> > [49372.985380] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) >> > [49372.985400] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) >> > >> > Anyone has more information about this? >> >> Is acpidump still not working? > > It works for me, I've uploaded it to > > http://www.damtp.cam.ac.uk/user/crm66/acpidump-rmbp.txt > > And my 'dmesg' from a freshly-booted 3.8-rc5 is here > > http://www.damtp.cam.ac.uk/user/crm66/dmesg-3.8-rc5.txt > >> What's under /sys/firmware/acpi/tables/ ? > > [mafra@linux-ahr8:~]$ ls /sys/firmware/acpi/tables/ > APIC DSDT ECDT FACS MCFG SSDT1 SSDT11 SSDT2 SSDT4 SSDT6 SSDT8 > DMAR dynamic/ FACP HPET SBST SSDT10 SSDT12 SSDT3 SSDT5 SSDT7 SSDT9 > > I should say that sometimes it takes +3 days for this problem to appear, > with many successful s2ram in between, sometimes it takes less than 1 day. > I could not figure out a pattern. > > Any other info I can provide? -- Azat Khuzhin ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2013-01-26 21:23 ` Azat Khuzhin @ 2013-01-27 12:37 ` Carlos R. Mafra 0 siblings, 0 replies; 26+ messages in thread From: Carlos R. Mafra @ 2013-01-27 12:37 UTC (permalink / raw) To: Azat Khuzhin Cc: Rafael J. Wysocki, Carlos R. Mafra, Greg KH, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Feng Tang, Lv Zheng, Len Brown, Moore, Robert On Sun, 27 Jan 2013 at 1:23:17 +0400, Azat Khuzhin wrote: > Carlos, did you try this patch? > > https://bugzilla.kernel.org/attachment.cgi?id=73510 I started to test it now and I will try to have an uptime of more than 7 days in order to have a veridict. [ The problem is that I started to encounter a dvb-related issue which requires me to reboot after trying to watch tv, so let's wee what happens. ] > On Sat, Jan 26, 2013 at 5:39 PM, Carlos R. Mafra <crmafra@gmail.com> wrote: > > On Sat, 26 Jan 2013 at 14:23:12 +0100, Rafael J. Wysocki wrote: > >> On Saturday, January 26, 2013 12:23:37 PM Carlos R. Mafra wrote: > >> > On Thu, 8 Nov 2012 at 5:47:15 +0100, Greg KH wrote: > >> > > 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. > >> > > >> > I'd like to ask what happened to this issue, because I'm seeing similar > >> > messages on latest 3.8-rc4 as well, and I cannot read the battery > >> > info anymore once this happens and the laptop does not suspend to RAM > >> > anymore -- it suspends fine before these messages. > >> > > >> > The laptop is a Macbook Pro with retina display and I'm using the > >> > develpoment version of openSUSE 12.3 updated as of yesterday. > >> > > >> > Here is the output from dmesg: > >> > > >> > [49367.993080] ACPI: EC: input buffer is not empty, aborting transaction > >> > [49367.993091] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > >> > [49367.993112] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > >> > [49367.993136] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > >> > [49367.993147] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > >> > [49367.993166] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > >> > [49368.491802] ACPI: EC: input buffer is not empty, aborting transaction > >> > [49368.491812] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > >> > [49368.491833] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > >> > [49368.491857] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > >> > [49368.491869] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > >> > [49368.491888] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > >> > [49372.985311] ACPI: EC: input buffer is not empty, aborting transaction > >> > [49372.985322] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20121018/evregion-501) > >> > [49372.985344] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff880264490920), AE_TIME (20121018/psparse-537) > >> > [49372.985368] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff8802644905b0), AE_TIME (20121018/psparse-537) > >> > [49372.985380] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff880264490678), AE_TIME (20121018/psparse-537) > >> > [49372.985400] ACPI Exception: AE_TIME, Evaluating _BST (20121018/battery-492) > >> > > >> > Anyone has more information about this? > >> > >> Is acpidump still not working? > > > > It works for me, I've uploaded it to > > > > http://www.damtp.cam.ac.uk/user/crm66/acpidump-rmbp.txt > > > > And my 'dmesg' from a freshly-booted 3.8-rc5 is here > > > > http://www.damtp.cam.ac.uk/user/crm66/dmesg-3.8-rc5.txt > > > >> What's under /sys/firmware/acpi/tables/ ? > > > > [mafra@linux-ahr8:~]$ ls /sys/firmware/acpi/tables/ > > APIC DSDT ECDT FACS MCFG SSDT1 SSDT11 SSDT2 SSDT4 SSDT6 SSDT8 > > DMAR dynamic/ FACP HPET SBST SSDT10 SSDT12 SSDT3 SSDT5 SSDT7 SSDT9 > > > > I should say that sometimes it takes +3 days for this problem to appear, > > with many successful s2ram in between, sometimes it takes less than 1 day. > > I could not figure out a pattern. > > > > Any other info I can provide? > > > > -- > Azat Khuzhin ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-11-07 21:49 ` Rafael J. Wysocki 2012-11-08 4:47 ` Greg KH @ 2012-11-09 9:28 ` Feng Tang 2012-11-09 14:30 ` Moore, Robert 1 sibling, 1 reply; 26+ messages in thread From: Feng Tang @ 2012-11-09 9:28 UTC (permalink / raw) To: Rafael J. Wysocki Cc: Greg KH, Azat Khuzhin, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Zheng, Lv, Len Brown, Moore, Robert On Thu, Nov 08, 2012 at 05:49:40AM +0800, 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)? I doubt this problem is sometimes inevitable for some machines, because AFAIK most modern machines have the race problem for EC HW controller, as both OS side and the BIOS may access the EC HW at the same time without any race control. For this case, usually the battery and thermal modules (which may be controlled through EC) are always monitored by BIOS, when OS also frequently visit them too, the EC's own state machine may be broken and not responsive due to the race, then cause the timeout error. And how severe the problem will be depends on the EC HW, the quality of BIOS code and OS/driver code. Myself have seen the similar "ACPI: EC: input buffer is not empty, aborting transaction" error message on one laptop when its EC is busy visited by OS. btw, in EC driver I see a "ec->global_lock", don't know if it was designed to control the race between OS and BIOS. Thanks, Feng ^ permalink raw reply [flat|nested] 26+ messages in thread
* RE: ACPI errors with 3.7-rc3 2012-11-09 9:28 ` Feng Tang @ 2012-11-09 14:30 ` Moore, Robert 2012-11-09 16:36 ` Feng Tang 0 siblings, 1 reply; 26+ messages in thread From: Moore, Robert @ 2012-11-09 14:30 UTC (permalink / raw) To: Tang, Feng, Rafael J. Wysocki Cc: Greg KH, Azat Khuzhin, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Zheng, Lv, Len Brown The ACPI Global Lock is in fact intended to provide exclusion between the BIOS and the OS. Bob > -----Original Message----- > From: Tang, Feng > Sent: Friday, November 09, 2012 1:29 AM > To: Rafael J. Wysocki > Cc: Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; Linux Kernel > Mailing List; Zheng, Lv; Len Brown; Moore, Robert > Subject: Re: ACPI errors with 3.7-rc3 > > On Thu, Nov 08, 2012 at 05:49:40AM +0800, 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)? > > I doubt this problem is sometimes inevitable for some machines, because > AFAIK most modern machines have the race problem for EC HW controller, as > both OS side and the BIOS may access the EC HW at the same time > without any race control. > > For this case, usually the battery and thermal modules (which may be > controlled through EC) are always monitored by BIOS, when OS also > frequently visit them too, the EC's own state machine may be broken and > not responsive due to the race, then cause the timeout error. > And how severe the problem will be depends on the EC HW, the quality of > BIOS code and OS/driver code. > > Myself have seen the similar "ACPI: EC: input buffer is not empty, > aborting transaction" error message on one laptop when its EC is busy > visited by OS. > > btw, in EC driver I see a "ec->global_lock", don't know if it was designed > to control the race between OS and BIOS. > > Thanks, > Feng ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-11-09 14:30 ` Moore, Robert @ 2012-11-09 16:36 ` Feng Tang 2012-11-09 16:45 ` Moore, Robert 2012-11-17 5:40 ` Robert Hancock 0 siblings, 2 replies; 26+ messages in thread From: Feng Tang @ 2012-11-09 16:36 UTC (permalink / raw) To: Moore, Robert Cc: Rafael J. Wysocki, Greg KH, Azat Khuzhin, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Zheng, Lv, Len Brown On Fri, Nov 09, 2012 at 10:30:43PM +0800, Moore, Robert wrote: > The ACPI Global Lock is in fact intended to provide exclusion between the BIOS and the OS. > Bob Thanks for the info. And per my check, most of ACPI FW don't implement this lock, say after driver probe, the ec->global_lock will be 0. - Feng > > > > -----Original Message----- > > From: Tang, Feng > > Sent: Friday, November 09, 2012 1:29 AM > > To: Rafael J. Wysocki > > Cc: Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; Linux Kernel > > Mailing List; Zheng, Lv; Len Brown; Moore, Robert > > Subject: Re: ACPI errors with 3.7-rc3 > > > > On Thu, Nov 08, 2012 at 05:49:40AM +0800, 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)? > > > > I doubt this problem is sometimes inevitable for some machines, because > > AFAIK most modern machines have the race problem for EC HW controller, as > > both OS side and the BIOS may access the EC HW at the same time > > without any race control. > > > > For this case, usually the battery and thermal modules (which may be > > controlled through EC) are always monitored by BIOS, when OS also > > frequently visit them too, the EC's own state machine may be broken and > > not responsive due to the race, then cause the timeout error. > > And how severe the problem will be depends on the EC HW, the quality of > > BIOS code and OS/driver code. > > > > Myself have seen the similar "ACPI: EC: input buffer is not empty, > > aborting transaction" error message on one laptop when its EC is busy > > visited by OS. > > > > btw, in EC driver I see a "ec->global_lock", don't know if it was designed > > to control the race between OS and BIOS. > > > > Thanks, > > Feng ^ permalink raw reply [flat|nested] 26+ messages in thread
* RE: ACPI errors with 3.7-rc3 2012-11-09 16:36 ` Feng Tang @ 2012-11-09 16:45 ` Moore, Robert 2012-11-11 10:00 ` Azat Khuzhin 2012-11-17 5:40 ` Robert Hancock 1 sibling, 1 reply; 26+ messages in thread From: Moore, Robert @ 2012-11-09 16:45 UTC (permalink / raw) To: Tang, Feng Cc: Rafael J. Wysocki, Greg KH, Azat Khuzhin, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Zheng, Lv, Len Brown > And per my check, most of ACPI FW don't implement this lock, say after > driver probe, the ec->global_lock will be 0 Take a look at the FACS table, it contains the address of the global lock. I believe that the ACPI specification requires that the global lock be present. > -----Original Message----- > From: Tang, Feng > Sent: Friday, November 09, 2012 8:36 AM > To: Moore, Robert > Cc: Rafael J. Wysocki; Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; > Linux Kernel Mailing List; Zheng, Lv; Len Brown > Subject: Re: ACPI errors with 3.7-rc3 > > On Fri, Nov 09, 2012 at 10:30:43PM +0800, Moore, Robert wrote: > > The ACPI Global Lock is in fact intended to provide exclusion between > the BIOS and the OS. > > Bob > > Thanks for the info. > > And per my check, most of ACPI FW don't implement this lock, say after > driver probe, the ec->global_lock will be 0. > > - Feng > > > > > > > > -----Original Message----- > > > From: Tang, Feng > > > Sent: Friday, November 09, 2012 1:29 AM > > > To: Rafael J. Wysocki > > > Cc: Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; Linux Kernel > > > Mailing List; Zheng, Lv; Len Brown; Moore, Robert > > > Subject: Re: ACPI errors with 3.7-rc3 > > > > > > On Thu, Nov 08, 2012 at 05:49:40AM +0800, 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)? > > > > > > I doubt this problem is sometimes inevitable for some machines, > > > because AFAIK most modern machines have the race problem for EC HW > > > controller, as both OS side and the BIOS may access the EC HW at the > > > same time without any race control. > > > > > > For this case, usually the battery and thermal modules (which may be > > > controlled through EC) are always monitored by BIOS, when OS also > > > frequently visit them too, the EC's own state machine may be broken > > > and not responsive due to the race, then cause the timeout error. > > > And how severe the problem will be depends on the EC HW, the quality > > > of BIOS code and OS/driver code. > > > > > > Myself have seen the similar "ACPI: EC: input buffer is not empty, > > > aborting transaction" error message on one laptop when its EC is > > > busy visited by OS. > > > > > > btw, in EC driver I see a "ec->global_lock", don't know if it was > > > designed to control the race between OS and BIOS. > > > > > > Thanks, > > > Feng ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-11-09 16:45 ` Moore, Robert @ 2012-11-11 10:00 ` Azat Khuzhin 2012-11-13 0:41 ` Moore, Robert 0 siblings, 1 reply; 26+ messages in thread From: Azat Khuzhin @ 2012-11-11 10:00 UTC (permalink / raw) To: Moore, Robert Cc: Tang, Feng, Rafael J. Wysocki, Greg KH, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Zheng, Lv, Len Brown Robert, You say that FACS table contains the address of the global lock. But in my case https://gist.github.com/4037687 it seems to be empty, so this means that my laptop don't have global lock? On Fri, Nov 9, 2012 at 8:45 PM, Moore, Robert <robert.moore@intel.com> wrote: >> And per my check, most of ACPI FW don't implement this lock, say after >> driver probe, the ec->global_lock will be 0 > > Take a look at the FACS table, it contains the address of the global lock. > > I believe that the ACPI specification requires that the global lock be present. > > > >> -----Original Message----- >> From: Tang, Feng >> Sent: Friday, November 09, 2012 8:36 AM >> To: Moore, Robert >> Cc: Rafael J. Wysocki; Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; >> Linux Kernel Mailing List; Zheng, Lv; Len Brown >> Subject: Re: ACPI errors with 3.7-rc3 >> >> On Fri, Nov 09, 2012 at 10:30:43PM +0800, Moore, Robert wrote: >> > The ACPI Global Lock is in fact intended to provide exclusion between >> the BIOS and the OS. >> > Bob >> >> Thanks for the info. >> >> And per my check, most of ACPI FW don't implement this lock, say after >> driver probe, the ec->global_lock will be 0. >> >> - Feng >> >> > >> > >> > > -----Original Message----- >> > > From: Tang, Feng >> > > Sent: Friday, November 09, 2012 1:29 AM >> > > To: Rafael J. Wysocki >> > > Cc: Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; Linux Kernel >> > > Mailing List; Zheng, Lv; Len Brown; Moore, Robert >> > > Subject: Re: ACPI errors with 3.7-rc3 >> > > >> > > On Thu, Nov 08, 2012 at 05:49:40AM +0800, 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)? >> > > >> > > I doubt this problem is sometimes inevitable for some machines, >> > > because AFAIK most modern machines have the race problem for EC HW >> > > controller, as both OS side and the BIOS may access the EC HW at the >> > > same time without any race control. >> > > >> > > For this case, usually the battery and thermal modules (which may be >> > > controlled through EC) are always monitored by BIOS, when OS also >> > > frequently visit them too, the EC's own state machine may be broken >> > > and not responsive due to the race, then cause the timeout error. >> > > And how severe the problem will be depends on the EC HW, the quality >> > > of BIOS code and OS/driver code. >> > > >> > > Myself have seen the similar "ACPI: EC: input buffer is not empty, >> > > aborting transaction" error message on one laptop when its EC is >> > > busy visited by OS. >> > > >> > > btw, in EC driver I see a "ec->global_lock", don't know if it was >> > > designed to control the race between OS and BIOS. >> > > >> > > Thanks, >> > > Feng -- Azat Khuzhin ^ permalink raw reply [flat|nested] 26+ messages in thread
* RE: ACPI errors with 3.7-rc3 2012-11-11 10:00 ` Azat Khuzhin @ 2012-11-13 0:41 ` Moore, Robert 2012-11-14 17:33 ` Azat Khuzhin 0 siblings, 1 reply; 26+ messages in thread From: Moore, Robert @ 2012-11-13 0:41 UTC (permalink / raw) To: Azat Khuzhin Cc: Tang, Feng, Rafael J. Wysocki, Greg KH, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Zheng, Lv, Len Brown Actually, it is not the address of the global lock, the FACS contains the actual global lock: From acpi5.0 spec: ROM BIOS. The Global Lock is a 32-bit (DWORD) value in read/write memory located within the FACS and is accessed and updated by both the OS environment and the SMI environment in a defined manner to provide an exclusive lock. Note: this is not a pointer to the Global Lock, it is the actual memory location of the lock. The FACS and Global Lock may be located anywhere in physical memory. > -----Original Message----- > From: a3at.mail@gmail.com [mailto:a3at.mail@gmail.com] On Behalf Of Azat > Khuzhin > Sent: Sunday, November 11, 2012 2:01 AM > To: Moore, Robert > Cc: Tang, Feng; Rafael J. Wysocki; Greg KH; linux-acpi@vger.kernel.org; > Linux Kernel Mailing List; Zheng, Lv; Len Brown > Subject: Re: ACPI errors with 3.7-rc3 > > Robert, > > You say that FACS table contains the address of the global lock. > But in my case https://gist.github.com/4037687 it seems to be empty, so > this means that my laptop don't have global lock? > > On Fri, Nov 9, 2012 at 8:45 PM, Moore, Robert <robert.moore@intel.com> > wrote: > >> And per my check, most of ACPI FW don't implement this lock, say > >> after driver probe, the ec->global_lock will be 0 > > > > Take a look at the FACS table, it contains the address of the global > lock. > > > > I believe that the ACPI specification requires that the global lock be > present. > > > > > > > >> -----Original Message----- > >> From: Tang, Feng > >> Sent: Friday, November 09, 2012 8:36 AM > >> To: Moore, Robert > >> Cc: Rafael J. Wysocki; Greg KH; Azat Khuzhin; > >> linux-acpi@vger.kernel.org; Linux Kernel Mailing List; Zheng, Lv; Len > >> Brown > >> Subject: Re: ACPI errors with 3.7-rc3 > >> > >> On Fri, Nov 09, 2012 at 10:30:43PM +0800, Moore, Robert wrote: > >> > The ACPI Global Lock is in fact intended to provide exclusion > >> > between > >> the BIOS and the OS. > >> > Bob > >> > >> Thanks for the info. > >> > >> And per my check, most of ACPI FW don't implement this lock, say > >> after driver probe, the ec->global_lock will be 0. > >> > >> - Feng > >> > >> > > >> > > >> > > -----Original Message----- > >> > > From: Tang, Feng > >> > > Sent: Friday, November 09, 2012 1:29 AM > >> > > To: Rafael J. Wysocki > >> > > Cc: Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; Linux > >> > > Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert > >> > > Subject: Re: ACPI errors with 3.7-rc3 > >> > > > >> > > On Thu, Nov 08, 2012 at 05:49:40AM +0800, 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)? > >> > > > >> > > I doubt this problem is sometimes inevitable for some machines, > >> > > because AFAIK most modern machines have the race problem for EC > >> > > HW controller, as both OS side and the BIOS may access the EC HW > >> > > at the same time without any race control. > >> > > > >> > > For this case, usually the battery and thermal modules (which may > >> > > be controlled through EC) are always monitored by BIOS, when OS > >> > > also frequently visit them too, the EC's own state machine may be > >> > > broken and not responsive due to the race, then cause the timeout > error. > >> > > And how severe the problem will be depends on the EC HW, the > >> > > quality of BIOS code and OS/driver code. > >> > > > >> > > Myself have seen the similar "ACPI: EC: input buffer is not > >> > > empty, aborting transaction" error message on one laptop when its > >> > > EC is busy visited by OS. > >> > > > >> > > btw, in EC driver I see a "ec->global_lock", don't know if it was > >> > > designed to control the race between OS and BIOS. > >> > > > >> > > Thanks, > >> > > Feng > > > > -- > Azat Khuzhin ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-11-13 0:41 ` Moore, Robert @ 2012-11-14 17:33 ` Azat Khuzhin 0 siblings, 0 replies; 26+ messages in thread From: Azat Khuzhin @ 2012-11-14 17:33 UTC (permalink / raw) To: Moore, Robert Cc: Tang, Feng, Rafael J. Wysocki, Greg KH, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Zheng, Lv, Len Brown Robert, thanks. I have such message again, and load avg up to 30, and the increase up to 40, after to 50. I found this https://bugzilla.kernel.org/show_bug.cgi?id=14733 and I after I compile kernel with this patch write message about results. Also I want to note that after I suspend laptop to ~20-15 minutes and resume, it works fine. And no such spam in log. But after this hack if open lid, laptop not exit from suspend mode, for exit from it, I must manually press key on keyboard. I try to restart acpid, laptop-mode but nothing of this helped me. $ dmesg | tail -n20 [122582.074256] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff88026547e740), AE_TIME (20120711/psparse-536) [122582.076668] ACPI Exception: AE_TIME, Evaluating _BST (20120711/battery-464) [122582.572501] ACPI: EC: input buffer is not empty, aborting transaction [122582.573710] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20120711/evregion-501) [122582.576121] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff88026547ea10), AE_TIME (20120711/psparse-536) [122582.578548] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff88026547e678), AE_TIME (20120711/psparse-536) [122582.580964] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff88026547e740), AE_TIME (20120711/psparse-536) [122582.583378] ACPI Exception: AE_TIME, Evaluating _BST (20120711/battery-464) [122583.079191] ACPI: EC: input buffer is not empty, aborting transaction [122583.080488] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20120711/evregion-501) [122583.083073] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff88026547ea10), AE_TIME (20120711/psparse-536) [122583.085671] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff88026547e678), AE_TIME (20120711/psparse-536) [122583.088264] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff88026547e740), AE_TIME (20120711/psparse-536) [122583.090893] ACPI Exception: AE_TIME, Evaluating _BST (20120711/battery-464) [122583.585891] ACPI: EC: input buffer is not empty, aborting transaction [122583.587100] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20120711/evregion-501) [122583.589578] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC__.SMB0.SBRW] (Node ffff88026547ea10), AE_TIME (20120711/psparse-536) [122583.592003] ACPI Error: Method parse/execution failed [\_SB_.BAT0.UBST] (Node ffff88026547e678), AE_TIME (20120711/psparse-536) [122583.594419] ACPI Error: Method parse/execution failed [\_SB_.BAT0._BST] (Node ffff88026547e740), AE_TIME (20120711/psparse-536) [122583.596859] ACPI Exception: AE_TIME, Evaluating _BST (20120711/battery-464) On Tue, Nov 13, 2012 at 4:41 AM, Moore, Robert <robert.moore@intel.com> wrote: > Actually, it is not the address of the global lock, the FACS contains the actual global lock: > > From acpi5.0 spec: > > ROM BIOS. The Global Lock is a 32-bit (DWORD) value in read/write memory located within the FACS and is accessed and updated by both the OS environment and the SMI environment in a defined manner to provide an exclusive lock. Note: this is not a pointer to the Global Lock, it is the actual memory location of the lock. The FACS and Global Lock may be located anywhere in physical memory. > > > > >> -----Original Message----- >> From: a3at.mail@gmail.com [mailto:a3at.mail@gmail.com] On Behalf Of Azat >> Khuzhin >> Sent: Sunday, November 11, 2012 2:01 AM >> To: Moore, Robert >> Cc: Tang, Feng; Rafael J. Wysocki; Greg KH; linux-acpi@vger.kernel.org; >> Linux Kernel Mailing List; Zheng, Lv; Len Brown >> Subject: Re: ACPI errors with 3.7-rc3 >> >> Robert, >> >> You say that FACS table contains the address of the global lock. >> But in my case https://gist.github.com/4037687 it seems to be empty, so >> this means that my laptop don't have global lock? >> >> On Fri, Nov 9, 2012 at 8:45 PM, Moore, Robert <robert.moore@intel.com> >> wrote: >> >> And per my check, most of ACPI FW don't implement this lock, say >> >> after driver probe, the ec->global_lock will be 0 >> > >> > Take a look at the FACS table, it contains the address of the global >> lock. >> > >> > I believe that the ACPI specification requires that the global lock be >> present. >> > >> > >> > >> >> -----Original Message----- >> >> From: Tang, Feng >> >> Sent: Friday, November 09, 2012 8:36 AM >> >> To: Moore, Robert >> >> Cc: Rafael J. Wysocki; Greg KH; Azat Khuzhin; >> >> linux-acpi@vger.kernel.org; Linux Kernel Mailing List; Zheng, Lv; Len >> >> Brown >> >> Subject: Re: ACPI errors with 3.7-rc3 >> >> >> >> On Fri, Nov 09, 2012 at 10:30:43PM +0800, Moore, Robert wrote: >> >> > The ACPI Global Lock is in fact intended to provide exclusion >> >> > between >> >> the BIOS and the OS. >> >> > Bob >> >> >> >> Thanks for the info. >> >> >> >> And per my check, most of ACPI FW don't implement this lock, say >> >> after driver probe, the ec->global_lock will be 0. >> >> >> >> - Feng >> >> >> >> > >> >> > >> >> > > -----Original Message----- >> >> > > From: Tang, Feng >> >> > > Sent: Friday, November 09, 2012 1:29 AM >> >> > > To: Rafael J. Wysocki >> >> > > Cc: Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; Linux >> >> > > Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert >> >> > > Subject: Re: ACPI errors with 3.7-rc3 >> >> > > >> >> > > On Thu, Nov 08, 2012 at 05:49:40AM +0800, 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)? >> >> > > >> >> > > I doubt this problem is sometimes inevitable for some machines, >> >> > > because AFAIK most modern machines have the race problem for EC >> >> > > HW controller, as both OS side and the BIOS may access the EC HW >> >> > > at the same time without any race control. >> >> > > >> >> > > For this case, usually the battery and thermal modules (which may >> >> > > be controlled through EC) are always monitored by BIOS, when OS >> >> > > also frequently visit them too, the EC's own state machine may be >> >> > > broken and not responsive due to the race, then cause the timeout >> error. >> >> > > And how severe the problem will be depends on the EC HW, the >> >> > > quality of BIOS code and OS/driver code. >> >> > > >> >> > > Myself have seen the similar "ACPI: EC: input buffer is not >> >> > > empty, aborting transaction" error message on one laptop when its >> >> > > EC is busy visited by OS. >> >> > > >> >> > > btw, in EC driver I see a "ec->global_lock", don't know if it was >> >> > > designed to control the race between OS and BIOS. >> >> > > >> >> > > Thanks, >> >> > > Feng >> >> >> >> -- >> Azat Khuzhin -- Azat Khuzhin ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-11-09 16:36 ` Feng Tang 2012-11-09 16:45 ` Moore, Robert @ 2012-11-17 5:40 ` Robert Hancock 2012-12-01 20:59 ` Azat Khuzhin 1 sibling, 1 reply; 26+ messages in thread From: Robert Hancock @ 2012-11-17 5:40 UTC (permalink / raw) To: Feng Tang Cc: Moore, Robert, Rafael J. Wysocki, Greg KH, Azat Khuzhin, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Zheng, Lv, Len Brown On 11/09/2012 10:36 AM, Feng Tang wrote: > On Fri, Nov 09, 2012 at 10:30:43PM +0800, Moore, Robert wrote: >> The ACPI Global Lock is in fact intended to provide exclusion between the BIOS and the OS. >> Bob > > Thanks for the info. > > And per my check, most of ACPI FW don't implement this lock, say > after driver probe, the ec->global_lock will be 0. The DSDT is supposed to define the _GLK control method on the EC if the BIOS needs to perform its own access which may conflict with the OS usage. If it doesn't, then it should be the case that either the BIOS doesn't touch the EC itself or it uses a separate interface that doesn't cause conflicts with what the OS is doing. > > - Feng > >> >> >>> -----Original Message----- >>> From: Tang, Feng >>> Sent: Friday, November 09, 2012 1:29 AM >>> To: Rafael J. Wysocki >>> Cc: Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; Linux Kernel >>> Mailing List; Zheng, Lv; Len Brown; Moore, Robert >>> Subject: Re: ACPI errors with 3.7-rc3 >>> >>> On Thu, Nov 08, 2012 at 05:49:40AM +0800, 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)? >>> >>> I doubt this problem is sometimes inevitable for some machines, because >>> AFAIK most modern machines have the race problem for EC HW controller, as >>> both OS side and the BIOS may access the EC HW at the same time >>> without any race control. >>> >>> For this case, usually the battery and thermal modules (which may be >>> controlled through EC) are always monitored by BIOS, when OS also >>> frequently visit them too, the EC's own state machine may be broken and >>> not responsive due to the race, then cause the timeout error. >>> And how severe the problem will be depends on the EC HW, the quality of >>> BIOS code and OS/driver code. >>> >>> Myself have seen the similar "ACPI: EC: input buffer is not empty, >>> aborting transaction" error message on one laptop when its EC is busy >>> visited by OS. >>> >>> btw, in EC driver I see a "ec->global_lock", don't know if it was designed >>> to control the race between OS and BIOS. >>> >>> Thanks, >>> Feng > -- > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-11-17 5:40 ` Robert Hancock @ 2012-12-01 20:59 ` Azat Khuzhin 2012-12-01 21:54 ` Azat Khuzhin 0 siblings, 1 reply; 26+ messages in thread From: Azat Khuzhin @ 2012-12-01 20:59 UTC (permalink / raw) To: Robert Hancock Cc: Feng Tang, Moore, Robert, Rafael J. Wysocki, Greg KH, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Zheng, Lv, Len Brown I tried this patch - https://bugzilla.kernel.org/attachment.cgi?id=73510 from https://bugzilla.kernel.org/show_bug.cgi?id=14733. And I don't see such messages any more. But another problem surfaced - laptop can't resume working after a long time held in suspend, end there is not messages in kern.log about that laptop trying to resume. On Sat, Nov 17, 2012 at 9:40 AM, Robert Hancock <hancockrwd@gmail.com> wrote: > On 11/09/2012 10:36 AM, Feng Tang wrote: >> >> On Fri, Nov 09, 2012 at 10:30:43PM +0800, Moore, Robert wrote: >>> >>> The ACPI Global Lock is in fact intended to provide exclusion between the >>> BIOS and the OS. >>> Bob >> >> >> Thanks for the info. >> >> And per my check, most of ACPI FW don't implement this lock, say >> after driver probe, the ec->global_lock will be 0. > > > The DSDT is supposed to define the _GLK control method on the EC if the BIOS > needs to perform its own access which may conflict with the OS usage. If it > doesn't, then it should be the case that either the BIOS doesn't touch the > EC itself or it uses a separate interface that doesn't cause conflicts with > what the OS is doing. > >> >> - Feng >> >>> >>> >>>> -----Original Message----- >>>> From: Tang, Feng >>>> Sent: Friday, November 09, 2012 1:29 AM >>>> To: Rafael J. Wysocki >>>> Cc: Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; Linux Kernel >>>> Mailing List; Zheng, Lv; Len Brown; Moore, Robert >>>> Subject: Re: ACPI errors with 3.7-rc3 >>>> >>>> On Thu, Nov 08, 2012 at 05:49:40AM +0800, 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)? >>>> >>>> >>>> I doubt this problem is sometimes inevitable for some machines, because >>>> AFAIK most modern machines have the race problem for EC HW controller, >>>> as >>>> both OS side and the BIOS may access the EC HW at the same time >>>> without any race control. >>>> >>>> For this case, usually the battery and thermal modules (which may be >>>> controlled through EC) are always monitored by BIOS, when OS also >>>> frequently visit them too, the EC's own state machine may be broken and >>>> not responsive due to the race, then cause the timeout error. >>>> And how severe the problem will be depends on the EC HW, the quality of >>>> BIOS code and OS/driver code. >>>> >>>> Myself have seen the similar "ACPI: EC: input buffer is not empty, >>>> aborting transaction" error message on one laptop when its EC is busy >>>> visited by OS. >>>> >>>> btw, in EC driver I see a "ec->global_lock", don't know if it was >>>> designed >>>> to control the race between OS and BIOS. >>>> >>>> Thanks, >>>> Feng >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in >> >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > -- Azat Khuzhin ^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: ACPI errors with 3.7-rc3 2012-12-01 20:59 ` Azat Khuzhin @ 2012-12-01 21:54 ` Azat Khuzhin 0 siblings, 0 replies; 26+ messages in thread From: Azat Khuzhin @ 2012-12-01 21:54 UTC (permalink / raw) To: Robert Hancock Cc: Feng Tang, Moore, Robert, Rafael J. Wysocki, Greg KH, linux-acpi@vger.kernel.org, Linux Kernel Mailing List, Zheng, Lv, Len Brown Update: laptop don't resume working not only after a long time held in suspend, but also after a short period of time for example 3 minutes. As for a long time - it about 24-36 hours. On Sun, Dec 2, 2012 at 12:59 AM, Azat Khuzhin <dohardgopro@gmail.com> wrote: > I tried this patch - https://bugzilla.kernel.org/attachment.cgi?id=73510 > from https://bugzilla.kernel.org/show_bug.cgi?id=14733. > > And I don't see such messages any more. > But another problem surfaced - laptop can't resume working after a > long time held in suspend, > end there is not messages in kern.log about that laptop trying to resume. > > On Sat, Nov 17, 2012 at 9:40 AM, Robert Hancock <hancockrwd@gmail.com> wrote: >> On 11/09/2012 10:36 AM, Feng Tang wrote: >>> >>> On Fri, Nov 09, 2012 at 10:30:43PM +0800, Moore, Robert wrote: >>>> >>>> The ACPI Global Lock is in fact intended to provide exclusion between the >>>> BIOS and the OS. >>>> Bob >>> >>> >>> Thanks for the info. >>> >>> And per my check, most of ACPI FW don't implement this lock, say >>> after driver probe, the ec->global_lock will be 0. >> >> >> The DSDT is supposed to define the _GLK control method on the EC if the BIOS >> needs to perform its own access which may conflict with the OS usage. If it >> doesn't, then it should be the case that either the BIOS doesn't touch the >> EC itself or it uses a separate interface that doesn't cause conflicts with >> what the OS is doing. >> >>> >>> - Feng >>> >>>> >>>> >>>>> -----Original Message----- >>>>> From: Tang, Feng >>>>> Sent: Friday, November 09, 2012 1:29 AM >>>>> To: Rafael J. Wysocki >>>>> Cc: Greg KH; Azat Khuzhin; linux-acpi@vger.kernel.org; Linux Kernel >>>>> Mailing List; Zheng, Lv; Len Brown; Moore, Robert >>>>> Subject: Re: ACPI errors with 3.7-rc3 >>>>> >>>>> On Thu, Nov 08, 2012 at 05:49:40AM +0800, 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)? >>>>> >>>>> >>>>> I doubt this problem is sometimes inevitable for some machines, because >>>>> AFAIK most modern machines have the race problem for EC HW controller, >>>>> as >>>>> both OS side and the BIOS may access the EC HW at the same time >>>>> without any race control. >>>>> >>>>> For this case, usually the battery and thermal modules (which may be >>>>> controlled through EC) are always monitored by BIOS, when OS also >>>>> frequently visit them too, the EC's own state machine may be broken and >>>>> not responsive due to the race, then cause the timeout error. >>>>> And how severe the problem will be depends on the EC HW, the quality of >>>>> BIOS code and OS/driver code. >>>>> >>>>> Myself have seen the similar "ACPI: EC: input buffer is not empty, >>>>> aborting transaction" error message on one laptop when its EC is busy >>>>> visited by OS. >>>>> >>>>> btw, in EC driver I see a "ec->global_lock", don't know if it was >>>>> designed >>>>> to control the race between OS and BIOS. >>>>> >>>>> Thanks, >>>>> Feng >>> >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in >>> >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> >> > > > > -- > Azat Khuzhin -- Azat Khuzhin ^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2013-01-27 12:37 UTC | newest] Thread overview: 26+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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
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).