From: Qian Cai <cai@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: Jens Axboe <axboe@kernel.dk>,
Matthew Wilcox <willy@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: kernel BUG at mm/page-writeback.c:2241 [ BUG_ON(PageWriteback(page); ]
Date: Wed, 04 Nov 2020 10:40:03 -0500 [thread overview]
Message-ID: <37abe67a5a7d83b361932464b4af499fdeaf5ef7.camel@redhat.com> (raw)
In-Reply-To: <20201104151605.GG5600@quack2.suse.cz>
On Wed, 2020-11-04 at 16:16 +0100, Jan Kara wrote:
> On Mon 26-10-20 10:26:26, Qian Cai wrote:
> > On Mon, 2020-10-26 at 07:55 -0600, Jens Axboe wrote:
> > > I've tried to reproduce this as well, to no avail. Qian, could you perhaps
> > > detail the setup? What kind of storage, kernel config, compiler, etc.
> > >
> >
> > So far I have only been able to reproduce on this Intel platform:
> >
> > HPE DL560 gen10
> > Intel(R) Xeon(R) Gold 6154 CPU @ 3.00GHz
> > 131072 MB memory, 1000 GB disk space (smartpqi nvme)
>
> Did you try running with the debug patch Matthew sent? Any results?
Running every day, but no luck so far.
next prev parent reply other threads:[~2020-11-04 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 0:30 kernel BUG at mm/page-writeback.c:2241 [ BUG_ON(PageWriteback(page); ] Qian Cai
2020-10-22 0:49 ` Matthew Wilcox
2020-10-22 13:23 ` William Kucharski
2020-10-22 16:46 ` Matthew Wilcox
2020-10-22 15:35 ` Qian Cai
2020-10-22 17:12 ` Matthew Wilcox
2020-10-30 12:08 ` Qian Cai
2020-10-26 9:49 ` Jan Kara
2020-10-26 13:13 ` Matthew Wilcox
2020-10-26 13:55 ` Jens Axboe
2020-10-26 14:26 ` Qian Cai
2020-11-04 15:16 ` Jan Kara
2020-11-04 15:40 ` Qian Cai [this message]
2020-10-26 14:51 ` Qian Cai
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=37abe67a5a7d83b361932464b4af499fdeaf5ef7.camel@redhat.com \
--to=cai@redhat.com \
--cc=axboe@kernel.dk \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).