RE: [newbie] System locks up every 10days

2004-09-06 Thread Tony S. Sykes
Have you got lapic disabled in lilo/grub? I found stopping this keeps my system up 
24/7 after I was having problems of it dropping every now and again.

Tony.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Tom Brinkman
 Sent: Saturday, September 04, 2004 3:46 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [newbie] System locks up every 10days
 
 
 On Friday 03 September 2004 04:06 pm, Chris wrote:
  Sep 3 14:18:21 cpollock sensord:  SYS Temp: 40.0 C (limit =
  49.7 C, hysteresis = 39.9 C)
  Sep 3 14:18:21 cpollock sensord:  SBr Temp: 26.0 C (limit =
  65.4 C, hysteresis = 59.9 C)
 
 I forgot to deal with this in my last reply.  For your board, 
 SYS is your chipset, SBr can be taken as your case temp. 26C is 
 79F, and that should be close to, but a touch higher than your 
 ambient room temperature.  Which it appears to be so.
 -- 
   Tom Brinkman Corpus Christi, Texas
Proud to be an American
 
 


-+-+-+-+-+-+-+-+-+ Business Computer Projects - Disclaimer -+-+-+-+-+-+-+-+-+-
This message, and any associated attachment is confidential.  If you have received
it in error, please delete it from your system, do not use or disclose the information
in any way, and notify either the sender or [EMAIL PROTECTED] immediately.
The contents of this message may contain personal views which are not necessarily 
the views of Business Computer Projects Ltd., unless specifically stated.  Whilst every
effort has been made to ensure that emails and their attachments are virus free, it is 
the responsibility of the recipient(s) to verify the integrity of such emails.
Business Computer Projects Ltd
BCP House
151 Charles Street
Stockport
Cheshire
SK1 3JY
Tel: +44 (0)161 355-3000
Fax: +44 (0)161 355-3001
Web: http://www.bcpsoftware.com


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com



Re: [newbie] System locks up every 10days

2004-09-04 Thread Tom Brinkman
On Friday 03 September 2004 04:06 pm, Chris wrote:
 On Friday 03 September 2004 09:50 am, Tom Brinkman wrote:
  SYS = SBr   On most all boards the SB temp is from a
  thermistor at or very near the boards main chipset. The
  warmest part of your motherboard.  Usually taken from a pin
  on the chipset. Normally around 40C, should stay under 45C,
  but 50C would be the upper limit.  Mine'll hit 46C running
  cpuburn's 'burnK7' (extreme load), CPU is in the upper 50C's
  at this point, also an upper limit, with ambient room temp
  around 80F.

 From the googling done, SBr is the southbridge chip, but, as I
 said earlier I don't know what its function is.

South bridge is part of the Mboard's chipset. EG, VIA KT600, 
nForce2, SiS M741, etc.  As to function, start here 
http://computer.howstuffworks.com/motherboard.htm
and keep lookin ;)  Basically the chipset (northsouth) bridge, is 
just that... a bridge between the CPU and other parts of the 
system. 

 Sep  3 14:18:21 cpollock sensord:   CPU Temp: 46.9 C (limit =
 59.9 C, hysteresis = 55.1 C)
 Sep  3 14:18:21 cpollock sensord:   SYS Temp: 40.0 C (limit =
 49.7 C, hysteresis = 39.9 C)
 Sep  3 14:18:21 cpollock sensord:   SBr Temp: 26.0 C (limit =
 65.4 C, hysteresis = 59.9 C)

 These are reported twice an hour with logcheck and emailed to
 me.

 That's fine, but if you're temps are in the normal range, 
which yours are for an Athlon, you really only need to monitor 
them while under heavy to extreme load.  EG, using mprime's 
torture test  
'./mprime -m, choose 17'  http://www.mersenne.org/freesoft.htm

  in one console, start another and run 'sensors' frequently 
to monitor temps.  At least till they stabilize at an upper 
limit.  This is a very good stress test and is a first step if 
hardware problems are suspected, eg, system lock ups, freezes, 
random reboots, failed compiles (at different points), etc.

 FWIW, I use an alias to display CPU, SBr, and HDD temps
alias sc='sensors | grep Temp:  /usr/sbin/hddtemp /dev/hd[ab]'
 tom $ sc
