Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Zhang <yi.zhang@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: regression from 5.10.0-rc3: BUG: Bad page state in process kworker/41:0 pfn:891066 during fio on devdax
Date: Mon, 9 Nov 2020 11:13:02 +0800	[thread overview]
Message-ID: <1bac0f55-367c-d2d5-7847-54b9a47ea525@redhat.com> (raw)
In-Reply-To: <CAPcyv4jto-LCR6EUZj0bka8De9NTwB5OkYLbK83O5hubGfknPQ@mail.gmail.com>



On 11/9/20 11:00 AM, Dan Williams wrote:
> On Sun, Nov 8, 2020 at 6:38 PM Yi Zhang <yi.zhang@redhat.com> wrote:
>> Hello
>>
>> I found this regression during devdax fio test on 5.10.0-rc3, could anyone help check it, thanks.
> Have you been able to bisect it?
>
Yeah, the bisect is WIP, will update it later. :)
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org

  reply	other threads:[~2020-11-09  3:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1934921834.1085815.1604889035798.JavaMail.zimbra@redhat.com>
2020-11-09  2:38 ` regression from 5.10.0-rc3: BUG: Bad page state in process kworker/41:0 pfn:891066 during fio on devdax Yi Zhang
2020-11-09  3:00   ` Dan Williams
2020-11-09  3:13     ` Yi Zhang [this message]
2020-11-09 12:11   ` Yi Zhang
     [not found]     ` <20201109141216.GD244516@ziepe.ca>
2020-11-09 17:26       ` Dan Williams
     [not found]         ` <20201109175442.GE244516@ziepe.ca>
2020-11-10  0:36           ` Jason Gunthorpe
2020-11-10  7:36             ` Yi Zhang
2020-11-10 16:51               ` Yi Zhang
2020-11-11  3:44                 ` Yi Zhang
2020-11-18 14:02                   ` Yi Zhang
2020-12-01  1:36                 ` Dan Williams

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=1bac0f55-367c-d2d5-7847-54b9a47ea525@redhat.com \
    --to=yi.zhang@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-nvdimm@lists.01.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