Description:
We have a custom kernel, patched with netfilter and recompiled with the same RH .config file to ensure that all the same modules are installed. Everything seemes to work great with the exception of MySQL 4.1.8/4.1.9. If you are running the stock kernel 2.4.29-20.EL and install either of these two it works fine. Upgrading the kernel causes them to fail. Expected this to be some type of module incompatability. Build MySQL from source with new kernel and it still fails on "make test".
Installing MySQL from binary RPM works fine on this box. So, MySQL must work with the custom kernel. It appears to be a compilation issue against kernel/glibc/etc... Kernel is compiled i686. A couple include files have been modified under /usr/include/linux/netfilter_ipv4 and nothing else. This should have no impact on this as this is a seperate userspace/. This leads me to believe that there is a compilier config setting that needs to be tweak for MySQL under this version.
The error code in the sym just basically says end. There is no lag from the time you execute ./mysqld to the time the error appears.
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x415d179c, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81440a6
0x40053df8
(nil)
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
Segmentation fault
How to repeat:
Install a standard or custom kernel configuration using 2.4.29 and then try to install MySQL from source and it will fail.
