I got a different stack trace though: 2017-03-08T07:04:36.804061Z 0 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.7.15-9' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Percona Server (GPL), Release '9', Revision '9f0fd0a' 07:05:31 UTC - 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. Please help us make Percona Server better by reporting any bugs at http://bugs.percona.com/ key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=201 max_threads=301 thread_count=201 connection_count=201 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 127617 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f7f000555c0 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 = 7f7ec671ce40 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xec804c] /usr/sbin/mysqld(handle_fatal_signal+0x461)[0x79e2f1] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f7f63564330] /usr/sbin/mysqld(_ZN4Item17make_string_fieldEP5TABLE+0x15d)[0x8114ed] /usr/sbin/mysqld(_ZNK4Item27numeric_context_result_typeEv+0x35)[0x7c5ba5] /usr/sbin/mysqld(_ZN9Item_func12fix_func_argEP3THDPP4Item+0x76)[0x86a736] /usr/sbin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0xd7)[0x86a8a7] /usr/sbin/mysqld(_ZN13Item_str_func10fix_fieldsEP3THDPP4Item+0x12)[0xb95412] /usr/sbin/mysqld(_ZN9Item_func12fix_func_argEP3THDPP4Item+0xf9)[0x86a7b9] /usr/sbin/mysqld(_ZN9Item_func10fix_fieldsEP3THDPP4Item+0xd7)[0x86a8a7] /usr/sbin/mysqld(_ZN13Item_str_func10fix_fieldsEP3THDPP4Item+0x12)[0xb95412] /usr/sbin/mysqld[0xd41567] /usr/sbin/mysqld(_ZN5TABLE14refix_gc_itemsEP3THD+0xe4)[0xd49af4] /usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0x388)[0xc4aed8] /usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x5f2)[0xc526b2] /usr/sbin/mysqld(_Z21open_tables_for_queryP3THDP10TABLE_LISTj+0x4b)[0xc52fcb] /usr/sbin/mysqld[0x75d7fe] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x4375)[0xca8345] /usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x5c5)[0xcab7c5] /usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x92f)[0xcac17f] /usr/sbin/mysqld(_Z10do_commandP3THD+0x1b7)[0xcadb17] /usr/sbin/mysqld(handle_connection+0x2a0)[0xd70c60] /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x12464a4] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7f7f6355c184] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f7f62a6937d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f7f0005e5c0): SELECT GUID from testtbl where ID=279742 Connection ID (thread ID): 170 Status: NOT_KILLED ubuntu@mysql57u:~$ sudo cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" NAME="Ubuntu" VERSION="14.04.5 LTS, Trusty Tahr" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 14.04.5 LTS" VERSION_ID="14.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" ubuntu@mysql57u:~$ sudo dpkg -l | grep -i percona ii libperconaserverclient20:amd64 5.7.15-9-1.trusty amd64 Percona Server database client library ii percona-server-client-5.7 5.7.15-9-1.trusty amd64 Percona Server database client binaries ii percona-server-common-5.7 5.7.15-9-1.trusty amd64 Percona Server database common files (e.g. /etc/mysql/my.cnf) ii percona-server-server-5.7 5.7.15-9-1.trusty amd64 Percona Server database server binaries ubuntu@mysql57u:~$ Also tested on centos7.3 And the way to reproduce is to first execute SET NAMES utf8; then run a SHOW TABLE STATUS. Same stack trace. I will try to upgrade to 5.7.17 and see if I can reproduce. Lastly, I could not get a similar stack trace like the one reported here.