From: Marco Rebhan <me@dblsaiko.net>
To: colyli@suse.de
Cc: linux-bcache@vger.kernel.org, victor@westerhu.is
Subject: Re: Kernel Oops: kernel BUG at block/bio.c:52
Date: Tue, 27 Apr 2021 20:57:07 +0200 [thread overview]
Message-ID: <5607192.MhkbZ0Pkbq@invader> (raw)
In-Reply-To: <210bc2f6-32c6-be3e-1c9a-40f635ba4580@suse.de>
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
Hi,
I'm getting the same issue on kernel 5.12.0 after upgrading from
5.11.16. For me, so far the error always occurs a short while after
boot.
> Could you please help to apply a debug patch and gather some debug
> information when it reproduces ?
I could do that as well, which patch should I apply?
Thanks,
Marco
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-27 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 14:54 Kernel Oops: kernel BUG at block/bio.c:52 Victor Westerhuis
2021-04-20 16:14 ` Coly Li
2021-04-27 18:57 ` Marco Rebhan [this message]
2021-05-06 2:50 ` Coly Li
2021-05-06 7:36 ` Marco Rebhan
2021-05-06 10:04 ` Coly Li
2021-05-06 15:46 ` Marco Rebhan
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=5607192.MhkbZ0Pkbq@invader \
--to=me@dblsaiko.net \
--cc=colyli@suse.de \
--cc=linux-bcache@vger.kernel.org \
--cc=victor@westerhu.is \
/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;
as well as URLs for NNTP newsgroup(s).