linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Regression in gdm-2.18 since 2.6.24
Date: Fri, 4 Apr 2008 16:02:21 +0100	[thread overview]
Message-ID: <20080404150221.GB21753@deepthought> (raw)
In-Reply-To: <20080404144825.GB890@linux.vnet.ibm.com>

On Fri, Apr 04, 2008 at 08:18:25PM +0530, Dhaval Giani wrote:
> On Fri, Apr 04, 2008 at 01:37:17PM +0100, Ken Moffat wrote:
> > On Fri, Apr 04, 2008 at 02:20:00AM +0200, Rafael J. Wysocki wrote:
> > > On Friday, 4 of April 2008, Ken Moffat wrote:
> > > > On Thu, Apr 03, 2008 at 11:29:21PM +0200, Rafael J. Wysocki wrote:
> > > > > 
> > > > > Please unset CONFIG_GROUP_SCHED and retest.  It is known to cause problems
> > > > > (see http://bugzilla.kernel.org/show_bug.cgi?id=9969, for example).
> > > > > 
> > > > > Thanks,
> > > > > Rafael
> > > >  Thanks for the suggestion.  Tried it on 2.6.24.4, and
> > > > double-checked /proc/config.gz after booting -
> > > > 
> > > > # CONFIG_FAIR_GROUP_SCHED is not set
> > > > 
> > > >  Unfortunately, the first test reboot failed in the same way.
> > > 
> > > Please unset CONFIG_GROUP_SCHED too.
> > > 
> > > Thanks,
> > > Rafael
> > 
> >  Yet again, I'm confused.  I thought you'd missed a word in what you
> > asked because the config for 2.6.24.4 doesn't show this.
> > ken@bluesbreaker ~ $zgrep GROUP /proc/config.gz 
> > # CONFIG_CGROUPS is not set
> > # CONFIG_FAIR_GROUP_SCHED is not set
> > ken@bluesbreaker ~ $
> > 
> >  I _can_ see it in the 2.6.25 configs (except for rc1).  Will retry
> > rc8 with them both turned off.
> > 
> 
> Right, in 2.6.24 we called it CONFIG_FAIR_GROUP_SCHED since group
> scheduling was available only for CFS. In 2.6.25 we have group
> scheduling for RT as well, so it is called CONFIG_GROUP_SCHED now.
> 
> -- 
> regards,
> Dhaval
 OK, thanks for the explanation.  Just gave -rc8 the first test with
CONFIG_GROUP_SCHED unset, and again it fails.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

  reply	other threads:[~2008-04-04 15:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 19:19 Regression in gdm-2.18 since 2.6.24 Ken Moffat
2008-04-03 19:56 ` Rafael J. Wysocki
2008-04-03 21:08   ` Ken Moffat
2008-04-03 21:29     ` Rafael J. Wysocki
2008-04-03 23:48       ` Ken Moffat
2008-04-04  0:20         ` Rafael J. Wysocki
2008-04-04 12:37           ` Ken Moffat
2008-04-04 14:48             ` Dhaval Giani
2008-04-04 15:02               ` Ken Moffat [this message]
2008-04-04 14:47         ` Dhaval Giani
2008-04-04 15:00           ` Ken Moffat
2008-04-04 14:37 ` Srivatsa Vaddagiri
2008-04-04 15:32   ` Ken Moffat
2008-04-05 14:40     ` Srivatsa Vaddagiri
2008-04-05 21:03       ` Ken Moffat
2008-04-06 23:48         ` Ken Moffat
2008-04-08  8:50           ` Srivatsa Vaddagiri
2008-04-08  8:42             ` Peter Zijlstra
2008-04-08 11:21             ` Carlos R. Mafra
2008-04-09 13:07             ` Ken Moffat

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=20080404150221.GB21753@deepthought \
    --to=zarniwhoop@ntlworld.com \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --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;
as well as URLs for NNTP newsgroup(s).