InnoDB: End of page dump
150908 23:04:33  InnoDB: Page checksum 4068774198, prior-to-4.0.14-form checksum 2865448789
InnoDB: stored checksum 4068774198, prior-to-4.0.14-form stored checksum 3309707613
InnoDB: Page lsn 0 1823820451, low 4 bytes of lsn at page end 1823271692
InnoDB: Page number (if stored to page already) 5,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a transaction system page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
150908 23:04:33  InnoDB: Assertion failure in thread 140327967921984 in file buf0buf.c line 3620
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
23:04:33 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.

key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 461388 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7fa0a704dd79]
/usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7fa0a6f12923]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7fa0a5c5acb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7fa0a52c60d5]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7fa0a52c983b]
/usr/sbin/mysqld(+0x64bbc1)[0x7fa0a713dbc1]
/usr/sbin/mysqld(+0x657438)[0x7fa0a7149438]
/usr/sbin/mysqld(+0x657ddc)[0x7fa0a7149ddc]
/usr/sbin/mysqld(+0x6477f0)[0x7fa0a71397f0]
/usr/sbin/mysqld(+0x619afc)[0x7fa0a710bafc]
/usr/sbin/mysqld(+0x61bd1c)[0x7fa0a710dd1c]
/usr/sbin/mysqld(+0x607aea)[0x7fa0a70f9aea]
/usr/sbin/mysqld(+0x5d1399)[0x7fa0a70c3399]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fa0a6f14ff1]
/usr/sbin/mysqld(+0x30ecb1)[0x7fa0a6e00cb1]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xad4)[0x7fa0a6e043d4]
/usr/sbin/mysqld(+0x2852b6)[0x7fa0a6d772b6]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x624)[0x7fa0a6d7ad24]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7fa0a52b176d]
/usr/sbin/mysqld(+0x27eb29)[0x7fa0a6d70b29]
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.