From: kernel test robot <oliver.sang@intel.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>,
Ming Lei <ming.lei@redhat.com>,
"John Garry" <john.g.garry@oracle.com>,
Hannes Reinecke <hare@suse.de>, <linux-scsi@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [bvanassche:block-scsi-iops] [scsi] fb5a7f1b2b: INFO:task_blocked_for_more_than#seconds
Date: Thu, 20 Nov 2025 13:59:43 +0800 [thread overview]
Message-ID: <202511201331.ab9300d2-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "INFO:task_blocked_for_more_than#seconds" on:
commit: fb5a7f1b2bb3442ab270404463be4f0d7578295f ("scsi: core: Improve IOPS in case of host-wide tags")
https://github.com/bvanassche/linux block-scsi-iops
in testcase: boot
config: x86_64-kexec
compiler: clang-20
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-----------------------------------------+------------+------------+
| | 0997980774 | fb5a7f1b2b |
+-----------------------------------------+------------+------------+
| boot_successes | 12 | 0 |
| boot_failures | 0 | 12 |
| INFO:task_blocked_for_more_than#seconds | 0 | 12 |
| BUG:kernel_hang_in_boot_stage | 0 | 12 |
+-----------------------------------------+------------+------------+
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/202511201331.ab9300d2-lkp@intel.com
[ 972.310477][ T31] INFO: task swapper/0:1 blocked for more than 491 seconds.
[ 972.325924][ T31] Not tainted 6.18.0-rc1-00154-gfb5a7f1b2bb3 #1
[ 972.328555][ T31] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 972.331938][ T31] task:swapper/0 state:D stack:0 pid:1 tgid:1 ppid:0 task_flags:0x0040 flags:0x00080000
[ 972.337218][ T31] Call Trace:
[ 972.338813][ T31] <TASK>
[ 972.340068][ T31] __schedule (kernel/sched/core.c:5328)
[ 972.347907][ T31] ? prepare_to_wait_event (kernel/sched/wait.c:317)
[ 972.350544][ T31] schedule (arch/x86/include/asm/preempt.h:85 kernel/sched/core.c:7012 kernel/sched/core.c:7026)
[ 972.352679][ T31] async_synchronize_cookie_domain (kernel/async.c:317)
[ 972.355241][ T31] ? __pfx_autoremove_wake_function (kernel/sched/wait.c:402)
[ 972.357773][ T31] wait_for_device_probe (drivers/base/dd.c:777)
[ 972.364734][ T31] ? __pfx_autoremove_wake_function (kernel/sched/wait.c:402)
[ 972.367566][ T31] wait_for_devices (net/ipv4/ipconfig.c:1452)
[ 972.369621][ T31] ip_auto_config (net/ipv4/ipconfig.c:1510)
[ 972.371610][ T31] ? __pfx_ip_auto_config (net/ipv4/ipconfig.c:1477)
[ 972.373727][ T31] do_one_initcall (init/main.c:1283)
[ 972.375828][ T31] ? __alloc_frozen_pages_noprof (mm/page_alloc.c:5183)
[ 972.378358][ T31] ? alloc_pages_mpol (mm/mempolicy.c:2416)
[ 972.380533][ T31] ? new_slab (mm/slub.c:631 mm/slub.c:3250 mm/slub.c:3266)
[ 972.382406][ T31] ? sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)
[ 972.385612][ T31] ? asm_sysvec_apic_timer_interrupt (arch/x86/include/asm/idtentry.h:697)
[ 972.388164][ T31] ? __pfx_ignore_unknown_bootoption (init/main.c:1329)
[ 972.390842][ T31] ? strlen (lib/string.c:420)
[ 972.392746][ T31] ? parameq (kernel/params.c:90 kernel/params.c:99)
[ 972.394571][ T31] ? __pfx_ignore_unknown_bootoption (init/main.c:1329)
[ 972.397175][ T31] ? parse_args (kernel/params.c:153 kernel/params.c:186)
[ 972.399055][ T31] do_initcall_level (init/main.c:1344)
[ 972.401133][ T31] do_initcalls (init/main.c:1358)
[ 972.402859][ T31] kernel_init_freeable (init/main.c:1597)
[ 972.404994][ T31] ? __pfx_kernel_init (init/main.c:1475)
[ 972.406897][ T31] kernel_init (init/main.c:1485)
[ 972.409309][ T31] ret_from_fork (arch/x86/kernel/process.c:164)
[ 972.411068][ T31] ? __pfx_kernel_init (init/main.c:1475)
[ 972.413229][ T31] ret_from_fork_asm (arch/x86/entry/entry_64.S:255)
[ 972.415613][ T31] </TASK>
BUG: kernel hang in boot stage
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251120/202511201331.ab9300d2-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-11-20 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 5:59 kernel test robot [this message]
2025-11-21 21:15 ` [bvanassche:block-scsi-iops] [scsi] fb5a7f1b2b: INFO:task_blocked_for_more_than#seconds Bart Van Assche
2025-11-26 5:00 ` Oliver Sang
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=202511201331.ab9300d2-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=john.g.garry@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ming.lei@redhat.com \
--cc=oe-lkp@lists.linux.dev \
/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.