From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20070417 Fedora/18.104.22.168-4.fc7 Firefox/22.214.171.124
Description of problem:
Right after boot 'dmesg' shows ACPI exceptions already. And more and more are added. After some undefined period of time (say about 10 minutes) the system hangs with a kernel oops (probably because of this, haven't been able to copy this exact error yet). The above url shows dmesg output.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Just boot.
- Battery is not reckognized correctly.
- System hangs (I'm forced to power off).
My Notebook is an Acer Aspire 1640Z.
It worked fine with Fedora Core 6 (but then I had some other problems, which are fixed now :)
There doesn't seem to be any link to dmesg output in the bug report.
Can we get the exact error messages/ oops report?
Sorry, I hid it in the additional bug information (the URL points to it).
I provided three files now:
- One immediately after booting: (has only few errors at the end)
- One after some work: (same as in additional bug information)
- One immediately after booting with acpi=off:
I wouldn't know how to copy/paste the final bug, I tried to write something
down, if you need more information, I'll do it in more detail. The beginning
might be chopped of, I could not scroll further up.
Thanks very much for your time! Jonne.
Message from syslogd
localhost kernel: invalid opcode 0000 [#1]
localhost kernel: SMP
localhost kernel: CPU: 0
localhost kernel: EIP: 0060:[<c04f56f4>] Not tainted VLI
... show_trace_log_lvl ...
... show_stack_log_lvl ...
... show_registers ...
... die ...
... do_trap ...
... do_invalid_op ...
... error_code ...
... free_block ...
... drain_array ...
... cache_reap ...
... run_workqueue ...
... worker_thread ...
... kthread ...
... kernel_thread_helper ...
Same problem is still existent with this kernel
Really hope somebody has a workaround or fix for this.
Something changed with this kernel: (though I hope it's not only a change in
[root@localhost ~]# uname -a
Linux localhost 2.6.21-1.3149.fc7 #1 SMP Fri May 11 12:12:11 EDT 2007 i686 i686
[root@localhost ~]# rpm -qa |grep kernel
I still get these lines in 'dmesg'
ACPI Exception (battery-0216): AE_SUPPORT, Extracting _BST 
But they're *not* anymore followed by this:
slab error in verify_redzone_free(): cache `size-64': memory outside object was
Battery is still not working correctly.
Here is some (hopefully usuable) additional info:
[root@localhost ~]# cat /proc/acpi/battery/BAT1/state ; echo "return: $?"
ERROR: Unable to read battery status
[root@localhost ~]# grep . /proc/acpi/battery/* -r
/proc/acpi/battery/BAT1/state:ERROR: Unable to read battery status
/proc/acpi/battery/BAT1/info:design capacity: 2000 mAh
/proc/acpi/battery/BAT1/info:last full capacity: 65317 mAh
/proc/acpi/battery/BAT1/info:battery technology: rechargeable
/proc/acpi/battery/BAT1/info:design voltage: 14800 mV
/proc/acpi/battery/BAT1/info:design capacity warning: 300 mAh
/proc/acpi/battery/BAT1/info:design capacity low: 2612 mAh
/proc/acpi/battery/BAT1/info:capacity granularity 1: 32 mAh
/proc/acpi/battery/BAT1/info:capacity granularity 2: 32 mAh
/proc/acpi/battery/BAT1/info:model number: 12ZL
/proc/acpi/battery/BAT1/info:serial number: 20064
/proc/acpi/battery/BAT1/info:battery type: LION
/proc/acpi/battery/BAT1/info:OEM info: SONY
I'm afraid it could also be some hardware problem that occurred when upgrading
to F7. With the Knoppix dvd (KNOPPIX_V5.1.1DVD-2007-01-04-EN with 2.6.x kernel)
the same problem arises.
Here's dmesg output:
Anybody knows what I can do to be sure? Should I replace the battery??
Sorry, typo in the URL, should have been
in the previous comment.
Same problem occurred with replaced battery. It is a software bug, right?
I know have kernel-2.6.21-1.3194.fc7 and it still shows the battery exception, see:
any advice on what I can try?
I was able to replace the battery with someone elses and that solved the
problem. Hence, I must conclude it's very likely to be hardware failure.
The battery exception was a good indication for that, so I guess I should not
have filed this bug report (although such a thing is frustrating and hard to
check or be sure). So, thanks everybody for helping and I'll close this bug.