cpufreqd assert failure: *** glibc detected *** /usr/sbin/cpufreqd: free(): invalid pointer: 0x08d1cec8 ***

Bug #755639 reported by cocoon
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cpufreqd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: cpufreqd

I use laptop. When i added battery, cpufreq is crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: cpufreqd 2.4.2-1 [modified: usr/bin/cpufreqd-get usr/bin/cpufreqd-set usr/sbin/cpufreqd]
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/sbin/cpufreqd: free(): invalid pointer: 0x08d1cec8 ***
Date: Sun Apr 10 01:26:16 2011
ExecutablePath: /usr/sbin/cpufreqd
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/sbin/cpufreqd -f /etc/cpufreqd.conf
ProcEnviron: PATH=(custom, no user)
Signal: 6
SourcePackage: cpufreqd
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
Title: cpufreqd assert failure: *** glibc detected *** /usr/sbin/cpufreqd: free(): invalid pointer: 0x08d1cec8 ***
UpgradeStatus: Upgraded to natty on 2011-04-01 (8 days ago)
UserGroups:

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #733507, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.