|
Bugzilla – Full Text Bug Listing |
| Summary: | Kernel does'nt update /proc/acpi/battery/*/state on Laptop HP Compaq nx6125 | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Tob Sch <Tob_Sch> |
| Component: | Kernel | Assignee: | Thomas Renninger <trenn> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | ihno, suse-beta |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | output from command "acpidump" | ||
|
Description
Tob Sch
2006-08-07 14:03:57 UTC
Sometimes the kernel hangs (without any messages). Sometimes I get following message (without kernel hanging): Aug 7 16:03:23 MyLaptop [powersave]: WARNING (continueEvent:264) Could not exec ute program /usr/lib/powersave/scripts for event daemon.scheme.change: No such f ile or directory Retrieving the battery state is an ACPI function. > That seems to be a kernel bug :-( Or BIOS. Best you search for the newest BIOS of the machine first. If you still have problems, please attach acpidump and dmesg output. This is probably a duplicate of: http://bugzilla.kernel.org/show_bug.cgi?id=5534 We also have such a machine. I try to have a look at it this week. -> Still better go for the latest BIOS. The same happens with the newest BIOS (F.OF) from http://h18007.www1.hp.com/support/files/hpcpqnk/us/locate/64_6170.html#0 Created attachment 95484 [details]
output from command "acpidump"
Holger/Seife: Aug 7 16:03:23 MyLaptop [powersave]: WARNING (continueEvent:264) Could not execute program /usr/lib/powersave/scripts for event daemon.scheme.change: No such file or directory Any idea how that could happen The nx6125 has ACPI problems with current kernels, also see: http://bugzilla.kernel.org/show_bug.cgi?id=5534 I currently try to figure out what is going wrong here, but it's complicated... This is probably a duplicate... Does boot parameter: ec_intr=0 help here? *** This bug has been marked as a duplicate of bug 200169 *** |