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

MariaDB crashes with SIGILL because the OS does not support AVX512

    XMLWordPrintable

Details

    Description

      The mariadb service start up is failing on AlmaLinux 9.4.

      Env:
      AlmaLinux 9.4
      libgcc-11.4.1-3.el9.alma.1.x86_64

      Mariadb packages installed:
      MariaDB-shared-10.11.8-1.el9.x86_64
      MariaDB-common-10.11.8-1.el9.x86_64
      MariaDB-client-10.11.8-1.el9.x86_64
      galera-4-26.4.18-1.el9.x86_64
      MariaDB-server-10.11.8-1.el9.x86_64
      MariaDB-backup-10.11.8-1.el9.x86_64

      my.cnf : Default (almost empty)

      #
      # This group is read both by the client and the server
      # use it for options that affect everything
      #
      [client-server]
       
      #
      # include *.cnf from the config directory
      #
      !includedir /etc/my.cnf.d
      

      Hardware Info:
      -VM

      [root@node1]# lscpu
      Architecture:            x86_64
        CPU op-mode(s):        32-bit, 64-bit
        Address sizes:         45 bits physical, 57 bits virtual
        Byte Order:            Little Endian
      CPU(s):                  2
        On-line CPU(s) list:   0,1
      Vendor ID:               GenuineIntel
        BIOS Vendor ID:        GenuineIntel
        Model name:            Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
          BIOS Model name:     Intel(R) Xeon(R) Gold 6330 CPU @ 2.00GHz
          CPU family:          6
          Model:               106
          Thread(s) per core:  1
          Core(s) per socket:  1
          Socket(s):           2
          Stepping:            6
          BogoMIPS:            3990.62
          Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon nopl xtopology
                               tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes f16c rdrand hypervisor lahf_lm abm 3dn
                               owprefetch cpuid_fault ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 smep bmi2 invpcid rdseed adx smap clflushopt clwb sha_ni wbnoinvd arat umip rdpid md_cle
                               ar flush_l1d arch_capabilities
      Virtualization features:
        Hypervisor vendor:     VMware
        Virtualization type:   full
      Caches (sum of all):
        L1d:                   96 KiB (2 instances)
        L1i:                   64 KiB (2 instances)
        L2:                    2.5 MiB (2 instances)
        L3:                    84 MiB (2 instances)
      NUMA:
        NUMA node(s):          1
        NUMA node0 CPU(s):     0,1
      Vulnerabilities:
        Gather data sampling:  Unknown: Dependent on hypervisor status
        Itlb multihit:         KVM: Mitigation: VMX unsupported
        L1tf:                  Not affected
        Mds:                   Not affected
        Meltdown:              Not affected
        Mmio stale data:       Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state unknown
        Retbleed:              Not affected
        Spec rstack overflow:  Not affected
        Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
        Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
        Spectre v2:            Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
        Srbds:                 Not affected
        Tsx async abort:       Not affected
      [root@node1]#
      

      Error message from /var/log/message:

      Jul 11 01:36:45 node1 mariadbd[79583]: 2024-07-11  1:36:45 0 [Note] Starting MariaDB 10.11.8-MariaDB source revision 3a069644682e336e445039e48baae9693f9a08ee as process 79583
      Jul 11 01:36:45 node1 mariadbd[79583]: 240711  1:36:45 [ERROR] mysqld got signal 4 ;
      Jul 11 01:36:45 node1 mariadbd[79583]: Sorry, we probably made a mistake, and this is a bug.
      Jul 11 01:36:45 node1 mariadbd[79583]: Your assistance in bug reporting will enable us to fix this for the next release.
      Jul 11 01:36:45 node1 mariadbd[79583]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
      Jul 11 01:36:45 node1 mariadbd[79583]: We will try our best to scrape up some info that will hopefully help
      Jul 11 01:36:45 node1 mariadbd[79583]: diagnose the problem, but since we have already crashed,
      Jul 11 01:36:45 node1 mariadbd[79583]: something is definitely wrong and this may fail.
      Jul 11 01:36:45 node1 mariadbd[79583]: Server version: 10.11.8-MariaDB source revision: 3a069644682e336e445039e48baae9693f9a08ee
      Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size=134217728
      Jul 11 01:36:45 node1 mariadbd[79583]: read_buffer_size=131072
      Jul 11 01:36:45 node1 mariadbd[79583]: max_used_connections=0
      Jul 11 01:36:45 node1 mariadbd[79583]: max_threads=153
      Jul 11 01:36:45 node1 mariadbd[79583]: thread_count=0
      Jul 11 01:36:45 node1 mariadbd[79583]: It is possible that mysqld could use up to
      Jul 11 01:36:45 node1 mariadbd[79583]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468061 K  bytes of memory
      Jul 11 01:36:45 node1 mariadbd[79583]: Hope that's ok; if not, decrease some variables in the equation.
      Jul 11 01:36:45 node1 mariadbd[79583]: Thread pointer: 0x0
      Jul 11 01:36:45 node1 mariadbd[79583]: Attempting backtrace. You can use the following information to find out
      Jul 11 01:36:45 node1 mariadbd[79583]: where mysqld died. If you see no messages after this, something went
      Jul 11 01:36:45 node1 mariadbd[79583]: terribly wrong...
      Jul 11 01:36:45 node1 mariadbd[79583]: stack_bottom = 0x0 thread_stack 0x49000
      Jul 11 01:36:45 node1 mariadbd[79583]: Printing to addr2line failed
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55fb1b527cee]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(handle_fatal_signal+0x468)[0x55fb1afffa28]
      Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x3e6f0)[0x7fbf8803e6f0]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xfcbff5)[0x55fb1b53eff5]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc286f3)[0x55fb1b19b6f3]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0xc2071c)[0x55fb1b19371c]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x7e)[0x55fb1b002b1e]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x84b523)[0x55fb1adbe523]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x8519fc)[0x55fb1adc49fc]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x8f1)[0x55fb1adc5a21]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(+0x7244ff)[0x55fb1ac974ff]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x415)[0x55fb1ac9ca55]
      Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(+0x29590)[0x7fbf88029590]
      Jul 11 01:36:45 node1 mariadbd[79583]: /lib64/libc.so.6(__libc_start_main+0x80)[0x7fbf88029640]
      Jul 11 01:36:45 node1 mariadbd[79583]: /usr/sbin/mariadbd(_start+0x25)[0x55fb1ac91595]
      Jul 11 01:36:45 node1 mariadbd[79583]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
      Jul 11 01:36:45 node1 mariadbd[79583]: information that should help you find out what is causing the crash.
      Jul 11 01:36:45 node1 mariadbd[79583]: Writing a core file...
      Jul 11 01:36:45 node1 mariadbd[79583]: Working directory at /var/lib/mysql
      Jul 11 01:36:45 node1 mariadbd[79583]: Resource Limits:
      Jul 11 01:36:45 node1 mariadbd[79583]: Limit                     Soft Limit           Hard Limit           Units
      Jul 11 01:36:45 node1 mariadbd[79583]: Max cpu time              unlimited            unlimited            seconds
      Jul 11 01:36:45 node1 mariadbd[79583]: Max file size             unlimited            unlimited            bytes
      Jul 11 01:36:45 node1 mariadbd[79583]: Max data size             unlimited            unlimited            bytes
      Jul 11 01:36:45 node1 mariadbd[79583]: Max stack size            8388608              unlimited            bytes
      Jul 11 01:36:45 node1 mariadbd[79583]: Max core file size        0                    unlimited            bytes
      Jul 11 01:36:45 node1 mariadbd[79583]: Max resident set          unlimited            unlimited            bytes
      Jul 11 01:36:45 node1 mariadbd[79583]: Max processes             30630                30630                processes
      Jul 11 01:36:45 node1 mariadbd[79583]: Max open files            32768                32768                files
      Jul 11 01:36:45 node1 mariadbd[79583]: Max locked memory         8388608              8388608              bytes
      Jul 11 01:36:45 node1 mariadbd[79583]: Max address space         unlimited            unlimited            bytes
      Jul 11 01:36:45 node1 mariadbd[79583]: Max file locks            unlimited            unlimited            locks
      Jul 11 01:36:45 node1 mariadbd[79583]: Max pending signals       30630                30630                signals
      Jul 11 01:36:45 node1 mariadbd[79583]: Max msgqueue size         819200               819200               bytes
      Jul 11 01:36:45 node1 mariadbd[79583]: Max nice priority         0                    0
      Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime priority     0                    0
      Jul 11 01:36:45 node1 mariadbd[79583]: Max realtime timeout      unlimited            unlimited            us
      Jul 11 01:36:45 node1 mariadbd[79583]: Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
      Jul 11 01:36:45 node1 mariadbd[79583]: Kernel version: Linux version 5.14.0-427.18.1.el9_4.x86_64 (mockbuild@x64-builder02.almalinux.org) (gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3), GNU ld version 2.35.2-43.el9) #1 SMP PREEMPT_DYNAMIC Tue May 28 06:27:02 EDT 2024
      Jul 11 01:36:45 node1 systemd-coredump[79592]: Process 79583 (mariadbd) of user 1001 dumped core.
      Jul 11 01:36:45 node1 systemd[1]: systemd-coredump@1493-79590-0.service: Deactivated successfully.
      Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Main process exited, code=dumped, status=4/ILL
      Jul 11 01:36:45 node1 systemd[1]: mariadb.service: Failed with result 'core-dump'.
      Jul 11 01:36:45 node1 systemd[1]: Failed to start MariaDB 10.11.8 database server.
      

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              bijjupatel Bijju Patel
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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