CPU Temp:+46°C  (low  =   +35°C, high =   +55°C)   sensor = 
thermistor
M/B Temp:+40°C  (low  =   +20°C, high =   +45°C)   sensor = 
thermistor
/dev/hda: Maxtor 6Y080L0: 62°C
/dev/hdb: MAXTOR 6L040J2: 38°C
-- 
  Tom Brinkman Corpus Christi, Texas
   Proud to be an American


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com



Re: [newbie] System locks up every 10days

2004-09-04 Thread Tom Brinkman
On Friday 03 September 2004 04:06 pm, Chris wrote:
 Sep  3 14:18:21 cpollock sensord:   SYS Temp: 40.0 C (limit =
 49.7 C, hysteresis = 39.9 C)
 Sep  3 14:18:21 cpollock sensord:   SBr Temp: 26.0 C (limit =
 65.4 C, hysteresis = 59.9 C)

I forgot to deal with this in my last reply.  For your board, 
SYS is your chipset, SBr can be taken as your case temp. 26C is 
79F, and that should be close to, but a touch higher than your 
ambient room temperature.  Which it appears to be so.
-- 
  Tom Brinkman Corpus Christi, Texas
   Proud to be an American


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com



Re: [newbie] System locks up every 10days

2004-09-03 Thread Chris
On Friday 03 September 2004 09:50 am, Tom Brinkman wrote:

 SYS = SBr   On most all boards the SB temp is from a
 thermistor at or very near the boards main chipset. The warmest
 part of your motherboard.  Usually taken from a pin on the
 chipset. Normally around 40C, should stay under 45C, but 50C
 would be the upper limit.  Mine'll hit 46C running cpuburn's
 'burnK7' (extreme load), CPU is in the upper 50C's at this point,
 also an upper limit, with ambient room temp around 80F.


From the googling done, SBr is the southbridge chip, but, as I said earlier 
I don't know what its function is.  

Sep  3 14:18:21 cpollock sensord:   CPU Temp: 46.9 C (limit = 59.9 C, 
hysteresis = 55.1 C)
Sep  3 14:18:21 cpollock sensord:   SYS Temp: 40.0 C (limit = 49.7 C, 
hysteresis = 39.9 C)
Sep  3 14:18:21 cpollock sensord:   SBr Temp: 26.0 C (limit = 65.4 C, 
hysteresis = 59.9 C)

These are reported twice an hour with logcheck and emailed to me.

-- 
Chris
Registered Linux User 283774 http://counter.li.org
3:55pm up 1 day, 19:13, 2 users, load average: 0.47, 0.45, 0.28

There has been an alarming increase in the number of things you know
nothing about.

Live - From Virgin Radio UK Ramones - Do you remember rock and roll



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com



Re: [newbie] System locks up every 10days

2004-09-02 Thread Tom Brinkman
On Wednesday 01 September 2004 07:59 pm, Chris wrote:
  out.

 SYS Temp:  +45.5°C  (limit =  +50°C, hysteresis =  +40°C)
 CPU Temp:  +38.0°C  (limit =  +60°C, hysteresis =  +55°C)

 In 'F' Gkrellm reports these to be around 113 and 100, which to
 me appear to be ok, although I may be wrong here.

Read /etc/sensors.conf   You appear to have one of the many 
boards that reverses temperatures.  45C is your CPU, 38C is your 
Mboard (chipset), SYS.  You can fix it by editing sensors.conf, 
or just keep in mind that your temps are reversed.

Both those temps are about right for moderate (normal) loads 
in relatively normal ambient (room) temp, 75 to 80F.
-- 
  Tom Brinkman Corpus Christi, Texas
   Proud to be an American


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com



Re: [newbie] System locks up every 10days

2004-09-02 Thread Chris
On Thursday 02 September 2004 10:49 am, Tom Brinkman wrote:
 On Wednesday 01 September 2004 07:59 pm, Chris wrote:
   out.
 
  SYS Temp:  +45.5°C  (limit =  +50°C, hysteresis =  +40°C)
  CPU Temp:  +38.0°C  (limit =  +60°C, hysteresis =  +55°C)
 
  In 'F' Gkrellm reports these to be around 113 and 100, which to
  me appear to be ok, although I may be wrong here.

 Read /etc/sensors.conf   You appear to have one of the many
 boards that reverses temperatures.  45C is your CPU, 38C is your
 Mboard (chipset), SYS.  You can fix it by editing sensors.conf,
 or just keep in mind that your temps are reversed.

 Both those temps are about right for moderate (normal) loads
 in relatively normal ambient (room) temp, 75 to 80F.

