Computer crashes after 2 days

[Peter Collier]

I've noticed these logwatch messages sent to root. Don't know if this
gives a clue.

--------------------- ModProbe Begin ------------------------

Errors running install command:
   sound_slot_1  : 7 Time(s)

---------------------- ModProbe End -------------------------

--------------------- pam_unix Begin ------------------------

su:
   Sessions Opened:
      peter(uid=500) -> root: 2 Time(s)

up2date:
   Unknown Entries:
      authentication failure; logname= uid=500 euid=0 tty= ruser=peter
rhost=  user=root: 1 Time(s)

---------------------- pam_unix End -------------------------

--------------------- Connections (secure-log) Begin
------------------------

Connections:
   Service sgi_fam:
      <no address>: 3 Time(s)

**Unmatched Entries**
gdm[2839]: pam_succeed_if: requirement "uid < 100" not met by user
"peter"
userhelper[5595]: pam_timestamp: timestamp file
`/var/run/sudo/peter/unknown:root' has unacceptable age (35100 seconds),
disallowing access to system-config-network for UID 500
userhelper[5595]: pam_timestamp: updated timestamp file
`/var/run/sudo/peter/unknown:root'
userhelper[5598]: running '/usr/sbin/system-config-network' with root
privileges on behalf of 'peter'
gdm[2839]: pam_succeed_if: requirement "uid < 100" not met by user
"irene"
gdm[2839]: pam_succeed_if: requirement "uid < 100" not met by user
"peter"
userhelper[7845]: pam_timestamp: timestamp file
`/var/run/sudo/peter/unknown:root' has unacceptable age (54590 seconds),
disallowing access to up2date for UID 500

---------------------- Connections (secure-log) End
-------------------------

Box is a pcchips fsb266 k7 motherboard. Athlon 1700, wdig 40 gb with an
ex suse 9.0 install, maxtor 40gb with fedora 2 install ( this is the
operating system I'm active/using, the suse hard drive is only used for
a backup copy now) . 512 2100 266 ddr, ati 7800 graphics. All updates
applied.

Peter

[PriouAlexandre]

Le samedi 30 Octobre 2004 20:31, Peter Collier a écrit :
> I've noticed these logwatch messages sent to root. Don't know if this
> gives a clue.
>
> --------------------- ModProbe Begin ------------------------
>
> Errors running install command:
>    sound_slot_1  : 7 Time(s)
> .......... / CUT/..................
> Peter

this routine Crond doesn't say why your system crashed after 2 day 
it's a rapport only for the service : sendmail, modprob imap , ssh ....

see your dmesg or your files message in /var/log/

my knowledge has, I had the same problem 
after have erase the xscreensaver on my fedora , this problem disappeared

alexandre

[Peter Collier]

On Sat, 2004-10-30 at 19:58, priou wrote:
> Le samedi 30 Octobre 2004 20:31, Peter Collier a écrit :
> > I've noticed these logwatch messages sent to root. Don't know if this
> > gives a clue.
> >
> > --------------------- ModProbe Begin ------------------------
> >
> > Errors running install command:
> >    sound_slot_1  : 7 Time(s)
> > .......... / CUT/..................
> > Peter
>
> this routine Crond doesn't say why your system crashed after 2 day 
> it's a rapport only for the service : sendmail, modprob imap , ssh ....
>
> see your dmesg or your files message in /var/log/
>
> my knowledge has, I had the same problem 
> after have erase the xscreensaver on my fedora , this problem disappeared
>
> alexandre

What may be error messages from dmesg :-

SELinux:  Initializing. ##(I didn't choose selinux on install, but later
in this file it does disable selinux))
SELinux:  Starting in permissive mode
There is already a security framework initialized, register_security
failed.
selinux_register_security:  Registering secondary module capability
vesafb: probe of vesafb0 failed with error -6
audit: initializing netlink socket (disabled)
Loading keyring
- Added public key 9488DB81FF525AA3
- User ID: Red Hat, Inc. (Kernel Module GPG key)
ksign: invalid packet (ctb=00)
Unable to load default keyring: error=74
ide: Assuming 33MHz system bus speed for PIO modes; override with

idebus=xx ## (Should I change this to 66?, 100?)

agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
  ##(should this not be 4x?)

hub 4-0:1.0: 6 ports detected
usb 1-2: device not accepting address 2, error -71

My other log messages are similar to the logwatch message I posted in my
first email.

Peter

[PriouAlexandre]

Le samedi 30 Octobre 2004 22:09, Peter Collier a écrit :
> On Sat, 2004-10-30 at 19:58, priou wrote:
> > Le samedi 30 Octobre 2004 20:31, Peter Collier a écrit :
> > > I've noticed these logwatch messages sent to root. Don't know if this
> > > gives a clue.
> > >
> > > --------------------- ModProbe Begin ------------------------
> > >
> > > Errors running install command:
> > >    sound_slot_1  : 7 Time(s)
> > >
> > > .......... / CUT/..................
> > >
> > > Peter
> >
> > this routine Crond doesn't say why your system crashed after 2 day
> > it's a rapport only for the service : sendmail, modprob imap , ssh ....
> >
> > see your dmesg or your files message in /var/log/
> >
> > my knowledge has, I had the same problem
> > after have erase the xscreensaver on my fedora , this problem disappeared
> >
> > alexandre
>
> What may be error messages from dmesg :-
>
> SELinux:  Initializing. ##(I didn't choose selinux on install, but later
> in this file it does disable selinux))

fedora is a SELinux , see the doc of fedora in redhat or  SELinux on nsa.org  
(national security agency ) 
this normal
> SELinux:  Starting in permissive mode
> There is already a security framework initialized, register_security
> failed.
> selinux_register_security:  Registering secondary module capability
> vesafb: probe of vesafb0 failed with error -6

here you have a probleme with your card graphic driver or hardward 
try : man vesa 
and configure your card correctly
> audit: initializing netlink socket (disabled)
> Loading keyring
> Added public key 9488DB81FF525AA3
> User ID: Red Hat, Inc. (Kernel Module GPG key)
>
> ksign: invalid packet (ctb=00)
> Unable to load default keyring: error=74
> ide: Assuming 33MHz system bus speed for PIO modes; override with
>
> idebus=xx ## (Should I change this to 66?, 100?)
>
> agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
> agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
> agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
>   ##(should this not be 4x?)

no it's the version of your slot AGP on your mother board, if your motherboard 
assuming the 4X or greater 
you have a probleme with your motherboard

please check your bios, and see your describ motherboard manual

for your problem try this command :

more /var/log/messages | grep erreur
and 
more /var/log/messages | grep panic 
or 
more /var/log/messages | grep kernel

if that return nothing, try :

rpm -q xscreensaver 
after 
rpm -e {version-xscreensaver}

Alexandre Priou
@France

[Peter Collier]

On Sun, 2004-10-31 at 06:12, priou wrote:
> Le samedi 30 Octobre 2004 22:09, Peter Collier a écrit :
> > On Sat, 2004-10-30 at 19:58, priou wrote:
> > > Le samedi 30 Octobre 2004 20:31, Peter Collier a écrit :
> > > > I've noticed these logwatch messages sent to root. Don't know if this
> > > > gives a clue.
> > > >
> > > > --------------------- ModProbe Begin ------------------------
> > > >
> > > > Errors running install command:
> > > >    sound_slot_1  : 7 Time(s)
> > > >
> > > > .......... / CUT/..................
> > > >
> > > > Peter

snip----------
> for your problem try this command :
>
> more /var/log/messages | grep erreur
> and 
> more /var/log/messages | grep panic 
> or 
> more /var/log/messages | grep kernel
>
> if that return nothing, try :
>
> rpm -q xscreensaver 
> after 
> rpm -e {version-xscreensaver}
>
> Alexandre Priou
> @France

Due to catching up with emails I haven't as yet tried the above yet but
I think the problem comes with (could be a coincidence) to when I have a
terminal open on alt-F1 running mc as root and I close evolution that is
running in X windows, may have another app open eg nautilus. 512 meg
memory 1 gb swap shouldn't give a memory problem I would have thought.
Peter

[korgull]

On Wednesday 03 November 2004 09:06, Peter Collier wrote:
> 512 meg
> memory 1 gb swap shouldn't give a memory problem I would have thought.
> Peter

Perhaps the memory timings in your BIOS are set too critical.
Caused me some strange crashes (every few days a crash) a while ago.

Regards,
Marcel

[HaJo Schatz]

On Sun, October 31, 2004 2:31, Peter Collier said:
> Box is a pcchips fsb266 k7 motherboard. Athlon 1700, wdig 40 gb with an
> ex suse 9.0 install, maxtor 40gb with fedora 2 install ( this is the
> operating system I'm active/using, the suse hard drive is only used for
> a backup copy now) . 512 2100 266 ddr, ati 7800 graphics. All updates
> applied.

Can you exclude a hardware issue, Ie did the problem occur after changing
to FC? I have a very similar config and know that I have a heat problem --
after about 2 days the system gets too hot & crashes by just freezing.

[Peter Collier]

On Mon, 2004-11-01 at 10:10, HaJo Schatz wrote:
> On Sun, October 31, 2004 2:31, Peter Collier said:
> > Box is a pcchips fsb266 k7 motherboard. Athlon 1700, wdig 40 gb with an
> > ex suse 9.0 install, maxtor 40gb with fedora 2 install ( this is the
> > operating system I'm active/using, the suse hard drive is only used for
> > a backup copy now) . 512 2100 266 ddr, ati 7800 graphics. All updates
> > applied.
>
> Can you exclude a hardware issue, Ie did the problem occur after changing
> to FC? I have a very similar config and know that I have a heat problem --
> after about 2 days the system gets too hot & crashes by just freezing.
>
> -- 
> HaJo Schatz 
> http://www.HaJo.Net
>
> PGP-Key:  http://www.hajo.net/hajonet/keys/pgpkey_hajo.txt

Heat sink for processor feels cool. The heat sink for the graphics card
feels about 70 degrees C. Is that too hot?
Peter

[HaJo Schatz]

On Wed, 2004-11-03 at 16:13, Peter Collier wrote:
> Heat sink for processor feels cool. The heat sink for the graphics card
> feels about 70 degrees C. Is that too hot?

Dunno for sure, but seems on the high end to me. 70C at the heat-sink
means significantly higher @ the core. And considering that
consumer-grade silicon is usually not specified beyond around 100C, you
might run somewhere at the limit.
Try keeping it cooler (don't run a 3D screensaver but do a simple "blank
screen" or install a fan) and see for yourself...