From: Boszormenyi Zoltan <zboszor@freemail.hu>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Havoc Pennington <hp@redhat.com>
Subject: Re: 2.6.0-test6-mm1
Date: Mon, 29 Sep 2003 11:58:45 +0200 [thread overview]
Message-ID: <3F780255.6010408@freemail.hu> (raw)
Hi,
I am trying it out on a RH9. It compiled and seems
to run nicely.
However, there is a problem that annoys me enough now to report.
This is a problem for some time now, it is not a new one.
But it seems to be a problem outside the kernel, read on.
Have you tried to run "make menuconfig" on a 2.6.0testX
in a gnome-terminal?
It gets stuck, not always, but very often. The exact problem
is that on a menu draw (e.g. on entering a submenu or going
one level up) the gnome-terminal window is cleared (everything
is repainted with the background color) but the newly selected
menu does not appear.
gnome-terminal starts (or tries to start) eating 100% CPU,
starting another terminal window succeeds and runnig pstree in
it shows this (I left the pids out):
|-gnome-terminal---bash---pstree
| |-bash---make---make---mconf---lxdialog
| |-gnome-pty-helper
Running kernel[-smp]-2.4.20-20.9 it does not happen.
Closing the stuck window, the CPU usage drops.
"LD_ASSUME_KERNEL=2.2.5 make menuconfig" produces the same
result.
I am cc-ing Havoc Pennington (I found his address in
gnome-terminal's About dialog), he may know where to fix or
he can confirm that a newer gnome-terminal is already fixed.
Using "make menuconfig" in a plain or color xterm, in Konsole
or in the console, the problem does not occur.
--
Best regards,
Zoltán Böszörményi
---------------------
What did Hussein say about his knife?
One in Bush worth two in the hand.
next reply other threads:[~2003-09-29 9:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 9:58 Boszormenyi Zoltan [this message]
2003-09-29 11:28 ` 2.6.0-test6-mm1 Boszormenyi Zoltan
-- strict thread matches above, loose matches on Subject: below --
2003-09-29 2:10 2.6.0-test6-mm1 Andrew Morton
2003-09-29 2:10 ` 2.6.0-test6-mm1 Andrew Morton
2003-09-29 11:14 ` 2.6.0-test6-mm1 Dave Jones
2003-09-29 11:14 ` 2.6.0-test6-mm1 Dave Jones
2003-09-29 18:56 ` 2.6.0-test6-mm1 Andrew Morton
2003-09-29 18:56 ` 2.6.0-test6-mm1 Andrew Morton
2003-09-29 11:32 ` 2.6.0-test6-mm1 Dave Jones
2003-09-29 11:32 ` 2.6.0-test6-mm1 Dave Jones
2003-09-29 17:09 ` 2.6.0-test6-mm1 Daniel McNeil
2003-09-29 17:09 ` 2.6.0-test6-mm1 Daniel McNeil
2003-09-29 17:20 ` 2.6.0-test6-mm1 Andrew Morton
2003-09-29 17:20 ` 2.6.0-test6-mm1 Andrew Morton
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=3F780255.6010408@freemail.hu \
--to=zboszor@freemail.hu \
--cc=hp@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.