From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@meta.com>,
linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCH] nvme-pci: enhance timeout kernel log
Date: Thu, 7 Dec 2023 13:41:37 -0700 [thread overview]
Message-ID: <ZXIuAZ_mfnW6Ydhm@kbusch-mbp> (raw)
In-Reply-To: <d66d032f-e564-4a76-b9ce-cc09ab94188c@kernel.dk>
On Thu, Dec 07, 2023 at 01:38:04PM -0700, Jens Axboe wrote:
> On 12/7/23 11:32 AM, Keith Busch wrote:
> > From: Keith Busch <kbusch@kernel.org>
> >
> > Kernel configs don't necessarily have opcode decoding, and some opcodes
> > are not even decodable. It is still interesting for debugging SSD issues
> > to know what opcode is timing out, what request type it came from, and
> > the data size (if applicable).
> >
> > Signed-off-by: Keith Busch <kbusch@kernel.org>
> > ---
> > drivers/nvme/host/pci.c | 9 +++++----
> > 1 file changed, 5 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> > index fad4cccce745c..49771919b01f1 100644
> > --- a/drivers/nvme/host/pci.c
> > +++ b/drivers/nvme/host/pci.c
> > @@ -1284,6 +1284,7 @@ static enum blk_eh_timer_return nvme_timeout(struct request *req)
> > struct request *abort_req;
> > struct nvme_command cmd = { };
> > u32 csts = readl(dev->bar + NVME_REG_CSTS);
> > + u8 opcode;
> >
> > /* If PCI error recovery process is happening, we cannot reset or
> > * the recovery mechanism will surely fail.
> > @@ -1361,11 +1362,11 @@ static enum blk_eh_timer_return nvme_timeout(struct request *req)
> > cmd.abort.cid = nvme_cid(req);
> > cmd.abort.sqid = cpu_to_le16(nvmeq->qid);
> >
> > + opcode = nvme_req(req)->cmd->common.opcode,
> > dev_warn(nvmeq->dev->ctrl.device,
> > - "I/O %d (%s) QID %d timeout, aborting\n",
> > - req->tag,
> > - nvme_get_opcode_str(nvme_req(req)->cmd->common.opcode),
> > - nvmeq->qid);
> > + "I/O %d (%s %d) QID %d timeout, aborting req_op:%u size:%u\n",
> > + req->tag, nvme_get_opcode_str(opcode), opcode, nvmeq->qid,
> > + req_op(req), blk_rq_bytes(req));
>
> Your additions look good to me, but I do wish that we'd be equally
> verbose on what the other values are. Ala:
>
> I/O tag %d (opcode: %s %d) ...
>
> would be a lot more useful, for example. I find myself having to dig
> into the source for a specific kernel sometimes when looking at various
> nvme errors, which is really annoying.
That is annoying. I'll add your suggestion in.
next prev parent reply other threads:[~2023-12-07 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 18:32 [PATCH] nvme-pci: enhance timeout kernel log Keith Busch
2023-12-07 20:38 ` Jens Axboe
2023-12-07 20:41 ` Keith Busch [this message]
2023-12-07 20:47 ` Chaitanya Kulkarni
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=ZXIuAZ_mfnW6Ydhm@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@meta.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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