Messages in this thread | | | From | "Bernhard K. Weisshuhn" <> | Subject | 2.0.27 locked solid, need help diagnosing | Date | Thu, 5 Dec 1996 13:30:08 +0100 (MET) |
| |
Hi,
I just killed my 2.0.27. No response whatsoever, no pings, no logfile-entries, sudden death.
I could try to reproduce the thing (suspect is an svga-screensaver, lockvc), but I'm scared. Of course I want to help trace this sucker down, but I want to get it right the first time, since there is some valueable data on the drives.
Could a kind soul supply some pointers on how to conduct such an investigation the safest and most effective way, and what info I should post then to the list?
The lockvc in question was a beta, compiled on a different machine ages ago. This is what ldd says about it:
libm.so.4 (DLL Jump 4.5pl26) => /lib/libm.so.4.6.27 libvga.so.1 (DLL Jump 1.2) => /usr/i486-linuxaout/lib/libvga.so.1.2.6 libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.7.5
Does it make sense to spend time on this or should I recompile with decent libs first and shut up if the problem does not reoccur?
Sort of clueless, --Bernhard
| |