From: kernel test robot <yi1.lai@intel.com>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
kbusch@kernel.org, hch@lst.de, hare@suse.de, sagi@grimberg.me,
chaitanyak@nvidia.com, gjoyce@linux.ibm.com,
Nilay Shroff <nilay@linux.ibm.com>
Date: Tue, 11 Aug 2026 16:36:27 +0800 [thread overview]
Message-ID: <202608111002.8c383e35-lkp@intel.com> (raw)
In-Reply-To: <20260727151652.3660476-3-nilay@linux.ibm.com>
Hello,
kernel test robot noticed "blktests.nvme/048.fail" on:
commit: 657b4cd151e042afc228615869b2a6876b91b8fc ("[PATCH v2 2/4] nvme-tcp: limit I/O queue count based on NIC queue count")
url: https://github.com/intel-lab-lkp/linux/commits/Nilay-Shroff/net-add-helper-for-device-lookup-by-destination-address/20260731-154725
patch link: https://lore.kernel.org/all/20260727151652.3660476-3-nilay@linux.ibm.com/
patch subject: [PATCH v2 2/4] nvme-tcp: limit I/O queue count based on NIC queue count
in testcase: blktests
version: blktests-x86_64-72a6349-1_20260804
with following parameters:
disk: 1SSD
test: nvme-group-02
nvme_trtype: tcp
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 16 threads Intel(R) Core(TM) i7-13620H (Raptor Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <yi1.lai@intel.com>
| Closes:
| https://lore.kernel.org/oe-lkp/202608111002.8c383e35-lkp@intel.com
nvme/048 (tr=tcp) (Test queue count changes on reconnect)
runtime 4.358s ...
nvme/048 (tr=tcp) (Test queue count changes on reconnect) [failed]
runtime 4.358s ... 7.340s
--- tests/nvme/048.out 2026-08-04 23:49:51.000000000 +0000
+++ /mnt/nvme-group-02/nodev_tr_tcp/nvme/048.out.bad 2026-08-06 06:04:55.281322408 +0000
@@ -1,2 +1,4 @@
Running nvme/048
+expected queue count 3 not set
+FAIL
Test complete
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260811/202608111002.8c383e35-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-08-11 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 15:16 [PATCH v2 0/4] nvme-tcp: NIC topology aware I/O queue scaling and queue info export Nilay Shroff
2026-07-27 15:16 ` [PATCH v2 1/4] net: add helper for device lookup by destination address Nilay Shroff
2026-07-30 23:15 ` Jakub Kicinski
2026-07-31 6:10 ` Nilay Shroff
2026-07-27 15:16 ` [PATCH v2 2/4] nvme-tcp: limit I/O queue count based on NIC queue count Nilay Shroff
2026-08-11 8:36 ` kernel test robot [this message]
2026-08-12 11:49 ` Nilay Shroff
2026-08-12 12:57 ` Re: kernel test bot
2026-07-27 15:16 ` [PATCH v2 3/4] nvme: add debugfs helpers for NVMe drivers Nilay Shroff
2026-07-27 15:16 ` [PATCH v2 4/4] nvme: expose queue information via debugfs Nilay Shroff
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=202608111002.8c383e35-lkp@intel.com \
--to=yi1.lai@intel.com \
--cc=chaitanyak@nvidia.com \
--cc=gjoyce@linux.ibm.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@intel.com \
--cc=nilay@linux.ibm.com \
--cc=oe-lkp@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.