Hello,

I get very strange things with my Linux. It is a Asus PI-P55TP4XE
motherboard with an Intel P120, 64 MB RAM and two SCSI disks controlled
by an Adaptec 2940 controller. The problem occured under Linux 2.0.23,
.24, .27 and .29 so I think it's not a kernel problem.

After the machine runs for a while suddenly many programs get trapped
(SIGSEGV) or fall in an "uninterruptable sleep" state. Sometimes even
the whole machine crashes so I can't even switch between test consoles.
Moreover it happens that I don't get a login after entering the
loginname - the process gets stuck there forever.

I also tried to compile the kernel on this computer and again very
strange things happened. Sometimes the computer locks up, sometimes I
get strange error messages from the GCC compiler. After restarting the
"make zImage" it walks over the former problem and reports some new
errors somewhere else. This seems to happen randomly!

I already changed harddisks and changed the whole RAM with that of
another Linuxbox. The 2nd box has no problem accessing the disk AND the
RAM. Both are ok in the 2nd computer and even with totally different RAM
SIM's the errors occur.

Any tips are very welcome - I don't know where I could look for this
error!

--

Yours,
   Harry Brueckner
    http://www.**-**.com/

In article <3328FFB1.4251D...@mail.respublica.de>, Harald Brueckner <brueck...@mail.respublica.de> writes:
|> Hello,
|>
|> I get very strange things with my Linux. It is a Asus PI-P55TP4XE
|> motherboard with an Intel P120, 64 MB RAM and two SCSI disks controlled
|> by an Adaptec 2940 controller. The problem occured under Linux 2.0.23,
|> .24, .27 and .29 so I think it's not a kernel problem.
|>
|> After the machine runs for a while suddenly many programs get trapped
|> (SIGSEGV) or fall in an "uninterruptable sleep" state. Sometimes even
|> the whole machine crashes so I can't even switch between test consoles.
|> Moreover it happens that I don't get a login after entering the
|> loginname - the process gets stuck there forever.
|>
|> I also tried to compile the kernel on this computer and again very
|> strange things happened. Sometimes the computer locks up, sometimes I
|> get strange error messages from the GCC compiler. After restarting the
|> "make zImage" it walks over the former problem and reports some new
|> errors somewhere else. This seems to happen randomly!
|>
|> I already changed harddisks and changed the whole RAM with that of
|> another Linuxbox. The 2nd box has no problem accessing the disk AND the
|> RAM. Both are ok in the 2nd computer and even with totally different RAM
|> SIM's the errors occur.
|>
|> Any tips are very welcome - I don't know where I could look for this
|> error!

Is it really a 120MHz-P5? Maybe you got a faked 100MHz-P5... Look at the
CPU/Bus-clock jumpers on the mainboard, if they are set at 120Mhz, try it
with 100MHz. The DRAM timing is maybe on its limit, change it in the BIOS to
the slowest setting available. It can be the cache (disable in the BIOS) or ...
You should try to run some hardware test programs (eg. the ctsi-tools from c't,
a good RAM-checker is included...).

--
        Bye
         Georg Acher, ac...@informatik.tu-muenchen.de        
         http://www.informatik.tu-muenchen.de/~acher/
          "Oh no, not again !" The bowl of petunias          

Try limiting your memorysize to say 60MB (e.g. with LILO), just for
testpurposes. I had problems in compiling the kernel after upgrading to
64MB because of the fact that anything from >=64MB won't be detected
automatically. Giving the kernel the exact RAM-size didn't solve my
problem. So I tried a setting one step below the exact size and any
strange behaviour disappeared! :-)))

Greetinx
        Harvey
------------------------
har...@scray.unterland.de

Linux'95 Upgrade...
        It's not shit!!!