public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tmhikaru@gmail.com
To: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.35.6
Date: Mon, 27 Sep 2010 15:09:30 -0400	[thread overview]
Message-ID: <20100927190930.GA7086@roll> (raw)
In-Reply-To: <20100927175412.GA23347@suse.de>

[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]

On Mon, Sep 27, 2010 at 10:54:12AM -0700, Greg KH wrote:
> On Mon, Sep 27, 2010 at 12:32:08PM -0400, tmhikaru@gmail.com wrote:
> > 	I'm not exactly sure what's going on here and I'd like some help
> > figuring out what is. For some inexplicable reason, ever since I started
> > using the 2.6.35.x series with the 2.6.35.3 release, my loadaverages tend to
> > bounce anywhere from as low to .2 to 1.5 - constantly, while the machine
> > seems idle.
> 
> But .34 doesn't show this issue?
> 
> If so, can you run 'git bisect' between the .34 and .35 releases to find
> out where the problem comes in?

.34 does not, that is correct.
> 
> > Consistently, there are no programs in D state in ps aux output,
> > no cpu hogging programs running in top, nothing I can see that should
> > explain the bizzarely high load average.
> 
> Loadaverage can be affected by a driver doing an uninteruptable sleep.
> This doesn't actually cause a load on the system, but it does affect the
> way that number is calcuated.  Perhaps that's the problem here.
>

That would explain a lot.
> > 	If you have any tips or recommendations on what I should use to
> > investigate this further, please let me know. Once I have ensured to my own
> > satisfaction that I'm not doing something bizzare that's screwing up my
> > machine, I'll make a detailed bug report and start on figuring out how to
> > use git bisect.
> 
> 'man git-bisect' will help with this :)
> 
> thanks,
> 
> greg k-h

Thank you for the tips. If I don't find anything obvious I'll bisect it very
soon, but I'll likely attempt to track backwards from .3 myself since I've
backtracked through patches before. Once I have narrowed it down to a patch
release it'll likely take less time to bisect. (eg, if I know it happened
between 2.6.35-rc1 and rc2 I'd only have to bisect the patches between those
versions, whereas right now I only know positively between 2.6.34 and
2.6.35.3 something went wrong.)

Tim McGrath

[-- Attachment #2: Type: application/pgp-signature, Size: 482 bytes --]

  reply	other threads:[~2010-09-27 19:09 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 [this message]
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
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=20100927190930.GA7086@roll \
    --to=tmhikaru@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.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