From: Gregory Haskins <ghaskins@novell.com>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>, Mike Galbraith <efault@gmx.de>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Greg KH <greg@kroah.com>, Nick Piggin <npiggin@suse.de>,
Robin Holt <holt@sgi.com>
Subject: Re: 2.6.27.8 scheduler bug - threads not being scheduled for long periods
Date: Mon, 05 Jan 2009 13:44:41 -0500 [thread overview]
Message-ID: <49625519.4050902@novell.com> (raw)
In-Reply-To: <20090105175641.GA17055@sgi.com>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
Dimitri Sivanich wrote:
>
> I'm wondering if anyone else has run into this problem, and whether they've
> found a resolution for it?
>
>
Hi Dimitri,
I have observed similar problems on my opensuse 11.0 box (2.6.25
based) when doing kernel builds. Often times other apps will get
starved (like firefox, etc). I was talking to peterz about it and he
pointed me at a commit that went into 28-rcx that fixes this (the sha
escapes me at the moment). I've been meaning to pull the patch into our
2.6.25 and 2.6.27 trees to verify if it fixes it, but I have fairly high
confidence it will. Perhaps Peter can point you at the same patch and
you can give it a whirl. For the time being, can you see if 28 is fixed?
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-01-05 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 17:56 2.6.27.8 scheduler bug - threads not being scheduled for long periods Dimitri Sivanich
2009-01-05 18:44 ` Gregory Haskins [this message]
2009-01-05 18:51 ` Dimitri Sivanich
2009-01-05 18:59 ` Gregory Haskins
2009-01-14 22:34 ` kenneth johansson
2009-01-05 20:55 ` Peter Zijlstra
2009-01-05 21:54 ` Dimitri Sivanich
2009-01-05 22:36 ` Dimitri Sivanich
2009-01-05 23:02 ` Dimitri Sivanich
2009-01-06 7:36 ` Peter Zijlstra
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=49625519.4050902@novell.com \
--to=ghaskins@novell.com \
--cc=efault@gmx.de \
--cc=greg@kroah.com \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=sivanich@sgi.com \
--cc=vatsa@linux.vnet.ibm.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