From: Florian Mickler <florian@mickler.org>
To: tmhikaru@gmail.com
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.35.6
Date: Tue, 28 Sep 2010 08:35:05 +0200 [thread overview]
Message-ID: <20100928083505.0a808ffd@schatten.dmk.lab> (raw)
In-Reply-To: <20100927233956.GA15705@roll>
On Mon, 27 Sep 2010 19:39:56 -0400
tmhikaru@gmail.com wrote:
> On Mon, Sep 27, 2010 at 09:51:35PM +0200, Florian Mickler wrote:
> > I can't comment on the bouncing part, but increased load average is
> > partly bisected down in Bug 16525 (unexpected high load since 2.6.35
> > Bug 16525)[1]. Maybe you are seeing something similiar?
>
> If you're referring to
>
> https://bugzilla.kernel.org/show_bug.cgi?id=16525
>
> then I have to admit that's very interesting; in fact, I tested my machine
> without X running, and the problem I'm having goes away entirely - loadavg
> quickly settles to 0.00 - and even with *only* a mrxvt terminal running,
> that is to say NO window manager, just mrxvt running, X on 2.6.35.3 and
> later has the wildly bouncy load averages.
That would of course lead one to think it happens
somewhere in the gfx stack.
>
> Here's a graphical example of just how wacky this is:
>
> http://yfrog.com/6lloadbp
>
> In this image, the dip down to less than 0.5 after the 18'th is due to me
> experimenting using the slackware distribution kernel (2.6.33.4) after I
> finally noticed something was amiss. The sharp rise afterwards is due to me
> first, building 2.6.35.5, and then afterwards, using it. To be perfectly
> clear, I've previously used 2.6.34.2 and did not experience the problem
> there either, nor is it in 2.6.33.4.
What load figure are you basing your observations on? The 15 minutes
average should be the most interesting (sampled at a 7 minutes
interval...)
Regards,
Flo
next prev parent reply other threads:[~2010-09-28 6:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 0:36 Linux 2.6.35.6 Greg KH
2010-09-27 0:36 ` Greg KH
2010-09-27 1:00 ` Felipe Contreras
2010-09-27 1:31 ` Greg KH
2010-09-27 17:05 ` Felipe Contreras
2010-09-27 16:32 ` tmhikaru
2010-09-27 17:54 ` Greg KH
2010-09-27 19:09 ` tmhikaru
2010-09-27 19:51 ` Florian Mickler
2010-09-27 23:39 ` tmhikaru
2010-09-28 4:45 ` tmhikaru
2010-09-28 6:35 ` Florian Mickler [this message]
2010-09-28 19:03 ` tmhikaru
2010-09-29 7:29 ` Florian Mickler
2010-09-29 11:02 ` tmhikaru
2010-09-29 11:33 ` Miguel Ojeda
2010-09-29 11:52 ` Florian Mickler
2010-09-29 12:19 ` Florian Mickler
2010-09-30 1:33 ` tmhikaru
2010-09-30 5:29 ` Florian Mickler
2010-09-30 7:38 ` tmhikaru
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=20100928083505.0a808ffd@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tmhikaru@gmail.com \
/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