2014-08-03 07:29:42 7f2898eac840 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
140803  7:29:42 [Note] InnoDB: Using mutexes to ref count buffer pool pages
140803  7:29:42 [Note] InnoDB: The InnoDB memory heap is disabled
140803  7:29:42 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
140803  7:29:42 [Note] InnoDB: Compressed tables use zlib 1.2.8
140803  7:29:42 [Note] InnoDB: Using Linux native AIO
140803  7:29:42 [Note] InnoDB: Not using CPU crc32 instructions
140803  7:29:42 [Note] InnoDB: Initializing buffer pool, size = 80.0M
140803  7:29:42 [Note] InnoDB: Completed initialization of buffer pool
140803  7:29:42 [Note] InnoDB: Highest supported file format is Barracuda.
140803  7:29:42 [Note] InnoDB: The log sequence numbers 700821932630 and 700821932630 in ibdata files do not match the log sequence number 702580978934 in the ib_logfiles!
140803  7:29:42 [Note] InnoDB: Database was not shutdown normally!
140803  7:29:42 [Note] InnoDB: Starting crash recovery.
140803  7:29:42 [Note] InnoDB: Reading tablespace information from the .ibd files...
140803  7:29:42 [Note] InnoDB: Restoring possible half-written data pages 
140803  7:29:42 [Note] InnoDB: from the doublewrite buffer...
140803  7:29:42 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 10.0.12-MariaDB
key_buffer_size=16384
read_buffer_size=131072
max_used_connections=0
max_threads=258
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 566740 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x7f28998b11fd]
/usr/libexec/mysqld(handle_fatal_signal+0x345)[0x7f2899421405]
/lib64/libpthread.so.0(+0x107d0)[0x7f2898ac07d0]
/usr/libexec/mysqld(+0x907d69)[0x7f28997fad69]
/usr/libexec/mysqld(+0x909f73)[0x7f28997fcf73]
/usr/libexec/mysqld(+0x8697e5)[0x7f289975c7e5]
/usr/libexec/mysqld(+0x7a345b)[0x7f289969645b]
/usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x7f28994235a4]
/usr/libexec/mysqld(+0x3e5323)[0x7f28992d8323]
/usr/libexec/mysqld(_Z11plugin_initPiPPci+0x558)[0x7f28992d9138]
/usr/libexec/mysqld(+0x34b490)[0x7f289923e490]
/usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x5ad)[0x7f289924258d]
/lib64/libc.so.6(__libc_start_main+0xf0)[0x7f2896fdb0e0]
/usr/libexec/mysqld(+0x343e5d)[0x7f2899236e5d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.