All of lore.kernel.org
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: Xan Charbonnet <xan@charbonnet.com>,
	1093243@bugs.debian.org, Jens Axboe <axboe@kernel.dk>
Cc: Bernhard Schmidt <berni@debian.org>,
	Pavel Begunkov <asml.silence@gmail.com>,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Bug#1093243: Upgrade to 6.1.123 kernel causes mariadb hangs
Date: Thu, 23 Jan 2025 21:49:06 +0100	[thread overview]
Message-ID: <Z5KrQktoX4f2ysXI@eldamar.lan> (raw)
In-Reply-To: <dde09d65-8912-47e4-a1bb-d198e0bf380b@charbonnet.com>

Hi Xan,

On Thu, Jan 23, 2025 at 02:31:34PM -0600, Xan Charbonnet wrote:
> I rented a Linode and have been trying to load it down with sysbench
> activity while doing a mariabackup and a mysqldump, also while spinning up
> the CPU with zstd benchmarks.  So far I've had no luck triggering the fault.
> 
> I've also been doing some kernel compilation.  I followed this guide:
> https://www.dwarmstrong.org/kernel/
> (except that I used make -j24 to build in parallel and used make
> localmodconfig to compile only the modules I need)
> 
> I've built the following kernels:
> 6.1.123 (equivalent to linux-image-6.1.0-29-amd64)
> 6.1.122
> 6.1.121
> 6.1.120
> 
> So far they have all exhibited the behavior.  Next up is 6.1.119 which is
> equivalent to linux-image-6.1.0-28-amd64.  My expectation is that the fault
> will not appear for this kernel.
> 
> It looks like the issue is here somewhere:
> https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.120
> 
> I have to work on some other things, and it'll take a while to prove the
> negative (that is, to know that the failure isn't happening).  I'll post
> back with the 6.1.119 results when I have them.

Additionally please try with 6.1.120 and revert this commit 

3ab9326f93ec ("io_uring: wake up optimisations")

(which landed in 6.1.120).

If that solves the problem maybe we miss some prequisites in the 6.1.y
series here?

Regards,
Salvatore

  parent reply	other threads:[~2025-01-23 20:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a2194f09-aea4-4f07-b23c-a64b3dbdce42@dfn.de>
     [not found] ` <Z4_wKuDhmbktlbF-@fliwatuet.svr02.mucip.net>
     [not found]   ` <173706089225.4380.9492796104667651797.reportbug@backup22.biblionix.com>
     [not found]     ` <Z5FLufDg65O1ZDiA@eldamar.lan>
2025-01-23 20:05       ` Bug#1093243: Upgrade to 6.1.123 kernel causes mariadb hangs Salvatore Bonaccorso
2025-01-23 20:26         ` Jens Axboe
     [not found]     ` <dde09d65-8912-47e4-a1bb-d198e0bf380b@charbonnet.com>
2025-01-23 20:49       ` Salvatore Bonaccorso [this message]
2025-01-23 23:20         ` Pavel Begunkov
2025-01-24  2:10           ` Xan Charbonnet
2025-01-24  5:24           ` Salvatore Bonaccorso
2025-01-24 10:33             ` Pavel Begunkov
2025-01-24 16:30               ` Xan Charbonnet
2025-01-24 18:40                 ` Pavel Begunkov
2025-01-24 20:33                   ` Salvatore Bonaccorso
2025-01-24 20:51                     ` Jens Axboe
2025-01-26 22:48                       ` Xan Charbonnet
2025-01-27 16:38                         ` Xan Charbonnet
2025-01-27 17:21                           ` Pavel Begunkov
2025-01-27 16:49                         ` Pavel Begunkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z5KrQktoX4f2ysXI@eldamar.lan \
    --to=carnil@debian.org \
    --cc=1093243@bugs.debian.org \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=berni@debian.org \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xan@charbonnet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.