> 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.
> 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.
> 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
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 07 2002 - 22:00:26 EST