cpufreq-selector hangs

Bug #511794 reported by klausner
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gnome-applets (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: gnome-applets

In Unbuntu 9.10, cpufreq-selector hangs from the command line. If I enter something like "cpufreq-selector -c 0 -g ondemand", nothing happens. Literally. The only way to get back to a prompt is to use Ctl-C. The -h option works, but -c, -f, or -g hang if used with valid arguments. If used with invalid arguments, it gives an error message, and then hangs.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Please try to obtain a backtrace of that hang following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-applets (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
klausner (klausner) wrote :

Reinstalled:

    * gnome-applets
    * gnome-applets-data
    * libpanel-applets2-0

and solved problem.

Revision history for this message
Phillip Susi (psusi) wrote :

Marking as invalid since the user fixed it by reinstalling.

Changed in gnome-applets (Ubuntu):
status: Incomplete → Invalid
Bogdan (agresso)
Changed in gnome-applets (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

don't reopen bugs without a comment

Changed in gnome-applets (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: Confirmed → Invalid
Revision history for this message
karatedog (karatedog) wrote :

I can confirm that cpufreq-selector has strange behavior in Ubuntu 10.04.

cpufreq-selector never hangs, it is just very slow if issued this way: 'sudo cpufreq-selector -c 1 -g performance'
I noticed that it takes almost exactly 30 seconds to finish the operation, which is strange.

$ time sudo cpufreq-selector -c 1 -g performance
real 0m30.300s
user 0m0.008s
sys 0m0.004s

$ time sudo cpufreq-selector -c 1 -g performance
real 0m30.252s
user 0m0.004s
sys 0m0.004s

$ time sudo cpufreq-selector -c 1 -g performance
real 0m30.061s
user 0m0.004s
sys 0m0.004s

However if I set SUID on 'cpufreq-selector' and issue: 'cpufreq-selector -c 1 -g performance', it will be lightning fast, tested about 1000 times.

Revision history for this message
karatedog (karatedog) wrote :

$ strace cpufreq-selector -c 1 -g performance

......
gettimeofday({1275498260, 793905}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}], 3, 0) = 0 (Timeout)
gettimeofday({1275498260, 794152}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}], 3, 0) = 0 (Timeout)
gettimeofday({1275498260, 794270}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}], 3, 0) = 0 (Timeout)
gettimeofday({1275498260, 794392}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}], 3, 0) = 0 (Timeout)
gettimeofday({1275498260, 794489}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}], 3, 0) = 0 (Timeout)
gettimeofday({1275498260, 794562}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}], 3, 0) = 0 (Timeout)
gettimeofday({1275498260, 794749}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}], 3, 0) = 0 (Timeout)
gettimeofday({1275498260, 794812}, NULL) = 0
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}], 3, 30000

Is this that 30 seconds?

Changed in gnome-applets (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
vsespb (vi1tsr) wrote :

I am having same problem, same strace.

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.