Comment 8 for bug 1401133

We also have what seems to be the same issue with PXB crashing PXC node on CentOS 6.6

End of log from PXB:
---- cut here -----
150303 12:52:55 innobackupex: Executing LOCK BINLOG FOR BACKUP...
DBD::mysql::db do failed: Deadlock found when trying to get lock; try restarting transaction at /usr/bin/innobackupex line 3036.
innobackupex: got a fatal error with the following stacktrace: at /usr/bin/innobackupex line 3039
        main::mysql_query('HASH(0x162a220)', 'LOCK BINLOG FOR BACKUP') called at /usr/bin/innobackupex line 3501
        main::mysql_lock_binlog('HASH(0x162a220)') called at /usr/bin/innobackupex line 2000
        main::backup() called at /usr/bin/innobackupex line 1592
innobackupex: Error:
Error executing 'LOCK BINLOG FOR BACKUP': DBD::mysql::db do failed: Deadlock found when trying to get lock; try restarting transaction at /usr/bin/innobackupex line 3036.
150303 12:52:55 innobackupex: Waiting for ibbackup (pid=2844) to finish
Innobackupex failed. Please check logfiles
---------------------------

Log from PXC:

---- cut here -----
20:52:55 UTC - 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.
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.
Please help us make Percona XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster

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

Thread pointer: 0x3334940
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 = 7fb5a83c0d68 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8f97d5]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x6655c4]
/lib64/libpthread.so.0(+0xf710)[0x7fb5ac0d4710]
[0x7fab840000a8]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 148
Status: KILL_CONNECTION

You may download the Percona XtraDB Cluster operations manual by visiting
http://www.percona.com/software/percona-xtradb-cluster/. You may find information
in the manual which will help you identify the cause of the crash.
150303 12:52:57 mysqld_safe Number of processes running now: 0
150303 12:52:57 mysqld_safe WSREP: not restarting wsrep node automatically
150303 12:52:57 mysqld_safe mysqld from pid file /var/untd/mysql/log/mysqld.pid ended
---- cut here -----

Laimonas