linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Furness <paul.furness@vil.ite.mee.com>
To: "Urte Fürst" <Urte.Fuerst@dlr.de>
Cc: linux-admin@vger.kernel.org
Subject: Re: Linux 2.4.18 occassionally freezes
Date: 10 Oct 2002 14:16:55 +0100	[thread overview]
Message-ID: <1034255816.15487.51.camel@Zebra> (raw)
In-Reply-To: <3DA5626C.3D008324@dlr.de>

Apart from the kernel, have you updated all the other packages on the
systems? It's not just the kernel that needs to be updated; pretty much
everything gets updated over the course of a year or more. It seems more
likely to be the apps than the kernel; 2.4.18 is indeed the latest
stable, but which Red Hat version do you have? 2.4.18-10 is, I think,
the latest patch, but RH8.0 uses 2.4.18-14.
Also check your VMWare version - 3.2 is the latest.
  

I remember having many problems with RH7.1's stability, but when I moved
to 7.2 it fixed many of them (although others were introduced.) Applying
all the updates to 7.2 made it very much better. 7.3 seems pretty good
too. I'm currently trying out 8 on my workstation, but I had a number of
little problems with it because a number of key things work differently
in 8. 

You could experiment with upgrading one of the machines that's showing
problems to a later version of RedHat (I wouldn't go for 8 yet as it's
very new and although it seems really good, there may still be hidden
bugs).

Upgrading to 7.2 or even 7.3 should have very little impact on every day
usage because the changes are mostly bug-fixes etc, so even if you have
one machine at 7.3 and the rest at 7.1, it shouldn't generate too many
problems.

Paul.

On Thu, 2002-10-10 at 12:20, Urte Fürst wrote:
> 
> Hi list,
> 
> I'm experiencing strange system freezes occurring occassionally. I have
> > 20 machines (all DELL Precision 530 workstations) running RedHat 7.1
> plus an updated 2.4.18 kernel (latest stable AFAIK). There are slight
> differences in additional hardware: some of the machines have an
> internal
> CD burner. With those machines (containing an internal CDRW device) and
> especially when vmware is installed and used as well, I see the system
> freezing every now and then. I have difficulties figuring out the cause,
> as there are no messages in the system log which seem to point me in the
> right direction. I never had this behaviour so far with a
> non-CDRW-system.
> The freeze sometimes happens two or thress times within one week,
> afterwards
> the machine is just happily working for the next whole month.
> 
> What would be good way to catch and eliminate the problem? Should I try
> so run a kernel with debugging enabled? Or does anyone have similar
> problems
> and maybe some hints how to cope with it?
> 
> Many thanx in advance for any help!
> Kind regards,
> Urte
> 
> -- 
>                                                        \|/
>                                                        @ @
> ---------------------------------------------------oOO-(_)-OOo-------------
> 
> All wiyht. Rho sritched mg kegtops awound?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
-- 
Paul Furness

Systems Manager

2+2=5 for extremely large values of 2.

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2002-10-10 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 11:20 Linux 2.4.18 occassionally freezes Urte Fürst
2002-10-10 13:16 ` Paul Furness [this message]
2002-10-11  9:43   ` Urte Fürst
2002-10-10 14:27 ` Kyle
2002-10-11  9:49   ` Urte Fürst

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1034255816.15487.51.camel@Zebra \
    --to=paul.furness@vil.ite.mee.com \
    --cc=Urte.Fuerst@dlr.de \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).