From: Sean Christopherson <seanjc@google.com>
To: bugzilla-daemon@kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [Bug 219787] Guest's applications crash with EXCEPTION_SINGLE_STEP (0x80000004)
Date: Thu, 20 Feb 2025 09:43:38 -0800 [thread overview]
Message-ID: <Z7dpyiQtKNrAyOVe@google.com> (raw)
In-Reply-To: <bug-219787-28872-Buv2FGa6sL@https.bugzilla.kernel.org/>
On Thu, Feb 20, 2025, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=219787
>
> --- Comment #4 from rangemachine@gmail.com ---
> (In reply to Sean Christopherson from comment #2)
> > Are you able to bisect to an exact commit? There are significant KVM
> > changes in 6.13, but they're almost all related to memory management. I
> > can't think of anything that would manifest as an unexpected single step
> > #DB, especially not with any consistency.
> >
> > And just to double check, the only difference in the setup is that the host
> > kernel was upgraded from v6.12 => v6.13? E.g. there was no QEMU update or
> > guest-side changes?
>
> I was not able to bisect yet, sorry.
No need to be sorry, you didn't introduce the bug :-)
> And yes, I double checked, the only change is kernel upgraded from v6.12.10
> to v6.13.2 (did not checked v6.13.3 yet, but rc version had some behaviour).
Please let me know if you'll be able to bisect (or not). Unless I have a random
epiphany, this will likely require bisection.
next prev parent reply other threads:[~2025-02-20 17:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 9:53 [Bug 219787] New: Guest's applications crash with EXCEPTION_SINGLE_STEP (0x80000004) bugzilla-daemon
2025-02-16 9:54 ` [Bug 219787] " bugzilla-daemon
2025-02-16 10:01 ` bugzilla-daemon
2025-02-20 0:31 ` bugzilla-daemon
2025-02-20 2:57 ` bugzilla-daemon
2025-02-20 17:40 ` Sean Christopherson
2025-02-20 7:10 ` bugzilla-daemon
2025-02-20 17:43 ` Sean Christopherson [this message]
2025-02-20 17:41 ` bugzilla-daemon
2025-02-20 17:43 ` bugzilla-daemon
2025-02-20 17:46 ` bugzilla-daemon
2025-02-20 19:00 ` bugzilla-daemon
2025-02-21 1:31 ` bugzilla-daemon
2025-02-21 1:31 ` bugzilla-daemon
2025-02-21 1:32 ` bugzilla-daemon
2025-02-21 10:48 ` bugzilla-daemon
2025-02-21 18:22 ` bugzilla-daemon
2025-02-21 18:22 ` bugzilla-daemon
2025-02-21 20:04 ` bugzilla-daemon
2025-02-23 4:57 ` bugzilla-daemon
2025-02-24 11:33 ` bugzilla-daemon
2025-02-24 11:36 ` bugzilla-daemon
2025-06-27 13:19 ` bugzilla-daemon
2025-06-30 12:00 ` bugzilla-daemon
2025-07-02 9:05 ` bugzilla-daemon
2025-07-06 7:00 ` bugzilla-daemon
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=Z7dpyiQtKNrAyOVe@google.com \
--to=seanjc@google.com \
--cc=bugzilla-daemon@kernel.org \
--cc=kvm@vger.kernel.org \
/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).