From: kernel test robot <oliver.sang@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>,
<virtualization@lists.linux.dev>, <oliver.sang@intel.com>
Subject: [linux-next:master] [drm/bochs] bde4437839: WARNING:at_drivers/gpu/drm/drm_vblank.c:#drm_wait_one_vblank
Date: Fri, 24 Oct 2025 13:52:40 +0800 [thread overview]
Message-ID: <202510241329.c93f8908-lkp@intel.com> (raw)
Hello,
we are not sure if this issue is due to same reason as you mentioned in
https://lore.kernel.org/all/6c9eb081-45ad-4fbd-90df-ac87f0b6223a@suse.de/
and this issue is also quite random as we reported in
https://lore.kernel.org/all/202510221555.8c60c069-lkp@intel.com/
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/runtime/group/nr_groups:
vm-snb/trinity/yocto-x86_64-minimal-20190520.cgz/x86_64-dcg_x86_64_defconfig-tdx/gcc-14/300s/group-01/5
commit:
b245bc23ff5840f1f0d54d2d76ff5facc03a51bb
bde44378397b1969f2be5908f41083e900eb5294
b245bc23ff5840f1 bde44378397b1969f2be5908f41
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:1000 9% 94:1000 dmesg.RIP:drm_atomic_helper_wait_for_vblanks
:1000 15% 148:1000 dmesg.RIP:drm_wait_one_vblank
:1000 9% 94:1000 dmesg.WARNING:at_drivers/gpu/drm/drm_atomic_helper.c:#drm_atomic_helper_wait_for_vblanks
:1000 15% 148:1000 dmesg.WARNING:at_drivers/gpu/drm/drm_vblank.c:#drm_wait_one_vblank
below full report just FYI.
kernel test robot noticed "WARNING:at_drivers/gpu/drm/drm_vblank.c:#drm_wait_one_vblank" on:
commit: bde44378397b1969f2be5908f41083e900eb5294 ("drm/bochs: Use vblank timer")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: trinity
version:
with following parameters:
runtime: 300s
group: group-01
nr_groups: 5
config: x86_64-dcg_x86_64_defconfig-tdx
compiler: gcc-14
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(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/202510241329.c93f8908-lkp@intel.com
[ 70.704709][ T11] ------------[ cut here ]------------
[ 70.705152][ T11] bochs-drm 0000:00:02.0: [drm] vblank wait timed out on crtc 0
[ 70.705792][ T11] WARNING: CPU: 0 PID: 11 at drivers/gpu/drm/drm_vblank.c:1320 drm_wait_one_vblank (drivers/gpu/drm/drm_vblank.c:1320 (discriminator 5))
[ 70.706480][ T11] Modules linked in: intel_rapl_msr joydev ppdev ata_generic pata_acpi intel_rapl_common i2c_piix4 psmouse serio_raw bochs ata_piix parport_pc i2c_smbus drm_shmem_helper parport
[ 70.707621][ T11] CPU: 0 UID: 0 PID: 11 Comm: kworker/0:1 Not tainted 6.18.0-rc1-00238-gbde44378397b #1 PREEMPT(none)
[ 70.708301][ T11] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[ 70.708950][ T11] Workqueue: events drm_fb_helper_damage_work
[ 70.709368][ T11] RIP: 0010:drm_wait_one_vblank (drivers/gpu/drm/drm_vblank.c:1320 (discriminator 5))
[ 70.709794][ T11] Code: 00 4d 8b 75 50 4d 85 f6 0f 84 5e 01 00 00 4c 89 ef e8 8d eb 74 00 89 e9 4c 89 f2 48 c7 c7 60 0b c6 9c 48 89 c6 e8 e9 d1 e2 fd <0f> 0b e9 9a fe ff ff 48 85 db 74 23 48 b8 00 00 00 00 00 fc ff df
All code
========
0: 00 4d 8b add %cl,-0x75(%rbp)
3: 75 50 jne 0x55
5: 4d 85 f6 test %r14,%r14
8: 0f 84 5e 01 00 00 je 0x16c
e: 4c 89 ef mov %r13,%rdi
11: e8 8d eb 74 00 call 0x74eba3
16: 89 e9 mov %ebp,%ecx
18: 4c 89 f2 mov %r14,%rdx
1b: 48 c7 c7 60 0b c6 9c mov $0xffffffff9cc60b60,%rdi
22: 48 89 c6 mov %rax,%rsi
25: e8 e9 d1 e2 fd call 0xfffffffffde2d213
2a:* 0f 0b ud2 <-- trapping instruction
2c: e9 9a fe ff ff jmp 0xfffffffffffffecb
31: 48 85 db test %rbx,%rbx
34: 74 23 je 0x59
36: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
3d: fc ff df
Code starting with the faulting instruction
===========================================
0: 0f 0b ud2
2: e9 9a fe ff ff jmp 0xfffffffffffffea1
7: 48 85 db test %rbx,%rbx
a: 74 23 je 0x2f
c: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
13: fc ff df
[ 70.710948][ T11] RSP: 0018:ffffc900000bfb78 EFLAGS: 00010282
[ 70.711336][ T11] RAX: 0000000000000000 RBX: ffff88815d8e0000 RCX: 0000000000000000
[ 70.711854][ T11] RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001
[ 70.713251][ T11] RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff3b6a008
[ 70.714593][ T11] R10: 0000000000000003 R11: 0000000000000001 R12: 1ffff92000017f70
[ 70.715986][ T11] R13: ffff88811066c0c8 R14: ffff88810ee51120 R15: ffff88815c68ec30
[ 70.717248][ T11] FS: 0000000000000000(0000) GS:ffff888405a34000(0000) knlGS:0000000000000000
[ 70.718597][ T11] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 70.719964][ T11] CR2: 0000560364c92008 CR3: 000000015c274000 CR4: 00000000000406f0
[ 70.724517][ T11] Call Trace:
[ 70.726398][ T11] <TASK>
[ 70.728373][ T11] ? __pfx_drm_wait_one_vblank (drivers/gpu/drm/drm_vblank.c:1301)
[ 70.730396][ T11] ? __pfx_autoremove_wake_function (kernel/sched/wait.c:402)
[ 70.732602][ T11] ? do_raw_spin_unlock (arch/x86/include/asm/atomic.h:23 include/linux/atomic/atomic-arch-fallback.h:457 include/linux/atomic/atomic-instrumented.h:33 include/asm-generic/qspinlock.h:57 kernel/locking/spinlock_debug.c:101 kernel/locking/spinlock_debug.c:141)
[ 70.734628][ T11] ? _raw_spin_unlock_irqrestore (include/linux/spinlock_api_smp.h:152 (discriminator 3) kernel/locking/spinlock.c:194 (discriminator 3))
[ 70.736771][ T11] drm_client_modeset_wait_for_vblank (drivers/gpu/drm/drm_client_modeset.c:1331)
[ 70.738810][ T11] drm_fb_helper_fb_dirty (drivers/gpu/drm/drm_fb_helper.c:373)
[ 70.740680][ T11] ? do_raw_spin_lock (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 kernel/locking/spinlock_debug.c:116)
[ 70.742607][ T11] ? __pfx_drm_fb_helper_fb_dirty (drivers/gpu/drm/drm_fb_helper.c:364)
[ 70.749405][ T11] ? __pfx_do_raw_spin_lock (kernel/locking/spinlock_debug.c:114)
[ 70.751600][ T11] process_one_work (arch/x86/include/asm/atomic.h:23 include/linux/atomic/atomic-arch-fallback.h:457 include/linux/jump_label.h:262 include/trace/events/workqueue.h:110 kernel/workqueue.c:3268)
[ 70.753684][ T11] worker_thread (kernel/workqueue.c:3340 (discriminator 2) kernel/workqueue.c:3427 (discriminator 2))
[ 70.755736][ T11] ? __kthread_parkme (arch/x86/include/asm/bitops.h:202 (discriminator 1) arch/x86/include/asm/bitops.h:232 (discriminator 1) include/asm-generic/bitops/instrumented-non-atomic.h:142 (discriminator 1) kernel/kthread.c:290 (discriminator 1))
[ 70.757807][ T11] ? __pfx_worker_thread (kernel/workqueue.c:3373)
[ 70.759926][ T11] ? __pfx_worker_thread (kernel/workqueue.c:3373)
[ 70.761937][ T11] kthread (kernel/kthread.c:463)
[ 70.763842][ T11] ? __pfx_kthread (kernel/kthread.c:412)
[ 70.765814][ T11] ? __pfx_kthread (kernel/kthread.c:412)
[ 70.769880][ T11] ? __pfx_kthread (kernel/kthread.c:412)
[ 70.771788][ T11] ret_from_fork (arch/x86/kernel/process.c:164)
[ 70.774087][ T11] ? __pfx_kthread (kernel/kthread.c:412)
[ 70.775966][ T11] ret_from_fork_asm (arch/x86/entry/entry_64.S:255)
[ 70.777858][ T11] </TASK>
[ 70.779512][ T11] ---[ end trace 0000000000000000 ]---
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20251024/202510241329.c93f8908-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-10-24 5:52 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=202510241329.c93f8908-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=kraxel@redhat.com \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=tzimmermann@suse.de \
--cc=virtualization@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 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).