linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Coly Li <colyli@suse.de>
To: Rolf Fokkens <rolf@rolffokkens.nl>
Cc: linux-bcache@vger.kernel.org, Thorsten Knabe <linux@thorsten-knabe.de>
Subject: Re: PROBLEM: bcache related kernel BUG() since Linux 5.12
Date: Fri, 4 Jun 2021 18:35:23 +0800	[thread overview]
Message-ID: <709c9a11-686d-9b82-b016-e65fdca41f01@suse.de> (raw)
In-Reply-To: <5df1c881-02e9-f951-5dbd-016a390d8d54@rolffokkens.nl>

On 6/4/21 5:07 PM, Rolf Fokkens wrote:
> Hi Coly, Thorsten,
>
> I survived 48 hours perfectly:
>
> bash-5.0$ uptime
>  10:45:53 up 2 days, 11:05,  1 user,  load average: 2.82, 3.45, 2.67
> bash-5.0$ cat /proc/version
> Linux version 5.12.8-200.rf.fc33.x86_64
> (mockbuild@tb-sandbox-mjolnir.local.tbai.nl) (gcc (GCC) 10.3.1 20210422
> (Red Hat 10.3.1-1), GNU ld version 2.35-18.fc33) #1 SMP Tue Jun 1
> 23:10:39 CEST 2021
> bash-5.0$
>
> Furthermore there are no concerning messages in the syslog.

Hi Rolf,

Thanks for your update. Which kind of applications/workload are running
in the past 2 days ?

Coly Li

  reply	other threads:[~2021-06-04 10:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 19:06 PROBLEM: bcache related kernel BUG() since Linux 5.12 Thorsten Knabe
2021-05-16  8:42 ` Matthias Ferdinand
2021-05-16 14:43   ` Coly Li
2021-05-31  9:37 ` Rolf Fokkens
2021-06-01 15:34   ` Coly Li
2021-06-01 21:04     ` Rolf Fokkens
2021-06-01 21:46       ` Rolf Fokkens
2021-06-02  8:33     ` Thorsten Knabe
2021-06-02  9:45       ` Rolf Fokkens
2021-06-02 11:08         ` Coly Li
2021-06-04  9:07           ` Rolf Fokkens
2021-06-04 10:35             ` Coly Li [this message]
2021-06-04 12:06               ` Thorsten Knabe
2021-06-05 15:20                 ` Coly Li
     [not found]               ` <ec9f73fa-a16c-b0c1-d1f8-2bf4e585be5f@rolffokkens.nl>
2021-06-07 10:11                 ` Coly Li

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=709c9a11-686d-9b82-b016-e65fdca41f01@suse.de \
    --to=colyli@suse.de \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux@thorsten-knabe.de \
    --cc=rolf@rolffokkens.nl \
    /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).