[ILUG] Re: Sleeping Beauty ;(

[Brady, Padraig]

Hrm.. I would suggest CPU problem.
Could you easily clock the CPU back
a bit below the rated spec, say to 400MHz?

Could also be a memory error.
you could get a util to run various
pattern tests on your RAM.
You may find the following links useful:
http://reality.sgi.com/cbrady_denver/memtest86/
http://home.zonnet.nl/vanrein/badram/

Padraig.

> -----Original Message-----
> From: Gerard Gorman [mailto:g.gorman at ic.ac.uk]
> Sent: 18 September 2000 17:33
> To: ilug at linux.ie
> >
> 
> Hi,
> Some of you might remember this thread from last week..... 
> Well things are still
> shagged (Yes..I'm really starting to lose it now). The linux 
> box (2.2.16) seems
> to crash in a non deterministic manner.  On most occasions it 
> crashed while
> running a screen saver (no time correlation observable). It 
> has also crashed
> during compilations.
> 
> The other observation I made is it makes a mistake during a 
> fft calculation.
> 
> The processor is a K6-500 AMD. Should I start getting 
> suspicious of the
> processor?
> The only other fact that I can think of which may be 
> important is that there is
> no thermal paste between the processor and cooling fins 
> (though it is firmly
> attached with a fan). Might this be a problem of overheating. 
> The core voltage is
> 2.2V which is the recommended.
> 
> I'd **really** appreciate suggestions regarding this as I am 
> on the verge of
> throwing in the towel and getting a regular intel proc & chipset. :((
> 
> Cheers
> g
> 
> 
> > Kenn Humborg wrote:
> >
> > > > Sep 14 04:02:00 athos anacron[5196]: Updated timestamp for job
> > > > `cron.daily' to
> > > > 2000-09-14
> > > > Sep 14 04:04:05 athos PAM_pwdb[5309]: (su) session 
> opened for user news by
> > > > (uid=0)
> > > > Sep 14 04:04:05 athos PAM_pwdb[5309]: (su) session 
> closed for user news
> > > > Sep 14 11:43:34 athos syslogd 1.3-3: restart.
> > > > Sep 14 11:43:34 athos syslog: syslogd startup succeeded
> > > >
> > > >
> > > > ? Does this mean that news is crashing my system?
> > >
> > > No.  The news job ends (session closed for user news).
> > >
> > > Modify the startup script for syslogd to give it a "-m 20"
> > > option.  This writes a timestamp into the logs every 20 minutes.
> > >
> > > This will help to determine exactly when the machine hangs.
> > > If this stops it hanging, perhaps it is APM related, as this
> > > will kick the disk every 20 mins.  Increase the interval until
> > > it hangs again.  This might provide some clues.
> > >
> > > Later,
> > > Kenn