From: Ingo Molnar Subject: Re: konqueror deadlocks on 2.6.22 Date: Tue, 22 Jan 2008 11:10:15 +0100 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-Transfer-Encoding: QUOTED-PRINTABLE Cc: Al Boldi , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Oliver Pinter =?iso-8859-1?B?KFBpbnTpciBPbGl26XIp?= Return-path: Received: from mx3.mail.elte.hu ([157.181.1.138]:36443 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751146AbYAVKK2 (ORCPT ); Tue, 22 Jan 2008 05:10:28 -0500 Content-Disposition: inline In-Reply-To: <6101e8c40801191417k7906422chf657895152b61a2d@mail.gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: * Oliver Pinter (Pint=E9r Oliv=E9r) wrote: > and then please update to CFS-v24.1 > http://people.redhat.com/~mingo/cfs-scheduler/sched-cfs-v2.6.22.15-v2= 4.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=20 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= =20 will change again. Would be nice to debug this on the konqueror side an= d=20 analyze why it fails and how. You can probably tune the timings by=20 enabling SCHED_DEBUG and tweaking /proc/sys/kernel/*sched* values - in=20 particular sched_latency and the granularity settings. Setting wakeup=20 granularity to 0 might be one of the things that could make a=20 difference. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html