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

StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=2, fmt=0x24a73c "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=<value optimized out>, str=<value optimized out>, ptr=0x9067b10) at malloc.c:6283

This forum comment from Debian project may be of interest. Has anyone else tested if this is a "reboot/resume" issue for them only, as well? I'll try testing tonight.
http://forums.debian.net/viewtopic.php?f=10&t=70191

With some debugging I found, that cpufreqd crashes within the plugin cpufreqd_acpi.so. The function acpi_battery_update tries to read battery information in sysfs (/sys directory) with libsysfs functions. Because of an invalid pointer cpufreqd crashes here.

I could work around this bug with renaming the cpufreqd_acpi.so plugin. Unfortunately the functions of this plugin are essential. Without this plugin cpufreqd cannot read battery status and other important information.

There are actually two bugs in cpufreqd_acpi_battery.c:

1. update_battery() doesn't check whether a battery is open or not. This causes the SIGSEGV

2. init_battery() doesn't know about that attribute current_now has been replaced by power_now in recent kernels.

Both bugs are fixed with the patch attached to this comment.

The attachment "A fix for this bug." 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.]

This affects me as well.

Just tested the attached patch from comment #7 and can confirm (as far as i can test) that this fixes the reported problem.

Also can confirm this patch works. Kubuntu 12.10 (Lenovo T430) and Kubuntu 12.03 (Lenovo T500)

Mhhh, strange that there is no effort in Ubuntu AND Debian to fix this problem. A working patch is known since nearly one year but no effort is shown in both distros to fix this.

I second that. I run cpufreqd with this patch applied since 2012-04-05 on my laptop for everydays work which is heavily loaded and cpufreqd makes a big difference for me with respect to noise and battery lifetime under heavy load. The apparent lack of interest in fixing that is puzzling: is Ubuntu not interested in good user experience for laptop users?

There seems to be some activity on debian:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619913#25

This patch will probably shipped with cpufreqd in wheezy.

Ah, it's fixed in debian with cpufreqd 2.4.2-2 (see bugreport above)

Should be fixed in raring with this release:

http://changelogs.ubuntu.com/changelogs/pool/universe/c/cpufreqd/cpufreqd_2.4.2-2/changelog