[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CH2PR19MB4024BF1FB16E9FF9D00058CAA0839@CH2PR19MB4024.namprd19.prod.outlook.com>
Date: Mon, 25 Oct 2021 09:02:52 +0000
From: Li Chen <lchen@...arella.com>
To: "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
CC: Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Rob Herring <robh@...nel.org>, "kw@...ux.com" <kw@...ux.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: nvme may get timeout from dd when using different non-prefetch
mmio outbound/ranges
> [ 81.634065][ T7] nvme nvme0: Shutdown timeout set to 8 seconds
> [ 81.674332][ T7] nvme nvme0: 1/0/0 default/read/poll queues
> [ 112.168136][ T256] nvme nvme0: I/O 12 QID 1 timeout, disable controller
I/O 12 QID 1 is nvme_cmd_write, reproduce after rebooting and using ftrace:
# dmesg | grep QID
[ 99.456260] nvme nvme0: I/O 128 QID 1 timeout, disable controller
# grep "qid=1" /sys/kernel/tracing/trace | egrep "cmdid=128\b"
kworker/0:1H-65 [000] .... 68.987492: nvme_setup_cmd: nvme0: disk=nvme0n1, qid=1, cmdid=128, nsid=1, flags=0x0, meta=0x0, cmd=(nvme_cmd_write slba=216856, len=1015, ctrl=0x0, dsmgmt=0, reftag=0)
<idle>-0 [001] ..s1 99.475164: nvme_complete_rq: nvme0: disk=nvme0n1, qid=1, cmdid=128, res=0x0, retries=1, flags=0x1, status=0x371
Regards,
Li
**********************************************************************
This email and attachments contain Ambarella Proprietary and/or Confidential Information and is intended solely for the use of the individual(s) to whom it is addressed. Any unauthorized review, use, disclosure, distribute, copy, or print is prohibited. If you are not an intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you.
Powered by blists - more mailing lists