Bug #60002 mysqld got signal 11
Submitted: 8 Feb 2011 7:12 Modified: 26 Jan 2012 17:29
Reporter: 雅臣 二見 Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.1.41 OS:Linux
Assigned to:
Tags: __intel_new_memcpy

[8 Feb 2011 7:12] 雅臣 二見
Description:
We have experienced slave server has crash and restarted .

MySQL vaersion is 5.1.41 (icc Compiled) with innodb plugin 1.06

I could find only error log below.
And I have no idea about what __intel_new_memcpy is.

Please any suggestion

thank you.

===============
mysqld: - mysqld got signal 11 ;
mysqld: This could be because you hit a bug. It is also possible that this binary
mysqld: or one of the libraries it was linked against is corrupt, improperly built,
mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
mysqld: We will try our best to scrape up some info that will hopefully help diagnose
mysqld: the problem, but since we have already crashed, something is definitely wrong
mysqld: and this may fail.
mysqld: key_buffer_size=67108864
mysqld: read_buffer_size=2097152
mysqld: max_used_connections=211
mysqld: max_threads=800
mysqld: threads_connected=199
mysqld: It is possible that mysqld could use up to
mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 14819273 K
mysqld: bytes of memory
mysqld: Hope that's ok; if not, decrease some variables in the equation.
mysqld: stack_bottom = 0x49d6b138 thread_stack 0x30000
mysqld: /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x20) [0xa06528]
mysqld: /usr/local/mysql/bin/mysqld(handle_segfault+0x368) [0x603c50]
mysqld: /lib64/tls/libpthread.so.0 [0x3878c0c4f0]
mysqld: /usr/local/mysql/bin/mysqld(__intel_new_memcpy+0x8f) [0xa5d5df]
mysqld: Trying to get some variables.
mysqld: Some pointers may be invalid and cause the dump to abort...
mysqld: thd->query at 0x2b10329f10 is an invalid pointer
mysqld: thd->thread_id=109101
mysqld: thd->killed=NOT_KILLED
mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
mysqld: information that should help you find out what is causing the crash.
mysqld_safe: Number of processes running now: 0
mysqld_safe: mysqld restarted

How to repeat:
Cannot repeat, as it happen only one time.

Suggested fix:
N/A
[8 Feb 2011 10:49] Valeriy Kravchuk
Please, send your my.cnf file content and the output of:

uname -a
free

Linux commands.
[9 Feb 2011 5:09] 雅臣 二見
Thank you for your reply.

The output of free and uname command is below.

# uname -a
Linux -  2.6.9-78.0.17.ELsmp #1 SMP Thu Mar 5 04:58:34 EST 2009 x86_64 x86_64 x86_64 GNU/Linux

# free
             total       used       free     shared    buffers     cached
Mem:      32960828   31829260    1131568          0     541716   26836172
-/+ buffers/cache:    4451372   28509456
Swap:      2096440        248    2096192

And following is part of my.cnf.

[mysqld]
port            = 3306

transaction_isolation = READ-COMMITTED

default-character-set = utf8
tmpdir                = /var/tmp
tmp_table_size        = 256M

query_cache_type = 1
query_cache_size = 256M
query_cache_limit = 2M

# ** innodb-plugin options **
ignore-builtin-innodb
plugin-load = innodb=ha_innodb.so;innodb_trx=ha_innodb.so;innodb_locks=ha_innodb.so;innodb_lock_waits=ha_innodb.so;innodb_cmp=ha_innodb.so;innodb_cmp_reset=ha_innodb.so;innodb_cmpmem=ha_innodb.so;innodb_cmpmem_reset=ha_innodb.so
plugin_dir= /usr/local/mysql/lib/plugin

max_connect_errors = 10
table_cache = 2048
max_allowed_packet = 16M
max_heap_table_size = 64M

sort_buffer_size = 16M
join_buffer_size = 16M

thread_stack = 192K
thread_cache_size = 8
thread_concurrency = 8

# ** INNODB options **
innodb_buffer_pool_size = 1500M
innodb_thread_concurrency = 4
innodb_additional_mem_pool_size = 16M
innodb_flush_log_at_trx_commit = 0
innodb_log_buffer_size = 8M
innodb_log_file_size = 256M
innodb_log_group_home_dir = /log/mysql
innodb_max_dirty_pages_pct = 90
innodb_lock_wait_timeout = 120

# ** MyISAM options **
key_buffer_size = 64M
read_buffer_size = 2M
read_rnd_buffer_size = 16M
bulk_insert_buffer_size = 64M
myisam_sort_buffer_size = 128M
myisam_max_sort_file_size = 10G
myisam_max_extra_sort_file_size = 10G
myisam_repair_threads = 1
myisam_recover
[23 Dec 2011 19:28] Sveta Smirnova
Severity changed: crash can not be feature request.
[26 Dec 2011 17:29] Valeriy Kravchuk
If you still get similar problem with a recent version, 5.1.60, please, send error log with crash info.
[27 Jan 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".