From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751353AbdH1N3R (ORCPT ); Mon, 28 Aug 2017 09:29:17 -0400 Received: from mail-wm0-f51.google.com ([74.125.82.51]:35655 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751170AbdH1N3Q (ORCPT ); Mon, 28 Aug 2017 09:29:16 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170828130600.rgm5vilrhwkjmjxq@angband.pl> From: Richard Weinberger Date: Mon, 28 Aug 2017 15:29:13 +0200 Message-ID: Subject: Re: 4.13-rc7: WARNING at arch/x86/kvm/mmu.c:717 (and a crash thereafter) To: Takashi Iwai Cc: Adam Borowski , Paolo Bonzini , kvm , "x86@kernel.org" , LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 28, 2017 at 3:15 PM, Takashi Iwai 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