2014-12-17 08:52:26 30442 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)

2014-12-17 08:52:26 30442 [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000)

2014-12-17 08:52:26 30442 [Warning] Using unique option prefix innodb_track_changed_page instead of innodb-track-changed-pages is deprecated and will be removed in a future release. Please use the full name instead.
2014-12-17 08:52:26 30442 [Note] Plugin 'FEDERATED' is disabled.
2014-12-17 08:52:26 30442 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-12-17 08:52:26 30442 [Note] InnoDB: The InnoDB memory heap is disabled
2014-12-17 08:52:26 30442 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-12-17 08:52:26 30442 [Note] InnoDB: Memory barrier is not used
2014-12-17 08:52:26 30442 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-12-17 08:52:26 30442 [Note] InnoDB: Using Linux native AIO
2014-12-17 08:52:26 30442 [Note] InnoDB: Using CPU crc32 instructions
2014-12-17 08:52:26 30442 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2014-12-17 08:52:27 30442 [Note] InnoDB: Completed initialization of buffer pool
2014-12-17 08:52:27 30442 [Note] InnoDB: Highest supported file format is Barracuda.
2014-12-17 08:52:27 30442 [Note] InnoDB: starting tracking changed pages from LSN 1625987

2014-12-17 08:52:27 30442 [Note] InnoDB: 128 rollback segment(s) are active.
2014-12-17 08:52:27 30442 [Note] InnoDB: Waiting for purge to start
2014-12-17 08:52:27 30442 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.21-rel70.0 started; log sequence number 1625987
2014-12-17 08:52:27 30442 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 06e67dd1-85ca-11e4-b09b-002590e76afe.
2014-12-17 08:52:27 30442 [Note] Server hostname (bind-address): '*'; port: 14412
2014-12-17 08:52:27 30442 [Note] IPv6 is available.
2014-12-17 08:52:27 30442 [Note]   - '::' resolves to '::';
2014-12-17 08:52:27 30442 [Note] Server socket created on IP: '::'.
2014-12-17 08:52:27 30442 [Note] Event Scheduler: Loaded 0 events
2014-12-17 08:52:27 30442 [Note] /ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld: ready for connections.
Version: '5.6.21-70.0-log'  socket: '/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/socket.sock'  port: 14412  Percona Server (GPL), Release 70.0, Revision 693
2014-12-17 08:52:27 30442 [Note] Event Scheduler: scheduler thread started with id 1
InnoDB: Error: MySQL is trying to perform a consistent read
InnoDB: but the read view is not assigned!
TRANSACTION 1805, ACTIVE 0 sec fetching rows
mysql tables in use 1, locked 0
MySQL thread id 2, OS thread handle 0x7f7dc4315700, query id 7 localhost root Opening tables
SELECT CONVERT_TZ(1,1,a)FROM t1

2014-12-17 08:52:31 7f7dc4315700  InnoDB: Assertion failure in thread 140178139207424 in file row0sel.cc line 4071
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:52:31 UTC - mysqld got signal 6 ;
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.
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=1
max_threads=153
thread_count=2
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 69184 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f7d33735000
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 = 7f7dc4314e40 thread_stack 0x40000
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(my_print_stacktrace+0x2c)[0x8e9f2c]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(handle_fatal_signal+0x461)[0x676831]
/lib64/libpthread.so.0(+0xf130)[0x7f7dc3d61130]
/lib64/libc.so.6(gsignal+0x39)[0x7f7dc29625c9]
/lib64/libc.so.6(abort+0x148)[0x7f7dc2963cd8]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld[0x9b7751]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld[0x9084d6]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_ZN7handler11ha_rnd_nextEPh+0x94)[0x5bc114]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_ZN12ha_partition8rnd_nextEPh+0x4a)[0xb63b6a]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_ZN7handler11ha_rnd_nextEPh+0x5d)[0x5bc0dd]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x20)[0x820320]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x101)[0x6d4891]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_ZN4JOIN4execEv+0x2b8)[0x6d3b08]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x275)[0x71c965]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x165)[0x71d1c5]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld[0x57e6d2]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_Z21mysql_execute_commandP3THD+0x1e49)[0x6f6e99]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5c8)[0x6fc0e8]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xff9)[0x6fd859]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x162)[0x6cb3c2]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(handle_one_connection+0x40)[0x6cb4b0]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(pfs_spawn_thread+0x143)[0xaf86d3]
/lib64/libpthread.so.0(+0x7df3)[0x7f7dc3d59df3]
/lib64/libc.so.6(clone+0x6d)[0x7f7dc2a2301d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7d0a41d010): SELECT CONVERT_TZ(1,1,a)FROM t1
Connection ID (thread ID): 2
Status: KILL_TIMEOUT

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
Writing a core file