Re: Tracking down a Linux crash

From: Haines Brown (owhyheh.ypqgvyiuaw@csc.com)
Date: Wed Oct 16 2002 - 17:40:35 EEST

  • Next message: jjgpg: "Re: Tracking down a Linux crash"

    I don't have much to offer except commiseration ;-)

    It would help to define just what happens to your system. If you
    really mean "crash," in that the screen goes black, and your drive
    access stops, and a reboot begins, etc., then the usual culprit may be
    flakey RAM.

    Had it happen to me twice over the years, where RAM replacement solved
    the problem. Manufacturers usually pretty willing to replace RAM,
    questions unasked, if covered by warranty.

    If you've got RAM kicking around, try a substitution. If you have
    plenty of RAM and can take out a bank, try that. Real RAM testers are
    prohibitively expensive, but software testers I'm told work OK
    (apparently better than they did ten years ago). If that's the route
    for you, consider memtester-2.93.1. It compiles easily. The only catch
    is that it runs and runs until you stop it. I didn't know that and
    spent a week with it running in the background before it dawned on me
    it would not complete by itself ;-(

    If instead your system freezes (no keyboard our mouse inputs), forcing
    you to RESET, you might have a problem with your video card. I'm not
    positive, but I believe I once had this kind of problem because the
    heat sink on the card had fallen off. When I put it back on with
    thermal glue, the problem stopped (so far)..

    Haines KB1GRM
    -
    To unsubscribe from this list: send the line "unsubscribe linux-hams" in
    the body of a message to venq.vbvcs@btal.com.au
    More majordomo info at http://vger.kernel.org/majordomo-info.html



    This archive was generated by hypermail 2b30 : Wed Oct 16 2002 - 17:44:52 EEST