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 12-20-2008, 10:27 PM
Moritz Muehlenhoff
 
Default Bug#470474: cpufrequtils: Laptop limited to 1.2GHz vs 2.2GHz when no battery, running on AC only.

On Tue, Mar 11, 2008 at 04:43:59PM -0400, Greg Folkert wrote:
>
> On Tue, 2008-03-11 at 23:58 +0900, Mattia Dongili wrote:
> > reassign 470474 linux-image-2.6.24-1-686
> > thanks
> >
> > I assume you are using the Debian kernel packages right?
> > Anyway this is a kernel bug, not cpufrqutils.
>
> Yes 100% Debian.

Does this error still occur with more recent kernel versions?

Cheers,
Moritz



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-20-2008, 11:59 PM
Greg Folkert
 
Default Bug#470474: cpufrequtils: Laptop limited to 1.2GHz vs 2.2GHz when no battery, running on AC only.

On Sun, 2008-12-21 at 00:27 +0100, Moritz Muehlenhoff wrote:
> On Tue, Mar 11, 2008 at 04:43:59PM -0400, Greg Folkert wrote:
> >
> > On Tue, 2008-03-11 at 23:58 +0900, Mattia Dongili wrote:
> > > reassign 470474 linux-image-2.6.24-1-686
> > > thanks
> > >
> > > I assume you are using the Debian kernel packages right?
> > > Anyway this is a kernel bug, not cpufrqutils.
> >
> > Yes 100% Debian.
>
> Does this error still occur with more recent kernel versions?

Yes, in fact its worse.

No now I get 800MHz only with no battery in on either the 65w or 90w
external power brick.

ii cpufrequtils 004-2 utilities to deal with the cpufreq Linux kernel feature
ii libcpufreq0 004-2 shared library to deal with the cpufreq Linux kernel feature
ii linux-image-2.6.26-1-686-bigmem 2.6.26-12 Linux 2.6.26 image on PPro/Celeron/PII/PIII/P4
ii linux-image-2.6-686-bigmem 2.6.26+17 Linux 2.6 image on PPro/Celeron/PII/PIII/P4

Anything else?
--
greg@gregfolkert.net
PGP key 1024D/B524687C 2003-08-05
Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C
Alternate Fingerprint: 09F9 1102 9D74 E35B D841 56C5 6356 88C0
Alternate Fingerprint: 455F E104 22CA 29C4 933F 9505 2B79 2AB2
 
Old 02-17-2010, 05:28 PM
Moritz Muehlenhoff
 
Default Bug#470474: cpufrequtils: Laptop limited to 1.2GHz vs 2.2GHz when no battery, running on AC only.

On Sat, Dec 20, 2008 at 07:59:56PM -0500, Greg Folkert wrote:
>
> On Sun, 2008-12-21 at 00:27 +0100, Moritz Muehlenhoff wrote:
> > On Tue, Mar 11, 2008 at 04:43:59PM -0400, Greg Folkert wrote:
> > >
> > > On Tue, 2008-03-11 at 23:58 +0900, Mattia Dongili wrote:
> > > > reassign 470474 linux-image-2.6.24-1-686
> > > > thanks
> > > >
> > > > I assume you are using the Debian kernel packages right?
> > > > Anyway this is a kernel bug, not cpufrqutils.
> > >
> > > Yes 100% Debian.
> >
> > Does this error still occur with more recent kernel versions?
>
> Yes, in fact its worse.
>
> No now I get 800MHz only with no battery in on either the 65w or 90w
> external power brick.

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: 20100217182848.GA3265@galadriel.inutil.org">http://lists.debian.org/20100217182848.GA3265@galadriel.inutil.org
 
Old 04-23-2010, 01:30 PM
Greg Folkert
 
Default Bug#470474: cpufrequtils: Laptop limited to 1.2GHz vs 2.2GHz when no battery, running on AC only.

Ok, its better. I now get 1.6GHz on this same machine, without the
battery in the battery slot.

But now with the latest kernel, even on AC power, with the battery in
place, cpufreqd will never ever go above 1.6GHz. I can select the
frequency or profile and I see the clock speed change for about 20ms to
2207MHz... but immediately goes back to 1600MHz.

