2.2.16, 2.4.*, harddeadlocks with XFree86 and framebuffer

2.2.16, 2.4.*, harddeadlocks with XFree86 and framebuffer

[Elmer Joandi]

So, the problem is on different hardware and kernel versions.

1. looks like VT switch with multiple X copies running  hangs  on
certain conditions
2. More critical: Matrox  G400  dualhead AGP 16M hangs immediately with
fb.


Tested computers:
   1.  Tyan 230 SMP Dual PIII  667Mhz , 512MB
   2. MSI  SMP Dual PIII 667Mhz 512MB
   3. Tyan 1834  SMP Dual Celeron 256MB
Software:
  1  compiled: 2.4.0,2.4.2,.2.4.2-ac8
   2  RH7 stock: 2.2.16

1. True multihead hang on computers 2, 3, both software :
     First,  to get it fly:
     I must log in via network, because executing X behind
X/console causes vt switch.
    First I run USB keyboard patched X for ATI cards, non-fb.
     That one I can run forever, normally, until:
     if to execute matrox (two cards : Millenium + Mystique) server,
    it hangs or wont work
    if I modprobe  matrofb_base, then now I have single possibility
    to run Xfree86-4  _once_ for matrox fb.
     If either of X's(for two matroxes or ATIs) quits, there is
hardlock.
    ping stops, capslock doesnt work(for console keyboard, USB one
    naturally doesnt work at all),

2.  Single dualhed G400 hang, on computers 1 2 3, software 1,2 .
    Well, it is simpler, it hangs with framebuffer and with normal X
mode,
    with 2.2.16 and with 2.4.*, quite soon.
     inserting framebuffer module hangs the beast.
    framebuffer matrox compiled into kernel does not hang until I try to

    start X in some ways or do other console change/swtiching
operations...

      Actually, RedHat 7.0 doesnt install on SMP Matrox dualhead G400 as

    XWindows setup probe lock the box up.



It looks like I should tear it down and use old nfsroot based Xtermian
again...
And sell G400, with which there is nothing to do.

Pity, everything works, but once a day ATI XFree86 sucks some dust in
and
gets killed and the whole box goes with it., cant stand it...



Elmer.