[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#550017: marked as done (linux-2.6.30-2-686-bigmem: ondemand governor never maxes cpu frequency)

Your message dated Tue, 13 Oct 2009 22:43:58 -0700
with message-id <87my3ufs2p.fsf@raven.defaultvalue.org>
and subject line Re: Bug#550017: Acknowledgement (linux-2.6.30-2-686-bigmem: ondemand  governor never maxes cpu frequency)
has caused the Debian Bug report #550017,
regarding linux-2.6.30-2-686-bigmem: ondemand governor never maxes cpu frequency
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
550017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550017
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6.30-2-bigmem
Version: 2.6.30-8

On a Core2Duo E8500, the ondemand governor never sets the CPU to
maxfreq.  Actually, it never appears to change the frequency from
2000.000 (as reported by /proc/cpuinfo).

Setting the scaling_governor to performance immediately takes the cpu(s)
to cpuinfo_max_freq (2834000).

To test the ondemand governor, two instances of this command were run as
root:

  gzip -9v -c /dev/urandom > /dev/null

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

--- End Message ---
--- Begin Message --- 
This appears to have been caused by the local BIOS.  After some
(re)adjustment, ondemand appears to be working correctly.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

--- End Message ---
Reply to: