From: Vicente Bergas <vicencb@gmail.com>
To: Coly Li <colyli@suse.de>, Ming Lei <ming.lei@redhat.com>,
Hannes Reinecke <hare@suse.de>,
Jack Wang <jinpu.wang@cloud.ionos.com>,
Jens Axboe <axboe@kernel.dk>
Cc: Bart Van Assche <bvanassche@acm.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Evan Green <evgreen@chromium.org>,
linux-block@vger.kernel.org, linux-rockchip@lists.infradead.org,
Xiao Ni <xni@redhat.com>, Enzo Matsumiya <ematsumiya@suse.com>,
Christoph Hellwig <hch@lst.de>
Subject: [BUG] discard_granularity is 0 on rk3399-gru-kevin
Date: Sun, 27 Sep 2020 22:29:14 +0200 [thread overview]
Message-ID: <2438c500-eb41-4ae2-b890-83d287ad3bcd@gmail.com> (raw)
Hi,
since recently the rk3399-gru-kevin is reporting the trace below.
The issue has been uncovered by
b35fd7422c2f8e04496f5a770bd4e1a205414b3f
block: check queue's limits.discard_granularity in
__blkdev_issue_discard()
Regards,
Vicente.
WARNING: CPU: 0 PID: 135 at __blkdev_issue_discard+0x200/0x294
CPU: 0 PID: 135 Comm: f2fs_discard-17 Not tainted 5.9.0-rc6 #1
Hardware name: Google Kevin (DT)
pstate: 00000005 (nzcv daif -PAN -UAO BTYPE=--)
pc : __blkdev_issue_discard+0x200/0x294
lr : __blkdev_issue_discard+0x54/0x294
sp : ffff800011dd3b10
x29: ffff800011dd3b10 x28: 0000000000000000
x27: ffff800011dd3cc4 x26: ffff800011dd3e18
x25: 000000000004e69b x24: 0000000000000c40
x23: ffff0000f1deaaf0 x22: ffff0000f2849200
x21: 00000000002734d8 x20: 0000000000000008
x19: 0000000000000000 x18: 0000000000000000
x17: 0000000000000000 x16: 0000000000000000
x15: 0000000000000000 x14: 0000000000000394
x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000000 x10: 00000000000008b0
x9 : ffff800011dd3cb0 x8 : 000000000004e69b
x7 : 0000000000000000 x6 : ffff0000f1926400
x5 : ffff0000f1940800 x4 : 0000000000000000
x3 : 0000000000000c40 x2 : 0000000000000008
x1 : 00000000002734d8 x0 : 0000000000000000
Call trace:
__blkdev_issue_discard+0x200/0x294
__submit_discard_cmd+0x128/0x374
__issue_discard_cmd_orderly+0x188/0x244
__issue_discard_cmd+0x2e8/0x33c
issue_discard_thread+0xe8/0x2f0
kthread+0x11c/0x120
ret_from_fork+0x10/0x1c
---[ end trace e4c8023d33dfe77a ]---
mmcblk1p2: Error: discard_granularity is 0.
mmcblk1p2: Error: discard_granularity is 0.
<last message repeated multiple times>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2020-09-27 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 20:29 Vicente Bergas [this message]
2020-09-28 3:15 ` [BUG] discard_granularity is 0 on rk3399-gru-kevin Coly Li
2020-09-28 5:02 ` Coly Li
2020-09-30 0:07 ` Vicente Bergas
2020-09-30 1:58 ` Coly Li
2020-09-30 10:48 ` Adrian Hunter
2020-09-30 11:06 ` 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=2438c500-eb41-4ae2-b890-83d287ad3bcd@gmail.com \
--to=vicencb@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=colyli@suse.de \
--cc=darrick.wong@oracle.com \
--cc=ematsumiya@suse.com \
--cc=evgreen@chromium.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=xni@redhat.com \
/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).