Bug 492699 - kernel shows ACPI errors (battery?) on Asus eeepc 1002HA
Summary: kernel shows ACPI errors (battery?) on Asus eeepc 1002HA
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-28 14:53 UTC by Michal Jaegermann
Modified: 2010-06-28 11:35 UTC (History)
1 user (show)

Fixed In Version: 2.6.30.9-90.fc11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 11:35:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg output for 2.6.27.19-170.2.35.fc10.i686 (32.76 KB, text/plain)
2009-03-28 14:53 UTC, Michal Jaegermann
no flags Details
dmidecode for the board in question (9.31 KB, text/plain)
2009-03-28 14:55 UTC, Michal Jaegermann
no flags Details
acpidump output (104.76 KB, text/plain)
2009-03-28 14:56 UTC, Michal Jaegermann
no flags Details
/proc/ioports (1.21 KB, text/plain)
2009-03-28 14:58 UTC, Michal Jaegermann
no flags Details
an output from 'lspci -tv' (1.24 KB, text/plain)
2009-03-28 14:59 UTC, Michal Jaegermann
no flags Details
dmesg output for 2.6.31.5-96.fc12.i686 (35.00 KB, application/octet-stream)
2009-10-31 19:21 UTC, Michal Jaegermann
no flags Details
dmesg output for 2.6.32.10-90.fc12.i686 (36.19 KB, text/plain)
2010-04-03 20:51 UTC, Michal Jaegermann
no flags Details

Description Michal Jaegermann 2009-03-28 14:53:50 UTC
Created attachment 337106 [details]
dmesg output for 2.6.27.19-170.2.35.fc10.i686

Description of problem:

Errors like that show up with various kernels I tried - either right after boot or after attempts to access a battery information:

ACPI: EC: missing confirmations, switch off interrupt mode.
ACPI Exception (evregion-0419): AE_TIME, Returned by Handler for [EmbeddedControl] [20080609]
ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.BST2] (Node f7815e58), AE_TIME
ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.PCI0.CBST] (Node f7816fc0), AE_TIME
ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.PCI0.BAT0._BST] (Node f7816f00), AE_TIME
ACPI Exception (battery-0360): AE_TIME, Evaluating _BST [20080609]

Some battery information is returned after all but with all the above it is hard to be sure what it may really mean.  That seems to be quite similar to bug 472650 only it does not seem to be as critical as reported there.

I cannot really tell if:

ACPI: I/O resource 0000:00:1f.3 [0x400-0x41f] conflicts with ACPI region SMRG [0
x400-0x40f]
ACPI: Device needs an ACPI driver

is directly related or this is another issue.  "0000:00:1f.3" looks like
"Intel Corporation 82801G (ICH7 Family) SMBus Controller".

Attached is dmesg for 2.6.27.19-170.2.35.fc10.i686 and other information


Version-Release number of selected component (if applicable):
kernel-2.6.27.19-170.2.35.fc10.i686
kernel-2.6.29-3.fc10.i686 (from koji)

How reproducible:
always

Comment 1 Michal Jaegermann 2009-03-28 14:55:40 UTC
Created attachment 337107 [details]
dmidecode for the board in question

Comment 2 Michal Jaegermann 2009-03-28 14:56:46 UTC
Created attachment 337108 [details]
acpidump output

Comment 3 Michal Jaegermann 2009-03-28 14:58:13 UTC
Created attachment 337109 [details]
/proc/ioports

Comment 4 Michal Jaegermann 2009-03-28 14:59:15 UTC
Created attachment 337110 [details]
an output from 'lspci -tv'

Comment 5 Michal Jaegermann 2009-04-28 04:23:23 UTC
With 2.6.29.1-42.fc10.i686 kernel from "updates-testing" I see really the same.
Various identifiers are slightly different.  Here we go for the record:

ACPI: EC: missing confirmations, switch off interrupt mode.
ACPI Exception (evregion-0422): AE_TIME, Returned by Handler for [EmbeddedControl] [20081204]
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.EBTS] (Node f6c14e88), AE_TIME
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.UBCS] (Node f6c15e40), AE_TIME
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.CBST] (Node f6c15fc0), AE_TIME
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.BAT0._BST] (Node f6c15f00), AE_TIME
ACPI Exception (battery-0382): AE_TIME, Evaluating _BST [20081204]

Comment 6 Bug Zapper 2009-06-09 12:46:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Chuck Ebbert 2009-10-06 07:34:02 UTC
Should be fixed in 2.6.30.9-74

Comment 8 Fedora Update System 2009-10-18 01:56:38 UTC
kernel-2.6.30.9-90.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/kernel-2.6.30.9-90.fc11

Comment 9 Fedora Update System 2009-10-27 06:46:33 UTC
kernel-2.6.30.9-90.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Chuck Ebbert 2009-10-30 17:55:55 UTC
Reopen the bug if this is not fixed.

Comment 11 Michal Jaegermann 2009-10-31 19:18:59 UTC
> Reopen the bug if this is not fixed.

OK.  This is for 2.6.31.5-96.fc12.i686 used on the latest rawhide installation images:
.....
ACPI: EC: missing confirmations, switch off interrupt mode.
ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] 20090521 evregion-424
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.EBTS] (Node f6c13e88), AE_TIME
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.UBCS] (Node f6c14e40), AE_TIME
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.CBST] (Node f6c14fc0), AE_TIME
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.BAT0._BST] (Node f6c14f00), AE_TIME
ACPI Exception: AE_TIME, Evaluating _BST 20090521 battery-385

Not precisely the same as the original but it looks quite similar.
Full dmesg output attached.

Comment 12 Michal Jaegermann 2009-10-31 19:21:03 UTC
Created attachment 366967 [details]
dmesg output for 2.6.31.5-96.fc12.i686

Comment 13 Chuck Ebbert 2010-03-25 15:11:46 UTC
The latest problems is a new bug, should be fixed in 2.6.32.10-45.fc11

Comment 14 Michal Jaegermann 2010-04-03 20:50:37 UTC
(In reply to comment #13)
> The latest problems is a new bug, should be fixed in 2.6.32.10-45.fc11    

The netbook which showed these errors is running now Fedora 12.  Indeed
I do not see errors like reported previously anymore.  With 2.6.32.10-90.fc12.i686 I have

ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P6._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT]

(a full dmesg from 2.6.32.10-90.fc12.i686 attached for a reference).

The only remaining visible ACPI issue is that:

eeepc_laptop: Eee PC Hotkey Driver
i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ACPI: I/O resource 0000:00:1f.3 [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f]
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver 

with 0000:00:1f.3 beeing "Intel Corporation 82801G (ICH7 Family) SMBus Controller".  That looks like something entirely different (although I am not sure how to pick up this "instead" with a distribution kernel).

Comment 15 Michal Jaegermann 2010-04-03 20:51:41 UTC
Created attachment 404343 [details]
dmesg output for 2.6.32.10-90.fc12.i686

Comment 16 Bug Zapper 2010-04-27 13:21:25 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 17 Bug Zapper 2010-06-28 11:35:15 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.