Board index Linux Kernel

Review: Servercrash with kernel SuSE 2.4.

Review: Servercrash with kernel SuSE 2.4.

Post by Peter Samuelso » Tue, 07 May 2002 21:40:05



[Oliver Schersand]

Quote:> 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

Translation: you purchased hardware which requires binary-only kernel
modules to provide needed functionality.

Quote:> This shows us a main problem of Linux in datacenter environment.

No, it shows us a main problem of Compaq high-availability storage
products in a Linux environment.  If you're going to point fingers,
make sure they're pointed the right direction.

Quote:> 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.
[...]
> Thank you very much for all the help with this problem

I'm not sure how the linux-kernel list is supposed to help you.  The
development model of open-source drivers and source-only compatibility
(even that being broken from time to time) is well-established.  It's
not going to change.  And Compaq is fully aware of it.  They have
chosen to swim against the current, providing themselves (and
occasionally their customers, as you have seen) with considerable
headaches as a result.  If they are unable to produce high-quality
drivers for the kernels you wish to run, or at least for a list of
kernels they explicitly support, there are other datacenter storage
vendors (and indeed other operating systems) out there.  IBM for
instance makes all the right noises - maybe they have products you can
use.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
 
 
 
Top

Review: Servercrash with kernel SuSE 2.4.

Post by Peter Samuelso » Tue, 07 May 2002 23:10:05


[I wrote]

Quote:> I'm not sure how the linux-kernel list is supposed to help you.

As Alessandro Suardi pointed out in private mail, I completely
misunderstood the message.  I thought Oliver was *asking* for help with
what was already determined to be a Compaq problem.  In fact he was
following up from help he had previously received.  My mistake; my
apologies.

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 
Top

1. Review: Servercrash with kernel SuSE 2.4.16

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Which subnet will a WS get?

3. Suse 7.1 with 2.4 kernel: masquerading

4. Q: Mulitple processors

5. SUSE 6 review in CT S.U.S.E.

6. RH7.3, partition or empty space

7. Standard Kernel 2.4.x on Suse 7.1

8. YQ¨ CERN httpd proxy : can't find in cache - goes to another proxy

9. tcp connections terribly slow (SuSE 7.2, kernel 2.4)

10. routing SuSE kernel 2.4

11. Suse Linux 7.1 and kernel 2.4 >> help needed for linmodem

12. Suse 7.3 + adsl + kernel 2.4 + private Network

13. Cannot get Creative Vibra16x Soundcard to work on alsa (2.4 kernel, SUSE 7.1)


All times are UTC
Board index