linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qian Cai <cai@redhat.com>
To: Jens Axboe <axboe@kernel.dk>,
	Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>
Cc: 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: Mon, 26 Oct 2020 10:26:26 -0400	[thread overview]
Message-ID: <aa3dfe1f9705f02197f9a75b60d4c28cc97ddff4.camel@redhat.com> (raw)
In-Reply-To: <d06d3d2a-7032-91da-35fa-a9dee4440a14@kernel.dk>

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)

It was running some CPU and memory hotplug, KVM and then LTP workloads
(syscalls, mm, and fs). Finally, it was always this LTP test case to trigger it:

# export LTPROOT; rwtest -N iogen01 -i 120s -s read,write -Da -Dv -n 2 500b:$TMPDIR/doio.f1.$$ 1000b:$TMPDIR/doio.f2.$$
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/fs/doio/rwtest

gcc-8.3.1-5.1.el8.x86_64
.config: https://git.code.tencent.com/cail/linux-mm/blob/master/x86.config


== storage information == 
[   46.131150] smartpqi 0000:23:00.0: Online Firmware Activation enabled
[   46.138495] smartpqi 0000:23:00.0: Serial Management Protocol enabled
[   46.145701] smartpqi 0000:23:00.0: New Soft Reset Handshake enabled
[   46.152705] smartpqi 0000:23:00.0: RAID IU Timeout enabled
[   46.158934] smartpqi 0000:23:00.0: TMF IU Timeout enabled
[   46.168740] scsi host0: smartpqi
[   47.750425] nvme nvme1: 31/0/0 default/read/poll queues
[   47.826211] scsi 0:0:0:0: Direct-Access     ATA      MM1000GEFQV      HPG8 PQ: 0 ANSI: 6
[   47.841752] smartpqi 0000:23:00.0: added 0:0:0:0 0000000000000000 Direct-Access     ATA      MM1000GEFQV      AIO+ qd=32    
[   47.941249]  nvme1n1: p1
[   47.943078] scsi 0:0:1:0: Enclosure         HPE      Smart Adapter    2.62 PQ: 0 ANSI: 5
[   47.958506] smartpqi 0000:23:00.0: added 0:0:1:0 51402ec001f36448 Enclosure         HPE      Smart Adapter    AIO-
[   47.962844] nvme nvme0: 31/0/0 default/read/poll queues
[   48.015511] scsi 0:2:0:0: RAID              HPE      P408i-a SR Gen10 2.62 PQ: 0 ANSI: 5
[   48.029736] smartpqi 0000:23:00.0: added 0:2:0:0 0000000000000000 RAID              HPE      P408i-a SR Gen10 
[   48.042711] smartpqi 0000:4e:00.0: Microsemi Smart Family Controller found
[   48.149820]  nvme0n1: p1
[   48.956194] smartpqi 0000:4e:00.0: Online Firmware Activation enabled
[   48.963399] smartpqi 0000:4e:00.0: Serial Management Protocol enabled
[   48.970625] smartpqi 0000:4e:00.0: New Soft Reset Handshake enabled
[   48.977645] smartpqi 0000:4e:00.0: RAID IU Timeout enabled
[   48.983873] smartpqi 0000:4e:00.0: TMF IU Timeout enabled
[   48.994687] scsi host1: smartpqi
[   50.612955] scsi 1:0:0:0: Enclosure         HPE      Smart Adapter    2.62 PQ: 0 ANSI: 5
[   50.628219] smartpqi 0000:4e:00.0: added 1:0:0:0 51402ec01040ffc8 Enclosure         HPE      Smart Adapter    AIO-
[   50.681859] scsi 1:2:0:0: RAID              HPE      E208i-p SR Gen10 2.62 PQ: 0 ANSI: 5
[   50.695843] smartpqi 0000:4e:00.0: added 1:2:0:0 0000000000000000 RAID              HPE      E208i-p SR Gen10 
[   50.856683] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[   50.865195] sd 0:0:0:0: [sda] 4096-byte physical blocks
[   50.871354] sd 0:0:0:0: [sda] Write Protect is off
[   50.876956] sd 0:0:0:0: [sda] Mode Sense: 46 00 10 08
[   50.877299] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, supports DPO and FUA
[   50.898824]  sda: sda1 sda2 sda3
[   50.943835] sd 0:0:0:0: [sda] Attached SCSI disk


  reply	other threads:[~2020-10-26 14:26 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 [this message]
2020-11-04 15:16           ` Jan Kara
2020-11-04 15:40             ` Qian Cai
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=aa3dfe1f9705f02197f9a75b60d4c28cc97ddff4.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).