linux-kernel - Re: PANIC: double fault, error_code: 0x0 in 4.0.0-rc3-2, kvm related?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hk2ydteq2.wl-tiwai@suse.de>
Date:	Thu, 19 Mar 2015 12:21:25 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Denys Vlasenko <dvlasenk@...hat.com>
Cc:	Andy Lutomirski <luto@...capital.net>,
	Jiri Kosina <jkosina@...e.cz>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Stefan Seyfried <stefan.seyfried@...glemail.com>,
	X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: PANIC: double fault, error_code: 0x0 in 4.0.0-rc3-2, kvm related?

At Thu, 19 Mar 2015 11:58:19 +0100,
Denys Vlasenko wrote:
> 
> 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.

I tried w/o PARAVIRT and the bug is still seen.  The dmesg is attached
below.


Takashi


View attachment "dmesg.txt" of type "text/plain" (67391 bytes)