Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261667AbVE3SVl (ORCPT ); Mon, 30 May 2005 14:21:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261668AbVE3SVl (ORCPT ); Mon, 30 May 2005 14:21:41 -0400 Received: from fire.osdl.org ([65.172.181.4]:23765 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261667AbVE3SVZ (ORCPT ); Mon, 30 May 2005 14:21:25 -0400 Date: Mon, 30 May 2005 11:22:48 -0700 (PDT) From: Linus Torvalds To: Kyle Moffett cc: Pekka Enberg , Pekka Enberg , Kernel Mailing List , Ingo Molnar Subject: Re: [PROBLEM] Machine Freezes while Running Crossover Office In-Reply-To: Message-ID: References: <1117291619.9665.6.camel@localhost> <84144f0205052911202863ecd5@mail.gmail.com> <1117399764.9619.12.camel@localhost> <1117466611.9323.6.camel@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 820 Lines: 22 On Mon, 30 May 2005, Kyle Moffett wrote: > > If X is hung and not accepting data on any of its sockets, then this > could hang the Xterm in the background, and therefore hang the printout > from the "date" process. Nope. There's a pty in between, and the pty buffer is much bigger than just a few lines, so even if an xterm is hung, the program displaing on an xterm wouldn't be affected normally (unless it reads from the tty or outputs several kB of data). So it's either a kernel scheduling problem, or Crossover running with RT priority and screwing up. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/