From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Derek Yerger <derek@djy.llc>
Cc: Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, "Bonzini, Paolo" <pbonzini@redhat.com>
Subject: Re: PROBLEM: Regression of MMU causing guest VM application errors
Date: Thu, 24 Oct 2019 10:32:12 -0700 [thread overview]
Message-ID: <20191024173212.GC20633@linux.intel.com> (raw)
In-Reply-To: <4af8cbac-39b1-1a20-8e26-54a37189fe32@djy.llc>
On Thu, Oct 24, 2019 at 11:18:59AM -0400, Derek Yerger wrote:
> On 10/22/19 4:28 PM, Sean Christopherson wrote:
> >On Thu, Oct 17, 2019 at 07:57:35PM -0400, Derek Yerger wrote:
> >Heh, should've checked from the get go... It's definitely not the memslot
> >issue, because the memslot bug is in 5.1.16 as well. :-)
> I didn't pick up on that, nice catch. The memslot thread was the closest
> thing I could find to an educated guess.
> >>I'm stuck on 5.1.x for now, maybe I'll give up and get a dedicated windows
> >>machine /s
> >What hardware are you running on? I was thinking this was AMD specific,
> >but then realized you said "AMD Radeon 540 GPU" and not "AMD CPU".
> Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
>
> 07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7)
> Subsystem: Gigabyte Technology Co., Ltd Device 22fe
> Kernel driver in use: vfio-pci
> Kernel modules: amdgpu
> (plus related audio device)
>
> I can't think of any other data points that would be helpful to solving
> system instability in a guest OS.
Can you bisect starting from v5.2? Identifying which commit in the kernel
introduced the regression would help immensely.
> But given my troubleshooting before, it
> looks like presence/absence of a PCI passthrough device is inconsequential
> to whether the problem is occurring.
>
> I may have to try out other VMs or a fresh windows guest.
next prev parent reply other threads:[~2019-10-24 17:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 4:49 PROBLEM: Regression of MMU causing guest VM application errors Derek Yerger
2019-10-16 7:28 ` Paolo Bonzini
2019-10-16 17:28 ` Alex Williamson
2019-10-16 17:49 ` Sean Christopherson
2019-10-17 23:57 ` Derek Yerger
2019-10-22 20:28 ` Sean Christopherson
2019-10-24 15:18 ` Derek Yerger
2019-10-24 17:32 ` Sean Christopherson [this message]
2019-10-31 3:44 ` Derek Yerger
2019-11-19 20:01 ` Sean Christopherson
2019-11-20 9:19 ` Wanpeng Li
2019-11-20 9:57 ` Paolo Bonzini
2019-11-20 18:19 ` Sean Christopherson
2019-11-20 19:04 ` Derek Yerger
2019-11-20 19:28 ` Sean Christopherson
2019-11-27 15:24 ` Sean Christopherson
2019-12-17 23:11 ` Sean Christopherson
2019-12-17 23:13 ` Derek Yerger
2020-01-02 13:42 ` Derek Yerger
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=20191024173212.GC20633@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=alex.williamson@redhat.com \
--cc=derek@djy.llc \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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).