From: torvic9@mailbox.org
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"paolo.valente@linaro.org" <paolo.valente@linaro.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [BUG] kernel BUG at mm/slub.c - possible BFQ issue?
Date: Fri, 1 Oct 2021 17:01:09 +0200 (CEST) [thread overview]
Message-ID: <1889051823.161943.1633100469857@office.mailbox.org> (raw)
In-Reply-To: <1624640454.149631.1632987871186@office.mailbox.org>
> torvic9@mailbox.org hat am 30.09.2021 09:44 geschrieben:
>
>
> Hello,
>
> I encounter a hard freeze on both 5.14 and 5.15 when using BFQ.
> Unfortunately, I do not have a full error log, because the computer
> totally freezes and slightly corrupts the display, so it's
> impossible to read the entire message.
>
> However, what I could get is the following:
>
> kernel BUG at mm/slub.c:379
> invalid opcode: 0000 [#1]
> RIP: 0010:__slab_free
> [...]
> Call Trace:
> bfq_set_next_ioprio_data
> [...]
> bfq_put_queue
> bfq_insert_requests
> [...]
>
> This issue appears more or less randomly and it sometimes takes a
> little while to reproduce it (running fio helps).
> The call trace always contains references to BFQ, but they are not
> always the exact same. Once, I could see on the corrupted display
> the message "general protection fault".
> I could reproduce this issue on two computers.
>
> Not quite sure but I *think* the issue first appeared somewhere around
> 5.14.5 or 5.14.6, during which time BFQ only got the following commit:
>
> (88013a0c5d99) block, bfq: honor already-setup queue merges
I have now reverted the above commit and launched some heavy I/O like
e.g. git kernel, fio, xz compression, and so far, no freezes anymore!
Too early to say that this commit really is the cause though.
Would be great if someone could have a look at it.
>
> 5.13 doesn't seem to be affected AFAICS.
>
> Does anyone have an idea what is going on?
> I will now revert the above commit and see if that helps...
>
> Thanks,
> Tor
next prev parent reply other threads:[~2021-10-01 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 7:44 torvic9
2021-10-01 15:01 ` torvic9 [this message]
2021-10-01 15:02 ` Jens Axboe
2021-10-05 15:06 ` Paolo Valente
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=1889051823.161943.1633100469857@office.mailbox.org \
--to=torvic9@mailbox.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®