From: Pekka Enberg <penberg@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>, linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] Machine Freezes while Running Crossover Office
Date: Sun, 29 May 2005 21:20:45 +0300 [thread overview]
Message-ID: <84144f0205052911202863ecd5@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505291059540.10545@ppc970.osdl.org>
Hi Linus,
On Sat, 28 May 2005, Pekka Enberg wrote:
> > I did a binary search and found out that 2.6.10-bk10 introduced this
> > bug. The kernel includes Linus' changes for pipes to use circular buffers.
> > A oprofile run shows that kernel is spending lots of time in poll_pipe. I
> > also have Alt-Sysrq-P traces that indicate to the same direction. I have
> > included vmstat, Alt-SysRq-P, and oprofile traces in this mail (see below
> > for section X.).
On 5/29/05, Linus Torvalds <torvalds@osdl.org> wrote:
> Can you try to see if you can get an "strace" snippet of X (or the window
> manager) when this happens, since it seems to reproducible by you..
>
> Also, I actually find it very surprising that you see X doing anything
> _at_all_ with a pipe, since all the X connections should be just normal
> sockets. There are no pipes involved anywhere afaik.
>
> Your description sounds exactly like X is busy processing some slow
> operation (or possibly the window manager, but I think virtual console
> switches happen without the WM being involved). The most common such slow
> operation is a new font being generated, but I don't see why that would
> have anything to do with pipes either...
Looking at output of lsof, I can see that Crossover is using pipes. I
am not very familiar with wine internals but there seems to be two
processes, wine_preloader and wine, that talk to each other through
pipes. Unfortunately, stracing either one of the processes masks the
problem. That is, I cannot reproduce the hang while doing strace.
Pekka
next prev parent reply other threads:[~2005-05-29 18:21 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 [this message]
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
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=84144f0205052911202863ecd5@mail.gmail.com \
--to=penberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--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