Your message dated Tue, 9 Dec 2025 15:55:39 -0800
with message-id
<caou6taaw8t1fhe3-amw7wrxjev8fvn1jdqr_xfwg3cs3qfc...@mail.gmail.com>
and subject line mariadb: FTBFS on hppa: builds, but test suite crashes
immediately, previously also main.func_json_notembedded crash
has caused the Debian Bug report #1006529,
regarding mariadb: FTBFS on hppa: builds, but test suite crashes immediately,
previously also main.func_json_notembedded crash and anon_inode:io_uring
warning (regression from 10.11.1-3 with only 2/1021 tests failed and 10.5.12-1
all 792 tests passed)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1006529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006529
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mariadb-10.6
Version: 1:10.6.7-1
Tags: upstream, confirmed, help, ftbfs
User: [email protected]
Usertags: hppa
Builds on hppa succeed, but as the mariadbd binary crashes immediately on start:
mysql-test-run: *** ERROR: Error executing mariadbd --bootstrap
Could not install system database from
/<<PKGBUILDDIR>>/builddir/mysql-test/var/log/bootstrap.sql
The /<<PKGBUILDDIR>>/builddir/mysql-test/var/log/bootstrap.log file contains:
/<<PKGBUILDDIR>>/builddir/sql/mariadbd --no-defaults
--disable-getopt-prefix-matching --bootstrap
--basedir=/<<PKGBUILDDIR>>
--datadir=/<<PKGBUILDDIR>>/builddir/mysql-test/var/install.db
--plugin-dir=/<<PKGBUILDDIR>>/builddir/mysql-test/var/plugins
--default-storage-engine=myisam --loose-skip-plugin-feedback
--loose-skip-plugin-innodb --loose-skip-plugin-innodb-buffer-page-lru
--loose-skip-plugin-innodb-buffer-pool-stats
--loose-skip-plugin-innodb-cmp
--loose-skip-plugin-innodb-cmp-per-index
--loose-skip-plugin-innodb-cmp-per-index-reset
--loose-skip-plugin-innodb-cmp-reset --loose-skip-plugin-innodb-cmpmem
--loose-skip-plugin-innodb-cmpmem-reset
--loose-skip-plugin-innodb-ft-being-deleted
--loose-skip-plugin-innodb-ft-config
--loose-skip-plugin-innodb-ft-default-stopword
--loose-skip-plugin-innodb-ft-deleted
--loose-skip-plugin-innodb-ft-index-cache
--loose-skip-plugin-innodb-ft-index-table
--loose-skip-plugin-innodb-sys-columns
--loose-skip-plugin-innodb-sys-fields
--loose-skip-plugin-innodb-sys-foreign
--loose-skip-plugin-innodb-sys-foreign-cols
--loose-skip-plugin-innodb-sys-indexes
--loose-skip-plugin-innodb-sys-tables
--loose-skip-plugin-innodb-sys-tablespaces
--loose-skip-plugin-innodb-sys-tablestats
--loose-skip-plugin-innodb-sys-virtual
--loose-skip-plugin-innodb-tablespaces-encryption
--loose-skip-plugin-partition --loose-skip-plugin-sequence
--loose-skip-plugin-thread-pool-groups
--loose-skip-plugin-thread-pool-queues
--loose-skip-plugin-thread-pool-stats
--loose-skip-plugin-thread-pool-waits --loose-skip-plugin-unix-socket
--loose-skip-plugin-user-variables --loose-innodb
--loose-innodb-log-file-size=10M --disable-sync-frm
--tmpdir=/<<PKGBUILDDIR>>/builddir/mysql-test/var/tmp/ --core-file
--console --character-set-server=latin1
--lc-messages-dir=/<<PKGBUILDDIR>>/builddir/sql/share/
--character-sets-dir=/<<PKGBUILDDIR>>/sql/share/charsets
2022-02-25 13:18:37 0 [Note] /<<PKGBUILDDIR>>/builddir/sql/mariadbd
(server 10.6.7-MariaDB-2~exp1) starting as process 3949 ...
2022-02-25 13:18:37 0 [Warning] Could not increase number of
max_open_files to more than 1024 (request: 32186)
2022-02-25 13:18:37 0 [Warning] Changed limits: max_open_files: 1024
max_connections: 151 (was 151) table_cache: 421 (was 2000)
2022-02-25 13:18:37 0 [Note] Plugin 'partition' is disabled.
2022-02-25 13:18:37 0 [Note] Plugin 'SEQUENCE' is disabled.
2022-02-25 13:18:37 0 [Note] InnoDB: The first data file './ibdata1'
did not exist. A new tablespace will be created!
2022-02-25 13:18:37 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-02-25 13:18:37 0 [Note] InnoDB: Number of pools: 1
2022-02-25 13:18:37 0 [Note] InnoDB: Using generic crc32 instructions
2022-02-25 13:18:37 0 [Note] InnoDB: Using liburing
2022-02-25 13:18:37 0 [Note] InnoDB: Initializing buffer pool, total
size = 134217728, chunk size = 134217728
2022-02-25 13:18:37 0 [Note] InnoDB: Completed initialization of buffer pool
2022-02-25 13:18:37 0 [Note] InnoDB: Setting O_DIRECT on file ./ibdata1 failed
2022-02-25 13:18:37 0 [Note] InnoDB: Setting file './ibdata1' size to
12 MB. Physically writing the file full; Please wait ...
2022-02-25 13:18:37 0 [Note] InnoDB: File './ibdata1' size is now 12 MB.
2022-02-25 13:18:37 0 [Note] InnoDB: Setting log file ./ib_logfile101
size to 10485760 bytes
2022-02-25 13:18:38 0 [ERROR] InnoDB: File ./ibdata1: 'aio write'
returned OS error 0. Cannot continue operation
220225 13:18:38 [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-2~exp1
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
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 =
466655 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
/<<PKGBUILDDIR>>/builddir/sql/mariadbd(my_print_stacktrace-0xb5a76b42)[0x4203d89c]
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 /<<PKGBUILDDIR>>/builddir/mysql-test/var/install.db
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 31969 31969 processes
Max open files 1024 1024 files
Max locked memory 1050423296 1050423296 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 31969 31969 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: core
See full log at
https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6&arch=hppa&ver=1%3A10.6.7-2%7Eexp1&stamp=1645795163&raw=0
This is a regression, as hppa has (at least occasionally) built and
passed test suite before:
https://buildd.debian.org/status/logs.php?pkg=mariadb-10.6&arch=hppa
https://buildd.debian.org/status/logs.php?pkg=mariadb-10.5&arch=hppa
--- End Message ---
--- Begin Message ---
I am closing this bug now, as hppa builds haven't run since
1:10.11.8-1 in 2024, and have since been blocked due to missing
java-common build on hppa. Seems the last successful one there was in
2021: https://buildd.debian.org/status/logs.php?pkg=java-common&arch=hppa
--- End Message ---
