linux-kernel - Re: [PATCH] x86, FPU: Fix FPU initialization

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130415155415.GB12144@pd.tnic>
Date:	Mon, 15 Apr 2013 17:54:15 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>, Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH] x86, FPU: Fix FPU initialization

On Mon, Apr 15, 2013 at 12:18:25PM +0200, Ingo Molnar wrote:
> It was tip:master with x86/cpu merged in freshly.

Ok, some more observations. I can trigger some oops similar yours (I
haven't caught mine yet over serial or such) with latest tip/master +
tip:x86/cpu.

When I remove tip:x86/cpu, the machine boots fine so I probably can
say now that I can reproduce at least similar behavior to what you're
observing.

Anyway, I'll try to catch the oops and try to decipher it and do a
bisection. Will keep you posted.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/