From: Paul Dickson <dickson@permanentmail.com>
To: linux-kernel@vger.kernel.org, rhl-devel-list@redhat.com
Cc: Antonio Vargas <wind@cocodriloo.com>
Subject: Re: My report on running 2.6.0-test2 on a Dell Inspiron 7000 (possible tty trouble)
Date: Wed, 6 Aug 2003 06:09:39 -0700 [thread overview]
Message-ID: <20030806060939.1b2a1521.dickson@permanentmail.com> (raw)
In-Reply-To: <20030806114234.GD814@wind.cocodriloo.com>
On Wed, 6 Aug 2003 13:42:34 +0200, Antonio Vargas wrote:
> On Wed, Aug 06, 2003 at 02:22:56AM -0700, Paul Dickson wrote:
>
> > I built 2.6.0-test2 for my Dell Inspiron 7000 notebook (PII, 300Mhz) with
> > a RH9 distribution. I build the kernel on another system (1.33GHz) using
> > ssh.
> >
> > I was missing some device support, so did a "make menuconfig". The
> > configuration options were shown, I selected "Sound -->" and pressed
> > enter. The terminal went back to text mode and then hung. Gnome-terminal
> > started consuming all unused CPU cycles.
> >
> > I could recover the process by closing the tab or resetting the terminal,
> > but this would only fix the problem for the moment. Frequently, it
> > wouldn't even finish redisplaying the screen before it locked again.
> >
> > This would happen running "make menuconfig" locally or via ssh on another
> > system.
> >
> > This is likely caused by some difference in the tty code in 2.6.0-test2.
> > The problem does not occur under 2.4.20-18.9. If 2.6.0-test2 is correct,
> > then I might need an updated version of gnome-terminal suitable for 2.6.0.
>
> This is a bug in gnome-terminal:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=89151
>
This bug is still in the gnome-terminal version included with Severn.
-Paul
next prev parent reply other threads:[~2003-08-06 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 9:16 My report on running 2.6.0-test2 on a Dell Inspiron 7000 (PII, 300MHz with 256MB) Paul Dickson
2003-08-06 9:22 ` My report on running 2.6.0-test2 on a Dell Inspiron 7000 (possible tty trouble) Paul Dickson
2003-08-06 11:42 ` Antonio Vargas
2003-08-06 13:09 ` Paul Dickson [this message]
2003-08-06 14:12 ` Havoc Pennington
2003-08-06 9:35 ` My report on running 2.6.0-test2 on a Dell Inspiron 7000 (PII, 300MHz with 256MB) Paul Dickson
2003-08-06 10:03 ` My report on running 2.6.0-test2 on a Dell Inspiron 7000 (lost USB mouse) Paul Dickson
2003-08-06 21:40 ` Greg KH
2003-08-06 10:58 ` My report on running 2.6.0-test2 on a Dell Inspiron 7000 (poor sound from crond) Paul Dickson
2003-08-06 13:49 ` My report on running 2.6.0-test2 on a Dell Inspiron 7000 (crash while shutting down) Paul Dickson
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=20030806060939.1b2a1521.dickson@permanentmail.com \
--to=dickson@permanentmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rhl-devel-list@redhat.com \
--cc=wind@cocodriloo.com \
/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;
as well as URLs for NNTP newsgroup(s).