FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 02-25-2010, 05:27 PM
Moritz Muehlenhoff
 
Default Bug#536183: Can't change CPU scaling governor after .29 to .30 upgrade.

tags 536183 moreinfo
thanks

On Wed, Jul 08, 2009 at 12:16:58PM +1000, Trent W. Buck wrote:
> Package: linux-image-2.6.30-1-686
> Version: 2.6.30-1
> Severity: normal
>
> After upgrading from .29 to .30, I can no longer change my CPU
> frequency scaling governor:
>
> # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
> ondemand performance
> # printf ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> performance
>
> This is super annoying. I am using an EeePC 701 with a Celeron CPU.

Hi,
The next release of Debian (6.0, code name Squeeze) will be based
on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
us whether the problem persists. If so, we should report it upstream
to the kernel.org developers.

The 2.6.32 kernel is available from packages.debian.org and can
be installed in both Debian stable, testing and unstable
installations.

Thanks,
Moritz



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100225182743.GA6702@galadriel.inutil.org">http://lists.debian.org/20100225182743.GA6702@galadriel.inutil.org
 
Old 02-25-2010, 09:57 PM
"Trent W. Buck"
 
Default Bug#536183: Can't change CPU scaling governor after .29 to .30 upgrade.

Moritz Muehlenhoff wrote:
>> After upgrading from .29 to .30, I can no longer change my CPU
>> frequency scaling governor: [...]
>
> The next release of Debian (6.0, code name Squeeze) will be based on
> 2.6.32. Please test the current 2.6.32 from unstable/testing and
> tell us whether the problem persists.

It does:

# uname -a
Linux Clio 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 GNU/Linux
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
ondemand performance
# printf ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
performance
# dmesg | tail -1
[38198.312686] ondemand governor failed, too long transition latency of HW, fallback to performance governor
#

> If so, we should report it upstream to the kernel.org developers.

Do you need me to take further action, or can I leave that part to
you?



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100225225734.GA4747@Clio">http://lists.debian.org/20100225225734.GA4747@Clio
 
Old 02-25-2010, 10:01 PM
Moritz Muehlenhoff
 
Default Bug#536183: Can't change CPU scaling governor after .29 to .30 upgrade.

Hi Trent,

On Fri, Feb 26, 2010 at 09:57:37AM +1100, Trent W. Buck wrote:
> Moritz Muehlenhoff wrote:
> >> After upgrading from .29 to .30, I can no longer change my CPU
> >> frequency scaling governor: [...]
> >
> > The next release of Debian (6.0, code name Squeeze) will be based on
> > 2.6.32. Please test the current 2.6.32 from unstable/testing and
> > tell us whether the problem persists.
>
> It does:
>
> # uname -a
> Linux Clio 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 GNU/Linux
> # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
> ondemand performance
> # printf ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> performance
> # dmesg | tail -1
> [38198.312686] ondemand governor failed, too long transition latency of HW, fallback to performance governor
> #
>
> > If so, we should report it upstream to the kernel.org developers.
>
> Do you need me to take further action, or can I leave that part to
> you?