Thanks Tom, I made the change after reading the notes for my chip.  Makes a 
little more sense now.  One thing though, what is the SBr temp?  I've done 
some Googling but can't seem to find an explanation of what the Southbridge 
chip is/does.

-- 
Chris
Registered Linux User 283774 http://counter.li.org
5:15pm up 20:32, 2 users, load average: 0.41, 0.26, 0.13

He is truly wise who gains wisdom from another's mishap.




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com



Re: [newbie] System locks up every 10days

2004-09-01 Thread Vincent Voois

Chris wrote:
This an odd question and there may not be a valid answer, but here goes.  
About every 10days the system locks up for seemingly unrelated reasons.  
For instance, last time it happened it locked up while one of the 
X-Screensavers was running.  I noted which one was on the screen at the 
time and disabled it.  I've since only enabled two of the screensavers, 
Nose Guy and Phosper.  Last night I installed FSV just to see how it 
looked, install went fine and it ran great, tonight I brought it up, went 
to open a directory and the system locked up tighter than a drum, uptime 
was at about 10days, 20+ hrs.  Last time the lockup came at about the same 
amount of uptime.  This is with MDK 9.0.  Althought I've gone 30+ days 
previously before I had to hit the reset due to a lockup and if I remember 
that was due to a game that the system just didn't like.  Any ideas on what 
could be the problem?
It does it around every 11 days right?
I have seen a similar problem once before but it only locked up certain software and not the whole system
The cause was a program running a system timer (in milliseconds) that collapsed due to the limit of the type of variable used 
for it.
Hmmz... a 32bit Unsigned long how many milliseconds can it hold? And how many days is that together?

Are you sure it's the system hanging and not the screensaver causing you not able to 
interact with the rest of the system anymore?



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com



Re: [newbie] System locks up every 10days

2004-09-01 Thread Chris
On Tuesday 31 August 2004 10:50 pm, jon fuller wrote:
 I can't even seem to load the program from the disks I bought is there
 any driver issues with my hardware?  It haults and asks me to reboot when
 I'm loading the packages. Specifically when it gets to Fonts.

 mandrake 10 64 version

 athlon 64 3000
 asus K8V
 2 raptors 70 gigs apiece
 9600XT
 sony CDRW

 Dennis Myers [EMAIL PROTECTED] wrote:

 On Tuesday 31 August 2004 09:54 pm, Chris wrote:
  On Tuesday 31 August 2004 09:30 pm, Dennis Myers wrote:
   On Tuesday 31 August 2004 08:25 pm, Chris wrote:
This an odd question and there may not be a valid answer, but here
goes. About every 10days the system locks up for seemingly
unrelated reasons. For instance, last time it happened it locked up
while one of

Methinks you hijacked my thread Jon.

-- 
Chris
Registered Linux User 283774 http://counter.li.org
5:38pm up 11:20, 1 user, load average: 0.36, 0.19, 0.10

Old Barlow was a crossing-tender at a junction where an express train
demolished an automobile and its occupants. Being the chief witness, his
testimony was vitally important. Barlow explained that the night was dark,
and he waved his lantern frantically, but the driver of the car paid
no attention to the signal.
The railroad company won the case, and the president of the company
complimented the old-timer for his story. You did wonderfully, he said,
I was afraid you would waver under testimony.
No sir, exclaimed the senior, but I sure was afraid that durned
lawyer was gonna ask me if my lantern was lit.

Live - From Virgin Radio UK Genesis - Turn It On Again



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com



Re: [newbie] System locks up every 10days

2004-08-31 Thread Dennis Myers
On Tuesday 31 August 2004 08:25 pm, Chris wrote:
 This an odd question and there may not be a valid answer, but here goes.
 About every 10days the system locks up for seemingly unrelated reasons.
 For instance, last time it happened it locked up while one of the
 X-Screensavers was running.  I noted which one was on the screen at the
 time and disabled it.  I've since only enabled two of the screensavers,
 Nose Guy and Phosper.  Last night I installed FSV just to see how it
 looked, install went fine and it ran great, tonight I brought it up, went
 to open a directory and the system locked up tighter than a drum, uptime
 was at about 10days, 20+ hrs.  Last time the lockup came at about the same
 amount of uptime.  This is with MDK 9.0.  Althought I've gone 30+ days
 previously before I had to hit the reset due to a lockup and if I remember
 that was due to a game that the system just didn't like.  Any ideas on what
 could be the problem?
