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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 19 Mar 2015 14:47:12 +0100
From:	Takashi Iwai <>
To:	Denys Vlasenko <>
Cc:	Denys Vlasenko <>,
	Andy Lutomirski <>,
	Jiri Kosina <>,
	Linus Torvalds <>,
	Stefan Seyfried <>,
	X86 ML <>, LKML <>,
	Tejun Heo <>
Subject: Re: PANIC: double fault, error_code: 0x0 in 4.0.0-rc3-2, kvm related?

At Thu, 19 Mar 2015 13:48:56 +0100,
Denys Vlasenko wrote:
> Having no more ideas at the moment, here is a tarball of 13 patches
> of commits touching entry_64.S up to 4.0.0-rc1.
> x0001.patch is the latest, x0015.patch is the oldest.
> Patches 0003 and 0008 are not there since 0003 is empty merge patch
> and 0008 does some PCI fixup.
> If this breakage is recent, it ought to be one of these.
> Most of them do some non-trivial surgery.
> Even though I did not spot anything suspicious in them,
> entry.S is notorious for subtle breakage.
> Try reverting them in sequence starting from x0001.patch
> and see reverting which one makes crash disappear.

OK, I'm going to check these git series.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists