mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Haozhong Zhang <haozhong.zhang@intel.com>
Cc: "Marc Haber" <mh+linux-kernel@zugschlus.de>,
	王金浦 <jinpuwang@gmail.com>, LKML <linux-kernel@vger.kernel.org>,
	"KVM-ML (kvm@vger.kernel.org)" <kvm@vger.kernel.org>,
	x86@kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: VMs freezing when host is running 4.14
Date: Tue, 13 Feb 2018 21:17:20 -0600	[thread overview]
Message-ID: <20180214031720.jq6c6yv652wt5r6u@treble> (raw)
In-Reply-To: <20180214025635.2lmvriql7uuzfop4@hz-desktop>

On Wed, Feb 14, 2018 at 10:56:35AM +0800, Haozhong Zhang wrote:
> On 02/13/18 20:04 -0600, Josh Poimboeuf wrote:
> > On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote:
> > > Hi,
> > > 
> > > after in total nine weeks of bisecting, broken filesystems, service
> > > outages (thankfully on unportant systems), 4.15 seems to have fixed the
> > > issue. After going to 4.15, the crashes never happened again.
> > > 
> > > They have, however, happened with each and every 4.14 release I tried,
> > > which I stopped doing with 4.14.15 on Jan 28.
> > > 
> > > This means, for me, that the issue is fixed and that I have just wasted
> > > nine weeks of time.
> > > 
> > > For you, this means that you have a crippling, data-eating issue in the
> > > current long-term releae kernel. I do sincerely hope that I never have
> > > to lay my eye on any 4.14 kernel and hope that no major distribution
> > > will release with this version.
> > 
> > I saw something similar today, also in kvm_async_pf_task_wait().  I had
> > -tip in the guest (based on 4.16.0-rc1) and Fedora
> > 4.14.16-300.fc27.x86_64 on the host.
> 
> Could you check whether this patch [1] on the host kernel fixes your
> issue?  Paolo had sent it to the stable tree and it may take a while
> to be merged in the next 4.14 stable release (perhaps in this week).
> 
> [1] https://patchwork.kernel.org/patch/10155177/

Unfortunately I don't know how to recreate it, the VM had been sitting
in idle for over an hour when it happened.  I'll leave it running
overnight without the patch and see if it happens again.

-- 
Josh

  reply	other threads:[~2018-02-14  3:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 16:18 Marc Haber
2017-11-22  9:39 ` Marc Haber
2017-11-22 15:04   ` 王金浦
2017-11-22 15:52     ` Marc Haber
2017-11-22 16:43       ` Radim Krčmář
2017-11-23 15:20         ` Marc Haber
2017-11-23 15:59           ` Radim Krčmář
2017-11-23 16:18             ` Liran Alon
2017-11-23 16:24               ` Radim Krčmář
2017-11-23 16:26                 ` Liran Alon
2017-11-24  8:08                   ` Marc Haber
2017-12-01 14:43     ` Marc Haber
2018-01-08  9:10       ` Marc Haber
2018-02-11 13:39         ` Marc Haber
2018-02-14  2:04           ` Josh Poimboeuf
2018-02-14  2:56             ` Haozhong Zhang
2018-02-14  3:17               ` Josh Poimboeuf [this message]
2018-02-14 10:23             ` Paolo Bonzini

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=20180214031720.jq6c6yv652wt5r6u@treble \
    --to=jpoimboe@redhat.com \
    --cc=haozhong.zhang@intel.com \
    --cc=jinpuwang@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mh+linux-kernel@zugschlus.de \
    --cc=pbonzini@redhat.com \
    --cc=x86@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

all inboxes | Powered by JetHome®