Bug #64125 mysql died suddenly,This problem appeared three times
Submitted: 25 Jan 2012 7:53 Modified: 25 Feb 2012 8:28
Reporter: victorino ZH Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.1.39 OS:Linux
Assigned to: CPU Architecture:Any
Tags: mysqld got signal 11, something went terribly wrong

[25 Jan 2012 7:53] victorino ZH
Description:
Maybe This problem was similar to the bug#41385.But,I really don't know how to solve it.I'm sorry.And here is the crash information:

120125 12:52:01 - 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=1048576
read_buffer_size=2097152
max_used_connections=3061
max_threads=7000
threads_connected=1102
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 28744281 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
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...
stack_bottom = (nil) thread_stack 0x80000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x84ac9e]
/usr/sbin/mysqld(handle_segfault+0x322)[0x5bf392]
/lib64/libpthread.so.0[0x3feec0e4c0]
/lib64/libc.so.6(memcpy+0xd2)[0x3fee07b512]
/usr/sbin/mysqld(_ZN6String6appendEPKcj+0xd0)[0x5bb1c0]
/usr/sbin/mysqld(thd_security_context+0x1b6)[0x5b0fe6]
/usr/sbin/mysqld(innobase_mysql_print_thd+0x30)[0x72ee40]
/usr/sbin/mysqld(lock_print_info_all_transactions+0x8a)[0x77d7aa]
/usr/sbin/mysqld(srv_printf_innodb_monitor+0x189)[0x7c3be9]
/usr/sbin/mysqld(srv_lock_timeout_and_monitor_thread+0x2f1)[0x7c43f1]
/lib64/libpthread.so.0[0x3feec06367]
/lib64/libc.so.6(clone+0x6d)[0x3fee0d2f7d]

The OS version:
# uname -s -m -p -r
Linux 2.6.18-128.el5 x86_64 x86_64

The machine memory:
#free -m
             total       used       free     shared    buffers     cached
Mem:         72436      46526      25909          0        496      18610
-/+ buffers/cache:      27420      45016
Swap:         1027          0       1027

my.cnf:
[mysqld_safe]
nice                            = -15
open-files-limit                = 8192

[client]
socket                          = /var/lib/mysql/mysql.sock
default-character-set           = utf8

[mysqld]
character-set-server            = utf8
collation-server                = utf8_general_ci
back_log                        = 300
open-files-limit                = 8192
open-files                      = 1024
port                            = 3306
socket                          = /var/lib/mysql/mysql.sock
pid-file                        = /var/lib/mysql/mysql.pid
skip-external-locking
skip-name-resolve
datadir                         = /data
log_warnings
log_slow_queries                = /data/mysql-slow.log
log_bin                         = /log/mysql-bin
binlog_format                   = MIXED
server-id                       = 1
innodb_data_home_dir            = /data
innodb_log_group_home_dir       = /log
innodb_thread_sleep_delay=6000
innodb_data_file_path           = ibdata1:10M:autoextend
innodb_lock_wait_timeout        = 60
innodb_max_dirty_pages_pct      = 90
skip-innodb-doublewrite
sync_binlog                     = 0
ft_min_word_len                 = 4
default-storage-engine          = InnoDB

[mysqldump]
quick
quote-names
max_allowed_packet              = 128M

[mysql]
no-auto-rehash
prompt                  = "[\\d][\\r:\\m:\\s]>"

[myisamchk]
key_buffer_size                 = 512M
sort_buffer_size                = 512M
read_buffer                     = 8M
write_buffer                    = 8M

[mysqlhotcopy]
interactive-timeout

And,here is the resolve stack dump:
0x84ac9e my_print_stacktrace + 46
0x5bf392 handle_segfault + 802
0x3feec0e4c0 _end + -303535528
0x3fee07b512 _end + -315671894
0x5bb1c0 String::append(char const*, unsigned int) + 208
0x5b0fe6 thd_security_context + 438
0x72ee40 innobase_mysql_print_thd + 48
0x77d7aa lock_print_info_all_transactions + 138
0x7c3be9 srv_printf_innodb_monitor + 393
0x7c43f1 srv_lock_timeout_and_monitor_thread + 753
0x3feec06367 _end + -303568641
0x3fee0d2f7d _end + -315312875

Besides,another machine as a slave had the same problem.

How to repeat:
really don't know.Sorry,it was no symptom .
[25 Jan 2012 8:28] Valeriy Kravchuk
To claim that there is some bug here and fix it we need a repeatable test case on recent version, 5.1.61.
[26 Feb 2012 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".