Bug 4845
Summary: | New battery generates AE_AML_BUFFER_LIMIT error | ||
---|---|---|---|
Product: | ACPI | Reporter: | Manuel Silva (msilva) |
Component: | Power-Battery | Assignee: | acpi_power-battery |
Status: | REJECTED WILL_NOT_FIX | ||
Severity: | normal | ||
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.4.26, 2.4.31 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | dmesg output |
Description
Manuel Silva
2005-07-05 09:02:11 UTC
Created attachment 5269 [details]
dmesg output
output from the error taken from dmesg. That occurs at GNU/Linux boot and each
time the battery is inserted.
Please test 2.6.13-rc1-mm1 Hello! I made several other tests and I found that the battery status is read with kernel 2.6.12 but I'm not used to compile the kernel and I forgot a few things (including network) and I wasn't able to find out where network chipsets were in the GTK configuration tool ("make gconfig") so I decided to try a distro with a kernel closed to 2.6.12 and I chose Mandriva (2.6.11-6mdk) and it worked also. The only problem I register with all 2.6.x kernels (even when I was using my previous battery) is that it doesn't update battery status oftenly. Is there any 2.4 kernel with the same ACPI updates that were made since 2.6.7 or any way to compile 2.6.12 (or .13) with, at least, the same options that were used to compile the Slackware one (which is 2.4)? Kind regards, Manuel Silva The problem persists under the latest stable 2.4 kernel tree (2.4.31). It seems to be partially solved once unplugging and replugging power cord the /proc/acpi/battery/BAT1 becomes usable to get all information about the battery. Is it reliable to use ACPI sources from kernel 2.6 under kernel 2.4? I'm sorry, if it isnt' data corruption, we don't have the bandwidth to backport 2.6 ACPI fixes to 2.4 -- there are not enough testers. Thanks for testing with 2.6, hopefully you'll be able to upgrade for real. |