Version: '10.1.8-MariaDB-debug-log'  socket: '/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/tmp/4/mysqld.1.sock'  port: 16060  Source distribution

2015-09-28 06:55:47 3fff7efff140  InnoDB: Assertion failure in thread 70366579913024 in file buf0buf.cc line 6019

InnoDB: Failing assertion: key_version == 0 || key_version >= bpage->key_version

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.

150928  6:55:47 [ERROR] 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.

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.1.8-MariaDB-debug-log

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=1

max_threads=153

thread_count=0

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62963 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

mysys/stacktrace.c:246(my_print_stacktrace)[0x396e806c]

sql/signal_handler.cc:160(handle_fatal_signal)[0x38df1d00]

linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)[0x3fff942b0478]

/opt/at8.0/lib64/power8/libc.so.6(gsignal-0x19261c)[0x3fff93900e6c]

/opt/at8.0/lib64/power8/libc.so.6(abort-0x18ff64)[0x3fff9390398c]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x16c0cc)[0x3fff8bf3c0cc]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17b014)[0x3fff8bf4b014]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17b708)[0x3fff8bf4b708]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17bfe4)[0x3fff8bf4bfe4]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17c36c)[0x3fff8bf4c36c]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17ce4c)[0x3fff8bf4ce4c]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(_Z15buf_flush_batchP10buf_pool_t11buf_flush_tmmP16flush_counters_t-0x409b64)[0x3fff8bf4d274]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x17db04)[0x3fff8bf4db04]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x21191c)[0x3fff8bfe191c]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x211e34)[0x3fff8bfe1e34]

/home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/var/4/plugins/ha_innodb.so(+0x212144)[0x3fff8bfe2144]

/opt/at8.0/lib64/power8/libpthread.so.0(+0xbcec)[0x3fff9426bcec]

/opt/at8.0/lib64/power8/libc.so.6(clone-0xa814c)[0x3fff939f403c]

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.

Writing a core file