From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 206215] QEMU guest crash due to random 'general protection fault' since kernel 5.2.5 on i7-3517UE
Date: Thu, 16 Jan 2020 01:15:42 +0000 [thread overview]
Message-ID: <bug-206215-28872-rhpjvSaKLd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206215-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206215
--- Comment #3 from derek@djy.llc ---
On 1/15/20 4:52 PM, Sean Christopherson wrote:
> +cc Derek, who is hitting the same thing.
>
> On Wed, Jan 15, 2020 at 09:18:56PM +0000, bugzilla-daemon@bugzilla.kernel.org
> wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=206215
> *snip*
> that's a big smoking gun pointing at commit ca7e6b286333 ("KVM: X86: Fix
> fpu state crash in kvm guest"), which is commit e751732486eb upstream.
>
> 1. Can you verify reverting ca7e6b286333 (or e751732486eb in upstream)
> solves the issue?
>
> 2. Assuming the answer is yes, on a buggy kernel, can you run with the
> attached patch to try get debug info?
I did these out of order since I had 5.3.11 built with the patch, ready to go
for weeks now, waiting for an opportunity to test.
Win10 guest immediately BSOD'ed with:
WARNING: CPU: 2 PID: 9296 at include/linux/thread_info.h:55
kernel_fpu_begin+0x6b/0xc0
Then stashed the patch, reverted ca7e6b286333, compile, reboot.
Guest is running stable now on 5.3.11. Did test my CAD under the guest, did not
experience the crashes that had me stuck at 5.1.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-01-16 1:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 21:18 [Bug 206215] New: QEMU guest crash due to random 'general protection fault' since kernel 5.2.5 on i7-3517UE bugzilla-daemon
2020-01-15 21:52 ` Sean Christopherson
2020-01-16 1:08 ` Derek Yerger
2020-01-16 15:38 ` Sean Christopherson
2020-01-16 18:08 ` Sean Christopherson
2020-01-16 19:21 ` Derek Yerger
2020-01-16 19:32 ` Sean Christopherson
2020-01-15 21:52 ` [Bug 206215] " bugzilla-daemon
2020-01-15 22:15 ` bugzilla-daemon
2020-01-16 1:15 ` bugzilla-daemon [this message]
2020-01-16 1:36 ` bugzilla-daemon
2020-01-16 15:38 ` bugzilla-daemon
2020-01-16 18:08 ` bugzilla-daemon
2020-01-16 19:21 ` bugzilla-daemon
2020-01-16 19:32 ` bugzilla-daemon
2020-01-17 22:43 ` 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=bug-206215-28872-rhpjvSaKLd@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).