Bug#996951: linux-image-5.14.0-3-amd64: iouring looses requests
Control: tags -1 + moreinfo
On Thu, Oct 21, 2021 at 11:03:16PM +1100, Daniel Black wrote:
> retested 5.14.14. Sorry not fixed there yet. Guess this is going upstream.
>
> few other fixes to try:
> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/log/?h=io_uring-5.15
>
> $ uname -a
> Linux impish 5.14.14-051414-generic #202110201037 SMP Wed Oct 20
> 11:04:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>
> dan@impish:/usr/share/mysql/mysql-test$ ./mtr --vardir=/tmp/var
> --parallel=4 stress.ddl_innodb stress.ddl_innodb stress.ddl_innodb
> stress.ddl_innodb
> Logging: ./mtr --vardir=/tmp/var --parallel=4 stress.ddl_innodb
> stress.ddl_innodb stress.ddl_innodb stress.ddl_innodb
> vardir: /tmp/var
> Removing old var directory...
> Creating var directory '/tmp/var'...
> Checking supported features...
> MariaDB Version 10.6.5-MariaDB-1:10.6.5+maria~impish
> - SSL connections supported
> - binaries built with wsrep patch
> Collecting tests...
> Installing system database...
>
> ==============================================================================
>
> TEST WORKER RESULT TIME (ms) or COMMENT
> --------------------------------------------------------------------------
>
> worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
> worker[4] Using MTR_BUILD_THREAD 301, with reserved ports 16020..16039
> worker[3] Using MTR_BUILD_THREAD 302, with reserved ports 16040..16059
> worker[2] Using MTR_BUILD_THREAD 303, with reserved ports 16060..16079
> stress.ddl_innodb 'innodb' w4 [ pass ] 235134
> stress.ddl_innodb 'innodb' w1 [ pass ] 245906
> stress.ddl_innodb 'innodb' w3 [ pass ] 301078
> stress.ddl_innodb 'innodb' w2 [ fail ]
> Test ended at 2021-10-21 11:23:30
> ......
> Version: '10.6.5-MariaDB-1:10.6.5+maria~impish-log' socket:
> '/tmp/var/tmp/2/mysqld.1.sock' port: 16060 mariadb.org binary
> distribution
> 2021-10-21 11:09:42 0 [Note] InnoDB: Buffer pool(s) load completed at
> 211021 11:09:42
> 2021-10-21 11:23:27 0 [ERROR] [FATAL] InnoDB:
> innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch.
> Please refer to
> https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
> 211021 11:23:27 [ERROR] mysqld got signal 6 ;
So I guess this needs to go upstream, can you report it there, or have
you in meanwhile isolated the changes which makes the fix in 5.15-rc6?
Can you keep us in the loop about it?
Regards,
Salvatore
Reply to: