Distribution: SuSE Pro. 9.2 Hardware Environment: Fujitsu Siemens Amilo A1640 (Mobile AMD Sempron 2800+), 512MB RAM (with latest BIOS: 1.01c) Software Environment: console Problem Description: battery related method executions throw an AE_TIME error, and battery status couldn't be retrieved, if the touchpad is used during the call. Steps to reproduce: Use the touchpad (it's enough to simply touch it, you do not need X for it) then the kernel will say this if I want to read battery status (eg. with powersave -b): [ACPI Debug] String: [0x09] "BST Start" evregion-0405: *** Error: Handler for [EmbeddedControl] returned AE_TIME dswexec-0438 [473] ds_exec_end_op : [Store]: Could not resolve operands, AE_TIME psparse-1138: *** Error: Method execution failed [\_SB_.PCI0.BAT0._BST] (Node c1435668), AE_TIME acpi_battery-0208 [465] acpi_battery_get_statu: Error evaluating _BST [ACPI Debug] String: [0x03] "BIf" evregion-0405: *** Error: Handler for [EmbeddedControl] returned AE_TIME dswexec-0438 [474] ds_exec_end_op : [Store]: Could not resolve operands, AE_TIME psparse-1138: *** Error: Method execution failed [\_SB_.PCI0.BAT0._BIF] (Node c14356e8), AE_TIME acpi_battery-0147 [466] acpi_battery_get_info : Error evaluating _BIF If I use an external USB mouse, then everything is fine. I think it's similar to Bug 1093.
Created attachment 4364 [details] Dmesg output
Created attachment 4365 [details] Output of dmidecode
Created attachment 4366 [details] Output of acpidmp
Created attachment 4367 [details] Output of lspci -vv
Created attachment 4368 [details] Contents of /proc/interrupts
Created attachment 4369 [details] Disassembled DSDT I don't know whether you need this...
As Luming Yu suggested in Bug 1093 I'll try the patches from Bug 3851...
With the patches from Bug 3851 (the first hunk of ec-1 patch must be slightly hacked for 2.6.10) I don't get the AE_TIME error anymore. Instead I've got "psmouse.c: TouchPad at isa0060/serio2/input0 lost sync at byte 1", but only once yet. So far, so good... BTW may this bug be related to my PCMCIA problem? I simply can't make the PCMCIA socket work. Or is it another IRQ configuration problem demanding another bugreport?
*** This bug has been marked as a duplicate of 3851 ***