From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Pekka Enberg <penberg@gmail.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PROBLEM] Machine Freezes while Running Crossover Office
Date: Mon, 30 May 2005 18:23:30 +0300 [thread overview]
Message-ID: <1117466611.9323.6.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0505291543070.10545@ppc970.osdl.org>
Hi,
On Sun, 2005-05-29 at 15:59 -0700, Linus Torvalds wrote:
> However, I don't understand how wine can block the X server from doing
> even cursor updates. It might be a scheduler bug, of course. The one thing
> a bigger pipe buffer does is end up changing scheduling behaviour.
>
> (On the other hand, I would not be surprised if Wine does something that
> makes X pause, like use DGA or whatever and tells X not to update the
> screen, including cursors).
It is not just X. Running the following shell script when hitting the
bug:
#!/bin/sh
while : ; do
date
sleep 1
done
shows the following output:
penberg ~/pipe-test 49 ./show-date
Mon May 30 18:16:52 EEST 2005
Mon May 30 18:16:53 EEST 2005
Mon May 30 18:16:54 EEST 2005
Mon May 30 18:16:55 EEST 2005
Mon May 30 18:17:15 EEST 2005
Mon May 30 18:17:16 EEST 2005
It looks like no other processes other than wineserver and
wine-preloader get any CPU time (also evident from Sysrq-P traces).
On Sun, 2005-05-29 at 15:59 -0700, Linus Torvalds wrote:
> Are you sure your oprofile PC map is correct?
Yes, the pipe_poll calls come from wineserver actually, not
wine-preloader (of which I showed strace output before).
Any suggestions on how to debug this further? I am not sure I understood
your point about watching poll timeouts.
Pekka
next prev parent reply other threads:[~2005-05-30 15:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 14:46 [PROBLEM] Machine Freezes while Running Crossover Office Pekka Enberg
2005-05-29 18:12 ` Linus Torvalds
2005-05-29 18:20 ` Pekka Enberg
2005-05-29 18:49 ` Linus Torvalds
2005-05-29 20:49 ` Pekka Enberg
2005-05-29 22:59 ` Linus Torvalds
2005-05-29 23:06 ` Kyle Moffett
2005-05-30 15:23 ` Pekka Enberg [this message]
2005-05-30 17:31 ` Linus Torvalds
2005-05-30 18:07 ` Kyle Moffett
2005-05-30 18:22 ` Ingo Molnar
2005-05-30 18:22 ` Linus Torvalds
2005-05-30 18:25 ` Linus Torvalds
2005-05-30 19:12 ` Ingo Molnar
2005-05-31 13:54 ` Greg Stark
2005-05-31 6:15 ` Pekka J Enberg
2005-05-31 6:35 ` Pekka J Enberg
2005-05-31 6:54 ` Ingo Molnar
2005-05-31 16:53 ` Pekka Enberg
2005-05-31 17:24 ` Linus Torvalds
2005-05-31 18:41 ` Ingo Molnar
2005-05-31 21:20 ` Pekka Enberg
2005-06-01 0:07 ` Con Kolivas
2005-06-01 2:31 ` David Lang
2005-06-01 7:35 ` [patch] TASK_NONINTERACTIVE (was: Machine Freezes while Running Crossover Office) Ingo Molnar
2005-06-01 8:42 ` Pekka J Enberg
2005-06-01 8:55 ` [patch] " Con Kolivas
2005-06-01 10:26 ` Pekka J Enberg
2005-06-01 18:06 ` [patch] " Gene Heskett
2005-06-03 8:34 ` Pekka J Enberg
2005-06-03 10:57 ` Ingo Molnar
2005-06-07 13:14 ` Pekka Enberg
2005-10-17 15:10 ` [patch] " Pekka Enberg
2005-10-17 15:15 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1117466611.9323.6.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@gmail.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox