[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090105185111.GA18084@sgi.com>
Date: Mon, 5 Jan 2009 12:51:11 -0600
From: Dimitri Sivanich <sivanich@....com>
To: Gregory Haskins <ghaskins@...ell.com>
Cc: linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...e.hu>, Mike Galbraith <efault@....de>,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
Greg KH <greg@...ah.com>, Nick Piggin <npiggin@...e.de>,
Robin Holt <holt@....com>
Subject: Re: 2.6.27.8 scheduler bug - threads not being scheduled for long periods
Hi Greg,
On Mon, Jan 05, 2009 at 01:44:41PM -0500, Gregory Haskins wrote:
> 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?
>
2.6.28 appears to be a little bit worse, actually:
Counts:
0: 50165855
1: 8879
2: 5462
3: 4990
4: 91805284
^C
# uname -r
2.6.28-03114-g3c92ec8
The master thread hangs up after printing only one set of counts.
--
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/
Powered by blists - more mailing lists