Please report this bug upstream at the upstream bugzilla
(http://bugzilla.kernel.org), so that it can be investigated/
fixed upstream and backported for Squeeze.

Once done, please add the bug number to this bug.

(We're asking you to file the bug report yourself, since the
kernel.org developers will have specific inquiries to your
hardware/setup)

Cheers,
Moritz



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100225230156.GA15938@galadriel.inutil.org">http://lists.debian.org/20100225230156.GA15938@galadriel.inutil.org
 
Old 02-25-2010, 10:54 PM
Ben Hutchings
 
Default Bug#536183: Can't change CPU scaling governor after .29 to .30 upgrade.

On Fri, 2010-02-26 at 00:01 +0100, Moritz Muehlenhoff wrote:
> Hi Trent,
>
> On Fri, Feb 26, 2010 at 09:57:37AM +1100, Trent W. Buck wrote:
> > Moritz Muehlenhoff wrote:
> > >> After upgrading from .29 to .30, I can no longer change my CPU
> > >> frequency scaling governor: [...]
[...]
> > > If so, we should report it upstream to the kernel.org developers.
> >
> > Do you need me to take further action, or can I leave that part to
> > you?
>
> Please report this bug upstream at the upstream bugzilla
> (http://bugzilla.kernel.org), so that it can be investigated/
> fixed upstream and backported for Squeeze.

Also, you could try using acpi-cpufreq instead of p4-clockmod. I don't
know whether it will work on this machine but it might do.

Ben.

--
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett
 
Old 02-25-2010, 10:59 PM
"Trent W. Buck"
 
Default Bug#536183: Can't change CPU scaling governor after .29 to .30 upgrade.

Ben Hutchings wrote:
> Also, you could try using acpi-cpufreq instead of p4-clockmod. I
> don't know whether it will work on this machine but it might do.

# modprobe acpi-cpufreq
FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.32-trunk-686/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko): No such device



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100225235953.GA2019@Clio">http://lists.debian.org/20100225235953.GA2019@Clio
 
Old 02-26-2010, 12:40 PM
Bastian Blank
 
Default Bug#536183: Can't change CPU scaling governor after .29 to .30 upgrade.

On Fri, Feb 26, 2010 at 09:57:37AM +1100, Trent W. Buck wrote:
> # printf ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

It should give an error here.

> # dmesg | tail -1
> [38198.312686] ondemand governor failed, too long transition latency of HW, fallback to performance governor

But now it is clear that the behaviour otherwise is correct. If the
hardware is not capable to do something, it is no software bug.

Bastian

--
Each kiss is as the first.
-- Miramanee, Kirk's wife, "The Paradise Syndrome",
stardate 4842.6



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100226134022.GA18476@wavehammer.waldi.eu.org">ht tp://lists.debian.org/20100226134022.GA18476@wavehammer.waldi.eu.org
 
Old 02-26-2010, 03:39 PM
"Trent W. Buck"
 
Default Bug#536183: Can't change CPU scaling governor after .29 to .30 upgrade.

Bastian Blank wrote:
> On Fri, Feb 26, 2010 at 09:57:37AM +1100, Trent W. Buck wrote:
>> # printf ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>
> It should give an error here.
>
>> # dmesg | tail -1
>> [38198.312686] ondemand governor failed, too long transition latency of HW, fallback to performance governor
>
> But now it is clear that the behaviour otherwise is correct. If the
> hardware is not capable to do something, it is no software bug.

The hardware didn't change; the kernel did. Either the kernel was
wrong to permit on-demand frequency scaling before, or it's wrong to
refuse it now.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100226163949.GA1466@Clio">http://lists.debian.org/20100226163949.GA1466@Clio
 
Old 02-26-2010, 05:11 PM
Bastian Blank
 
Default Bug#536183: Can't change CPU scaling governor after .29 to .30 upgrade.

On Sat, Feb 27, 2010 at 03:39:53AM +1100, Trent W. Buck wrote:
> Bastian Blank wrote:
> >> [38198.312686] ondemand governor failed, too long transition latency of HW, fallback to performance governor
> > But now it is clear that the behaviour otherwise is correct. If the
> > hardware is not capable to do something, it is no software bug.
> The hardware didn't change; the kernel did. Either the kernel was
> wrong to permit on-demand frequency scaling before, or it's wrong to
> refuse it now.

The kernel was wrong before.

Bastian

--
If I can have honesty, it's easier to overlook mistakes.
-- Kirk, "Space Seed", stardate 3141.9



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100226181157.GA25201@wavehammer.waldi.eu.org">ht tp://lists.debian.org/20100226181157.GA25201@wavehammer.waldi.eu.org
 

Thread Tools




All times are GMT. The time now is 04:24 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org