have you checked the syslogs? Kinda sounds like something is being saved to 
say /tmp until there is no room and /tmp is only cleared on reboot. Just a 
wild guess.
-- 
Dennis M. linux user #180842


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com



Re: [newbie] System locks up every 10days

2004-08-31 Thread Chris
On Tuesday 31 August 2004 09:30 pm, Dennis Myers wrote:
 On Tuesday 31 August 2004 08:25 pm, Chris wrote:
  This an odd question and there may not be a valid answer, but here
  goes. About every 10days the system locks up for seemingly unrelated
  reasons. For instance, last time it happened it locked up while one of

 have you checked the syslogs? Kinda sounds like something is being saved
 to say /tmp until there is no room and /tmp is only cleared on reboot.
 Just a wild guess.

Dennis, in the /root/tmp are 192 hidden files called .drakx-stdout.(a number 
here, ie..11153.  The contents of these files are:

alsa0:off   1:off   2:on3:on4:on5:on6:off
dm  0:off   1:off   2:off   3:off   4:off   5:on6:off
kheader 0:off   1:off   2:on3:on4:off   5:on6:off
keytable0:off   1:off   2:on3:on4:on5:on6:off
netfs   0:off   1:off   2:off   3:on4:on5:on6:off
network 0:off   1:off   2:on3:on4:on5:on6:off
partmon 0:off   1:off   2:off   3:on4:on5:on6:off
random  0:off   1:off   2:on3:on4:on5:on6:off
rawdevices  0:off   1:off   2:off   3:on4:on5:on6:off
sound   0:off   1:off   2:on3:on4:on5:on6:off
saslauthd   0:off   1:off   2:on3:on4:on5:on6:off
syslog  0:off   1:off   2:on3:on4:on5:on6:off
crond   0:off   1:off   2:on3:on4:on5:on6:off
xfs 0:off   1:off   2:on3:on4:on5:on6:off
portmap 0:off   1:off   2:off   3:on4:on5:on6:off
xinetd  0:off   1:off   2:off   3:on4:on5:on6:off
httpd   0:off   1:off   2:off   3:off   4:off   5:off   6:off
apmd0:off   1:off   2:on3:on4:on5:on6:off
cups0:off   1:off   2:on3:on4:on5:on6:off
linuxconf   0:off   1:off   2:on3:on4:on5:on6:off
iptables0:off   1:off   2:on3:on4:on5:on6:off
atd 0:off   1:off   2:off   3:on4:on5:on6:off
devfsd  0:off   1:off   2:on3:on4:on5:on6:off
gpm 0:off   1:off   2:on3:on4:on5:on6:off
postgresql  0:off   1:off   2:off   3:off   4:off   5:off   6:off
numlock 0:off   1:off   2:off   3:on4:on5:on6:off
rwhod   0:off   1:off   2:off   3:off   4:off   5:off   6:off
routed  0:off   1:off   2:off   3:off   4:off   5:off   6:off
postfix 0:off   1:off   2:on3:on4:on5:on6:off
mysql   0:off   1:off   2:off   3:off   4:off   5:off   6:off
named   0:off   1:off   2:off   3:on4:on5:on6:off
ipvsadm 0:off   1:off   2:off   3:on4:on5:on6:off
upsmon  0:off   1:off   2:on3:on4:on5:on6:off
prelude 0:off   1:off   2:on3:on4:on5:on6:off
yppasswdd   0:off   1:off   2:on3:on4:on5:on6:off
webmin  0:off   1:off   2:on3:on4:on5:on6:off
internet0:off   1:off   2:off   3:on4:off   5:on6:off
ypserv  0:off   1:off   2:on3:on4:on5:on6:off
ypxfrd  0:off   1:off   2:on3:on4:on5:on6:off
oki4daemon  0:off   1:off   2:off   3:off   4:off   5:off   6:off
ntpd0:off   1:off   2:on3:on4:on5:on6:off
firestarter 0:off   1:off   2:on3:on4:on5:on6:off
mtink   0:off   1:off   2:off   3:off   4:off   5:off   6:off
sensors 0:off   1:off   2:on3:on4:on5:on6:off
spamassassin0:off   1:off   2:on3:on4:on5:on6:off
sendmail0:off   1:off   2:on3:on4:on5:on6:off
xinetd based services:
chargen-udp:off
chargen:off
daytime-udp:off
daytime:off
echo-udp:   off
echo:   off
services:   off
servers:off
time-udp:   off
time:   off
cups-lpd:   off
xadmin: off
fam:on
linuxconf-web:  off
rsync:  off
cvs:off
I'd hazard a guess and say the above is not the 'tmp' you're referring to, 
however, now that I've mentioned these files, what are these and can they 
be deleted?

My actual /tmp is 125.5mb with 124mb free.  I assume that this was the /tmp 
you were referring to?  I'll keep an eye on /tmp over the next few days and 
see if it grows.

-- 
Chris
Registered Linux User 283774 http://counter.li.org
9:44pm up 1:39, 2 users, load average: 0.52, 0.60, 0.52

I hate it when my foot falls asleep during the day cause that means
it's going to be up all night.
-- Steven Wright

Live - From Virgin Radio UK Rod 

Re: [newbie] System locks up every 10days

2004-08-31 Thread Dennis Myers
On Tuesday 31 August 2004 09:54 pm, Chris wrote:
 On Tuesday 31 August 2004 09:30 pm, Dennis Myers wrote:
  On Tuesday 31 August 2004 08:25 pm, Chris wrote:
   This an odd question and there may not be a valid answer, but here
   goes. About every 10days the system locks up for seemingly unrelated
   reasons. For instance, last time it happened it locked up while one of
 
  have you checked the syslogs? Kinda sounds like something is being saved
  to say /tmp until there is no room and /tmp is only cleared on reboot.
  Just a wild guess.

 Dennis, in the /root/tmp are 192 hidden files called .drakx-stdout.(a
 number here, ie..11153.  The contents of these files are:

 alsa  0:off   1:off   2:on3:on4:on5:on6:off
 dm0:off   1:off   2:off   3:off   4:off   5:on6:off
 kheader   0:off   1:off   2:on3:on4:off   5:on6:off
 keytable  0:off   1:off   2:on3:on4:on5:on6:off
 netfs 0:off   1:off   2:off   3:on4:on5:on6:off
 network   0:off   1:off   2:on3:on4:on5:on6:off
 partmon   0:off   1:off   2:off   3:on4:on5:on6:off
 random0:off   1:off   2:on3:on4:on5:on6:off
 rawdevices0:off   1:off   2:off   3:on4:on5:on6:off
 sound 0:off   1:off   2:on3:on4:on5:on6:off
 saslauthd 0:off   1:off   2:on3:on4:on5:on6:off
 syslog0:off   1:off   2:on3:on4:on5:on6:off
 crond 0:off   1:off   2:on3:on4:on5:on6:off
 xfs   0:off   1:off   2:on3:on4:on5:on6:off
 portmap   0:off   1:off   2:off   3:on4:on5:on6:off
 xinetd0:off   1:off   2:off   3:on4:on5:on6:off
 httpd 0:off   1:off   2:off   3:off   4:off   5:off   6:off
 apmd  0:off   1:off   2:on3:on4:on5:on6:off
 cups  0:off   1:off   2:on3:on4:on5:on6:off
 linuxconf 0:off   1:off   2:on3:on4:on5:on6:off
 iptables  0:off   1:off   2:on3:on4:on5:on6:off
 atd   0:off   1:off   2:off   3:on4:on5:on6:off
 devfsd0:off   1:off   2:on3:on4:on5:on6:off
 gpm   0:off   1:off   2:on3:on4:on5:on6:off
 postgresql0:off   1:off   2:off   3:off   4:off   5:off   6:off
 numlock   0:off   1:off   2:off   3:on4:on5:on6:off
 rwhod 0:off   1:off   2:off   3:off   4:off   5:off   6:off
 routed0:off   1:off   2:off   3:off   4:off   5:off   6:off
 postfix   0:off   1:off   2:on3:on4:on5:on6:off
 mysql 0:off   1:off   2:off   3:off   4:off   5:off   6:off
 named 0:off   1:off   2:off   3:on4:on5:on6:off
 ipvsadm   0:off   1:off   2:off   3:on4:on5:on6:off
 upsmon0:off   1:off   2:on3:on4:on5:on6:off
 prelude   0:off   1:off   2:on3:on4:on5:on6:off
 yppasswdd 0:off   1:off   2:on3:on4:on5:on6:off
 webmin0:off   1:off   2:on3:on4:on5:on6:off
 internet  0:off   1:off   2:off   3:on4:off   5:on6:off
 ypserv0:off   1:off   2:on3:on4:on5:on6:off
 ypxfrd0:off   1:off   2:on3:on4:on5:on6:off
 oki4daemon0:off   1:off   2:off   3:off   4:off   5:off   6:off
 ntpd  0:off   1:off   2:on3:on4:on5:on6:off
 firestarter   0:off   1:off   2:on3:on4:on5:on6:off
 mtink 0:off   1:off   2:off   3:off   4:off   5:off   6:off
 sensors   0:off   1:off   2:on3:on4:on5:on6:off
 spamassassin  0:off   1:off   2:on3:on4:on5:on6:off
 sendmail  0:off   1:off   2:on3:on4:on5:on6:off
 xinetd based services:
   chargen-udp:off
   chargen:off
   daytime-udp:off
   daytime:off
   echo-udp:   off
   echo:   off
   services:   off
   servers:off
   time-udp:   off
   time:   off
   cups-lpd:   off
   xadmin: off
   fam:on
   linuxconf-web:  off
   rsync:  off
   cvs:off
 I'd hazard a guess and say the above is not the 'tmp' you're referring to,
 however, now that I've mentioned these files, what are these and can they
 be deleted?

 My actual /tmp is 125.5mb with 124mb free.  I assume that this was the /tmp
 you were referring to?  I'll keep an eye on /tmp over the next few days and
 see if it grows.
The above are the current xinit 

Re: [newbie] System locks up every 10days

2004-08-31 Thread jon fuller
I can't even seem to load the program from the disks I bought is there any driver issues with my hardware? It haults and asks me to reboot when I'm loading the packages. Specifically when it gets to Fonts.

mandrake 10 64 version

athlon 64 3000
asus K8V
2 raptors 70 gigs apiece
9600XT
sony CDRWDennis Myers [EMAIL PROTECTED] wrote:
On Tuesday 31 August 2004 09:54 pm, Chris wrote: On Tuesday 31 August 2004 09:30 pm, Dennis Myers wrote:  On Tuesday 31 August 2004 08:25 pm, Chris wrote:   This an odd question and there may not be a valid answer, but here   goes. About every 10days the system locks up for seemingly unrelated   reasons. For instance, last time it happened it locked up while one of   have you checked the syslogs? Kinda sounds like something is being saved  to say /tmp until there is no room and /tmp is only cleared on reboot.  Just a wild guess. Dennis, in the /root/tmp are 192 hidden files called .drakx-stdout.(a number here, ie..11153. The contents of these files are: alsa 0:off 1:off 2:on 3:on 4:on 5:on 6:off dm 0:off 1:off 2:off 3:off
 4:off 5:on 6:off kheader 0:off 1:off 2:on 3:on 4:off 5:on 6:off keytable 0:off 1:off 2:on 3:on 4:on 5:on 6:off netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off network 0:off 1:off 2:on 3:on 4:on 5:on 6:off partmon 0:off 1:off 2:off 3:on 4:on 5:on 6:off random 0:off 1:off 2:on 3:on 4:on 5:on 6:off rawdevices 0:off 1:off 2:off 3:on 4:on 5:on 6:off sound 0:off 1:off 2:on 3:on 4:on 5:on 6:off saslauthd 0:off 1:off 2:on 3:on 4:on 5:on 6:off syslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off xfs 0:off 1:off 2:on 3:on 4:on 5:on 6:off portmap 0:off 1:off 2:off 3:on 4:on 5:on 6:off xinetd 0:off 1:off 2:off 3:on 4:on 5:on 6:off httpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off apmd 0:off 1:off 2:on 3:on 4:on 5:on 6:off cups 0:off 1:off 2:on 3:on 4:on 5:on 6:off linuxconf 0:off 1:off 2:on 3:on 4:on 5:on 6:off
 iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off devfsd 0:off 1:off 2:on 3:on 4:on 5:on 6:off gpm 0:off 1:off 2:on 3:on 4:on 5:on 6:off postgresql 0:off 1:off 2:off 3:off 4:off 5:off 6:off numlock 0:off 1:off 2:off 3:on 4:on 5:on 6:off rwhod 0:off 1:off 2:off 3:off 4:off 5:off 6:off routed 0:off 1:off 2:off 3:off 4:off 5:off 6:off postfix 0:off 1:off 2:on 3:on 4:on 5:on 6:off mysql 0:off 1:off 2:off 3:off 4:off 5:off 6:off named 0:off 1:off 2:off 3:on 4:on 5:on 6:off ipvsadm 0:off 1:off 2:off 3:on 4:on 5:on 6:off upsmon 0:off 1:off 2:on 3:on 4:on 5:on 6:off prelude 0:off 1:off 2:on 3:on 4:on 5:on 6:off yppasswdd 0:off 1:off 2:on 3:on 4:on 5:on 6:off webmin 0:off 1:off 2:on 3:on 4:on 5:on 6:off internet 0:off 1:off 2:off 3:on 4:off 5:on 6:off ypserv 0:off 1:off 2:on 3:on 4:on 5:on 6:off ypxfrd 0:off
 1:off 2:on 3:on 4:on 5:on 6:off oki4daemon 0:off 1:off 2:off 3:off 4:off 5:off 6:off ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off firestarter 0:off 1:off 2:on 3:on 4:on 5:on 6:off mtink 0:off 1:off 2:off 3:off 4:off 5:off 6:off sensors 0:off 1:off 2:on 3:on 4:on 5:on 6:off spamassassin 0:off 1:off 2:on 3:on 4:on 5:on 6:off sendmail 0:off 1:off 2:on 3:on 4:on 5:on 6:off xinetd based services: chargen-udp: off chargen: off daytime-udp: off daytime: off echo-udp: off echo: off services: off servers: off time-udp: off time: off cups-lpd: off xadmin: off fam: on linuxconf-web: off rsync: off cvs: off I'd hazard a guess and say the above is not the 'tmp' you're referring to, however, now that I've mentioned these files, what are these and can they be deleted? My
 actual /tmp is 125.5mb with 124mb free. I assume that this was the /tmp you were referring to? I'll keep an eye on /tmp over the next few days and see if it grows.The above are the current xinit settings that your system is running. As 1-off is init 1 and alsa is off and so forth. Bad explanation, maybe someone can jump in here and explain better. And /tmp was what I had in mind but other tmp files could be causing a problem, like /home/your usr/.tmp could be acting up. Not real sure but a memory leak might end up tying up all of your ram also. Anyone else have a thought? Slap me if I'm leading down the garden path. : )-- Dennis M. linux user #180842Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.comJoin the Club : http://www.mandrakeclub.com
		Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!

Re: [newbie] System locks up every 10days

2004-08-31 Thread Lyvim Xaphir
On Tue, 2004-08-31 at 21:25, Chris wrote:
 This an odd question and there may not be a valid answer, but here goes.  
 About every 10days the system locks up for seemingly unrelated reasons.  
 For instance, last time it happened it locked up while one of the 
 X-Screensavers was running.  I noted which one was on the screen at the 
 time and disabled it.  I've since only enabled two of the screensavers, 
 Nose Guy and Phosper.  Last night I installed FSV just to see how it 
 looked, install went fine and it ran great, tonight I brought it up, went 
 to open a directory and the system locked up tighter than a drum, uptime 
 was at about 10days, 20+ hrs.  Last time the lockup came at about the same 
 amount of uptime.  This is with MDK 9.0.  Althought I've gone 30+ days 
 previously before I had to hit the reset due to a lockup and if I remember 
 that was due to a game that the system just didn't like.  Any ideas on what 
 could be the problem?

Install lm-sensors and start monitoring your motherboard and cpu
temperatures to eliminate that as a possibility.  Sometimes a system fan
will get clogged with dust and the cpu temp will climb to borderline
levels; this is especially true with AMD cpus, which are notorious for
maintaining deceptively respectable behavior right up until they flake
out.

I have also seen AMD's that are overclocked pass Prime95 tests
perfectly, but still lock up after a few days.  This probably isn't your
case but high case or cpu temperatures can cause the same thing to
happen.

I would say that you could have a program running that has a memory
leak, but it sounds like you've reinstalled and had the same symptoms
across multiple installs.  This would pretty much eliminate the memory
leak possibility.

If you want to try to narrow it down to hardware a little better, what
you can do is run the box at runlevel 3 for 11+ days and see if it locks
up without a gui running.  That would give is a little more information.

It also wouldn't hurt for you to download the sysrescuecd and run some
hardware checks and a test of the memory:

http://www.sysresccd.org/download.en.php

Regardless of how you feel about your hardware or your confidence level
you should still follow troubleshooting procedure and eliminate memory
and cpu as possibilities.

LX



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com