From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754599AbYC1LQi (ORCPT ); Fri, 28 Mar 2008 07:16:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752738AbYC1LQa (ORCPT ); Fri, 28 Mar 2008 07:16:30 -0400 Received: from www.tglx.de ([62.245.132.106]:35222 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752543AbYC1LQ3 (ORCPT ); Fri, 28 Mar 2008 07:16:29 -0400 Date: Fri, 28 Mar 2008 12:16:03 +0100 (CET) From: Thomas Gleixner To: Adrian Bunk cc: Peter Zijlstra , "Rafael J. Wysocki" , LKML , Andrew Morton , Linus Torvalds , Natalie Protasevich Subject: Re: 2.6.25-rc7-git2: Reported regressions from 2.6.24 In-Reply-To: <20080328111334.GD32200@cs181133002.pp.htv.fi> Message-ID: References: <200803272353.51901.rjw@sisk.pl> <1206702025.8514.624.camel@twins> <20080328111334.GD32200@cs181133002.pp.htv.fi> User-Agent: Alpine 1.00 (LFD 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 28 Mar 2008, Adrian Bunk wrote: > On Fri, Mar 28, 2008 at 12:00:25PM +0100, Peter Zijlstra wrote: > > On Fri, 2008-03-28 at 11:58 +0100, Thomas Gleixner wrote: > > > On Fri, 28 Mar 2008, Thomas Gleixner wrote: > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=9969 > > > > > Subject : 2.6.24-git15 Keyboard Issue? > > > > > Submitter : Chris Holvenstot > > > > > Date : 2008-02-06 14:02 (51 days old) > > > > > References : http://lkml.org/lkml/2008/2/6/100 > > > > > http://lkml.org/lkml/2008/2/13/82 > > > > > Handled-By : Thomas Gleixner > > > > > Patch : http://lkml.org/lkml/2008/2/15/343 > > > > > > > > asked the bug reporter for an update. > > > > > > Now that lkml.org is working again, I checked the patch which is > > > referenced above and I have a hard time to connect it even remotely to > > > that bug. > > > > > > As far as I can tell the discussion on lkml identified GROUP_SCHED=y > > > as the culprit, but I have no idea whether there was any resolution > > > other than disabling GROUP_SCHED. > > > > > > Peter ?? > > > > Correct, I am working on the issue but that's not going to be .25 stuff. > > How are we going to get 2.6.25 working no worse than 2.6.24? > > Letting GROUP_SCHED depend on BROKEN would sound logical, but that would > also kill FAIR_GROUP_SCHED. I think default it to off should be sufficient. Thanks, tglx