Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-42038

SHOW GLOBAL STATUS causes SIGBUS on armv7l

    XMLWordPrintable

Details

    • Bug
    • Status: Needs Feedback (View Workflow)
    • Critical
    • Resolution: Unresolved
    • 13.0.2
    • None
    • None
    • Arch Linux ARM on armv7l (32-bit)
      Kernel 6.6.159 #0 SMP Thu Oct 22 19:53:31 2026 armv7l GNU/Linux
    • Can result in hang or crash

    Description

      MariaDB crashes reproducibly with an unhandled alignment exception (SIGBUS) whenever executing SHOW GLOBAL STATUS on Arch Linux ARM running on a 32-bit armv7l processor.

      This is possibly still the same problem as MDEV-34197 which was closed as Incomplete in 2024.

      I run mariadb:

      Welcome to the MariaDB monitor.  Commands end with ; or \g.
      Your MariaDB connection id is 2456
      Server version: 13.0.2-MariaDB Arch Linux
       
      Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
       
      Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
       
      MariaDB [(none)]> SHOW GLOBAL STATUS;
      ERROR 2013 (HY000): Lost connection to server during query
      

      Journalctl of mariadb shows:

      mariadbd[4876]: 261104 12:45:23 [ERROR] /usr/bin/mariadbd got signal 7 ;
      mariadbd[4876]: Sorry, we probably made a mistake, and this is a bug.
      mariadbd[4876]: Your assistance in bug reporting will enable us to fix this for the next release.
      mariadbd[4876]: To report this bug, see https://mariadb.com/docs/general-resources/community/community/bug-tracking/reporting-bugs about how to report
      mariadbd[4876]: a bug on https://jira.mariadb.org/.
      mariadbd[4876]: Please include the information from the server start above, to the end of the
      mariadbd[4876]: information below.
      mariadbd[4876]: Server version: 13.0.2-MariaDB source revision: 620a4b5624222048fece7fe1789978ae0675cae2
      mariadbd[4876]: The information page at https://mariadb.com/docs/server/reference/product-development/mariadb-fault-finding/how-to-produce-a-full-stack-trace-for-mariadbdcontains instructions to obtain a better version of the backtrace below.
      mariadbd[4876]: Following these instructions will help MariaDB developers provide a fix quicker.
      mariadbd[4876]: Attempting backtrace. Include this in the bug report.
      mariadbd[4876]: (note: Retrieving this information may fail)
      mariadbd[4876]: Thread pointer: 0x96f7d6d0
      mariadbd[4876]: stack_bottom = 0x96fd8000 thread_stack 0x49000
      mariadbd[4876]: /usr/bin/mariadbd(my_print_stacktrace+0x2c) [0x12cd854]
      mariadbd[4876]: /usr/bin/mariadbd(handle_fatal_signal+0x1f0) [0xd416cc]
      mariadbd[4876]: /usr/lib/libc.so.6(__default_sa_restorer+0x0) [0xb63406e0]
      mariadbd[4876]: Connection ID (thread ID): 275
      mariadbd[4876]: Status: NOT_KILLED
      mariadbd[4876]: Query (0x96f29020): SHOW GLOBAL STATUS
      mariadbd[4876]: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,duplicateweedout=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=on,cset_narrowing=on,sargable_casefold=on,reorder_outer_joins=off
      mariadbd[4876]: Writing a core file...
      mariadbd[4876]: Working directory at /var/lib/mysql
      mariadbd[4876]: Resource Limits (excludes unlimited resources):
      mariadbd[4876]: Limit                     Soft Limit           Hard Limit           Units
      mariadbd[4876]: Max stack size            8388608              unlimited            bytes
      mariadbd[4876]: Max processes             7984                 7984                 processes
      mariadbd[4876]: Max open files            32768                32768                files
      mariadbd[4876]: Max locked memory         524288               524288               bytes
      mariadbd[4876]: Max pending signals       7984                 7984                 signals
      mariadbd[4876]: Max msgqueue size         819200               819200               bytes
      mariadbd[4876]: Max nice priority         0                    0
      mariadbd[4876]: Max realtime priority     0                    0
      mariadbd[4876]: Core pattern: /tmp/%e.%t.%p.%s.core
      mariadbd[4876]: Kernel version: Linux version 6.6.159 (packaging@turris.cz) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 13.3.0 r29285+93-b6fa907cb2) 13.3.0, GNU ld (GNU Binutils) 2.42) #0 SMP Thu Oct 22 19:53:31 2026
      systemd[1]: mariadb.service: Main process exited, code=dumped, status=7/BUS
      systemd[1]: mariadb.service: Failed with result 'core-dump'.
      

      and the corresponding dmesg is

      Alignment trap: not handling instruction f4422adf at [<012b87c4>]
      8<--- cut here ---
      Unhandled fault: alignment exception (0x811) at 0x96fd4094
      [96fd4094] *pgd=06679831, *pte=287e175f, *ppte=287e1c7f
      

      My attempt to addr2line the address shows my_b_printf but I’m not sure if this is correct.

      Attachments

        Activity

          People

            shipjain Shipra Jain
            mormegil Petr Kadlec
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.