Hi Daniel, I tried if I could use your gdb example to verify the issue which would then serve as vreification on the SRU as well. I don't need the gdb part to do so, but while going on I found that all works find until this step: $ make gunit_large
That was in artful, so that seems to be renamed in latter versions maybe? Or more than the enable downloads needed? Trying the last version from Xenial (which also is 5.7.19-0ubuntu0.16.04.1) ended up the same way. OTOH enable downloads sounded suspicious as I usually have only connection to a reduced set of canonical systems, so I set up proxies and re-executed the steps. That was it ending up in: $ ./unittest/gunit/merge_large_tests-t --gtest_filter=TCLogMMapTest.TClogCommit # Running 1 test from 1 test case 1..1 # Global test environment set-up # Run 1 TCLogMMapTest.TClogCommit 15:04:56 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. key_buffer_size=0 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 = 59998 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x1001bc465f0 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 = 7fffcc268aa0 thread_stack 0x40000 ./unittest/gunit/merge_large_tests-t[0x10b328f0] ./unittest/gunit/merge_large_tests-t[0x10901354] [0x74ed428504d8] ./unittest/gunit/merge_large_tests-t[0x108c4b48] ./unittest/gunit/merge_large_tests-t[0x108c4a34] ./unittest/gunit/merge_large_tests-t[0x1021e274] ./unittest/gunit/merge_large_tests-t[0x110a4134] ./unittest/gunit/merge_large_tests-t[0x110949f0] ./unittest/gunit/merge_large_tests-t[0x11094d78] ./unittest/gunit/merge_large_tests-t[0x110951bc] ./unittest/gunit/merge_large_tests-t[0x11095be0] ./unittest/gunit/merge_large_tests-t[0x11095e5c] ./unittest/gunit/merge_large_tests-t[0x10061ff0] /lib/powerpc64le-linux-gnu/libc.so.6(+0x2291c)[0x74ed4211291c] /lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x74ed42112b18] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0): Connection ID (thread ID): 1 Status: NOT_KILLED 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. So this can be used as steps-to-reproduce ** Description changed: - == Comment: #0 - Daniel Black + Steps-to-reproduce: + sudo vim /etc/apt/sources.list + sudo apt update + sudo apt install ubuntu-dev-tools build-essential + sudo apt-get build-dep mysql-5.7 + apt source mysql-5.7 + cd mysql-5.7-5.7.19/ + vim debian/rules + # enable -DENABLE_DOWNLOADS=1 \ + DEB_BUILD_OPTIONS=parallel=160 dpkg-buildpackage -us -uc -nc + cd builddir + make gunit_large + ./unittest/gunit/merge_large_tests-t --gtest_filter=TCLogMMapTest.TClogCommit + (crash) + + + == Comment: #0 - Daniel Black ---Problem Description--- MySQL-5.6/5.7: default log-tc-size too small on POWER - 3 * ( 64K page size) minimum needed - ---uname output--- Linux p87 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:09:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux - - Machine Type = Any P8 - + + Machine Type = Any P8 + ---Steps to Reproduce--- Perform a large number of XA transactions without a binary log configured. Its usually triggered in the MTR test run. As Power's page size is 64K by default the assumption that 3*8K was sufficient applies to x86 but not Power. - Userspace tool common name: MySQL-5.7 - - The userspace tool has the following bit modes: both + Userspace tool common name: MySQL-5.7 + + The userspace tool has the following bit modes: both Userspace rpm: MySQL-5.7 - Userspace tool obtained from project website: na - + Userspace tool obtained from project website: na Oracle have corrected this in 8.0 https://bugs.mysql.com/bug.php?id=80818 (https://github.com/mysql/mysql- server/commit/62b80f7d9db06d0edecf5a277e6a7fc489d806d5). A 5.7 backport is here https://bugs.mysql.com/bug.php?id=87175. Alternately (and more minimally) Alexey's patch in https://bugs.mysql.com/bug.php?id=80818 is sufficient (though replace 65535 -> 65536 in patch). --- Work arounds -- Set log-tc-size=196k or larger in my.cnf at startup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706291 Title: MySQL-5.7: default log-tc-size too small on POWER. 3 * ( 64K page size) minimum needed To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/1706291/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
