Hello!
On Mon, Apr 24, 2006 at 01:51:09AM -0500, anoop aryal wrote:
> Package: cpufrequtils
> Version: 001-2
> Severity: normal
>
>
> as cpufreq-set defaults to cpu 0 and /etc/init.d/cpufrequtils doesn't
> call cpufreq-set with cpu ids, it ends up not setting any options for
> the second (virtual) cpu on a 'core duo' processor. i've done the
doh. Silly me for not thinking of it... Ah, if I only had a
multiprcessor platform... :)
But do really the Duo processor can swith frequencies independently for
the 2 cores?
Just for the records, could you send the output of cpufreq-info?
> following to make it work for me but the line '/bin/true' was added to
> pacify log_action_end_msg so that probably needs to be fixed.
Indeed, it does need fixing. Using log_action_* functions to tell if the
action ended successfully for every cpu or not, may be really a better
idea.
[...]
> + grep "processor" /proc/cpuinfo | cut -f2 -d':' | \
much better if you could use 'cpufreq-info -a' and use this information
to tell _which_ cpus need to be switched. Can you include the output of
'cpufreq-info -a'? I could cook up a better patch but I'd really need
some real info to deal with.
> + while read cpu
> + do
> + $PROGRAM -cpu $cpu $CPUFREQ_OPTIONS 2>&1 > /dev/null
let me see, kind of:
RETVAL=0
for cpu in $(cpufreq-info -a | xargs echo) ; do
log_progress_msg "CPU${cpu}"
$PROGRAM -cpu $cpu $CPUFREQ_OPTIONS 2>&1 > /dev/null ||
RETVAL=$?
done
log_action_end_msg $RETVAL
> + done
> + /bin/true
Oooh! I see now why you need this: since your 2 cores need to switch
together (eg: you need to invoke cpufreq-set on cpu0 only) the second
invocation of cpufreq-set gives an error and $? reports failure.
Could be?
Anyway the issue remains, can you test (and fix eventually :)) the code
I provided?
Still, could you send the output of the commands I requested above?
Thanks
--
mattia
:wq!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
