[Prev][Next][Index][Thread]
My machine going crazy
Hi all.
First of all - this is a long letter. Sorry. I have a big problem
and a lot of information might be connected to it.
Well I have a problem. I don't know if it is a hardware problem,
A virus, error in upgrading or just very unstable kernel...
I'll start by stating that I read over and over again and again the
release notes of the kernels I used and other packages I installed.
Well I have 486/66Mhz old machine with two IDE disks. The one that
run the Linux is the second one (1.2G) (the linux root partition of
it is 300M and is the first one).
I start the linux with lodlin.
The distribution I installed was Slackware 3.0 with 1.2.13.
I upgraded this kernel to 1.3.89. Here I had already something wierd:
I got the file linuxelf-1.3.90.tgz and after the compiling and the
installation I got kernel 1.3.89.
BTW I upgraded since I had to have quota. Because
I didn't find a quota that will work with 1.2.13 I upgraded
to kernel above 1.3.80 (where the quota comes with the kernel).
After upgrading the kernel I upgraded the following:
procps-0.99a
gcc-2.7.2
libc-5.2.18
libg++-2.7.1.4
binutils-2.6.0.14
ld.so-1.7.14
make-3.74 (+the patch in realese.libc-5.2.18)
modules-1.3.57
sysinit-2.60
I worked with this configuration for few days. And I had a problem: the
computer stoped to react from time to time for few seconds (till
2 minutes!). I.e. It looked like a real crash (no keyboard lights, no
disk noises) but after a while the computer came back.
I thought - maybe this kernel is lousy, and took the 2.0.pre7. (True -
this might be even more unstable... But I was naive and thought that
the problems in the older one must be solved already :-)
After the intallation the "crash" problem vanished and I was really
happy.
The real problems begun two days afterward. Sorry. I really don't
know what happen before the following problems begun - a preson doesn't
plan to have such problems and doesn't make a log of his reboot timings
etc...
The linux didn't let me login. "wierd" I thought, and reboot again.
Got in (by the same login) and thought "really wierd". I started the
"startx" and nothing. nothing ran. "rrr...." and reboot again.
login, start the startx the X windows started and then the screen slowly,
from the bottom of it, become black. A real crash --> I made a hard reset.
Now I started to write what happens:
I got in read only filesystem and made the necessary fsck.
reboot again: got in the messages of the startup -
init: can't resolve symbolic '__environ'
and crash.
reboot again:
crash after -
INIT: verstion 2.60 booting
hard reset:
of course I need to run fsck again - but I couldn't get
into
my account - the passwd was wrong!
reboot: Now my passwd was ok (the same of course). I ran fsck.
reboot: in the startup messages -
mapscrn: can't resolve symbolic 'opel'
but I could get in.
starting 'startx' nothing happen.
tried to understand what's going on and run man -k ...
and got -
usr/bin/apropos: syntax error near unexpected token `['
/usr/bin/apropos: /usr/bin/apropos: line 47: `while [ $found = 0
-a -n "$1" ]'
Error executing formatting or display command.
System command exited with status 512.
so I did another boot.
reboot: got crash in the startup messages -
init: can't resolve symbolic '__errno_locatiol'
reboot: got crash in the startup messages -
init: can't resolve symbolic 'strrchr'
.... well I tried a little more ... I got a lot new phenomenas like
'less' causing
segmentation fault, or 'man' gives:
Error executing formatting or display command.
System command exited with status 35584.
I really don't know what's going on here. A virus ? a bad disk ?
upgrading problems ?
Please give me hints if you have some.
Rani.
---------------------------------------------------------------------------
Rani Pinchuk <pinchuk@kinetica.com> Kinetica Internetting Solutions LTD.
Tel: 972-3-6418130
---------------------------------------------------------------------------
Follow-Ups:
References: