My report on running 2.6.0-test2 on a Dell Inspiron 7000 (possible tty trouble)

Paul Dickson dickson at permanentmail.com
Wed Aug 6 13:09:39 UTC 2003


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





More information about the devel mailing list