mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tomas Styblo" <trip@matrix.cyberspace.cz>
To: <linux-kernel@vger.kernel.org>
Subject: 2.4 freezes on VIA KT133
Date: Fri, 25 May 2001 00:48:11 +0200	[thread overview]
Message-ID: <000b01c0e4a3$9c96bae0$1700000a@kamamura> (raw)

Hi !

I've yet seen similar freeze reports here in the past, so I decided to post
my one too.
The said system is a server, Athlon 850, no overclocking, no overheating,
100 Mhz FSB, 512 MB brand RAM, Abit KT7A board with VIA KT133.

The system is heavy loaded in daytime, but almost idle at night. It crashes
only about three times per month. These freezes
started to happen after 2.2 -> 2.4 upgrade, that I performed early after the
2.4.1 revision was released. These crashes are completely untracable for me,
because there is nothing suspicious in the syslog afterwards. Also the
system runs ABSOLUTELY perfectly between the crashes  - no problems with
kernel compilations or similar tasks that push the system over stability.

The crashes occur absolutely unpredictably, sometimes even at night, when
the system is idle.

The system runs various network services and dynamic web applications that
use the MySQL database a lot. The only used filesystem is EXT2. I do not use
buggy redhat compiler.

This report is probably not very helpful, but it may be useful for those who
planned to purchase AMD / VIA solution for a server.
I am not subscribed to this list, but I will monitor it through a web
archive and will try to respond, if needed.

Thanks for your work !
Tomas Styblo



             reply	other threads:[~2001-05-24 22:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-24 22:48 Tomas Styblo [this message]
2001-05-24 23:23 ` Mark Hahn
2001-05-25  5:05   ` Albert D. Cahalan
2001-05-25 13:20     ` Mark Hahn
2001-05-25 16:22     ` Alan Cox
2001-05-31 22:30 Tomas Styblo

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='000b01c0e4a3$9c96bae0$1700000a@kamamura' \
    --to=trip@matrix.cyberspace.cz \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®