[php-maint] Bug#774795: php5, mysql-server-5.5: php5 FTBFS on ppc64el due to mysql assertion failure "InnoDB: Failing assertion: node->n_pending == 0"

[Niels Thykier]

Package: php5,mysql-server-5.5
Severity: serious

Hi PHP5 maintainers and MySQL maintainers,

I noticed that PHP5 FTBFS on powerpc64el with the following[1]:

"""
150105 16:07:30 InnoDB: 5.5.40 started; log sequence number 0
150105 16:07:30  InnoDB: Starting shutdown...
150105 16:07:31  InnoDB: Assertion failure in thread 70367505444544 in file fil0fil.c line 860
InnoDB: Failing assertion: node->n_pending == 0
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.
16:07:31 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=8388608
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 = 338508 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x48)[0x30f42bd8]
/usr/sbin/mysqld(handle_fatal_signal+0x4ac)[0x30dbff5c]
linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)[0x3fffb62b0478]
/lib/powerpc64le-linux-gnu/libc.so.6(gsignal+0x48)[0x3fffb5d70978]
/lib/powerpc64le-linux-gnu/libc.so.6(abort+0x26c)[0x3fffb5d72d7c]
/usr/sbin/mysqld(+0x70d8d0)[0x3109d8d0]
/usr/sbin/mysqld(+0x712908)[0x310a2908]
/usr/sbin/mysqld(+0x755950)[0x310e5950]
/usr/sbin/mysqld(+0x687b34)[0x31017b34]
/usr/sbin/mysqld(+0x6433b8)[0x30fd33b8]
/usr/sbin/mysqld(_Z22ha_finalize_handlertonP13st_plugin_int+0x5c)[0x30dc33dc]
/usr/sbin/mysqld(+0x3172d0)[0x30ca72d0]
/usr/sbin/mysqld(+0x31d00c)[0x30cad00c]
/usr/sbin/mysqld(_Z15plugin_shutdownv+0x2d0)[0x30cae8f0]
/usr/sbin/mysqld(+0x27f870)[0x30c0f870]
/usr/sbin/mysqld(unireg_abort+0x258)[0x30c108c8]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x948)[0x30c17698]
/usr/sbin/mysqld(main+0x18)[0x30bf9b98]
/lib/powerpc64le-linux-gnu/libc.so.6(+0x24e00)[0x3fffb5d54e00]
/lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xc4)[0x3fffb5d54ff4]
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.
make: *** [test-results.txt] Error 1
"""

Being an "assertion failure" (and given the remarks about the binary
being possibly corrupt) I suspect it is a problem in the MySQL
package.  If you agree with this, please reassign it to the relevant
mysql-server package (possibly with an "affects" on php5).

~Niels

[1] https://buildd.debian.org/status/fetch.php?pkg=php5&arch=ppc64el&ver=5.6.4%2Bdfsg-3&stamp=1420474234