upgrade from 10.1.8 to 10.1.9 crashes server

2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2015-11-24 13:48:45 140258989979520 [Note] InnoDB: The InnoDB memory heap is disabled

2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Memory barrier is not used

2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Compressed tables use zlib 1.2.8

2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Using Linux native AIO

2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Using CPU crc32 instructions

2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Initializing buffer pool, size = 2.0G

2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Completed initialization of buffer pool

2015-11-24 13:48:45 140258989979520 [Note] InnoDB: Highest supported file format is Barracuda.

2015-11-24 13:48:46 140258989979520 [Note] InnoDB: 128 rollback segment(s) are active.

2015-11-24 13:48:46 140258989979520 [Note] InnoDB: Waiting for purge to start

2015-11-24 13:48:46 140258989979520 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1555843502

2015-11-24 13:48:46 140256120637184 [Note] InnoDB: Dumping buffer pool(s) not yet started

2015-11-24 13:48:46 140258989979520 [Note] Plugin 'FEEDBACK' is disabled.

2015-11-24 13:48:46 140258989979520 [Note] Server socket created on IP: '127.0.0.1'.

2015-11-24 13:48:46 140258989979520 [Note] /usr/sbin/mysqld: ready for connections.

Version: '10.1.9-MariaDB-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution

151124 13:48:46 [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.1.9-MariaDB-log

key_buffer_size=33554432

read_buffer_size=249856

max_used_connections=0

max_threads=52

thread_count=0

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 59167 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/sbin/mysqld(my_print_stacktrace+0x29)[0x557fc0208e89]

/usr/sbin/mysqld(handle_fatal_signal+0x355)[0x557fbfdebd15]

/lib64/libpthread.so.0(+0x10220)[0x7f9095e00220]

/usr/sbin/mysqld(+0x7d3dfa)[0x557fc0078dfa]

/usr/sbin/mysqld(+0x7a84fa)[0x557fc004d4fa]

/usr/sbin/mysqld(+0x776640)[0x557fc001b640]

/usr/sbin/mysqld(+0x7d11b6)[0x557fc00761b6]

/usr/sbin/mysqld(+0x7c1b67)[0x557fc0066b67]

/lib64/libpthread.so.0(+0x7314)[0x7f9095df7314]

/lib64/libc.so.6(clone+0x6d)[0x7f9094c7051d]

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.{quote}