Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 10.1
-
Fix Version/s: 10.1
-
Component/s: Storage Engine - XtraDB
-
Labels:None
Description
Output: http://buildbot.askmonty.org/buildbot/builders/work-amd64-valgrind/builds/7530/steps/test/logs/stdio
Server log: http://buildbot.askmonty.org/buildbot/builders/work-amd64-valgrind/builds/7530/steps/test/logs/mysqld.1.err.4
From server error log
########################################
DEADLOCK of threads detected!
Mutex 0xa5d5e38 owned by thread 321247568 file /var/lib/buildbot/maria-slave/work-opensuse-amd64/build/storage/xtradb/mem/mem0pool.cc line 140
--Thread 321247568 has waited at mem0pool.cc line 387 for 0.0000 seconds the semaphore:
Mutex at 0xa5d5e38 '&pool->mutex', lock var 1
Last time reserved by thread 321247568 in file /var/lib/buildbot/maria-slave/work-opensuse-amd64/build/storage/xtradb/mem/mem0pool.cc line 140, waiters flag 1
########################################
2015-08-21 20:30:19 1325d950 InnoDB: Assertion failure in thread 321247568 in file sync0arr.cc line 467
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.
150821 20:30:19 [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.6-MariaDB-valgrind-max-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 = 63010 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:247(my_print_stacktrace)[0xe7500e]
sql/signal_handler.cc:153(handle_fatal_signal)[0x7e516b]
/lib64/libpthread.so.0[0x4e3ca90]
/lib64/libc.so.6(gsignal+0x35)[0x6258645]
/lib64/libc.so.6(abort+0x183)[0x6259c33]
sync/sync0arr.cc:352(sync_cell_get_event)[0xb4de18]
sync/sync0sync.cc:698(mutex_spin_wait(void*, bool, char const*, unsigned long))[0xb52cf2]
include/sync0sync.ic:279(mutex_enter_func)[0xa8c277]
mem/mem0mem.cc:336(mem_heap_create_block_func(mem_block_info_t*, unsigned long, char const*, unsigned long, unsigned long))[0xa89e74]
include/mem0mem.ic:449(mem_heap_create_func)[0xb4e622]
sync/sync0rw.cc:752(rw_lock_x_lock_low)[0xb4eb36]
sync/sync0rw.cc:810(rw_lock_x_lock_func(rw_lock_t*, unsigned long, char const*, unsigned long, bool, bool))[0xb4f8c7]
include/sync0rw.ic:937(pfs_rw_lock_x_lock_func)[0xbbc195]
buf/buf0lru.cc:2207(buf_LRU_free_page(buf_page_t*, bool))[0xbe88d1]
buf/buf0flu.cc:1583(buf_flush_LRU_list_batch)[0xbe0343]
buf/buf0flu.cc:1906(buf_flush_end)[0xbe0a0a]
buf/buf0flu.cc:2920(buf_flush_lru_manager_thread)[0xbe0e4f]
/lib64/libpthread.so.0[0x4e35070]
/lib64/libc.so.6(clone+0x6d)[0x62f913d]
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
==13039== 8 bytes in 1 blocks are still reachable in loss record 1 of 958
==13039== at 0x4C25DD6: malloc (vg_replace_malloc.c:270)
==13039== by 0xB459B6: srv_parse_data_file_paths_and_sizes(char*) (srv0start.cc:395)
==13039== by 0xA1059D: innobase_init(void*) (ha_innodb.cc:3701)
==13039== by 0x7E9E0B: ha_initialize_handlerton(st_plugin_int*) (handler.cc:513)
==13039== by 0x616BCA: plugin_initialize(st_mem_root*, st_plugin_int*, int*, char**, bool) (sql_plugin.cc:1407)
==13039== by 0x618C6C: plugin_init(int*, char**, int) (sql_plugin.cc:1679)
==13039== by 0x54C105: init_server_components() (mysqld.cc:5158)
==13039== by 0x54D53C: mysqld_main(int, char**) (mysqld.cc:5717)
==13039== by 0x6244585: (below main) (in /lib64/libc-2.9.so)
==13039==
{
<insert_a_suppression_name_here>
...
Gliffy Diagrams
Attachments
Issue Links
- blocks
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Stalled
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions