Created attachment 305503 [details] WARNING and Call Trace info in dmesg Follow WARNING and Call Trace observed based on test info below: WARNING: CPU: x PID: xxx at kernel/dma/debug.c:1131 check_sync+0x4a0/0x640 full WARNING and Call Trace in attachment Guest Kernel under test: mainline 6.7.0-rc2 or later. Test step: boot up above Guest Kernel in TDX VM, based on Linux KVM/QEMU reference QEMU config: $QEMU_IMAGE \ -accel kvm \ -no-reboot \ -name process=td_hy_inext,debug-threads=on \ -cpu host,host-phys-bits,pmu=off \ -smp cpus=1 \ -m ${MEM}G \ -machine q35 \ -bios $BIOS_IMAGE \ -nographic \ -vga none \ -device virtio-net-pci,netdev=mynet0,mac=00:16:3E:68:08:FF,romfile= \ -netdev user,id=mynet0,hostfwd=tcp::10012-:22,hostfwd=tcp::12012-:2375 \ -device vhost-vsock-pci,guest-cid=12 \ -chardev stdio,id=mux,mux=on,signal=off \ -device virtio-serial,romfile= \ -device virtconsole,chardev=mux \ -serial chardev:mux \ -monitor chardev:mux \ -drive file=${GUEST_IMAGE},if=virtio,format=raw \ -kernel ${KERNEL_IMAGE} \ -append "root=/dev/vda3 ro console=hvc0 earlyprintk=ttyS0 ignore_loglevel debug earlyprintk l1tf=off initcall_debug log_buf_len=200M tsc=reliable nokaslr efi=debug mce=off efi=debug" \ -monitor pty \ -monitor telnet:127.0.0.1:9012,server,nowait \ -no-hpet \ -nodefaults \
(In reply to hongyuni from comment #0) > Created attachment 305503 [details] > WARNING and Call Trace info in dmesg > > Follow WARNING and Call Trace observed based on test info below: > WARNING: CPU: x PID: xxx at kernel/dma/debug.c:1131 check_sync+0x4a0/0x640 > full WARNING and Call Trace in attachment > > Guest Kernel under test: mainline 6.7.0-rc2 or later. > Does v6.7-rc1 not have this regression?
(In reply to Bagas Sanjaya from comment #1) > (In reply to hongyuni from comment #0) > > Created attachment 305503 [details] > > WARNING and Call Trace info in dmesg > > > > Follow WARNING and Call Trace observed based on test info below: > > WARNING: CPU: x PID: xxx at kernel/dma/debug.c:1131 check_sync+0x4a0/0x640 > > full WARNING and Call Trace in attachment > > > > Guest Kernel under test: mainline 6.7.0-rc2 or later. > > > > Does v6.7-rc1 not have this regression? yes, it's ever seen since v6.6 cycle. in fact, there is an email thread discussion about this issue, based on local bisect results: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2561299.html
(In reply to hongyuni from comment #2) > (In reply to Bagas Sanjaya from comment #1) > > (In reply to hongyuni from comment #0) > > > Created attachment 305503 [details] > > > WARNING and Call Trace info in dmesg > > > > > > Follow WARNING and Call Trace observed based on test info below: > > > WARNING: CPU: x PID: xxx at kernel/dma/debug.c:1131 > check_sync+0x4a0/0x640 > > > full WARNING and Call Trace in attachment > > > > > > Guest Kernel under test: mainline 6.7.0-rc2 or later. > > > > > > > Does v6.7-rc1 not have this regression? > > yes, it's ever seen since v6.6 cycle. > > in fact, there is an email thread discussion about this issue, based on > local bisect results: > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2561299.html sorry, update email thread from lkml https://lore.kernel.org/lkml/f37cb55a-6fc8-4e21-8789-46d468325eea@linux.intel.com/
issue got conclusion in lkml, close here: https://lore.kernel.org/all/f37cb55a-6fc8-4e21-8789-46d468325eea@linux.intel.com/