Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261977AbVEaRKq (ORCPT ); Tue, 31 May 2005 13:10:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261936AbVEaRJ2 (ORCPT ); Tue, 31 May 2005 13:09:28 -0400 Received: from courier.cs.helsinki.fi ([128.214.9.1]:30120 "EHLO mail.cs.helsinki.fi") by vger.kernel.org with ESMTP id S261962AbVEaQ42 (ORCPT ); Tue, 31 May 2005 12:56:28 -0400 Subject: Re: Machine Freezes while Running Crossover Office From: Pekka Enberg To: Ingo Molnar Cc: Linus Torvalds , Pekka Enberg , Kernel Mailing List In-Reply-To: <20050531065456.GA21948@elte.hu> References: <1117291619.9665.6.camel@localhost> <84144f0205052911202863ecd5@mail.gmail.com> <1117399764.9619.12.camel@localhost> <1117466611.9323.6.camel@localhost> <20050531065456.GA21948@elte.hu> Date: Tue, 31 May 2005 19:53:54 +0300 Message-Id: <1117558435.9228.7.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Evolution 2.2.1.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 70536 Lines: 1051 Hi, I did a full strace of wine and its child processes and it does not call sys_sched_setscheduler. Furthermore, top shows that wineserver and wine-preloader are running on the same priority as X so I don't think it's using RT priorities. On Tue, 2005-05-31 at 08:54 +0200, Ingo Molnar wrote: > - run the Wine processes with nice +19 priority? (just to check > whether it's the interactivity code. After you've made sure they dont > have RT priorities.) nice +19 -> no hang On Tue, 2005-05-31 at 08:54 +0200, Ingo Molnar wrote: > - renice -20 the X server process renice -20 -> no hang On Tue, 2005-05-31 at 08:54 +0200, Ingo Molnar wrote: > - run a shell-script with RT priority that captures 'ps aux' every > second or so: Crossover hangs but script produces output. I've included it below. On Tue, 2005-05-31 at 08:54 +0200, Ingo Molnar wrote: > - apply the patch below and check whether doing: > > echo 0 > /proc/sys/kernel/interactive > > makes the hang go away. It's actually /proc/sys/vm/interactive but yes, 0 makes the hang go away while 1 makes it come back. On Tue, 2005-05-31 at 08:54 +0200, Ingo Molnar wrote: > - if the hang goes away then could you check whether removing the 2 new > sched_interactive lines in kernel/sched.c's effective_prio() function > (but keeping other portions of the patch applied) hang or not. Exactly the same results as the previous, 0 -> no hang, 1 -> hangs. Also, I tried the old date script in virtual console. It worked exactly the same as in xterm. I did not try your RT patch, Ingo. Do you want me to try it out? Pekka The hang starts almost immediately (from the first or second date): Tue May 31 18:40:29 EEST 2005 PID TID CLS RTPRIO NI PRI PSR %CPU STAT WCHAN COMMAND 1 1 TS - 0 23 0 0.0 S select init 2 2 TS - 19 5 0 0.0 SN ksoftirqd ksoftirqd/0 3 3 TS - -5 29 0 0.0 S< worker_thread events/0 4 4 TS - -5 25 0 0.0 S< worker_thread khelper 9 9 TS - -5 28 0 0.0 S< worker_thread kthread 18 18 TS - -5 29 0 0.0 S< worker_thread kacpid 90 90 TS - -5 29 0 0.0 S< worker_thread kblockd/0 139 139 TS - 0 24 0 0.0 S pdflush pdflush 140 140 TS - 0 24 0 0.0 S pdflush pdflush 142 142 TS - -5 27 0 0.0 S< worker_thread aio/0 141 141 TS - 0 24 0 0.0 S kswapd kswapd0 734 734 TS - 0 23 0 0.0 S serio_thread kseriod 929 929 TS - 0 24 0 0.0 S hub_thread khubd 1338 1338 TS - 0 24 0 0.0 S kjournald kjournald 5849 5849 TS - -4 25 0 0.0 S