cpufreqd crashed on startup

Bug #260567 reported by marcel
128
This bug affects 26 people
Affects Status Importance Assigned to Milestone
cpufreqd (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: cpufreqd

cpufreqd crashed on startup

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/cpufreqd
NonfreeKernelModules: nvidia
Package: cpufreqd 2.3.2-1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/sbin/cpufreqd -f /etc/cpufreqd.conf
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: cpufreqd
StacktraceTop:
 dlist_start () from /lib/libsysfs.so.2
 find_class_device ()
 acpi_ac_init ()
 ?? () from /usr/lib/cpufreqd/cpufreqd_acpi.so
 plugins_post_conf ()
Title: cpufreqd crashed with SIGSEGV in dlist_start()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups:

Revision history for this message
marcel (marcel-wojtek) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:find_class_device (
acpi_ac_init () at cpufreqd_acpi_ac.c:61
acpi_post_conf () at cpufreqd_acpi.c:74
plugins_post_conf (plugins=0x0) at plugin_utils.c:275
init_configuration (configuration=0x2133010)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in cpufreqd:
importance: Undecided → Medium
Revision history for this message
Ingo Bruell (ibruell) wrote :

i have the same problem since intrepid kernel.

/var/log/syslog:

Nov 30 10:33:14 ib-laptop cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:01/power_supply/C136/energy_full (No such file or directory)
Nov 30 10:33:14 ib-laptop cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:01/power_supply/C136/energy_now (No such file or directory)
Nov 30 10:33:14 ib-laptop cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/C137/energy_full (No such file or directory)
Nov 30 10:33:14 ib-laptop cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/C137/energy_now (No such file or directory)
Nov 30 10:33:14 ib-laptop acpid: client connected from 22227[0:0]
Nov 30 10:33:14 ib-laptop cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:01/power_supply/C136/energy_full (No such file or directory)
Nov 30 10:33:14 ib-laptop cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:01/power_supply/C136/energy_now (No such file or directory)
Nov 30 10:33:14 ib-laptop cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/C137/energy_full (No such file or directory)
Nov 30 10:33:14 ib-laptop cpufreqd: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/device:00/PNP0C0A:00/power_supply/C137/energy_now (No such file or directory)
Nov 30 10:33:14 ib-laptop kernel: [ 967.123934] cpufreqd[22227]: segfault at 0 ip b75fdd77 sp bfcb8b00 error 4 in cpufreqd_acpi.so[b75fb000+5000]

Revision history for this message
Ingo Bruell (ibruell) wrote :

what is going on here. Why no one will fix this bug ?

I have researched a little bit and found out, that the problem is the second battery. If i remove it, cpufreqd will not crash anymore.

Revision history for this message
Andrew Cleveland (evil-saltine) wrote :

It appears that a fix for this is present in 2.4.1 ( http://www.linux.it/~malattia/wiki/index.php/Cpufreqd ):

   " * Mattia Dongili (1):
        Fix segfault on reading the second battery value "

Revision history for this message
Andrew Cleveland (evil-saltine) wrote :
Changed in cpufreqd (Ubuntu):
status: New → Confirmed
Revision history for this message
sjn (steve-snewbury) wrote :

close_battery() is called after open_battery() fails, which obviously won't work! (close_battery() attempts to free unallocated memory; glibc detects info[x] is an invalid pointer)

A race condition exists between enumeration and reading of attributes, this is triggered in my case by the ACPI BIOS randomally making the battery disappear and reappear whilst transitioning between AC/Battery, it's much more likely to occur with multiple batteries due to the larger window .

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "cpufreqd-2.4.2-battery-crash.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Revision history for this message
1x6PY78 (1x6py78) wrote :
Changed in cpufreqd (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.