From: kernel test robot <oliver.sang@intel.com>
To: Yu Kuai <yukuai@fnnas.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>,
Nilay Shroff <nilay@linux.ibm.com>,
Ming Lei <ming.lei@redhat.com>, Hannes Reinecke <hare@suse.de>,
<linux-block@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [blk] 65d466b629: blktests.nvme/022.device.fail
Date: Fri, 13 Feb 2026 10:38:48 +0800 [thread overview]
Message-ID: <202602131044.6e7fc152-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "blktests.nvme/022.device.fail" on:
commit: 65d466b6298470ce21ab21ebfdb51309d515737d ("blk-mq-debugfs: warn about possible deadlock")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 37a93dd5c49b5fda807fd204edf2547c3493319c]
[test failed on linux-next/master af98e93c5c39e6d0b87b42f0a32dd3066f795718]
in testcase: blktests
version: blktests-x86_64-a94b770-1_20260205
with following parameters:
disk: 1SSD
test: nvme-group-01
nvme_trtype: rdma
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480+ (Sapphire Rapids) with 256G 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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202602131044.6e7fc152-lkp@intel.com
nvme/022 (tr=rdma bd=device) (test NVMe reset command)
nvme/022 (tr=rdma bd=device) (test NVMe reset command) [failed]
runtime ... 2.750s
something found in dmesg:
[ 166.159293] [ T4405] run blktests nvme/022 at 2026-02-12 07:46:06
[ 166.210905] [ T4580] loop0: detected capacity change from 0 to 2097152
[ 166.225648] [ T4584] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
[ 166.242028] [ T4589] nvmet_rdma: enabling port 0 (192.168.3.121:4420)
[ 166.290336] [ T4189] nvmet: Created nvm controller 1 for subsystem blktests-subsystem-1 for NQN nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349.
[ 166.317649] [ T4596] nvme nvme2: creating 128 I/O queues.
[ 166.802940] [ T4596] nvme nvme2: mapped 128/0/0 default/read/poll queues.
[ 166.878331] [ T4596] nvme nvme2: new ctrl: NQN "blktests-subsystem-1", addr 192.168.3.121:4420, hostnqn: nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349
[ 166.971637] [ T4632] nvme nvme2: resetting controller
[ 167.242104] [ T1026] nvmet: Created nvm controller 2 for subsystem blktests-subsystem-1 for NQN nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349.
...
(See '/mnt/nvme-group-01/nodev_tr_rdma_bd_device/nvme/022.dmesg' for the entire message)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260213/202602131044.6e7fc152-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-13 2:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202602131044.6e7fc152-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ming.lei@redhat.com \
--cc=nilay@linux.ibm.com \
--cc=oe-lkp@lists.linux.dev \
--cc=yukuai@fnnas.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