Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
11.4.2
-
Window 10 Pro 22H2
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
Issue Links
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
MDEV-31856 use ephemeral ssl certificates
-
- Closed
-
- links to
Activity
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.
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.
Reproducible on VBox on fresh Windows 10 install, on my machine
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.)
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.