ACPI errors with 3.7-rc3

DISCUSSION Greg KH 8 participants 26 messages Oct 31, 2012 – Jan 27, 2013 ACPI

lore

Share & tools

lore

Greg KH

author

2012-10-31 01:44 UTC #0 lore raw

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

Rafael J. Wysocki

2012-10-31 09:07 UTC #1 lore raw

Hi Greg,

Quoted 12 lines · Greg KH

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)

Quoted 3 lines

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 <[email protected]>
Date:   Fri Sep 28 15:22:01 2012 +0800

ACPI: EC: Add a quirk for CLEVO M720T/M730T laptop

commit a520d52e99b14ba7db135e916348f12f2a6e09be

Author: Feng Tang <[email protected]>
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

Signature · 2 lines

I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

Greg KH

author

2012-10-31 17:33 UTC #2 lore raw

Quoted 27 lines · Rafael J. Wysocki

Hi Greg,
Quoted 12 lines · Greg KH
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)
Quoted 3 lines
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 <[email protected]>
Date:   Fri Sep 28 15:22:01 2012 +0800
ACPI: EC: Add a quirk for CLEVO M720T/M730T laptop

Quoted 7 lines

commit a520d52e99b14ba7db135e916348f12f2a6e09be
Author: Feng Tang <[email protected]>
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

Azat Khuzhin

2012-11-06 12:42 UTC #3 lore raw

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

Quoted 42 lines · Greg KH

Quoted 27 lines · Rafael J. Wysocki
Hi Greg,
Quoted 12 lines · Greg KH
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)
Quoted 3 lines
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 <[email protected]>
Date:   Fri Sep 28 15:22:01 2012 +0800
ACPI: EC: Add a quirk for CLEVO M720T/M730T laptop
Quoted 7 lines
commit a520d52e99b14ba7db135e916348f12f2a6e09be
Author: Feng Tang <[email protected]>
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.

Quoted 8 lines

thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

--
Azat Khuzhin

Greg KH

author

2012-11-06 12:48 UTC #4 lore raw

Quoted 18 lines · Azat Khuzhin

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

Quoted 8 lines

