It's the binary from mysql.com.
> > Which the Mysql support team says appears to be memory corruption.
> > Since this has happened on 4 different machines, and one of them had
> > memtest86 run on it (coming up clean), they seem (witness Sasha's
> > post) to think this may have something to do with the memory
> > handling in the kernel.
> There is a big difference between memory _corruption_ and a VM deficiency. No
> app can cope with a _corruption_ and is perfectly allowed to core dump or exit
> (or trash your disk). But this should not happen on allocation failures.
> Unless all your RAM is from the same series I do not really believe in mem
> corruption. I would try Martins small VM patch, as it looks like being a bit
> more efficient in low mem conditions and this may well be the case you are
> running into. This means 2.4.17 standard + patch.
Is there a reasonable chance that martins patch will get mainlined
in the near future? One of the big reasons I chose to upgrade to a
later kernel version (from 2.4.8ac<something>+LVMpatches+...) was
to get away from having to apply patches (and document which
patches and where to get them etc).
If this is the route I have to go, I'll do it but, well, I'm not
that comfortable with it.
-- Share and Enjoy. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/