From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753300AbbCSK6g (ORCPT <rfc822;w@1wt.eu>);
	Thu, 19 Mar 2015 06:58:36 -0400
Received: from mx1.redhat.com ([209.132.183.28]:53035 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750951AbbCSK6c (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 19 Mar 2015 06:58:32 -0400
Message-ID: <550AABCB.9040502@redhat.com>
Date: Thu, 19 Mar 2015 11:58:19 +0100
From: Denys Vlasenko <dvlasenk@redhat.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Takashi Iwai <tiwai@suse.de>, Andy Lutomirski <luto@amacapital.net>
CC: Jiri Kosina <jkosina@suse.cz>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Stefan Seyfried <stefan.seyfried@googlemail.com>,
        X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
        Tejun Heo <tj@kernel.org>
Subject: Re: PANIC: double fault, error_code: 0x0 in 4.0.0-rc3-2, kvm related?
References: <5505400B.8050300@message-id.googlemail.com>	<s5hr3smfl11.wl-tiwai@suse.de>	<s5hy4mukxpj.wl-tiwai@suse.de>	<s5h4mpi5hbv.wl-tiwai@suse.de>	<CALCETrVCMEcCOHZ35LneCU6uGH+W5SF0groKbUGp2zTjWpzB0w@mail.gmail.com>	<5509CBF7.3040602@message-id.googlemail.com>	<CALCETrU2R020HVniX2sczxexPO2qhEPbS++9DXzcxeycgxoGQg@mail.gmail.com>	<CA+55aFwT4BJVR10i2Cm8pMH0UGd-J3EwnEUYKf3BWTM0awebbA@mail.gmail.com>	<5509F161.3010101@redhat.com>	<CALCETrXZvSiT41+AYAPizSsGZ_=O=7wmb+Lwo_ChEZySxUnH-A@mail.gmail.com>	<alpine.LRH.2.00.1503182320490.13021@twin.jikos.cz>	<CALCETrVnJHXhz81QCr7qmm0uwdw2t0EWe_zUw4E7bZB2WXQNTQ@mail.gmail.com> <s5hiodxjnqs.wl-tiwai@suse.de>
In-Reply-To: <s5hiodxjnqs.wl-tiwai@suse.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 03/19/2015 11:16 AM, Takashi Iwai wrote:
> The kconfig is attached

You also have PARAVIRT enabled, like Stefan.

Just to obtain an additional data point, can you guys
try reproducing it with PARAVIRT off?

It won't help us that much if it won't trigger with PARAVIRT off
(the bug may just become much harder to trigger), but if it would
still happen, that'd reduce the number of things we can suspect.