(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.

Quoted 8 lines

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

2012-11-06 13:04 UTC #5 lore raw

When this messages appears, I was running from AC, not from battery.

Quoted 59 lines · Greg KH

Quoted 18 lines · Azat Khuzhin

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

Quoted 8 lines

(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.

Quoted 8 lines

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

Signature · 1 line

Azat Khuzhin

Rafael J. Wysocki

2012-11-07 21:45 UTC #6 lore raw

In reply to Greg KH

Quoted 50 lines · Greg KH

Quoted 18 lines · Azat Khuzhin

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

Quoted 8 lines

(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.

Quoted 8 lines

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

Quoted 5 lines

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

Signature · 2 lines

I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

Greg KH

author

2012-11-08 04:47 UTC #7 lore raw

Quoted 51 lines · Rafael J. Wysocki

Quoted 50 lines · Greg KH

Quoted 18 lines · Azat Khuzhin

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

Quoted 8 lines

(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.

Quoted 8 lines

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

Quoted 7 lines

Quoted 5 lines
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

2012-11-08 09:15 UTC #8 lore raw

Here is mine - https://gist.github.com/4037687

To Greg:
acpidump 20100513-3.1
And I don't have pmtools installed

Quoted 71 lines · Greg KH

Quoted 51 lines · Rafael J. Wysocki
Quoted 50 lines · Greg KH
Quoted 18 lines · Azat Khuzhin
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
Quoted 8 lines
(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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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

Signature · 1 line

Azat Khuzhin

Rafael J. Wysocki

2012-11-08 09:23 UTC #9 lore raw

In reply to Greg KH

Quoted 60 lines · Greg KH

Quoted 51 lines · Rafael J. Wysocki
Quoted 50 lines · Greg KH
Quoted 18 lines · Azat Khuzhin
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
Quoted 8 lines
(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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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)?

Quoted 7 lines

# ./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

Signature · 2 lines

I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

Carlos R. Mafra

2013-01-26 12:22 UTC #10 lore raw

In reply to Greg KH

Quoted 60 lines · Greg KH

Quoted 51 lines · Rafael J. Wysocki
Quoted 50 lines · Greg KH
Quoted 18 lines · Azat Khuzhin
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
Quoted 8 lines
(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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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)?

Quoted 7 lines

# ./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?

Rafael J. Wysocki

2013-01-26 13:17 UTC #11 lore raw

Quoted 98 lines · Carlos R. Mafra

Quoted 60 lines · Greg KH

Quoted 51 lines · Rafael J. Wysocki
Quoted 50 lines · Greg KH
Quoted 18 lines · Azat Khuzhin
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
Quoted 8 lines
(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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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)?

Quoted 7 lines

# ./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.

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)

Quoted 1 line

Anyone has more information about this?

Is acpidump still not working?

What's under /sys/firmware/acpi/tables/ ?

Rafael

Signature · 2 lines

I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

Carlos R. Mafra

2013-01-26 13:39 UTC #12 lore raw

Quoted 99 lines · Rafael J. Wysocki

Quoted 98 lines · Carlos R. Mafra

Quoted 60 lines · Greg KH

Quoted 51 lines · Rafael J. Wysocki
Quoted 50 lines · Greg KH
Quoted 18 lines · Azat Khuzhin
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
Quoted 8 lines
(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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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)?

Quoted 7 lines

# ./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.

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)

Quoted 3 lines

Quoted 1 line
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

Quoted 1 line

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?

Rafael J. Wysocki

2013-01-26 13:49 UTC #13 lore raw

Quoted 118 lines · Carlos R. Mafra

Quoted 99 lines · Rafael J. Wysocki
Quoted 98 lines · Carlos R. Mafra
Quoted 60 lines · Greg KH
Quoted 51 lines · Rafael J. Wysocki
Quoted 50 lines · Greg KH
Quoted 18 lines · Azat Khuzhin
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
Quoted 8 lines
(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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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)?
Quoted 7 lines
# ./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)
Quoted 3 lines
Quoted 1 line
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
Quoted 1 line
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

Quoted 5 lines

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

Signature · 2 lines

I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

Azat Khuzhin

2013-01-26 21:23 UTC #14 lore raw

In reply to Carlos R. Mafra

Carlos, did you try this patch?

https://bugzilla.kernel.org/attachment.cgi?id=73510

Quoted 123 lines · Carlos R. Mafra

Quoted 99 lines · Rafael J. Wysocki
Quoted 98 lines · Carlos R. Mafra
Quoted 60 lines · Greg KH
Quoted 51 lines · Rafael J. Wysocki
Quoted 50 lines · Greg KH
Quoted 18 lines · Azat Khuzhin
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
Quoted 8 lines
(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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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)?
Quoted 7 lines
# ./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)
Quoted 3 lines
Quoted 1 line
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
Quoted 1 line
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?

Signature · 1 line

Azat Khuzhin

Carlos R. Mafra

2013-01-27 12:37 UTC #15 lore raw

Quoted 3 lines · Azat Khuzhin

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. ]

Quoted 129 lines · Carlos R. Mafra

Quoted 123 lines · Rafael J. Wysocki
Quoted 99 lines · Carlos R. Mafra
Quoted 98 lines · Greg KH
Quoted 60 lines · Rafael J. Wysocki
Quoted 51 lines · Greg KH
Quoted 50 lines · Azat Khuzhin
Quoted 18 lines
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
Quoted 8 lines
(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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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)?
Quoted 7 lines
# ./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)
Quoted 3 lines
Quoted 1 line
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
Quoted 1 line
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?
Signature · 1 line
Azat Khuzhin

Feng Tang

2012-11-09 09:29 UTC #16 lore raw

In reply to Rafael J. Wysocki

Quoted 51 lines · Rafael J. Wysocki

Quoted 50 lines · Greg KH

Quoted 18 lines · Azat Khuzhin

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

Quoted 8 lines

(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.

Quoted 8 lines

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

Quoted 7 lines

Quoted 5 lines
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

Moore, Robert

2012-11-09 14:30 UTC #17 lore raw

The ACPI Global Lock is in fact intended to provide exclusion between the BIOS and the OS. Bob

Quoted 96 lines

-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 1:29 AM
To: Rafael J. Wysocki
Cc: Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert
Subject: Re: ACPI errors with 3.7-rc3
Quoted 58 lines · Rafael J. Wysocki
Quoted 57 lines · Greg KH
Quoted 20 lines · Azat Khuzhin
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)
Quoted 8 lines
[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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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

Feng Tang

2012-11-09 16:37 UTC #18 lore raw

Quoted 2 lines · Robert

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

Quoted 98 lines

Quoted 98 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 1:29 AM
To: Rafael J. Wysocki
Cc: Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert
Subject: Re: ACPI errors with 3.7-rc3
Quoted 58 lines · Rafael J. Wysocki
Quoted 57 lines · Greg KH
Quoted 20 lines · Azat Khuzhin
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)
Quoted 8 lines
[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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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

Moore, Robert

2012-11-09 16:45 UTC #19 lore raw

Quoted 2 lines

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.

Quoted 125 lines

-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 8:36 AM
To: Moore, Robert
Cc: Rafael J. Wysocki; Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown
Subject: Re: ACPI errors with 3.7-rc3
Quoted 1 line · Robert
The ACPI Global Lock is in fact intended to provide exclusion between
the BIOS and the OS.
Quoted 1 line
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
Quoted 15 lines
Quoted 15 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 1:29 AM
To: Rafael J. Wysocki
Cc: Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert
Subject: Re: ACPI errors with 3.7-rc3
Quoted 4 lines · Rafael J. Wysocki
Quoted 3 lines · Greg KH
Quoted 2 lines · Azat Khuzhin
I'v also have such errors on my macbook pro.
Quoted 14 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
$ 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
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
[\_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:
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 13 lines
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)
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
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:
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
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
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
ec_storm_threshold is still set to 8 in /sys/module/acpi/parameters/ so that's not the issue here.
Quoted 3 lines
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.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
(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
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
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)?
Quoted 22 lines
Quoted 22 lines
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

2012-11-11 10:00 UTC #20 lore raw

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?

Quoted 134 lines · Robert

Quoted 2 lines
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.
Quoted 125 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 8:36 AM
To: Moore, Robert
Cc: Rafael J. Wysocki; Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown
Subject: Re: ACPI errors with 3.7-rc3
Quoted 1 line · Robert
The ACPI Global Lock is in fact intended to provide exclusion between
the BIOS and the OS.
Quoted 1 line
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
Quoted 15 lines
Quoted 15 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 1:29 AM
To: Rafael J. Wysocki
Cc: Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert
Subject: Re: ACPI errors with 3.7-rc3
Quoted 4 lines · Rafael J. Wysocki
Quoted 3 lines · Greg KH
Quoted 2 lines · Azat Khuzhin
I'v also have such errors on my macbook pro.
Quoted 14 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
$ 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
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
[\_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:
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 13 lines
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)
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
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:
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
Quoted 11 lines
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
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
ec_storm_threshold is still set to 8 in /sys/module/acpi/parameters/ so that's not the issue here.
Quoted 3 lines
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.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
(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
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
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)?
Quoted 22 lines
Quoted 22 lines
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

Signature · 1 line

Azat Khuzhin

Moore, Robert

2012-11-13 00:41 UTC #21 lore raw

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.

Quoted 165 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Azat Khuzhin
Sent: Sunday, November 11, 2012 2:01 AM
To: Moore, Robert
Cc: Tang, Feng; Rafael J. Wysocki; Greg KH; [email protected]; 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?
Quoted 4 lines · Robert
Quoted 2 lines
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.
Quoted 2 lines
I believe that the ACPI specification requires that the global lock be
present.
Quoted 118 lines
Quoted 118 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 8:36 AM
To: Moore, Robert
Cc: Rafael J. Wysocki; Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown
Subject: Re: ACPI errors with 3.7-rc3
Quoted 2 lines · Robert
The ACPI Global Lock is in fact intended to provide exclusion between
the BIOS and the OS.
Quoted 1 line
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
Quoted 15 lines
Quoted 15 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 1:29 AM
To: Rafael J. Wysocki
Cc: Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert
Subject: Re: ACPI errors with 3.7-rc3
Quoted 4 lines · Rafael J. Wysocki
Quoted 3 lines · Greg KH
Quoted 2 lines · Azat Khuzhin
I'v also have such errors on my macbook pro.
Quoted 15 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
$ 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
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
(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:
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 13 lines
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)
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
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:
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
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
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
ec_storm_threshold is still set to 8 in /sys/module/acpi/parameters/ so that's not the issue here.
Quoted 4 lines
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.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
(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
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
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)?
Quoted 6 lines
Quoted 6 lines
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.
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
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.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
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.
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
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

2012-11-14 17:33 UTC #22 lore raw

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)

Quoted 174 lines · Robert

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.
Quoted 165 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Azat Khuzhin
Sent: Sunday, November 11, 2012 2:01 AM
To: Moore, Robert
Cc: Tang, Feng; Rafael J. Wysocki; Greg KH; [email protected]; 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?
Quoted 4 lines · Robert
Quoted 2 lines
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.
Quoted 2 lines
I believe that the ACPI specification requires that the global lock be
present.
Quoted 118 lines
Quoted 118 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 8:36 AM
To: Moore, Robert
Cc: Rafael J. Wysocki; Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown
Subject: Re: ACPI errors with 3.7-rc3
Quoted 2 lines · Robert
The ACPI Global Lock is in fact intended to provide exclusion between
the BIOS and the OS.
Quoted 1 line
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
Quoted 15 lines
Quoted 15 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 1:29 AM
To: Rafael J. Wysocki
Cc: Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert
Subject: Re: ACPI errors with 3.7-rc3
Quoted 4 lines · Rafael J. Wysocki
Quoted 3 lines · Greg KH
Quoted 2 lines · Azat Khuzhin
I'v also have such errors on my macbook pro.
Quoted 15 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
$ 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
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
(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:
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 13 lines
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)
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
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:
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
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
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
ec_storm_threshold is still set to 8 in /sys/module/acpi/parameters/ so that's not the issue here.
Quoted 4 lines
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.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
(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
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
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)?
Quoted 6 lines
Quoted 6 lines
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.
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
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.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
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.
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
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

Signature · 1 line

Azat Khuzhin

Robert Hancock

2012-11-17 05:40 UTC #23 lore raw

In reply to Feng Tang

Quoted 8 lines · Feng Tang

Quoted 2 lines · Robert
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.

Quoted 106 lines

- Feng
Quoted 93 lines
Quoted 93 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 1:29 AM
To: Rafael J. Wysocki
Cc: Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert
Subject: Re: ACPI errors with 3.7-rc3
Quoted 58 lines · Rafael J. Wysocki
Quoted 57 lines · Greg KH
Quoted 20 lines · Azat Khuzhin
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)
Quoted 8 lines
[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.
Quoted 8 lines
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
Quoted 7 lines
Quoted 5 lines
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.
Quoted 5 lines
Quoted 5 lines
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Azat Khuzhin

2012-12-01 20:59 UTC #24 lore raw

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.

Quoted 15 lines · Robert Hancock

Quoted 8 lines · Feng Tang
Quoted 4 lines · Robert
The ACPI Global Lock is in fact intended to provide exclusion between the BIOS and the OS.
Bob
Quoted 4 lines
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.

Quoted 125 lines

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.
Quoted 118 lines
- Feng
Quoted 102 lines
Quoted 102 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 1:29 AM
To: Rafael J. Wysocki
Cc: Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert
Subject: Re: ACPI errors with 3.7-rc3
Quoted 66 lines · Rafael J. Wysocki
Quoted 64 lines · Greg KH
Quoted 21 lines · Azat Khuzhin
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)
Quoted 8 lines
[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.
Quoted 8 lines
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 :)
Quoted 6 lines
Quoted 2 lines
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.
Quoted 6 lines
Quoted 6 lines
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
Azat Khuzhin

Azat Khuzhin

2012-12-01 21:59 UTC #25 lore raw

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.

Quoted 154 lines · Azat Khuzhin

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.
Quoted 15 lines · Robert Hancock
Quoted 8 lines · Feng Tang
Quoted 4 lines · Robert
The ACPI Global Lock is in fact intended to provide exclusion between the BIOS and the OS.
Bob
Quoted 4 lines
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.
Quoted 125 lines
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.
Quoted 118 lines
- Feng
Quoted 102 lines
Quoted 102 lines
-----Original Message-----
From: Tang, Feng
Sent: Friday, November 09, 2012 1:29 AM
To: Rafael J. Wysocki
Cc: Greg KH; Azat Khuzhin; [email protected]; Linux Kernel Mailing List; Zheng, Lv; Len Brown; Moore, Robert
Subject: Re: ACPI errors with 3.7-rc3
Quoted 66 lines · Rafael J. Wysocki
Quoted 64 lines · Greg KH
Quoted 21 lines · Azat Khuzhin
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)
Quoted 8 lines
[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.
Quoted 8 lines
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 :)
Quoted 6 lines
Quoted 2 lines
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.
Quoted 6 lines
Quoted 6 lines
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Azat Khuzhin

Signature · 1 line

Azat Khuzhin