From: Jens Axboe <axboe@kernel.dk>
To: kernel test robot <oliver.sang@intel.com>
Cc: lkp@lists.01.org, lkp@intel.com, linux-block@vger.kernel.org, hch@lst.de
Subject: Re: [nvme] f9c499bbbf: nvme nvme0: Identify Controller failed (16641)
Date: Wed, 3 Nov 2021 13:51:18 -0600 [thread overview]
Message-ID: <e6f09b9b-386a-8a26-7c4b-c528791f7c9a@kernel.dk> (raw)
In-Reply-To: <20211103141454.GA30634@xsang-OptiPlex-9020>
On 11/3/21 8:14 AM, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: f9c499bbbf603389abad60d1931c16b2f96dee06 ("[PATCH 1/2] nvme: move command clear into the various setup helpers")
> url: https://github.com/0day-ci/linux/commits/Jens-Axboe/nvme-move-command-clear-into-the-various-setup-helpers/20211018-214956
> base: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git 519d81956ee277b4419c723adfb154603c2565ba
> patch link: https://lore.kernel.org/linux-block/20211018124934.235658-2-axboe@kernel.dk
>
> in testcase: will-it-scale
> version: will-it-scale-x86_64-a34a85c-1_20211029
> with following parameters:
>
> nr_task: 50%
> mode: process
> test: readseek1
> cpufreq_governor: performance
> ucode: 0x700001e
>
> test-description: Will It Scale takes a testcase and runs it from 1 through to n parallel copies to see if the testcase will scale. It builds both a process and threads based test in order to see any differences between the two.
> test-url: https://github.com/antonblanchard/will-it-scale
>
>
> on test machine: 144 threads 4 sockets Intel(R) Xeon(R) Gold 5318H CPU @ 2.50GHz with 128G memory
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <oliver.sang@intel.com>
>
>
> [ 38.907274][ T868] nvme nvme0: pci function 0000:24:00.0
> [ 38.924627][ T1103] scsi host0: ahci
> 0m.
> [ 38.948010][ T773] nvme nvme0: Identify Controller failed (16641)
> [ 38.951220][ T1103] scsi host1: ahci
> [ 38.954193][ T773] nvme nvme0: Removing after probe failure status: -5
This is odd, looks like it's saying invalid opcode. Looking at the probe
path, it's pretty standard and the command passed in is cleared already.
So not quite sure why the patch would make a difference here. I'll
poke at it.
--
Jens Axboe
next parent reply other threads:[~2021-11-03 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211103141454.GA30634@xsang-OptiPlex-9020>
2021-11-03 19:51 ` Jens Axboe [this message]
2021-11-03 20:52 ` [nvme] f9c499bbbf: nvme nvme0: Identify Controller failed (16641) Chaitanya Kulkarni
2021-11-03 21:38 ` Keith Busch
2021-11-03 21:47 ` Keith Busch
2021-11-03 23:28 ` Jens Axboe
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=e6f09b9b-386a-8a26-7c4b-c528791f7c9a@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.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).