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

Starting MariaDB failed with illegal instruction in WolfSSL

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
        2. install.log
          2.32 MB
        3. mysqld.dmp
          130 kB
        4. systeminfo.txt
          2 kB
        5. wolfssl-test.cc
          2 kB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34668 Install mariadb-11.4.2-win64 on Windows 11 home Indonesia cannot start service

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11091 Bootstrap crashes with illegal instruction on Xen on Win Server 2012 R2

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MDEV-31856 use ephemeral ssl certificates

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          links to

          Web Link WolfSSL bug report 7663

          Activity

            Ascending order - Click to sort in descending order
            kenydinh Keny Dinh created issue -
            alice Alice Sherepa made changes -
            Field Original Value New Value
            serg Sergei Golubchik made changes -
            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]             		{noformat}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]{noformat}
            serg Sergei Golubchik added a comment -

            please include more of the error log. What lines are after

            server.dll!sp_2048_get_from_table_32()[sp_x86_64_asm.asm:13172]

            ?

            serg Sergei Golubchik added a comment - please include more of the error log. What lines are after server.dll!sp_2048_get_from_table_32()[sp_x86_64_asm.asm:13172] ?
            serg Sergei Golubchik made changes -
            Status Open [ 1 ] Needs Feedback [ 10501 ]
            kenydinh Keny Dinh made changes -
            Attachment DESKTOP-B4CQDOG.err [ 73658 ]
            Attachment install.log [ 73659 ]
            kenydinh Keny Dinh made changes -
            Attachment chuanuc.ico [ 73660 ]
            kenydinh Keny Dinh made changes -
            Attachment chuanuc.ico [ 73660 ]
            kenydinh Keny Dinh added a comment -

            It seems like there is no stack trace behind it.
            Here is the error log from MariaDB: DESKTOP-B4CQDOG.err
            And the installation log: install.log

            kenydinh Keny Dinh added a comment - It seems like there is no stack trace behind it. Here is the error log from MariaDB: DESKTOP-B4CQDOG.err And the installation log: install.log
            wlad Vladislav Vaintroub added a comment -

            There is an AVX instruction at this line of code in the version of wolfssl we use

            IFNDEF WC_NO_CACHE_RESISTANT
            		 
            _text SEGMENT READONLY PARA
            		 
            sp_2048_get_from_table_32 PROC
            		 
                    sub	rsp, 128
            		 
                    vmovdqu	OWORD PTR [rsp], xmm6  //<--- line 13172

            Looks like WolfSSL could have missed checking cpuid before using vmovdqu

            wlad Vladislav Vaintroub added a comment - There is an AVX instruction at this line of code in the version of wolfssl we use IFNDEF WC_NO_CACHE_RESISTANT _text SEGMENT READONLY PARA sp_2048_get_from_table_32 PROC sub rsp, 128 vmovdqu OWORD PTR [rsp], xmm6 //<--- line 13172 Looks like WolfSSL could have missed checking cpuid before using vmovdqu
            wlad Vladislav Vaintroub added a comment -

            kenydinh, can you also attach C:\Program Files\MariaDB 11.4\data\mysqld.dmp ? it should not be large.
            What is the CPU this machine is running on?
            Can you maybe provide output of C:\Windows\System32\systeminfo.exe ?

            wlad Vladislav Vaintroub added a comment - kenydinh , can you also attach C:\Program Files\MariaDB 11.4\data\mysqld.dmp ? it should not be large. What is the CPU this machine is running on? Can you maybe provide output of C:\Windows\System32\systeminfo.exe ?
            wlad Vladislav Vaintroub made changes -
            Labels installation SSL installation
            kenydinh Keny Dinh made changes -
            Attachment systeminfo.txt [ 73678 ]
            kenydinh Keny Dinh made changes -
            Attachment mysqld.dmp [ 73679 ]
            kenydinh Keny Dinh added a comment -

            I am using VirtualBox Windows 10 machine: systeminfo.txt, and I successfully installed MariaDB 11.3.2 but was unable to install MariaDB 11.4.2. Here is dump file: mysqld.dmp

            kenydinh Keny Dinh added a comment - I am using VirtualBox Windows 10 machine: systeminfo.txt , and I successfully installed MariaDB 11.3.2 but was unable to install MariaDB 11.4.2. Here is dump file: mysqld.dmp
            wlad Vladislav Vaintroub added a comment -

            Hmm, I was hoping to derive some Intel Pentium or Celeron from the processor description in the systeminfo.txt. Instead, it is Intel64 Family 6 Model 151, which is exactly like mine Alder Lake. Maybe you disabled AVX processor feature somehow?

            Anyway, the explanation for why it is in 11.4 is that some SSL code runs due to MDEV-31856, by the 3rd party library, which uses CPU instruction from AVX instruction set, and if you do not have it or disabled it, "invalid instruction" will be there.

            If you do not require installer, and can live with ZIP, you can disable this ssl with adding 

            [client-server]
            		 
            ssl=0

            to the my.ini after running mysql_install_db.exe

            wlad Vladislav Vaintroub added a comment - Hmm, I was hoping to derive some Intel Pentium or Celeron from the processor description in the systeminfo.txt . Instead, it is Intel64 Family 6 Model 151, which is exactly like mine Alder Lake. Maybe you disabled AVX processor feature somehow? Anyway, the explanation for why it is in 11.4 is that some SSL code runs due to MDEV-31856 , by the 3rd party library, which uses CPU instruction from AVX instruction set, and if you do not have it or disabled it, "invalid instruction" will be there. If you do not require installer, and can live with ZIP, you can disable this ssl with adding [client-server] ssl=0 to the my.ini after running mysql_install_db.exe
            wlad Vladislav Vaintroub added a comment -

            Filed https://github.com/wolfSSL/wolfssl/issues/7663

            wlad Vladislav Vaintroub added a comment - Filed https://github.com/wolfSSL/wolfssl/issues/7663
            wlad Vladislav Vaintroub made changes -
            wlad Vladislav Vaintroub made changes -
            wlad Vladislav Vaintroub added a comment -

            attached dump corroborates invalid instruction exception

            wlad Vladislav Vaintroub added a comment - attached dump corroborates invalid instruction exception
            wlad Vladislav Vaintroub made changes -
            Assignee Vladislav Vaintroub [ wlad ]
            Status Needs Feedback [ 10501 ] Open [ 1 ]
            wlad Vladislav Vaintroub made changes -
            Summary Starting MariaDB service failed during installation Starting MariaDB service failed during installation with invalid instruction in WolfSSL
            wlad Vladislav Vaintroub made changes -
            Summary Starting MariaDB service failed during installation with invalid instruction in WolfSSL Starting MariaDB failed with invalid instruction in WolfSSL
            wlad Vladislav Vaintroub made changes -
            Summary Starting MariaDB failed with invalid instruction in WolfSSL Starting MariaDB failed with illegal instruction in WolfSSL
            wlad Vladislav Vaintroub made changes -
            Attachment wolfssl-test.zip [ 73683 ]
            wlad Vladislav Vaintroub made changes -
            Attachment wolfssl-test.cc [ 73684 ]
            wlad Vladislav Vaintroub added a comment - - edited

            There is a tentative fix for wolfssl issue , for which the developer requests feedback.

            I created a test program wolfssl-test.cc, build an exe with patched wolfssl, and put into [^wolfssl-test.zip].
            kenydinh, could you try it out on the machine in question? Unpack and run wolfssl-test.exe on command line. Could attach its output?

            Thanks!

            PS. I'm still intrigued by what actual hardware is on that vbox. If you could download https://learn.microsoft.com/en-us/sysinternals/downloads/coreinfo and run it on the machine, and attach output as well, that would be great.

            wlad Vladislav Vaintroub added a comment - - edited There is a tentative fix for wolfssl issue , for which the developer requests feedback. I created a test program wolfssl-test.cc , build an exe with patched wolfssl, and put into [^wolfssl-test.zip] . kenydinh , could you try it out on the machine in question? Unpack and run wolfssl-test.exe on command line. Could attach its output? Thanks! PS. I'm still intrigued by what actual hardware is on that vbox. If you could download https://learn.microsoft.com/en-us/sysinternals/downloads/coreinfo and run it on the machine, and attach output as well, that would be great.
            wlad Vladislav Vaintroub made changes -
            Status Open [ 1 ] Needs Feedback [ 10501 ]
            infinitevs Static Dream added a comment - - edited

            I can confirm that I also experience the same behavior with 11.4.2 on windows server 2022, running on a VM inside proxmox. This vm was moved from a real machine and that machine was running a amd phenom II 4 core cpu, and had dd3 ram. (Please let me know if you need further information and I will be happy to provide.)

            2024-06-24 22:10:14 0 [Note] Starting MariaDB 11.4.2-MariaDB-log source revision 3fca5ed772fb75e3e57c507edef2985f8eba5b12 as process 5624
            2024-06-24 22:10:14 0 [Note] InnoDB: Compressed tables use zlib 1.3.1
            2024-06-24 22:10:14 0 [Note] InnoDB: Number of transaction pools: 1
            2024-06-24 22:10:15 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
            2024-06-24 22:10:15 0 [Note] InnoDB: Initializing buffer pool, total size = 1.000GiB, chunk size = 16.000MiB
            2024-06-24 22:10:15 0 [Note] InnoDB: Completed initialization of buffer pool
            2024-06-24 22:10:15 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
            2024-06-24 22:10:15 0 [Note] InnoDB: Resetting space id's in the doublewrite buffer
            2024-06-24 22:10:15 0 [Note] InnoDB: End of log at LSN=11391160912
            2024-06-24 22:10:15 0 [Note] InnoDB: Opened 3 undo tablespaces
            2024-06-24 22:10:15 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
            2024-06-24 22:10:15 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
            2024-06-24 22:10:15 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
            2024-06-24 22:10:15 0 [Note] InnoDB: log sequence number 11391160912; transaction id 4569019
            2024-06-24 22:10:15 0 [Note] Plugin 'FEEDBACK' is disabled.
            2024-06-24 22:10:15 0 [Note] InnoDB: Loading buffer pool(s) from C:\ProgramData\MySQL\MariaDB 10\data\ib_buffer_pool
            2024-06-24 22:10:15 0 [Note] mysqld.exe: SSPI: using principal name 'Administrator@XXXX, mech 'Negotiate'
            240624 22:10:15 [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-log source revision: 3fca5ed772fb75e3e57c507edef2985f8eba5b12
            key_buffer_size=8388608
            read_buffer_size=65536
            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 = 21047179 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]

            server.dll!sp_2048_mont_reduce_32()[sp_x86_64_asm.asm:12369]

            The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
            information that should help you find out what is causing the crash.
            Writing a core file at C:\ProgramData\MySQL\MariaDB 10\data
            Minidump written to C:\ProgramData\MySQL\MariaDB 10\data\mysqld.dmp

            11.3.2 runs fine and doesn't exhibit any weird behavior, however if I revert to a version in the 10.x.x branch then MariaDB complains about INNODB.

            2024-06-24 21:40:41 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 15172
            2024-06-24 21:40:41 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
            2024-06-24 21:40:41 0 [Note] InnoDB: Number of transaction pools: 1
            2024-06-24 21:40:41 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
            2024-06-24 21:40:41 0 [Note] InnoDB: Initializing buffer pool, total size = 1.000GiB, chunk size = 16.000MiB
            2024-06-24 21:40:42 0 [Note] InnoDB: Completed initialization of buffer pool
            2024-06-24 21:40:42 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
            2024-06-24 21:40:42 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=11391023341
            2024-06-24 21:40:42 0 [Note] InnoDB: End of log at LSN=11391041790
            2024-06-24 21:40:42 0 [ERROR] InnoDB: The change buffer is corrupted or has been removed on upgrade to MariaDB 11.0 or later
            2024-06-24 21:40:42 0 [Note] InnoDB: To recover: 6 pages
            2024-06-24 21:40:42 0 [Note] InnoDB: Reinitializing innodb_undo_tablespaces= 0 from 3
            2024-06-24 21:40:42 0 [Note] InnoDB: 128 rollback segments are active.
            2024-06-24 21:40:42 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
            2024-06-24 21:40:42 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
            2024-06-24 21:40:42 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
            2024-06-24 21:40:42 0 [Note] InnoDB: log sequence number 11391041790; transaction id 4569019
            2024-06-24 21:40:42 0 [Note] Plugin 'FEEDBACK' is disabled.
            2024-06-24 21:40:42 0 [Note] InnoDB: Loading buffer pool(s) from C:\ProgramData\MySQL\MariaDB 10\data\ib_buffer_pool
            2024-06-24 21:40:42 0 [Note] mysqld.exe: SSPI: using principal name 'COMPUTER$@xxxx', mech 'Negotiate'
            2024-06-24 21:40:42 0 [Note] CONNECT: Version 1.07.0002 Aug 11 2023 10:27:06
            2024-06-24 21:40:42 0 [Note] Server socket created on IP: '192.168.0.42'.
            2024-06-24 21:40:42 0 [Note] C:\Program Files\MariaDB 10.11\bin\mysqld.exe: ready for connections.
            Version: '10.11.5-MariaDB-log' socket: '' port: 3306 mariadb.org binary distribution
            2024-06-24 21:40:51 0 [Note] InnoDB: Buffer pool(s) load completed at 240624 21:40:51
            2024-06-24 21:46:42 0 [Note] Starting MariaDB 11.4.2-MariaDB-log source revision 3fca5ed772fb75e3e57c507edef2985f8eba5b12 as process 14940
            2024-06-24 21:46:42 0 [ERROR] InnoDB: The data file './ibdata1' must be writable
            2024-06-24 21:46:42 0 [ERROR] InnoDB: The data file './ibdata1' must be writable
            2024-06-24 21:46:42 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
            2024-06-24 21:46:42 0 [Note] Plugin 'FEEDBACK' is disabled.
            2024-06-24 21:46:42 0 [Note] mysqld.exe: SSPI: using principal name 'Administrator@xxx', mech 'Negotiate'
            2024-06-24 21:46:42 0 [Note] CONNECT: Version 1.07.0002 May 26 2024 21:26:37
            2024-06-24 21:46:42 0 [ERROR] Unknown/unsupported storage engine: INNODB
            2024-06-24 21:46:42 0 [ERROR] Aborting
            2024-06-24 21:46:54 0 [Note] Windows service "MYSQL_MARIADB": received SERVICE_CONTROL_STOP
            2024-06-24 21:46:54 0 [Note] C:\Program Files\MariaDB 10.11\bin\mysqld.exe (initiated by: unknown): Normal shutdown
            2024-06-24 21:46:54 0 [Note] InnoDB: FTS optimize thread exiting.
            2024-06-24 21:46:54 0 [Note] InnoDB: Starting shutdown...
            2024-06-24 21:46:54 0 [Note] InnoDB: Dumping buffer pool(s) to C:\ProgramData\MySQL\MariaDB 10\data\ib_buffer_pool
            2024-06-24 21:46:54 0 [Note] InnoDB: Restricted to 16224 pages due to innodb_buf_pool_dump_pct=25
            2024-06-24 21:46:54 0 [Note] InnoDB: Buffer pool(s) dump completed at 240624 21:46:54
            2024-06-24 21:46:55 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
            2024-06-24 21:46:55 0 [Note] InnoDB: Shutdown completed; log sequence number 11391058049; transaction id 4572128
            2024-06-24 21:46:55 0 [Note] C:\Program Files\MariaDB 10.11\bin\mysqld.exe: Shutdown complete

            infinitevs Static Dream added a comment - - edited I can confirm that I also experience the same behavior with 11.4.2 on windows server 2022, running on a VM inside proxmox. This vm was moved from a real machine and that machine was running a amd phenom II 4 core cpu, and had dd3 ram. (Please let me know if you need further information and I will be happy to provide.) 2024-06-24 22:10:14 0 [Note] Starting MariaDB 11.4.2-MariaDB-log source revision 3fca5ed772fb75e3e57c507edef2985f8eba5b12 as process 5624 2024-06-24 22:10:14 0 [Note] InnoDB: Compressed tables use zlib 1.3.1 2024-06-24 22:10:14 0 [Note] InnoDB: Number of transaction pools: 1 2024-06-24 22:10:15 0 [Note] InnoDB: Using SSE4.2 crc32 instructions 2024-06-24 22:10:15 0 [Note] InnoDB: Initializing buffer pool, total size = 1.000GiB, chunk size = 16.000MiB 2024-06-24 22:10:15 0 [Note] InnoDB: Completed initialization of buffer pool 2024-06-24 22:10:15 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2024-06-24 22:10:15 0 [Note] InnoDB: Resetting space id's in the doublewrite buffer 2024-06-24 22:10:15 0 [Note] InnoDB: End of log at LSN=11391160912 2024-06-24 22:10:15 0 [Note] InnoDB: Opened 3 undo tablespaces 2024-06-24 22:10:15 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active. 2024-06-24 22:10:15 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-06-24 22:10:15 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-06-24 22:10:15 0 [Note] InnoDB: log sequence number 11391160912; transaction id 4569019 2024-06-24 22:10:15 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-06-24 22:10:15 0 [Note] InnoDB: Loading buffer pool(s) from C:\ProgramData\MySQL\MariaDB 10\data\ib_buffer_pool 2024-06-24 22:10:15 0 [Note] mysqld.exe: SSPI: using principal name 'Administrator@XXXX, mech 'Negotiate' 240624 22:10:15 [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-log source revision: 3fca5ed772fb75e3e57c507edef2985f8eba5b12 key_buffer_size=8388608 read_buffer_size=65536 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 = 21047179 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] server.dll!sp_2048_mont_reduce_32() [sp_x86_64_asm.asm:12369] The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains information that should help you find out what is causing the crash. Writing a core file at C:\ProgramData\MySQL\MariaDB 10\data Minidump written to C:\ProgramData\MySQL\MariaDB 10\data\mysqld.dmp 11.3.2 runs fine and doesn't exhibit any weird behavior, however if I revert to a version in the 10.x.x branch then MariaDB complains about INNODB. 2024-06-24 21:40:41 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 15172 2024-06-24 21:40:41 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 2024-06-24 21:40:41 0 [Note] InnoDB: Number of transaction pools: 1 2024-06-24 21:40:41 0 [Note] InnoDB: Using SSE4.2 crc32 instructions 2024-06-24 21:40:41 0 [Note] InnoDB: Initializing buffer pool, total size = 1.000GiB, chunk size = 16.000MiB 2024-06-24 21:40:42 0 [Note] InnoDB: Completed initialization of buffer pool 2024-06-24 21:40:42 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2024-06-24 21:40:42 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=11391023341 2024-06-24 21:40:42 0 [Note] InnoDB: End of log at LSN=11391041790 2024-06-24 21:40:42 0 [ERROR] InnoDB: The change buffer is corrupted or has been removed on upgrade to MariaDB 11.0 or later 2024-06-24 21:40:42 0 [Note] InnoDB: To recover: 6 pages 2024-06-24 21:40:42 0 [Note] InnoDB: Reinitializing innodb_undo_tablespaces= 0 from 3 2024-06-24 21:40:42 0 [Note] InnoDB: 128 rollback segments are active. 2024-06-24 21:40:42 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-06-24 21:40:42 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-06-24 21:40:42 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-06-24 21:40:42 0 [Note] InnoDB: log sequence number 11391041790; transaction id 4569019 2024-06-24 21:40:42 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-06-24 21:40:42 0 [Note] InnoDB: Loading buffer pool(s) from C:\ProgramData\MySQL\MariaDB 10\data\ib_buffer_pool 2024-06-24 21:40:42 0 [Note] mysqld.exe: SSPI: using principal name 'COMPUTER$@xxxx', mech 'Negotiate' 2024-06-24 21:40:42 0 [Note] CONNECT: Version 1.07.0002 Aug 11 2023 10:27:06 2024-06-24 21:40:42 0 [Note] Server socket created on IP: '192.168.0.42'. 2024-06-24 21:40:42 0 [Note] C:\Program Files\MariaDB 10.11\bin\mysqld.exe: ready for connections. Version: '10.11.5-MariaDB-log' socket: '' port: 3306 mariadb.org binary distribution 2024-06-24 21:40:51 0 [Note] InnoDB: Buffer pool(s) load completed at 240624 21:40:51 2024-06-24 21:46:42 0 [Note] Starting MariaDB 11.4.2-MariaDB-log source revision 3fca5ed772fb75e3e57c507edef2985f8eba5b12 as process 14940 2024-06-24 21:46:42 0 [ERROR] InnoDB: The data file './ibdata1' must be writable 2024-06-24 21:46:42 0 [ERROR] InnoDB: The data file './ibdata1' must be writable 2024-06-24 21:46:42 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2024-06-24 21:46:42 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-06-24 21:46:42 0 [Note] mysqld.exe: SSPI: using principal name 'Administrator@xxx', mech 'Negotiate' 2024-06-24 21:46:42 0 [Note] CONNECT: Version 1.07.0002 May 26 2024 21:26:37 2024-06-24 21:46:42 0 [ERROR] Unknown/unsupported storage engine: INNODB 2024-06-24 21:46:42 0 [ERROR] Aborting 2024-06-24 21:46:54 0 [Note] Windows service "MYSQL_MARIADB": received SERVICE_CONTROL_STOP 2024-06-24 21:46:54 0 [Note] C:\Program Files\MariaDB 10.11\bin\mysqld.exe (initiated by: unknown): Normal shutdown 2024-06-24 21:46:54 0 [Note] InnoDB: FTS optimize thread exiting. 2024-06-24 21:46:54 0 [Note] InnoDB: Starting shutdown... 2024-06-24 21:46:54 0 [Note] InnoDB: Dumping buffer pool(s) to C:\ProgramData\MySQL\MariaDB 10\data\ib_buffer_pool 2024-06-24 21:46:54 0 [Note] InnoDB: Restricted to 16224 pages due to innodb_buf_pool_dump_pct=25 2024-06-24 21:46:54 0 [Note] InnoDB: Buffer pool(s) dump completed at 240624 21:46:54 2024-06-24 21:46:55 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-06-24 21:46:55 0 [Note] InnoDB: Shutdown completed; log sequence number 11391058049; transaction id 4572128 2024-06-24 21:46:55 0 [Note] C:\Program Files\MariaDB 10.11\bin\mysqld.exe: Shutdown complete
            wlad Vladislav Vaintroub added a comment - - edited

            infinitevs, the cause is already identified, and reported to developers of WolfSSL in https://github.com/wolfSSL/wolfssl/issues/7663, who have a tentative fix, but the fix needs to be confirmed by someone who runs hardware that does not have AVX instruction set. Neither WolfSSL people, nor we have spare Pentiums, Celerons or Phenoms.

            But since you have it , could you please unpack the attached [^wolfssl-test.zip] , and run test program on the machine in question? It is a testing for a fix, and unfortunately original reporter kenydinh did not get to do it so far. See my previous comment.

            wlad Vladislav Vaintroub added a comment - - edited infinitevs , the cause is already identified, and reported to developers of WolfSSL in https://github.com/wolfSSL/wolfssl/issues/7663 , who have a tentative fix, but the fix needs to be confirmed by someone who runs hardware that does not have AVX instruction set. Neither WolfSSL people, nor we have spare Pentiums, Celerons or Phenoms. But since you have it , could you please unpack the attached [^wolfssl-test.zip] , and run test program on the machine in question? It is a testing for a fix, and unfortunately original reporter kenydinh did not get to do it so far. See my previous comment.
            wlad Vladislav Vaintroub made changes -
            Attachment wolfssl-test.zip [ 73683 ]
            wlad Vladislav Vaintroub added a comment - - edited

            kenydinh, infinitevs, I realized that Windows misdetects the attachment as containing a virus. So sorry, I removed it now.

            Good news, I can reproduce it on a virtual box, on my normal workstation, on a new Windows 10 guest . vbox disables AVX/AVX2 even if supported on the host processor, aparently this is some interaction with other virtualization/hypervisor features, and for me likely WSL-related "virtualization platform". I do not know what causes it, but I do not need any more feedback from others.

            Bad news, the patch by wolfssl folks does not seem to be sufficient, it still throws illegal instruction, apparently on the same line.

            wlad Vladislav Vaintroub added a comment - - edited kenydinh , infinitevs , I realized that Windows misdetects the attachment as containing a virus. So sorry, I removed it now. Good news, I can reproduce it on a virtual box, on my normal workstation, on a new Windows 10 guest . vbox disables AVX/AVX2 even if supported on the host processor, aparently this is some interaction with other virtualization/hypervisor features, and for me likely WSL-related "virtualization platform". I do not know what causes it, but I do not need any more feedback from others. Bad news, the patch by wolfssl folks does not seem to be sufficient, it still throws illegal instruction, apparently on the same line.
            wlad Vladislav Vaintroub added a comment -

            Reproducible on VBox on fresh Windows 10 install, on my machine

            wlad Vladislav Vaintroub added a comment - Reproducible on VBox on fresh Windows 10 install, on my machine
            wlad Vladislav Vaintroub made changes -
            Status Needs Feedback [ 10501 ] Open [ 1 ]
            wlad Vladislav Vaintroub added a comment -

            Fixed with new WolfSSL 5.7.2

            wlad Vladislav Vaintroub added a comment - Fixed with new WolfSSL 5.7.2
            wlad Vladislav Vaintroub made changes -
            Fix Version/s 10.5.26 [ 29832 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            JIraAutomate JiraAutomate made changes -
            Fix Version/s 10.6.19 [ 29833 ]
            Fix Version/s 10.11.9 [ 29834 ]
            Fix Version/s 11.1.6 [ 29835 ]
            Fix Version/s 11.2.5 [ 29836 ]
            Fix Version/s 11.4.3 [ 29837 ]
            wlad Vladislav Vaintroub made changes -

            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.