Re: konqueror deadlocks on 2.6.22

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Oliver Pinter <oliver.pntr@...>
Cc: Al Boldi <a1426z@...>, <linux-kernel@...>, <linux-fsdevel@...>
Date: Tuesday, January 22, 2008 - 6:10 am

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



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
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
konqueror deadlocks on 2.6.22, Al Boldi, (Sat Jan 19, 2:14 pm)
Re: konqueror deadlocks on 2.6.22, Oliver Pinter (Pintér Olivér)..., (Sat Jan 19, 2:53 pm)
Re: konqueror deadlocks on 2.6.22, Al Boldi, (Sat Jan 19, 4:57 pm)
Re: konqueror deadlocks on 2.6.22, Oliver Pinter (Pintér Olivér)..., (Sat Jan 19, 6:17 pm)
Re: konqueror deadlocks on 2.6.22, Ingo Molnar, (Tue Jan 22, 6:10 am)
Re: konqueror deadlocks on 2.6.22, Al Boldi, (Tue Jan 22, 9:23 am)
Re: konqueror deadlocks on 2.6.22, Chris Mason, (Tue Jan 22, 10:25 am)
Re: konqueror deadlocks on 2.6.22, Al Boldi, (Tue Jan 22, 2:54 pm)
Re: konqueror deadlocks on 2.6.22, Chris Mason, (Tue Jan 22, 3:13 pm)