Bug 218204
Summary: | WARNING: CPU: x PID: xxx at kernel/dma/debug.c:1131 check_sync+0x4a0/0x640 and Call Trace related to virtnet | ||
---|---|---|---|
Product: | Virtualization | Reporter: | hongyuni (hongyu.ning) |
Component: | lguest | Assignee: | virtualization_lguest |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | bagasdotme, hongyu.ning |
Priority: | P3 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | v6.7.-rc3 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | WARNING and Call Trace info in dmesg |
Description
hongyuni
2023-11-29 08:20:57 UTC
(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/ |