I was running a UML virtual machine with 2.4.22 kernel, which worked
fine. Then I tried to start this machine with a 2.6.12 kernel. With
this kernel, mysql crashes immediately after the start. Nothing other
changed. Just the kernel. With 22.214.171.124 kernel the same thing. What
can be the problem?
The mysql errorlog shows:
050620 12:06:33 mysqld started
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 agaist 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 diagno=
the problem, but since we have already crashed, something is definitely wro=
and this may fail
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections =3D 233979 =
bytes of memory
Hope that's ok, if not, decrease some variables in the equation
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
Cannot determine thread, fp=3D0x4124e7c8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
New value of fp=3D(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/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
The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
050620 12:06:34 mysqld ended
Thanks for help,