mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver.Schersand@BASF-IT-Services.com
To: chris.mason@suse.com, alessandro.suardi@oracle.com
Cc: sbrand@mainz.ibm.com, reiser@namesys.com, linux-kernel@vger.kernel.org
Subject: Review: Servercrash with kernel SuSE 2.4.16
Date: Mon, 6 May 2002 10:57:15 +0200	[thread overview]
Message-ID: <OF10FE0462.9B5B7937-ONC1256BB1.002ADC0F@bcs.de> (raw)

Hi,

This is the actual result of the analys of our oracle server crashes on
linux servers with suse Enterprise Server 7 and Kernel 2.4.16

The reason for theses crashes where  the compaq remote inside and compaq
health drivers. These drivers are deliverd from compaq. On stardup of these
agents, they load binary kernel modules, which are very version sensitive.
This modules  corrupt the virtual memory management of the server on heavy
load

This shows us a main problem of Linux in datacenter environment. The
automatic guarding of the local attached storage and the hardware is very
importend in this environments. In this environment we use expensive high
performance hardware. These hardware is not  good  supported by the
standard linux kernel. The companies which sell these hardware deliver not
all features of these hardware to the community of linux.  There drivers
and guarding agents are not distributed under GPL.


Here is the statement of Compaq ( HPQ)

   The new health driver that can be run on any re-compiled kernel is due
   out in the SmartStart 5.50 timeframe (3Q02).  The reason for this is
   that it also provides support for new servers as well.
   The delivery method will be via the Compaq web site and the SmartStart
   Cd.

   The customer expectation is that it will work with any re-compiled
   kernel.  Most likely that will be true however it will be impossible for
   us to validate it with every possibility due to the open source nature
   of Linux.

   Today, customers actually can run the existing health driver on
   re-compiled kernels by evoking a "fix-up" script that will be available
   on our website.  This is not an ideal solution but it will work in a
   majority of the situations.


Thank you very much for all the help with this problem

Oliver Schersand


             reply	other threads:[~2002-05-06  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-06  8:57 Oliver.Schersand [this message]
2002-05-06 11:33 ` Hans Reiser
2002-05-06 15:17 ` Alan Cox

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=OF10FE0462.9B5B7937-ONC1256BB1.002ADC0F@bcs.de \
    --to=oliver.schersand@basf-it-services.com \
    --cc=alessandro.suardi@oracle.com \
    --cc=chris.mason@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=sbrand@mainz.ibm.com \
    /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®