Since revering to linux-image-5.10.0-20 we've been free of the same errors.
On Tue, Feb 28, 2023 at 5:24 PM Diederik de Haas wrote:
>
> On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote:
> > Source: linux
> > Version: 5.10.0-21-powerpc64le
> > Severity: grave
> > Justification: causes non-serious data loss
> > X-Debbugs-
Source: linux
Version: 5.10.0-21-powerpc64le
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: dan...@mariadb.org
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you d
Rex has created a commit to try to identify the cause of the problem
in the main.order_by_innodb tests:
https://github.com/MariaDB/server/commit/a0300390b5efbd7b408cb166e0ee715364a85f3c
I don't know if salsa supports this, but a PR is
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_r
Some crashes in the signal handler are the just created "MDEV-30613
output_core_info crashes in my_read()" with a probable cause. Doesn't
help the original crash reason however.
A single thread backtrace isn't sufficient on errors like:
" InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded
They won't crash, because the CPU features are tested before any call
to the optimized code is made.
https://github.com/MariaDB/server/blob/10.6/mysys/crc32/crc32c.cc#L542-L564
As the Debian CI undoubtedly runs the basic unit tests that cover
crc32 on the minimum hardware, and succeeds, it proves
-- Forwarded message -
From: Daniel Black
Date: Thu, Dec 23, 2021 at 10:40 AM
Subject: Re: MariaDB 10.6 regressed ruby-mysql2
To: Otto Kekäläinen
Cc: , Tuukka Pasanen
, Faustin Lammler
expected Mysql2::Error with message matching /Lost connection to
MySQL server/, got
Marko tested this is fixed in linux-image-5.14.0-4-amd64 (5.14.16-1).
Thanks for the update.
https://jira.mariadb.org/browse/MDEV-26674?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=204907#comment-204907
https://marc.info/?l=linux-block&m=163489378723217&w=2
https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
211021 11:23:27 [ERROR] mysqld got signal 6 ;
On Thu, Oct 21, 2021 at 10:10 PM Diederik de Haas wrote:
>
> On Thursday, 21 October 2021 12:41:34 CEST Salvatore Bonaccorso wrote:
> > On Thu, Oct 21, 2021 at 09:38
Package: src:linux
Version: 5.14.12-1
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: dan...@mariadb.org
Dear Maintainer,
MariaDB has been investigating a 10.6+ related problem for a while
https://jira.mariadb.org/browse/MDEV-26674
https://jira.mariadb.org/browse/MDEV-26
As Thadeu Lima de Souza Cascardo said, the build time detected page size
isn't correct, perhaps using --with-lg-page=/--with-lg-page-sizes at
compile time.
This is available in the 3.6.0 version of jemalloc.
(upstream currently
at 4.4.0).
As an aside, I've got part way though an upstream patch t
As Thadeu Lima de Souza Cascardo said, the build time detected page size
isn't correct, perhaps using --with-lg-page=/--with-lg-page-sizes at
compile time.
This is available in the 3.6.0 version of jemalloc. (upstream currently
at 4.4.0). I've got part way though an upstream patch to change this t
Package: corosync
Version: 2.3.0-1
Severity: serious
Justification: fails to build from source
While doing a backport of corosync-2.3.0-1 to squeeze I it wouldn't build and
complained that dbus was missing.
It seems libdbus-1-dev was missing from the dependancy list.
-- System Information:
Debi
14 matches
Mail list logo
