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

Starting MariaDB failed with illegal instruction in WolfSSL

    XMLWordPrintable

Details

    Description

      2024-06-12  2:02:04 0 [Note] Starting MariaDB 11.4.2-MariaDB source revision 3fca5ed772fb75e3e57c507edef2985f8eba5b12 as process 3904
      2024-06-12  2:02:04 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
      2024-06-12  2:02:04 0 [Note] InnoDB: Number of transaction pools: 1
      2024-06-12  2:02:04 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2024-06-12  2:02:04 0 [Note] InnoDB: Initializing buffer pool, total size = 1.999GiB, chunk size = 31.984MiB
      2024-06-12  2:02:04 0 [Note] InnoDB: Completed initialization of buffer pool
      2024-06-12  2:02:04 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
      2024-06-12  2:02:04 0 [Note] InnoDB: End of log at LSN=47629
      2024-06-12  2:02:04 0 [Note] InnoDB: Opened 3 undo tablespaces
      2024-06-12  2:02:04 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
      2024-06-12  2:02:04 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
      2024-06-12  2:02:04 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
      2024-06-12  2:02:04 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
      2024-06-12  2:02:04 0 [Note] InnoDB: log sequence number 47629; transaction id 14
      2024-06-12  2:02:04 0 [Note] Plugin 'FEEDBACK' is disabled.
      2024-06-12  2:02:04 0 [Note] InnoDB: Loading buffer pool(s) from C:\Program Files\MariaDB 11.4\data\ib_buffer_pool
      2024-06-12  2:02:04 0 [Note] mysqld.exe: SSPI: using principal name 'localhost', mech 'Negotiate'
      2024-06-12  2:02:04 0 [Note] InnoDB: Buffer pool(s) load completed at 240612  2:02:04
      2024-06-12  2:02:04 0 [Note] Recovering after a crash using tc.log
      2024-06-12  2:02:04 0 [Note] Starting table crash recovery...
      2024-06-12  2:02:04 0 [Note] Crash table recovery finished.
      240612  2:02:04 [ERROR] mysqld got exception 0xc000001d ;
      Sorry, we probably made a mistake, and this is a bug.
       
      Your assistance in bug reporting will enable us to fix this for the next release.
      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: 11.4.2-MariaDB source revision: 3fca5ed772fb75e3e57c507edef2985f8eba5b12
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=65537
      thread_count=0
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 142742985 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...
      server.dll!sp_2048_get_from_table_32()[sp_x86_64_asm.asm:13172]

      Attachments

        1. DESKTOP-B4CQDOG.err
          13 kB
          Keny Dinh
        2. install.log
          2.32 MB
          Keny Dinh
        3. mysqld.dmp
          130 kB
          Keny Dinh
        4. systeminfo.txt
          2 kB
          Keny Dinh
        5. wolfssl-test.cc
          2 kB
          Vladislav Vaintroub

        Issue Links

          Activity

            People

              wlad Vladislav Vaintroub
              kenydinh Keny Dinh
              Votes:
              1 Vote for this issue
              Watchers:
              4 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.