Source: mariadb-10.6
Version: 1:10.6.7-3
Tags: upstream, confirmed, ftbfs
User: debian-sp...@lists.debian.org
Usertags: sparc64
Forwarded: https://jira.mariadb.org/browse/MDEV-28052
X-Debbugs-CC: debian-sp...@lists.debian.org
After upload of mariadb-10.6 1:10.6.7-3 I noticed that sparc64 builds
at https://buildd.debian.org/status/package.php?p=mariadb-10.6 were
failing:
main.implicit_commit 'innodb'w9 [ fail ]
Test ended at 2022-03-11 18:18:39
CURRENT_TEST: main.implicit_commit
mysqltest: In included file "./include/implicit_commit_helper.inc":
included from /<>/mysql-test/main/implicit_commit.test at line 361:
At line 3: query '$statement' failed: (2013): Lost
connection to server during query
The result from queries just before the failure was:
< snip >
# SQLCOM_ALTER_VIEW
#
INSERT INTO db1.trans (a) VALUES (1);
alter view v1 as select 2;
CALL db1.test_if_commit();
IMPLICIT COMMIT
YES
#
# SQLCOM_DROP_VIEW
#
INSERT INTO db1.trans (a) VALUES (1);
drop view v1;
CALL db1.test_if_commit();
IMPLICIT COMMIT
YES
#
# SQLCOM_CREATE_INDEX
#
INSERT INTO db1.trans (a) VALUES (1);
create index idx1 on t1(a);
More results from queries before failure can be found in
/<>/builddir/mysql-test/var/9/log/implicit_commit.log
Server [mysqld.1 - pid: 3925230, winpid: 3925230, exit: 256] failed
during test run
Server log from this test:
--SERVER LOG START---
2022-03-11 18:18:36 0 [ERROR] [FATAL] InnoDB:
innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch.
Please refer to
https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
220311 18:18:36 [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 https://mariadb.com/kb/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.6.7-MariaDB-3-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
63733 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 = 0x0 thread_stack 0x49000
/<>/builddir/sql/mariadbd(my_print_stacktrace+0x14)[0x1e98a1c]
The manual page at
https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /<>/builddir/mysql-test/var/9/mysqld.1/data
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimitedunlimitedseconds
Max file size unlimitedunlimitedbytes
Max data size unlimitedunlimitedbytes
Max stack size8388608 unlimitedbytes
Max core file sizeunlimitedunlimitedbytes
Max resident set unlimitedunlimitedbytes
Max open files1024 1024 files
Max processes 128960 128960 processes
Max locked memory 4229464064 4229464064 bytes
Max address space unlimitedunlimitedbytes
Max file locksunlimitedunlimitedlocks
Max pending signals 128960 128960 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 00
Max realtime priority 00
Max realtime timeout unlimitedunlimitedus
Core pattern: core
--SERVER LOG END-
- found 'core' (0/5)
Trying 'dbx' to get a backtrace
Trying 'gdb' to get a backtrace from coredump
/<>/builddir/mysql-test/var/9/log/main.implicit_commit-innodb/mysqld.1/data/core
Core generated by '/<>/builddir/sql/mariadbd'
Output from gdb follows. The first stack trace is from the failing thread.
The following stack traces are from all threads (so the failing one is
duplicated).
--
warning: Can't open file anon_inode:[io_uring] which was expanded to
anon_inode:[io_uring] during file-backed mapping note processing
warning: Can't open file anon_inode:[io_uring] which was