I will do a reportbug to get all the details additionally to this
e-mail.


On Wed, 2010-02-17 at 19:28 +0100, Moritz Muehlenhoff wrote:
> 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
>

--
greg@gregfolkert.net
PGP key 1024D/B524687C 2003-08-05
Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C
Alternate Fingerprint: 09F9 1102 9D74 E35B D841 56C5 6356 88C0
Alternate Fingerprint: 455F E104 22CA 29C4 933F 9505 2B79 2AB2
 
Old 04-23-2010, 02:11 PM
Greg Folkert
 
Default Bug#470474: cpufrequtils: Laptop limited to 1.2GHz vs 2.2GHz when no battery, running on AC only.

Okay, I can't get reportbug to work properly at the moment, it fails to
reach BTS for linux-2.6


In any case, here is the details I have now:

Package: linux-2.6
Version: 2.6.32+25
Severity: normal

Running linux-image-2.6.32-3-686-bigmem 2.6.32-9, this problem is better
without a battery in the battery slot, giving me 1.6GHz.

Problems though, is that now the machine is preferring 1.6GHz now for
everything, no matter what power profile I give it. No matter what I try
to force. Sometimes it even locks at 800MHz. I can see the policy change for
a few milliseconds, but goes right back to 1.6GHz

Plus the 2.6.32 kernel screws up the X rendering and makes it feel like
I'm back in 1994 running CDE on OSF/1 box, using XDMCP. Lethargic response
times, likely due to the GEM system changes.

I've switched back to linux-image-2.6.31-rc4-686-bigmem
2.6.31~rc4-1~experimental.1~snapshot.14067 as my kernel in use. This gives
*MUCH* *MUCH* better CPU speed results *AND* the X renders fast and light,
like it should. Since the updates to cpufreq* packages (and other things I am sure)
I am running at 2.2GHz all the time (without the battery in, or out ON AC only)

This kernel was installed from the Debian Kernel Builder site back when I was having
huge issues with the earlier kernels and X rendering and everything now seems to
work with it and the updated packages for squeeze.

Someone needs to go look at that 2.6.31 kernel and figure out why it works so well,
va the cruddy way the "current" one works.


-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-rc4-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


ii cpufreqd 2.4.2-1 fully configurable daemon for dynamic frequency and voltage scal
ii cpufrequtils 006-2 utilities to deal with the cpufreq Linux kernel feature
ii debconf 1.5.32 Debian configuration management system
ii debconf-i18n 1.5.32 full internationalization support for debconf
ii debconf-utils 1.5.32 debconf utilities
ii grub 0.97-61 GRand Unified Bootloader (dummy package)
ii grub-common 1.98-1 GRand Unified Bootloader, version 2 (common files)
ii grub-pc 1.98-1 GRand Unified Bootloader, version 2 (PC/BIOS version)
ii initramfs-tools 0.94.4 tools for generating an initramfs
ii libc6-i686 2.10.2-6 GNU C Library: Shared libraries [i686 optimized]
ii libcpufreq0 006-2 shared library to deal with the cpufreq Linux kernel feature
ii linux-image-2.6-686 2.6.32+25 Linux 2.6 for modern PCs
ii linux-image-2.6-686-bigmem 2.6.32+25 Linux 2.6 for PCs with 4GB+ RAM
ii linux-image-2.6.30-1-686 2.6.30-6 Linux 2.6.30 image on PPro/Celeron/PII/PIII/P4
ii linux-image-2.6.30-1-686-bigmem 2.6.30-6 Linux 2.6.30 image on PPro/Celeron/PII/PIII/P4
ii linux-image-2.6.31-rc4-686 2.6.31~rc4-1~experimental.1~snapshot.14067 Linux 2.6.31-rc4 image on PPro/Celeron/PII/PIII/P4
ii linux-image-2.6.31-rc4-686-bigmem 2.6.31~rc4-1~experimental.1~snapshot.14067 Linux 2.6.31-rc4 image on PPro/Celeron/PII/PIII/P4
ii linux-image-2.6.32-3-686 2.6.32-9 Linux 2.6.32 for modern PCs
ii linux-image-2.6.32-3-686-bigmem 2.6.32-9 Linux 2.6.32 for PCs with 4GB+ RAM
ii linux-image-2.6.32-trunk-686 2.6.32-3 Linux 2.6.32 for modern PCs
ii linux-image-2.6.32-trunk-686-bigmem 2.6.32-3 Linux 2.6.32 for PCs with 4GB+ RAM
ii module-init-tools 3.12~pre2-3 tools for managing Linux kernel modules



