Date: Tue, 22 Jan 2008 11:10:15 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Oliver Pinter =?iso-8859-1?B?KFBpbnTpciBPbGl26XIp?= 
	<oliver.pntr@gmail.com>
Cc: Al Boldi <a1426z@gawab.com>, linux-kernel@vger.kernel.org,
       linux-fsdevel@vger.kernel.org
Subject: Re: konqueror deadlocks on 2.6.22
Message-ID: <20080122101014.GD5722@elte.hu>
References: <200801192114.41427.a1426z@gawab.com> <6101e8c40801191053j7e81988fm8aaf0a75fb8bd405@mail.gmail.com> <200801192357.13774.a1426z@gawab.com> <6101e8c40801191417k7906422chf657895152b61a2d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <6101e8c40801191417k7906422chf657895152b61a2d@mail.gmail.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1082
Lines: 27


* Oliver Pinter (Pint?r Oliv?r) <oliver.pntr@gmail.com> wrote:

> and then please update to CFS-v24.1
> http://people.redhat.com/~mingo/cfs-scheduler/sched-cfs-v2.6.22.15-v24.1.patch

> > Yes with CFSv20.4, as in the log.
> >
> > It also hangs on 2.6.23.13

my feeling is that this is some sort of timing dependent race in 
konqueror/kde/qt that is exposed when a different scheduler is put in.

If it disappears with CFS-v24.1 it is probably just because the timings 
will change again. Would be nice to debug this on the konqueror side and 
analyze why it fails and how. You can probably tune the timings by 
enabling SCHED_DEBUG and tweaking /proc/sys/kernel/*sched* values - in 
particular sched_latency and the granularity settings. Setting wakeup 
granularity to 0 might be one of the things that could make a 
difference.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/