Arch Linux

Description:

Tried upgrade to 10.1.8-1 and getting this:
http://www.universalconflicts.com/?tag=innodb

Additional info:
* 10.1.8-1
*

151102 15:43:32 mysqld_safe Starting mysqld daemon with databases from /home/mysql
2015-11-02 15:43:33 140010280671232 [Warning] option 'net_buffer_length': unsigned value 16777216 adjusted to 1048576
2015-11-02 15:43:33 140010280671232 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2015-11-02 15:43:33 140010280671232 [Note] /usr/bin/mysqld (mysqld 10.1.8-MariaDB) starting as process 4953 ...
2015-11-02 15:43:33 7f56af0b5800 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.
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: Memory barrier is not used
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: Compressed tables use zlib 1.2.8
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: Using Linux native AIO
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: Using CPU crc32 instructions
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: Completed initialization of buffer pool
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: 128 rollback segment(s) are active.
2015-11-02 15:43:33 140010280671232 [Note] InnoDB: Waiting for purge to start
2015-11-02 15:43:33 7f56737fb700 InnoDB: Assertion failure in thread 140009281664768 in file btr0cur.cc line 5341
InnoDB: Failing assertion: rb_ctx != RB_NONE
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.
151102 15:43:33 [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
key_buffer_size=536870912
read_buffer_size=131072
max_used_connections=0
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 = 625312 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/bin/mysqld(my_print_stacktrace+0x2e)[0x563bad2b3bde]
/usr/bin/mysqld(handle_fatal_signal+0x34d)[0x563bace02fad]
/usr/lib/libpthread.so.0(+0x10d60)[0x7f56acf01d60]
/usr/lib/libc.so.6(gsignal+0x38)[0x7f56ac5005f8]
/usr/lib/libc.so.6(abort+0x16a)[0x7f56ac501a7a]
/usr/bin/mysqld(+0x84c3d1)[0x563bad0c93d1]
/usr/bin/mysqld(+0x7db88e)[0x563bad05888e]
/usr/bin/mysqld(+0x7dc489)[0x563bad059489]
/usr/bin/mysqld(+0x7a4782)[0x563bad021782]
/usr/bin/mysqld(+0x80934a)[0x563bad08634a]
/usr/bin/mysqld(+0x7f868d)[0x563bad07568d]
/usr/lib/libpthread.so.0(+0x74a4)[0x7f56acef84a4]
/usr/lib/libc.so.6(clone+0x6d)[0x7f56ac5b613d]
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.
151102 15:43:33 mysqld_safe mysqld from pid file /home/mysql/claire.pid ended



Steps to reproduce: