All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard.weinberger@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Adam Borowski <kilobyte@angband.pl>,
	Paolo Bonzini <pbonzini@redhat.com>, kvm <kvm@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: 4.13-rc7: WARNING at arch/x86/kvm/mmu.c:717 (and a crash thereafter)
Date: Mon, 28 Aug 2017 15:29:13 +0200	[thread overview]
Message-ID: <CAFLxGvyGb2naU7icJb-b=Cxr5_3SQLFOVsWP87LOV=yx52e55w@mail.gmail.com> (raw)
In-Reply-To: <s5hinh7lton.wl-tiwai@suse.de>

On Mon, Aug 28, 2017 at 3:15 PM, Takashi Iwai <tiwai@suse.de> wrote:
> On Mon, 28 Aug 2017 15:06:00 +0200,
> Adam Borowski wrote:
>>
>> On Mon, Aug 28, 2017 at 02:26:06PM +0200, Takashi Iwai wrote:
>> > I seem to get a kernel warning when running KVM on Dell desktop with
>> > IvyBridge like below.  As you can see, a bad page BUG is triggered
>> > after that, too.  The problem is not triggered always, but it happens
>> > occasionally.
>>
>> See the thread starting with 20170820231302.s732zclznrqxwr46@angband.pl
>>
>> > I haven't seen this on 4.13-rc4 at all, and IIRC, it started happening
>> > since rc5.  So this might be a regression at rc5.  But, as it doesn't
>> > happen always, I can't be 100% sure about it, and it's quite difficult
>> > to bisect (the test case isn't reliable), unfortunately.
>>
>> Same here -- it sometimes takes a few hours of trying to reproduce, which
>> makes proving the negative greatly unpleasant.
>>
>> And all I've been able to tell so far is that the problem is between
>> 4.13-rc4 and 4.13-rc5, just like you say.
>
> Good to hear that we can chorus!
> So if it's really a regression between rc4 and rc5, I see no obvious
> changes in arch/x86, i.e. it's likely somewhere else.
>
> (snip)
>> The first WARN is always the above.  But the rest seems to be totally random
>> -- a nasty case of fandango on core whose results range from harmless
>> through crash to massive data loss (just guess what would happen if some
>> idiot picked balancing the disk as a test load -- no one would be that
>> stupid, right?  At least an incomplete idiot has checksums and backups).
>
> Yeah, the crash after the WARNING seems quite random.

I don't see that warning but running qemu-kvm crashed by laptop
(4.13-rc4) two times in a row and
some userspace applications such has firefox or bash crashed randomly.

pstore-efi is now enabled to capture the stacktrace.

-- 
Thanks,
//richard

  reply	other threads:[~2017-08-28 13:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 12:26 4.13-rc7: WARNING at arch/x86/kvm/mmu.c:717 (and a crash thereafter) Takashi Iwai
2017-08-28 13:06 ` Adam Borowski
2017-08-28 13:15   ` Takashi Iwai
2017-08-28 13:29     ` Richard Weinberger [this message]
2017-08-28 13:52 ` Mike Galbraith
2017-08-28 14:41   ` Mike Galbraith

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='CAFLxGvyGb2naU7icJb-b=Cxr5_3SQLFOVsWP87LOV=yx52e55w@mail.gmail.com' \
    --to=richard.weinberger@gmail.com \
    --cc=kilobyte@angband.pl \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=tiwai@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.