From: Jens Axboe <axboe@kernel.dk>
To: torvic9@mailbox.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"paolo.valente@linaro.org" <paolo.valente@linaro.org>,
"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 09:02:28 -0600 [thread overview]
Message-ID: <2abec603-cad9-d87e-356c-9fe49dbbb3a3@kernel.dk> (raw)
In-Reply-To: <1889051823.161943.1633100469857@office.mailbox.org>
On 10/1/21 9:01 AM, torvic9@mailbox.org wrote:
>> 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.
It's known buggy, and a revert has been queued up since earlier this
week. It'll go to Linus for 5.15-rc4, and will hit 5.14 stable shortly
thereafter.
--
Jens Axboe
next prev parent reply other threads:[~2021-10-01 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 7:44 [BUG] kernel BUG at mm/slub.c - possible BFQ issue? torvic9
2021-10-01 15:01 ` torvic9
2021-10-01 15:02 ` Jens Axboe [this message]
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=2abec603-cad9-d87e-356c-9fe49dbbb3a3@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=torvic9@mailbox.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 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.