mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Dickson <dickson@permanentmail.com>
To: "Chris Peterson" <chris@potamus.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] "ls -R" freezes when using gnome-terminal on linux-2.6.0-test4
Date: Sun, 7 Sep 2003 15:10:29 -0700	[thread overview]
Message-ID: <20030907151029.331f5fa4.dickson@permanentmail.com> (raw)
In-Reply-To: <001301c3756f$18f847d0$323be90c@bananacabana>

On Sun, 7 Sep 2003 11:37:31 -0700, Chris Peterson wrote:

> I have discovered a regression between linux-2.4.20-8 (Redhat 9) and
> linux-2.6.0-test4. I have not tried any other versions of linux-2.6.0-testX
> or 2.5.x.
> 
> How to reproduce the problem:
> 1. Running GNOME on linux-2.6.0-test4, open two gnome-terminals.
> 2. In the first gnome-terminal, run "ls -R /" or "ls -R /dev" (you won't
> have to wait as long :-).
> 3. In the second gnome-terminal, simply run "ls" (or just opening a
> gnome-terminal window will sometimes cause the same problem).
> 
> Actual Results:
> The ls in the first gnome-terminal will usually freeze. Neither CTRL+C nor
> CTRL+Z will kill the ls process. The gnome-terminal itself is NOT frozen.
> Its window menus are still responsive.
> 

If you reset the terminal via the menu, the terminal will unfreeze (until
the next freeze).

Grab the RPMs from Severn for gnome-terminal and vte.  It will slow down
the terminal I/O and avoid the problem.  I'm not entirely sure whether
this is a fix or just avoiding the problem with more computation (I'm
running on a 300 MHz notebook), but I can now do a "make menuconfig".

	-Paul


  reply	other threads:[~2003-09-07 22:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-07 18:37 Chris Peterson
2003-09-07 22:10 ` Paul Dickson [this message]
2003-09-07 22:52   ` Chris Peterson

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=20030907151029.331f5fa4.dickson@permanentmail.com \
    --to=dickson@permanentmail.com \
    --cc=chris@potamus.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®