lkml.org 
[lkml]   [2002]   [Jan]   [2]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
FromRob Landley <>
SubjectRe: [patch] Re: Framebuffer...Why oh Why???
DateTue, 1 Jan 2002 15:36:41 -0500
On Tuesday 01 January 2002 05:42 am, Alan Cox wrote:
> > > X11 isn't always an improvement.  I've got an X hang on my laptop
> > > (about once a week) that freezes the keyboard and ignores mouse clicks.
> > >  Numlock doesn't change the keyboard LEDs, CTRL-ALT-BACKSPACE won't do
> > > a thing, and although I can ssh in and run top (and see the CPU-eating
> > > loop), kill won't take X down and kill-9 leaves the video display up so
> > > the console that thinks it's in text mode, but isn't, is still useless.
> > >  (And that's assuming I'm plugged into the network and have another box
> > > around to ssh in from...)
>
> Neomagic Magicgraph 128XD ? If so check man neomagic first 8)

Neomagic 256AV.  I'll feed it the two disables the man page recommends and 
see if that makes the problem go away.  (I can trigger it almost at will by 
playing around with kmail with the threaded view of 2500+ linux-kernel 
messages and paging up and down really fast.  Or by switching the display 
when )

Kmail seems to be the only thing that actually triggers it.  I can't think of 
a lockup where kmail wasn't involved, but killing kmail (or the whole of kde) 
won't unfreeze the display and keyboard once it's borked, and when I ssh in 
and run top it's X that's got the cpu pegged at 99%, not any of the kde 
toys...

Rob

-
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/

\
 
 \ /
  Last update: 2005-03-22 12:15    [from the cache]
©2003-2008