On Sun, Dec 21, 2008 at 04:40:28PM +0100, Jonas Zeiger wrote:
> Package: cpufreqd
> Version: 2.3.3-3
> Severity: grave
> Justification: renders package unusable
>
>
> I've been trying to run cpufreqd on a Dell Latitude D530
> Laptop with a Intel Core2Duo 2.00Ghz CPU, 3GB of DDR2 RAM
> and two attached battery units using the stock Debian kernel
> version 2.6.26, but the problem is exactly the same with my
> custom kernel 2.6.26zlinux (tuned for install on SSD).
>
> Cpufreqd keeps segfaulting when starting up the system:
...
> acpi_battery_init : found 2 Batteries
> acpi_battery_update : BAT0 - present
> read_battery : BAT0 - reading battery levels
> read_battery : BAT0 - remaining capacity: 5200000
> acpi_battery_update : battery life for BAT0 is 109%
> acpi_battery_update : BAT1 - present
> acpi_battery_update : BAT1 - estimating battery life (timeout: 30.00 -
> status: (null))
> Speicherzugriffsfehler /* german locale, it' a segfault! :( */
can you run cpufreqd in a gdb session (make sure to start it with -D so
that is doesn't deamonize) and get a stack trace of the segfault?
Also, don't forget to build it with debug symbols.
> Ok, i've already tried to patch cpufreqd_2.3.3-3 with some patch found
> on the net:
>
> (Downloaded cpufreqd_2.3.3-3.diff and cpufreqd_2.3.3.orig.tar.gz)
> $ tar xvzf cpufreqd_2.3.3.orig.tar.gz
> $ patch -p0 < cpufreqd_2.3.3-3.diff
> $ cd cpufreqd-2.3.3
> $ sudo apt-get install libsensors-dev libcpufreqd-dev
> $ patch -p0
> Index: src/cpufreqd_acpi.c
> ===================================================================
> RCS file: /cvsroot/cpufreqd/sources2/src/cpufreqd_acpi.c,v
> retrieving revision 1.8
> diff -u -r1.8 cpufreqd_acpi.c
> --- src/cpufreqd_acpi.c 31 Aug 2008 01:17:25 -0000 1.8
> +++ src/cpufreqd_acpi.c 1 Oct 2008 12:22:23 -0000
> @@ -246,8 +246,8 @@
>
> /* read `clsname` devices */
> devs = sysfs_get_class_devices(cls);
> - if (!cls) {
> - clog(LOG_INFO, "class '%s' not found (%s)\n", clsname,
> + if (!devs) {
> + clog(LOG_INFO, "class device '%s' not found (%s)\n", clsname,
> strerror(errno));
> sysfs_close_class(cls);
> return -1;
this shouldn't even apply as it's already applied to the debian package
when building.
thanks
--
mattia
:wq!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