--
greg@gregfolkert.net
PGP key 1024D/B524687C 2003-08-05
Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C
Alternate Fingerprint: 09F9 1102 9D74 E35B D841 56C5 6356 88C0
Alternate Fingerprint: 455F E104 22CA 29C4 933F 9505 2B79 2AB2
 
Old 05-03-2010, 02:41 PM
Ben Hutchings
 
Default Bug#470474: cpufrequtils: Laptop limited to 1.2GHz vs 2.2GHz when no battery, running on AC only.

On Fri, 2010-04-23 at 10:11 -0400, Greg Folkert wrote:
> Okay, I can't get reportbug to work properly at the moment, it fails to
> reach BTS for linux-2.6
>
>
> In any case, here is the details I have now:
>
> Package: linux-2.6
> Version: 2.6.32+25
> Severity: normal
>
> Running linux-image-2.6.32-3-686-bigmem 2.6.32-9, this problem is better
> without a battery in the battery slot, giving me 1.6GHz.
>
> Problems though, is that now the machine is preferring 1.6GHz now for
> everything, no matter what power profile I give it. No matter what I try
> to force. Sometimes it even locks at 800MHz. I can see the policy change for
> a few milliseconds, but goes right back to 1.6GHz
>
> Plus the 2.6.32 kernel screws up the X rendering and makes it feel like
> I'm back in 1994 running CDE on OSF/1 box, using XDMCP. Lethargic response
> times, likely due to the GEM system changes.
>
> I've switched back to linux-image-2.6.31-rc4-686-bigmem
> 2.6.31~rc4-1~experimental.1~snapshot.14067 as my kernel in use. This gives
> *MUCH* *MUCH* better CPU speed results *AND* the X renders fast and light,
> like it should. Since the updates to cpufreq* packages (and other things I am sure)
> I am running at 2.2GHz all the time (without the battery in, or out ON AC only)
[...]

Please report this upstream at <https://bugzilla.kernel.org> under
product 'Power Management, component 'cpufreq'. Let us know the bug
number so that we can track it.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 
Old 05-05-2010, 12:05 AM
Ben Hutchings
 
Default Bug#470474: cpufrequtils: Laptop limited to 1.2GHz vs 2.2GHz when no battery, running on AC only.

On Mon, 2010-05-03 at 12:19 -0400, Greg Folkert wrote:
> On Mon, 2010-05-03 at 15:41 +0100, Ben Hutchings wrote:
> [...]
> >
> > Please report this upstream at <https://bugzilla.kernel.org> under
> > product 'Power Management, component 'cpufreq'. Let us know the bug
> > number so that we can track it.
> >
> > Ben.
>
> Umm, hmmm. This bug has been open for a number of years and has existed
> through any number of kernels. I thought the whole reason I'd use the
> Distro bugs system was to not have to deal with and make sure Debian
> gave back etc. etc. etc...

I'm sorry that no-one advised you to do this earlier. It is very
unlikely to be a Debian-specific problem and this is not an area where
anyone on the Debian kernel team has specific knowledge.

> I guess I must do this myself, rather than use Debian systems to get
> things working.

The upstream developers will need to ask you more questions. If we
report the bug then the questions will go to us and we will just have to
forward them to you, which will slow down solution of the bug.

Once you have reported the bug in Bugzilla, we can link it to the Debian
bug and track its progress.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 
Old 05-30-2010, 12:42 PM
Moritz Muehlenhoff
 
Default Bug#470474: cpufrequtils: Laptop limited to 1.2GHz vs 2.2GHz when no battery, running on AC only.

On Wed, May 05, 2010 at 01:05:50AM +0100, Ben Hutchings wrote:
> On Mon, 2010-05-03 at 12:19 -0400, Greg Folkert wrote:
> > On Mon, 2010-05-03 at 15:41 +0100, Ben Hutchings wrote:
> > [...]
> > >
> > > Please report this upstream at <https://bugzilla.kernel.org> under
> > > product 'Power Management, component 'cpufreq'. Let us know the bug
> > > number so that we can track it.
> > >
> > > Ben.
> >
> > Umm, hmmm. This bug has been open for a number of years and has existed
> > through any number of kernels. I thought the whole reason I'd use the
> > Distro bugs system was to not have to deal with and make sure Debian
> > gave back etc. etc. etc...
>
> I'm sorry that no-one advised you to do this earlier. It is very
> unlikely to be a Debian-specific problem and this is not an area where
> anyone on the Debian kernel team has specific knowledge.
>
> > I guess I must do this myself, rather than use Debian systems to get
> > things working.
>
> The upstream developers will need to ask you more questions. If we
> report the bug then the questions will go to us and we will just have to
> forward them to you, which will slow down solution of the bug.
>
> Once you have reported the bug in Bugzilla, we can link it to the Debian
> bug and track its progress.

Did you report this at bugzilla.kernel.org?

Cheers,
Moritz



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100530124221.GK2398@galadriel.inutil.org">http://lists.debian.org/20100530124221.GK2398@galadriel.inutil.org
 
Old 05-30-2010, 02:12 PM
Greg Folkert
 
Default Bug#470474: cpufrequtils: Laptop limited to 1.2GHz vs 2.2GHz when no battery, running on AC only.

On Sun, 2010-05-30 at 14:42 +0200, Moritz Muehlenhoff wrote:
> On Wed, May 05, 2010 at 01:05:50AM +0100, Ben Hutchings wrote:
> > On Mon, 2010-05-03 at 12:19 -0400, Greg Folkert wrote:
> > > On Mon, 2010-05-03 at 15:41 +0100, Ben Hutchings wrote:
> > > [...]
> > > >
> > > > Please report this upstream at <https://bugzilla.kernel.org> under
> > > > product 'Power Management, component 'cpufreq'. Let us know the bug
> > > > number so that we can track it.
> > > >
> > > > Ben.
> > >
> > > Umm, hmmm. This bug has been open for a number of years and has existed
> > > through any number of kernels. I thought the whole reason I'd use the
> > > Distro bugs system was to not have to deal with and make sure Debian
> > > gave back etc. etc. etc...
> >
> > I'm sorry that no-one advised you to do this earlier. It is very
> > unlikely to be a Debian-specific problem and this is not an area where
> > anyone on the Debian kernel team has specific knowledge.
> >
> > > I guess I must do this myself, rather than use Debian systems to get
> > > things working.
> >
> > The upstream developers will need to ask you more questions. If we
> > report the bug then the questions will go to us and we will just have to
> > forward them to you, which will slow down solution of the bug.
> >
> > Once you have reported the bug in Bugzilla, we can link it to the Debian
> > bug and track its progress.
>
> Did you report this at bugzilla.kernel.org?

No, I don't have any time now with the job I have. The problem is worse
than ever with the NEW kernel linux-image-2.6.32-5-686-bigmem v2.6.32-13

I don't even get ANY changes from 800MHz except when I restart
cpufreqd... various amounts of time... but no more than 2 minutes of
2.2GHz per restart. Its pegged at 800MHz and stays there.

This is bull. Just close this bug. I don't want to deal with it
anymore...

--
greg@gregfolkert.net
PGP key 1024D/B524687C 2003-08-05
Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C
Alternate Fingerprint: 09F9 1102 9D74 E35B D841 56C5 6356 88C0
Alternate Fingerprint: 455F E104 22CA 29C4 933F 9505 2B79 2AB2
 

Thread Tools




All times are GMT. The time now is 04:48 PM.

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