From: Takashi Iwai <tiwai@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Jiri Slaby <jslaby@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION 5.0.x] Windows XP broken on KVM
Date: Tue, 23 Apr 2019 22:28:29 +0200 [thread overview]
Message-ID: <s5h1s1spitu.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5hr29zpwkx.wl-tiwai@suse.de>
On Thu, 18 Apr 2019 10:05:34 +0200,
Takashi Iwai wrote:
>
> On Thu, 18 Apr 2019 09:53:28 +0200,
> Greg Kroah-Hartman wrote:
> >
> > On Thu, Apr 18, 2019 at 09:38:52AM +0200, Takashi Iwai wrote:
> > > Hi,
> > >
> > > we've got a regression report on the recent 5.0.x kernel, starting
> > > from 5.0.6, where Windows XP can't boot on KVM any longer.
> > >
> > > The culprit seems to be the patch
> > > KVM: x86: update %rip after emulating IO
> > > with the upstream commit 45def77ebf79e2e8942b89ed79294d97ce914fa0.
> > > Reverting this alone fixed the problem.
> > >
> > > The report is found at openSUSE bugzilla:
> > > https://bugzilla.suse.com/show_bug.cgi?id=1132694
> > >
> > > Is there already a followup fix? If not, we need to revert it from
> > > stable, at least.
> >
> > Is this also a problem in 5.1-rc5?
>
> Only 5.0.x has been tested, so far.
> I'll ask the reporter to try 5.1-rc if Paolo can't reproduce the
> problem in his side.
The reporter confirmed that the problem is present with the latest
5.1-rc kernel, too.
FWIW, it's a Ryzen system. Check the bugzilla URL above for details.
thanks,
Takashi
next prev parent reply other threads:[~2019-04-23 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 7:38 [REGRESSION 5.0.x] Windows XP broken on KVM Takashi Iwai
2019-04-18 7:53 ` Greg Kroah-Hartman
2019-04-18 8:05 ` Takashi Iwai
2019-04-18 23:31 ` Sean Christopherson
2019-04-23 20:28 ` Takashi Iwai [this message]
2019-04-26 8:17 ` Paolo Bonzini
2019-04-18 21:49 ` Harald Arnesen
2019-04-18 7:56 ` Paolo Bonzini
2019-04-23 20:23 ` Greg Kroah-Hartman
2019-04-24 0:18 ` Sean Christopherson
2019-04-18 21:59 ` Harald Arnesen
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=s5h1s1spitu.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.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).