From: Ben Hutchings <ben@decadent.org.uk>
To: tmhikaru@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.2.38
Date: Fri, 08 Feb 2013 01:11:30 +0000 [thread overview]
Message-ID: <1360285890.5374.76.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <20130207173630.GA8355@roll>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Thu, 2013-02-07 at 12:36 -0500, tmhikaru@gmail.com wrote:
> Hmm. I'm not sure what's going on here but ever since I upgraded to
> this kernel my CPU use has always been at 100% - various apps (top, pidstat,
> conky) give different reasons for this, conky&pidstat claims things like
> X/the most active X application are cpu hogging, while top seems to think
> the majority of cpu use is being done by 'sys' - the interesting thing
> though is that my loadaverage is staying very close to zero.
>
> I know that this is far from a useful bug report, but to be honest I
> don't even know where to begin checking, so I'll start a git bisect of
> 3.2.37 vs 3.2.38 tonight and see what happens.
There weren't any scheduler changes in 3.2.38 so I can't make any better
suggestion than to do that bisection.
Ben.
--
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-02-08 1:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 14:27 Linux 3.2.38 Ben Hutchings
2013-02-06 14:34 ` Ben Hutchings
2013-02-07 17:36 ` tmhikaru
2013-02-08 1:11 ` Ben Hutchings [this message]
2013-02-08 14:27 ` Roland Eggner
2013-02-08 19:08 ` tmhikaru
2013-02-10 15:11 ` tmhikaru
2013-02-12 5:01 ` 3.2.38 most of the time has 100% cpu use reported tmhikaru
2013-02-14 5:04 ` Ben Hutchings
2013-02-16 3:23 ` tmhikaru
2013-02-16 5:18 ` Ben Hutchings
2013-02-16 6:42 ` 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=1360285890.5374.76.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).