l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Apr 22 10:08

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] RH keeps crashing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] RH keeps crashing

On Mon, 22 Apr 2002, Richard S. Crawford wrote:
> My RH 7.2 box has crashed three times in the past 24 hours.  Each time I've 
> rebooted, I've run fsck / and gone through the entire check and repair 
> process, but I'm obviously missing something.
> What else should I be checking?

As Pete suggested, your log files will often hold useful information in
troubleshooting a problem related to crashing. Depending upon how the
crash took place, the latest log entries may not have been sync-ed to disk
though. However, early events in the crash that may lead uup to the crash
may be listed, and logs are almost always *very good* and should be
the first item consulted when you experience anything crashing or
failing to start. :-)

Rod suggess checking the filesystems to make sure they are not full (good
idea too) and then auggests hardware (also a common problem when the
uncommon association of "crashing" meets with the word "Linux". Assuming
they are not running anything experimental, these have been the most
common problems found when I have been asked to look at people's systems
with problems.

Some items for do-it-yourself troubleshooting:

Are you running anything that is considered experimental?
What Kernel Version? (Is it one of the stable series, or one with known
What is the common thread - what are you doing when it crashes, and what
   seems to be the same between all crashes you have experienced?
   (Say, are you running "X" in all of them? Are you at your system
    when it happens? Are you away from your system when it happens?
    are you making heavy use of the system when it happens?
Is this a new problem? (Say your system has been perfect for 6 months, and
  now it has started crashing) If So, what has changed around that time
  on your system?
What exactly is happening when it crashes? Any messages reported on
  console? Does it just freeze and not allow any input? Is "X" just
  frozen? (Say when you are in "X" and you notice a "freeze", what happens
  when your press control-alt-backkspace ? )
What do you see on the screen when it crashes? If you press shift or space
 or control-alt-backspace or control-alt-delete or control-alt-F1 does
 what you see change?

If running RH 7.0 or maybe even 7.1, a screensaver setting seemed to cause
problems when you never chose a default screen saver. To test this, of
course, try choosing a default screen saver and then set the time before
it comes on to never or so many minutes it adds up to days of time (if
possible.) This is just a shot in the dark on why it may be crashing, but
looking to answer the above may help you to troubleshoot the problem.


Version: 3.12
GCS/CM$/IT$/LS$/S/O$ !d--(++) !s !a+++(-----) C++$(++++) U++++$(+$) P+$>+++ 
L+++$(++) E W+++$(+) N+ o K w+$>++>+++ O-@ M+$ V-$>- !PS !PE Y+ !PGP
t@-(++) 5+@ X@ R- tv- b++ DI+++ D+ G--@ e+>++>++++ h(++)>+ r*>? z?
decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.