linux-kernel - Re: [stable] regression in 2.6.35.4 'load is to heavy (video subsystem?)'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <op.vjfg9fo2gp7xae@127.0.0.1>
Date:	Wed, 22 Sep 2010 11:42:41 +0200
FROM:	Karsten Mehrhoff <kawime@....de>
To:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Greg KH" <greg@...ah.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	dri-devel@...ts.freedesktop.org, stable@...nel.org
Subject: Re: [stable] regression in 2.6.35.4 'load is to heavy (video
 subsystem?)'

[Am 22.09.2010, 02:01 Uhr, schrieb Greg KH <greg@...ah.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@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/