public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karsten Mehrhoff <kawime@gmx.de>
To: "Andrew Morton" <akpm@linux-foundation.org>, "Greg KH" <greg@kroah.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org, stable@kernel.org
Subject: Re: [stable] regression in 2.6.35.4 'load is to heavy (video subsystem?)'
Date: Wed, 22 Sep 2010 11:42:41 +0200	[thread overview]
Message-ID: <op.vjfg9fo2gp7xae@127.0.0.1> (raw)
In-Reply-To: <20100922000101.GA5077@kroah.com>

[Am 22.09.2010, 02:01 Uhr, schrieb Greg KH <greg@kroah.com>]

> On Tue, Sep 21, 2010 at 04:50:07PM -0700, Andrew Morton wrote:
>> On Mon, 30 Aug 2010 10:02:36 +0200
>> Karsten Mehrhoff <kawime@gmx.de> wrote:
>>
>>> Using the same .config from 2.6.35.3 to compile 2.5.36.4 results in a
>>> heavy load with 2.6.35.4.
>>
>> A regression within -stable is rather bad.
>
> Agreed.
>
>>> Example:
>>>
>>> Difference between 2.6.35.1/2/3 and 2.6.35.4 while watching some  
>> videos:
>>> 2.6.35.4 switches the cpu for flash videos in the browser (opera or
>>> iceweasel) or other video outputs to 2200/2400/2600 MHz meanwhile  
>> 2.6.35.3
>>> (or older) stays at 1000 Mhz. That results in a higher cpu  
>> temperature,
>>> more power consumption and so one.
>>>
>>> Using other GUI program results in nearly the same problems with  
>> 2.6.35.4,
>>> so this kernel is unusable for me.
>>>
>>> Results to see the difference for the same action
>>> 2.6.35.4
>>> Core0 Temp:  +45.0__C
>>> Core1 Temp:  +43.0__C
>>> cpu MHz:	2200.000 or higher
>>>
>>> 2.6.35.3
>>> Core0 Temp:  +32.0__C
>>> Core1 Temp:  +31.0__C
>>> cpu MHz:	1000.000 (max. 1800, but falling back to 1000)
>
> Can you run 'git bisect' between 2.6.35.3 and 2.6.35.4 to try to find
> out the offending patch that caused this issue?
>
> thanks,
>
> greg k-h

Same for 2.6.35.5 using 256.53

For your info, I did run some tests today using a nVidia 9500GT

    Kernel       |   Performance with NVIDIA-Linux-x86_64-
                 |       256.53      |    260.19.04 (BETA)
----------------------------------------------------------
  2.6.35.3       |      good         |      good
----------------------------------------------------------
  2.6.35.4       |       bad         |     not tested
----------------------------------------------------------
  2.6.35.5       |       bad         |      ~ good
----------------------------------------------------------
  2.6.36-rc4     |                   |
    (git1-5)     |     failed        |      good
----------------------------------------------------------
  2.6.36-rc4     |                   |
    (git1)       |     failed        |      good
----------------------------------------------------------


Karsten

  reply	other threads:[~2010-09-22  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  8:02 regression in 2.6.35.4 'load is to heavy (video subsystem?)' Karsten Mehrhoff
2010-09-21 23:50 ` Andrew Morton
2010-09-21 23:57   ` Dave Airlie
2010-09-22  0:01   ` [stable] " Greg KH
2010-09-22  9:42     ` Karsten Mehrhoff [this message]
2010-09-22 10:27       ` Florian Mickler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.vjfg9fo2gp7xae@127.0.0.1 \
    --to=kawime@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox